XCP-ng 8.3 betas and RCs feedback 🚀

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.

TheFrisianClause

@Tristis-Oris Did it, same problem still. I don't understand why it tries to connect to a IPv6 address while it is not configured on the system.

Ajmind 0

@Ajmind-0 said in XCP-ng 8.3 beta :

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?

Update 22.02.2023:

Without feedback I have returned this host to XCP-NG 8.1 and from this version I updated via recent ISO to 8.2.1 without any problem.

Access from XO from sources or https no problem.

It seems to be that this old host does not work with 8.3 beta for whatever reason.

olivierlambert

Have you enabled IPv6 out of curiosity?

Ajmind 0

@olivierlambert

No, I have not enabled IPv6.

Had the 8.3 beta it enabled by default?

olivierlambert

No, you had a choice during 8.3 install (IPv4 only, or v4+v6 or v6 only)

Ajmind 0

@olivierlambert said in XCP-ng 8.3 beta :

No, you had a choice during 8.3 install (IPv4 only, or v4+v6 or v6 only)

The was no choice option or dialogue!
(I had selected to upgrade the exisiting 8.1 installation.)

olivierlambert

Ah because of the upgrade then, so your issue can't be related to that.

jivanpal

Feedback/comments relating to IPv6 after some usage of beta1 and beta2:

There is no way to configure IPv6 on the management interface via xsconsole, such as if one wants to switch between static configuration, autoconf via RAs, or DHCPv6.
There is apparently no support for IPv6 DNS servers, only IPv4. For example, if I try to add an IPv6 address like fd00::1 or [fd00::1] as a DNS server via xsconsole, there is apparently no change to the configuration. Editing /etc/resolv.conf works to achieve this (e.g. adding the line nameserver fd00::1), but this is known not to persist across reboots.
There is apparently no support for RDNSS (advertisement of DNS servers in RAs rather than via DHCPv6).
The "autoconf" option (available during installation, after choosing IPv6-only or dual-stack, and then being asked which mode to use to configure IPv6 addresses) appears to only be used at installation time to determine values such as the gateway's link-local address, the available address prefixes, and perform SLAAC and DAD, but then the resulting values are hard-coded and don't change according to changes in the environment, such as an upstream change in network prefix. (I will need to do some more testing to really confirm this, but this seems to be the case in my experience.) Compare this to when IPv4 is configured to use DHCP(v4), in which the management interface may have a different IPv4 address at different times, namely if it's assigned a different address by the DHCP server when it attempts to get or renew a lease.
Some repos are unreachable in IPv6-only environments, which I'm aware is already known, and I can get around this by using NAT64 (either with CLAT to perform 464XLAT; or with DNS64), but this fact is currently a blocker for me to move to being IPv6-only.
Speaking of NAT64, this is just a question, I haven't tested or looked into this myself: Does XCP-ng include a CLAT daemon and support for auto-configuring 464XLAT using either the "PREF64" RA option (RFC8781) or resolution of ipv4only.arpa via a DNS64 server (RFC7050)?

TheFrisianClause

@jivanpal I think I have the second option you mention. The yum update command tries to resolve via an IPv6 which is timing out unfortunately.

jivanpal

@TheFrisianClause No, my remark is about wanting to resolve any and all DNS queries using a DNS server that is accessible over IPv6 (such as wanting to use Google's 2001:4860:4860::8888 rather than Google's 8.8.8.8, or in my case wanting to use my LAN's DNS server at fd00::1 rather than 10.0.0.1), whereas yours is about your host attempting to connect to IPv6 addresses that it obtained by resolving AAAA queries, despite the host only having IPv4 connectivity.

The behaviour you're observing is definitely odd. Are you sure that no IPv6 addresses are configured? What is the output of ip a and ip -6 route? If you share the output here, you may want to redact any geographically identifying info in it.

BenjiReis

@jivanpal Thx for your report, I'll reply to you in the dedicated IPv6 thread.

Regards