XCP-ng 8.3 betas and RCs feedback 🚀

Strebor

I updated a test pool with 2 Intel NUC11TNHi5 hosts last week.
The updates went smooth. No issues after reboot.

Can't wait till 8.3 goes live!

r0ssar00

@fohdeesha I just did a reinstall of the interface-rename package to make sure I hadn't changed the shebang in the past, the reinstalled copy declares python3

NoHeadroom

@r0ssar00

I've notice the same python3 glitch.
You could manually amend /etc/sysconfig/network-scripts/interface-rename-data/static-rules.conf if that's an option for you.

stormi

@r0ssar00 @NoHeadroom Thanks for the feedback. You're both right, there's an issue. We will fix it ASAP.

stormi

I just pushed a few updates. Nothing worth mentioning, just a few minor fixes before the RC. The update might look big because XAPI was rebuilt, so many packages generated by this build are updated.

The interface-rename fix is to follow next, when it's ready.

manilx

@stormi updated 2 hosts (2 pools) and rebooted. No issues.

stormi

@NoHeadroom said in XCP-ng 8.3 beta :

@r0ssar00

I've notice the same python3 glitch.
You could manually amend /etc/sysconfig/network-scripts/interface-rename-data/static-rules.conf if that's an option for you.

Better avoid this kind of change to a file that was generated by the installer and is not meant to be touched.

Anyway, I've pushed the fixed interface-rename to the xcp-ng-base repository. Just update, and this will be fixed.

gskger

@stormi Update of my XCP-ng 8.3 test server through CLI (yum update) and rebooted. All VMs work as expected.

ph7

@stormi
I ran the updates and now my graphs in XO-lite are back.
weird

NoHeadroom

@stormi said in XCP-ng 8.3 beta :

Better avoid this kind of change to a file that was generated by the installer and is not meant to be touched.

Anyway, I've pushed the fixed interface-rename to the xcp-ng-base repository. Just update, and this will be fixed.

Thanks for the quick fix and the hard work getting 8.3 to production.

Anyway, it's better to have an option b) if option a) fails

stormi

@NoHeadroom said in XCP-ng 8.3 betas and RCs feedback :

Anyway, it's better to have an option b) if option a) fails

As you wish, but I won't support option b) in any case, so I prefer to mention it

exetico

I'm excited about the 8.3 production release. With that said, I joined XCP-ng with the 8.3 release, and it has been rock solid. I mean, there has been a few bugs, but nothing impacting the stability.

I also faced problems with controlling power-state of my VMs (reboot) yesterday, but after installing the latest patches to my host (through XO), and rebooted the host, things worked again, as expected.

@stormi said in XCP-ng 8.3 betas and RCs feedback :

Reboot after update

...

Question : What's the "upgrade path" for us starting on 8.3 alpha. Is it just a question about updating the system, and nothing else?
Or, should I plan some kind of operation, so I can "switch" to a stable 8.3 release at some time? Like switching from unstable to a stable branch in Manjaro. Maybe it should make sense to include something about that, in a upcoming final release for 8.3. I bet other people with a r8125 NIC also jumped directly on 8.3 alpha, due to the build-in support for that NIC.

Just a notice for the "newbies" like myself :
Remember to update your Xen Orchestra from time to time. I can't really explain why, but I've not thought about that at all. So yesterday I updated from a march 2023 commit, to the most recent one. Not much was changed, but I guess some kind of incompatibilities could be expected, after more than one year without a single update of Xen Orchestra .

manilx

@exetico said in XCP-ng 8.3 betas and RCs feedback :

Remember to update your Xen Orchestra from time to time. I can't really explain why, but I've not thought about that at all. So yesterday I updated from a march 2023 commit, to the most recent one. Not much was changed, but I guess some kind of incompatibilities could be expected, after more than one year without a single update of Xen Orchestra .

Actually there have been HUGE changes in 1 year! You should check them out (only the last weeks big changes to how backups/snapshots work).
Keep it updated and follow Vates' blog to have the news and changes.

olivierlambert

March 2023 means almost 16 releases since, and you can see the amount of change done each release, multiply it by 16…

Here is all the blog posts with the tag release: https://xen-orchestra.com/blog/tag/release/

You missed a LOT

exetico

@olivierlambert I clearly didn't spend much time in the updated interface, yesterday evening ! It was not meant as a "Well, no changes, boring and lazy devs", or anything like that. I really enjoy XO.

I normally update all other things quite often. But I simply didn't think of the fact, that XO was isolated in it's own VM, and living it's own dreams.

@manilx said in XCP-ng 8.3 betas and RCs feedback :

Keep it updated and follow Vates' blog to have the news and changes

Thank you. I'll start following that for news. My limited use of XO does mean that I'm not really digging into the deeper levels. This is a great shortcut for that .

vectr0n

Updated 2 hosts to 8.3 RC1 without any issues and all VM's are functioning correctly. I've been running 8.3 since I moved my personal stuff away from ESXi. Only ran into a few issues in the past with graphs not appearing in XO/XOA but the team was already working on fixes and came thru as always. Keep up the good work XCP-NG/XO teams!

14wkinnersley

Needing some assistance on where to start with the upgrade. I want to upgrade my 3-node cluster. As of right now all 3 nodes are on 8.2.1 but are BIOS boot, and it appears you need UEFI for 8.3 RC1. What is the best way to go about upgrading to where I wont lose data/vm’s? Understand I will most likely need to do a fresh install on each host.. What’s recommended? Should I start with the node that holds the master first on doing the fresh install?

stormi

@exetico said in XCP-ng 8.3 betas and RCs feedback :

Question : What's the "upgrade path" for us starting on 8.3 alpha. Is it just a question about updating the system, and nothing else?
Or, should I plan some kind of operation, so I can "switch" to a stable 8.3 release at some time? Like switching from unstable to a stable branch in Manjaro.

There are instructions in the blog post of the release candidate: https://xcp-ng.org/blog/2024/07/12/xcp-ng-8-3-release-candidate-1/

Currently, updating normally is enough. However, the blog post describes manual changes you have to do (deleting lines in SSH configuration files).

In the end, when the final release is published, then I advise that everyone upgrades using the installation ISO, to clean the system of leftovers of the intermediary test packages. Avoid doing it now, though, because we found a last minute issue specifically on upgrades from 8.3 pre-releases: TLS certificates of the pool are not retained, and this may cut the communications between members of a pool.

stormi

@14wkinnersley

For any upgrade (and in any case), make sure you have good backups, just in case.
The upgrade process doesn't touch your storage repositories nor VM metadata, so your VMs will still be there (but still apply 1.)
You can upgrade even if your boot mode is Legacy BIOS, but the installer will warn you that sooner or later, this won't work anymore. It's easier when you have enough resources to move your VMs around while reinstalling. I'm leaving the details on how to achieve this to others because I'm on vacation :). There's also our technical support to help on this kind of migration.

manilx

@stormi reading https://xcp-ng.org/blog/2024/07/12/xcp-ng-8-3-release-candidate-1/
I found this:

"Current XCP-ng 8.3 users will need to review these configuration files. Make sure to remove any lines starting with Ciphers, MACs, KexAlgorithms, and HostKeyAlgorithms if they are present. This ensures that future changes to the defaults made by our security team will be applied."

Checking /etc/ssh/ssh_config I find these lines at the end:

        Ciphers aes128-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
        MACs hmac-sha2-256,hmac-sha2-512,hmac-sha1
        KexAlgorithms curve25519-sha256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1
        HostKeyAlgorithms ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-rsa

Checking /etc/ssh/sshd_config I find the following in the middle of the file:

# Ciphers, MACs, KEX Algorithms & HostKeyAlgorithms
Ciphers aes128-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
MACs hmac-sha2-256,hmac-sha2-512,hmac-sha1
KexAlgorithms curve25519-sha256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1
HostKeyAlgorithms ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-rsa

So just to confirm/double check:

I'm supposed to delete those lines as per RC1 info, right?

I don't like to edit system files without having to do so
Thx in advance!