@manilx We recently upgraded our Koji build system. This may have caused disruptions in this recent update release yesterday, where an XML file was generated multiple times. This has now been fixed and should not happen again. This may explain the issue encountered this time, particularly with the notification of updates via XO.
Note that normally yum metadata expires after a few hours and so it should normally return to normal on its own.
I experienced the same issue!
What I found was that just doing a "yum update" was not enough, though it was needed.
When I was initially getting the error, I was trying to import on a host that was not the master of the pool. After I designated that host as the pool master, the same command worked easily.
I had to do both the update and import on the master only.
@psafont
is it safe to remove it on production pool?
whenever the SDN controller is turned on.
so, i can do something on new host, before joining into pool to generate this cert?
