XCP-ng 8.3 betas and RCs feedback 🚀

stormi

@TheFrisianClause Please open a separate thread for this, where we'll follow-up (was it you who already had one about this very problem?)

stormi

By the way, it is OK, and even good, to mention any issues you have with 8.3 here. It's what's this thread is for. However, if you don't see any answers because there are too many different discussions happening at the same time, I advise to open a separate thread and mention it here, so that people can jump there and help there.

psafont

@rmaclachlan This looks awfully similar to https://github.com/xapi-project/xen-api/pull/5451

freddy77 opened this pull request in xapi-project/xen-api

closed CP-47754: Do not report errors attempting to read PCI vendor:product #5451

gduperrey

A new version of xo-lite for XCP-ng 8.3 has been released:

Version: xo-lite-0.2.0-1.xcpng8.3

You can update it like this:

yum update xo-lite

For more information about the changes between version 0.1.3 and 0.2.0, you can consult this link: https://github.com/vatesfr/xen-orchestra/blob/master/%40xen-orchestra/lite/CHANGELOG.md

Tristis Oris

@gduperrey should it be available by usual way at XO?

yum update xo-lite
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
No packages marked for update

rmaclachlan

@Tristis-Oris Try a yum clean all and then redo your yum update

XO Update seems to be working well for us on 3 hosts!

Tristis Oris

@rmaclachlan nvm found it. Some long lived cache at repo proxy. Looks i need a wait about 1 extra hour.

jivanpal

@stormi I was able to get the new version of xo-lite via yum update (and it's looking good!), so I have everything up to date, though I'm still running Xen 4.13, not Xen 4.17. However, stats in XO (not XO Lite) still aren't working for me for some reason; I'm running XO v5.92.0 (commit 25982ca, from today), built from source. All VMs are running xe-guest-utilities / management agent 7.30.0-2, as that is the version provided by my installation of XCP-ng.

ThierryC01

@stormi said in XCP-ng 8.3 beta :

@ThierryC01 said in XCP-ng 8.3 beta :

For your information, the connection error icon in "Settings"-->"Remotes" that appears when entering a wrong password once, then connecting anyway afterwards with the correct password is still present after all the 8.3 updates.

Is this an XCP-ng issue?

After the latest XOA update, the annoying error icon is gone! So it was an XOA issue

rmaclachlan

Not sure if this is a known issue, I couldn't find it on Github but maybe I was looking in the wrong spot. Is anyone else's network Bond speeds 0? I thought I had seen a fix a month ago for this in a release but now I can't find that changelog

stormi

@jivanpal If it persists, please open a new thread in the Xen Orchestra section of the forum.

stormi

I just pushed a few updates to the xcp-ng-base repository for XCP-ng 8.3. Nothing really worth mentioning from the user point of view, so what matters is as usual to ensure no regressions are seen.

flakpyro

After installing all the latest patches from this week my XOA and xe pif-param-list are both still showing network bonds linking at 0 b/s just like @rmaclachlan pointed out above.

ph7

@stormi
In XO updated yesterday, it says: 6 missing patches. but in the patches tab i got no missing pathes ???

stormi

@ph7 This happens when not all hosts in the pool are up to date. Could it be the case?

ph7

@stormi No, they are on the same patchlevel. Exept these released just resently.

ph7

@ph7
Eureka. I can see them now !!!

ph7

@ph7 Running rolling pool update.
This is really fun.
Love this project

laurentm

XenOrchestra (from source) update failed with the latest updates of XCP-NG 8.3.
I opened a topic in XOA forum, but I succeeded to update in XCP-NG 8.2, so the
error is coming from 8.3.

fatal: unable to access 'https://github.com/vatesfr/xen-orchestra/': server certificate verification failed. CAfile: none CRLfile: none

Finally, I have bypassed the PFBlocker module during the update and no more error happened.

lethedata

ISO NFS can't seem to mount with an IPv6 address as it leads to a "DNS Error."

Error code: SR_BACKEND_FAILURE_140
Error parameters: , Incorrect DNS name, unable to resolve.,

sr-probe is able to find the target/paths and VDI SR NFS is able to mount using the same path. Tried with and without brackets but no success on the NFS ISO side