Comment 4 for bug 1482392

Given the amount of work in this area since this was reported, it seem likely this has been fixed.

Lets mark this as incomplete until we can get some update repo steps, and associated logs to hint at what is going wrong.

As it is, this doesn't give us enough information to look into fixing this bug.