Comment 3 for bug 436462

Revision history for this message
Vish (vish) wrote :

The release team did not want to fix this issue , this has been fixed upstream.