This bug has now been fixed in 2.0-4.fc7
Based on Successful testing of this bug in RHEL5, resolving this for now.