XCP-ng 8.3 betas and RCs feedback 🚀

r0ssar00

@stormi I found that the interface-rename script broke with this update due to changes in python, specifically the line where the script concats two dict.keys(): the keys() method signature changed to return dict_keys, which doesn't have the add (or w/e it's named) method, so "a.keys()+b.keys()" fails now. I had to hand-edit the script to get it working, the fix is trivial: concat lists of keys rather than the keys directly.

olivierlambert

Thanks for your feedback @r0ssar00 , pinging @stormi and @yann

fohdeesha

@r0ssar00 hi, that issue would arise if you ran this script with python3, but it's interpreter is set as /usr/bin/python - How did you call this script, did you manually call it with python3? It should be ran by just running the command on the CLI eg interface-rename

ravenet

@stormi
Updated ryzen 1700 late last week, and Threadripper 5975 and Epyc 7313p servers. No issues so far.
Installing fresh on epyc 9224 this week

ph7

@ph7 said in XCP-ng 8.3 beta :

@stormi
I can not see anything under Network throughput in XO-lite

edit:
When I hover I can see the numbers but no graph

I updated to latest version
Same again, no graphs

stormi

@ph7 You seem to be the only one with this issue remaining. Maybe try a reinstall?

Houbsi

Hi there,

i was wondering for the install Image via ipxe, will there be something? I have it, that currently it only works with Legacy Bios and not the UEFI one.

stormi

@Houbsi The best we can do with ipxe is chaining to grub, because ipxe doesn't support multiboot2 in EFI mode.

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 .