XCP-ng 8.3 betas and RCs feedback 🚀

Tristis Oris

Good news. Release at this year possible?
What xapi version now at 8.2.1? dunno how to check it.

wilsonqanda

@stormi I assume you had issue so took file down as link is giving a 404 page not found? lol

olivierlambert

8.3 will be obviously released this year @Tristis-Oris

ThierryC01

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.

lethedata

Has the emergency network reset and xe been updated to handle IPv6 only configurations with patches after Beta2 ISO or is there something special that needs to be done?

I'm not able to pull patches atm and after running the resets it didn't seem to like the v6 addressing and xe refused to set the management interface without v4 set. Couldn't drop the temporary v4 address either.

Looks like the answer is yes but only at boot? "The only way to enable IPv6 for the management interface is at boot time. It's something that can't be modified afterwards in XAPI."

ravenet

This update broke my mellanox network drivers for connectx-4 / 4 LX
Seems this latest patches included update from mennalox-mlnxen 5.4 to 5.9

I have no networking, and after an emergency network reset, eth0 and eth1 disappeared.

update1: used yum downgrade mellanox-mlnxen-5.4_1.0.3.0-4.xcpng8.3.x86_64
this didn't fix until I did another emergency network reset.

Looks like I'm back up and running.
Anyone else able to confirm this bug or am I alone in this hiccup?

olivierlambert

Thanks for your feedback @ravenet !

stormi

@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?

ravenet

@olivierlambert said in XCP-ng 8.3 beta :

Thanks for your feedback @ravenet !

ill do firther testing later, in case issue is out-of-date firmware on the adapter itself being incompatible with the new driver. ill try and check the mellanox 5.9 changelog for firmware version requirements.

Andrew

@ravenet @olivierlambert I have a 4Lx card on the way for testing...

flakpyro

One thing i have learned from testing various different 10G nics with XCP-NG that may be somewhat related to this is if you remove (or if a driver fails to load properly perhaps) a NIC that has the management interface assigned to it from a host, upon reboot the host will come up with no NICs present in XO or via xe pif-list, an emergency network rest will not restore them either, my only fix has been to re-install XCP-NG.

If you however first move the management interface to a different NIC before removing said NIC then everything will come up fine and if you have installed a different NIC it will be discovered no problem. I have tested this going from a Qlogic NIC to an Intel X520 and from an Intel X520 to an Intel X710.

Ajmind 0

I have today upgraded an very old Intel Server (S5520UR) running XCP-NG 8.1 to XCP-NG 8.3 beta with the latest beta ISO:

Server:

Intel S5520UR
Dual Xeon E5645
48GB RAM
Intel RAID Cotnroller
RAID1 73GB SSD for DOM0
RAID5 1100GB SAS HDD for Localstorage 2

As the Server was initially a XenServer 6.5 I had to change the partition layout with

touch /var/preserve/save2upgrade

The installation was running smooth, no error message.
I could manage local via CLI and via SSH but not via XO (commit a2c36) from sources or via Xolite.

server.enable
{
  "id": "a1886440-588f-4630-86b9-b1e888553a12"
}
{
  "errno": -111,
  "code": "ECONNREFUSED",
  "syscall": "connect",
  "address": "192.168.1.116",
  "port": 443,
  "originalUrl": "https://192.168.1.116/jsonrpc",
  "url": "https://192.168.1.116/jsonrpc",
  "call": {
    "method": "session.login_with_password",
    "params": "* obfuscated *"
  },
  "message": "connect ECONNREFUSED 192.168.1.116:443",
  "name": "Error",
  "stack": "Error: connect ECONNREFUSED 192.168.1.116:443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16)
    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)"
}

I could start VMs and they seem to run as expected.

~~I have not yet stated to use yum update.~~

Today I have updated the host via yum update. Everyting runs smooth, however still no luck in getting a https connection to that host.

Any advise where I could look into? Wbserver configuration or firewall settings?

gb.123

When trying to run :

yum install xcp-ng-updater

I get this error :

http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 302 - Found

Anyone else getting this ?

I have freshly installed from the link mentioned in the blog : https://xcp-ng.org/blog/2024/02/15/xcp-ng-8-3-beta-2/

UPDATE: This may be due to mismatch in System-time. I updated Time with Chrony and it worked. Maybe a co-incidence but its working not and the error is not re-producable for now.

TheFrisianClause

I would like to update XCP-ng 8.3 with 'yum update' but I am getting this error:

http://mirrors.xcp-ng.org/8/8.3/base/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:240:ab08:2::2: Cannot assign requested address"

What is the resolution to this? IPv6 has not been configured on the machine.

moussa854

@TheFrisianClause
I did yum update and it worked. See if this post provide any clue? https://community.spiceworks.com/topic/2165339-yum-update-not-working-after-disabling-ipv6

moussa854

@gb-123
I can not find yum install xcp-ng-updater in the blog post at you mentioned try yum update

gb.123

@moussa854

I think it was to do with chrony not updating the time. There was a mismatch in system time.

TheFrisianClause

Well the problem is dat it sometimes goes over IPv4 and most of the time it does not.. It did the samen on 8.2 LTS as well.

TheFrisianClause

@moussa854 This did not help, I have not even enabled IPv6. As I upgraded the 8.2 LTS system to 8.3 Beta 2.

Tristis Oris

@TheFrisianClause try with another dns. I have similar problem at some networks.