Mark -
I have been looking for the cause of this - but have not a clue. We thought it might have been a yum update, or update source - but this does not now seem to be the cause.
Further, this seems to be rather a new issue - it didn't crop up for some weeks after this solution was released and in use. So - I am still trying to ascertain what is causing it on some platforms, while leaving others totally unaffected.
It my hope that once we figure out what is causing it, it can be prevented. Sadly - I have no more info to offer at this time.