XCP-ng 8.3 betas and RCs feedback 🚀
-
@CJ Yes
-
Reworded to:
You can upgrade as usual through Xen Orchestra or by using yum update. A reboot is required. However, we recommend upgrading via the installation ISO image before putting XCP-ng 8.3 into production. If you upgrade now using the RC2 installation image, you won’t need to upgrade again to the final production release (a simple update will then be enough). Upgrading early helps us with testing.
Does it seem clearer?
-
@stormi Upgraded my homelab pool (2 Protectlis VP6670) via ISO.
Master first and then 2nd host.Only thing was that the master did not ask for network config and the 2nd host did ask for network configuration to use the repository BUT I did choose local repository...
After that all went fine.
What's the cli command to check the version?
-
If yum update says no update or no updates visible in XO, you are good
-
@olivierlambert No updates shown.
One thing I miss, my cli history on the hosts....
Should have expected this and save it. -
@manilx experienced the same thing while upgrading our test pool. Pool master did not ask, other hosts did ask for network config.
-
@flakpyro guess it should not differ from master to other hosts. It's a bit disconcerting.
-
Our main pool upgraded with no issues with the ISO. Same as the above posters though, master doesn't ask for network config but other hosts in the pool do...thankfully all the bonds and networking came up without issue on them.
Will attempt updating our other locations after hours but I don't foresee any problems
-
Upgrade to RC2 worked fine so far with netinstall ISO in ventoy on a 8 gen i5 HP laptop. And a "full" ISO on its own USB on a Lenovo Thinkcentre Ryzen 5 2400GE
-
I tried to upgrade my test cluster from 8.2.1 but encountered a few problems. I was basically trying to follow the instructions at https://docs.xcp-ng.org/installation/upgrade/ by doing a install from media (USB Key).
- screen resolution. Perhaps an option for a lower resolution console would be reasonable?
(I tried linking a screenshot but the forum software objected. It can be found at https://photos.app.goo.gl/Zkby9aHUEBYUzkfe8 )
My KVM display was upset by the resolution selected and put a splash screen in the middle of the display saying "Input sync out of range. Please select 1024x768 60Hz for best performance."
note: this only happens with a UEFI boot. It does not appear with a BIOS boot.
- lack of information about what non-standard things are in the way so they can be found and removed.
Another photo: https://photos.app.goo.gl/ZuTNKiXctUCBkSmf7
"Only product installations that cannot be upgraded have been detected. Continuing will result in a clean installation, all existing configuration will be lost. ..."
This box started as a default 8.2 host and was upgraded to 8.2.1 via yum. The only truly non-default thing is the package that enables waiting for NFS RSs to become available before starting any dependent VMs (plug-late-sr-1.1-1.xcpng8.2.noarch).
I removed that one RPM but still had the same error.
Hmm. I just remembered the first time I tried this I did get a warning about changing from BIOS to IPMI so I went in and changed boot mode. I guess I should go try booting from BIOS and see if that changes/removes the error....
Yep, sure does. No error at all when booting in BIOS mode. So, the message about installing with UEFI instead of BIOS might want to be re-worded to make it clear this is not an upgrade option. (and to perhaps suggest the best method for making said change?)
I've held off on applying the upgrade incase you wanted me to test something.
-
Upgraded 3-node pool (home lab: Dell OptiPlex 7040 SFF x 3) from 8.3 RC1 to 8.3 RC2 using bootable ISO. It worked perfectly for me. As others have noted, it does ask you to select the management interface when upgrading the slave nodes. Once you do that, it automatically populates all of the previously configured network parameters for that host so you are really only confirming the existing values. The OptiPlex 7040's (i7-6700) all have Intel VPro AMT so they are running headless. The MeshCommander program is used to access the VPro console on each host. A DisplayPort display emulator dongle is needed to keep the integrated-GPU active in order to be able to see the console and firmware setup screens with this configuration. It's effectively a poor man's iDRAC. So far, everything is working well on 8.3 RC2.
-
A week or two ago a bunch of updates went out. Were these part of RC2? I updated via yum back then and since this announcement nothing new has come up.
Is there a command line command to run to verify what is installed now is RC2?
-
@archw Yes, if you installed any 8.3 beta or RC and have recently performed a
yum updateand reboot, then you are up to date with the packages that are included in the 8.3-rc2 release. -
I decided to try upgrading my master to 8.3 in BIOS mode (see yesterday's post about UEFI failure). The upgrade seems to have gone well overall but when I try to access my NFS-mounted SRs I get
"SR_BACKEND_FAILURE_140(, Incorrect DNS name, unable to resolve., "
Evidently not everything was preserved in the upgrade.
-
@nomad A host is not supposed to lose its DNS configuration upon upgrade, but it looks like it did. Can you check from the CLI?
-
@stormi It was user error.
/etc/hosts wasn't preserved and the storage NAS isn't in DNS.
-
@nomad said in XCP-ng 8.3 betas and RCs feedback
:plug-late-sr
Looks like this RPM isn't available in 8.3 yet. Please remember to make it available as we need it.
It was created for Ticket#7714169
thanks!
-
-
@ph7 said in XCP-ng 8.3 betas and RCs feedback
:Upgrade to RC2 worked fine so far with netinstall ISO in ventoy on a 8 gen i5 HP laptop. And a "full" ISO on its own USB on a Lenovo Thinkcentre Ryzen 5 2400GE
2 days ago I upgraded my fully patched Ryzen 5 RC1 to RC2 by ISO.
Unfortunately I also upgraded my XO to commit aa490.
All backup jobs since then has triggered CPU performance alerts on my backed up delta, offline VM, XCP-ng host and the VM running XO.
I will update the XO to latest commit today.
Are there any changes in RC2 that could cause this?
I have only received 1 alert on high memory earlier. -
ISO update (as recommended) for my pool of three XCP-ng 8.3 RC1 hypervisors.
Everything went perfectly for each server.
I had to reinstall the additional packages (traceroute vim-enhanced mtr etc...), re-enable LLDP advertisements on the network interfaces (lldptool -L -i eth0 adminStatus=rxtx) and recreate the multipath configuration file (/etc/multipath/conf.d/huawei.conf).
In short, nothing seems abnormal.
