Closed namekal closed 6 years ago
Hi. There's a known bug when upgrading from 7.4.0 instead of 7.4.1, which would probably explain the issue. The second part your experience reveals is that we should make sure to clean the yum metadata cache after downloading the new repo file, because that's what caused the two-steps update.
so nothing to do here for XCP-ng Center :-)
so nothing to do here for XCP-ng Center :-)
Oh man, my bad on that. I was confused on why you mentioned that at first. At least it wasn't a serious issue that meant to be in the right repo. Thanks. :+1:
no problem :-)
Describe the bug I ran the [experimental] update command found here: https://xcp-ng.org/2018/08/10/xcp-ng-7-5-upgrade/ and upon reboot I could not connect via XCP-Center. XSConsole is displayed in the console as expected. The system info and "Management Network Parameters" displays the correct info.
However, when navigating menus, the network interface list is empty, along with all VMs, and Storage repositories. All empty.
I hopped down to command shell and ran
yum update
one more time for kicks. The summary:After all of this processed, I was immediately able to connect via XCP-Center again, and thankfully NO DATA/METADATA was lost.
Hard-/Software involved: