@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 probably would have just bought a cheap mini PC and used Virtual Box for this, which is something I did do in the past for an old XP machine when the hardware started to fail. Grabbed a disk to vhd of it before the final failure and loaded it into Vbox.
Might be able to do this in nested virtualization in XCP-ng.
@psafont
nvm something weird happens. I removed cert and everything fixed. Thank you.
Need to specify extention xe pool-uninstall-ca-certificate name=sdn-controller-ca.pem --force
But this cert shouldn't exist at backup because i never use sdn, plugin is disabled. Other hosts has no this cert. Looks like bug?
