This server is a different version to the master

Martín Lorente

Hello everyone,
I have one standalone host in a pool (yes, a pool of one), let's name it host0. This was a 8.1 versión updated to 8.2 by "yum update" before any VM was running there.

Now, I have a new and identical host (host1) to add to this pool, but I can't add it to the pool because it says that version of master (host0) is different.
Host0 was updated to 8.2 and started running several VM on it, so is not possible to reboot it in order to be updated, but a yum update was done, I mean, it is waiting for a reboot to be 100% efective.
Host1 was install in the same way, firstly 8.1 and it is updated later to 8.2. This process lets host1 updated to last available versions, while host0 is not, because the reboot is not possible.

I've look into host0 version and downgrade host1 to the same version, but it continues mismatching version.

xe host-param-list uuid=7fa3f334-f878-4608-9cb5-0d2707706f86 |grep version
                     API-version-major ( RO): 2
                     API-version-minor ( RO): 16
                    API-version-vendor ( RO): XenSource
     API-version-vendor-implementation (MRO): 
                      software-version (MRO): product_version: 8.2.0; product_version_text: 8.2; product_version_text_short: 8.2; platform_name: XCP; platform_version: 3.2.0; product_brand: XCP-ng; build_number: release/stockholm/master/7; hostname: localhost; date: 2020-11-05; dbv: 0.0.1; xapi: 1.20; xen: 4.13.1-9.8.2.xcpng8; linux: 4.19.0+1; xencenter_min: 2.16; xencenter_max: 2.16; network_backend: openvswitch; db_schema: 5.601
    virtual-hardware-platform-versions (SRO): 0; 1; 2

xe host-param-list uuid=7e5f26d9-59d6-4674-ad7f-344e93c5ebb2 |grep version
                     API-version-major ( RO): 2
                     API-version-minor ( RO): 16
                    API-version-vendor ( RO): XenSource
     API-version-vendor-implementation (MRO): 
                      software-version (MRO): product_version: 8.2.0; product_version_text: 8.2; product_version_text_short: 8.2; platform_name: XCP; platform_version: 3.2.0; product_brand: XCP-ng; build_number: release/stockholm/master/7; hostname: localhost; date: 2021-05-20; dbv: 0.0.1; xapi: 1.20; xen: 4.13.1-9.8.2.xcpng8; linux: 4.19.0+1; xencenter_min: 2.16; xencenter_max: 2.16; network_backend: openvswitch; db_schema: 5.602
    virtual-hardware-platform-versions (SRO): 0; 1; 2

As you can see, according to host, they are running the same version, but something is missing. What I'm trying is add host1 to the pool ruled by host0, move every VM to host1 and reboot host0 to get it updated, repeating the process with host1.
Any idea about how to get a matching version working only on host1?
Thanks in advance

Danp

Have you considered doing it this way?

Fully update host1
Migrate VMs to host1
Fully update host0
Join host0 to host1's pool

Martín Lorente

@danp Yes, I considered it, even tried a pool migration, but disks of 1TB take long hours to finally fail. What's more when I've migrate a machine, (and I've migrated several hundreds of them), time to time one of them gets bock and need a reboot, which is something I want to avoid, specially if I don't know when is going to finish, because i takes several hours (may finish at 3 a.m and no one there to check it's correct)

Danp

@martín-lorente Well, you said you intended to migrate the VMs anyway, so I thought this was a viable options.

db_schema: 5.601 vs db_schema: 5.602

I wonder if that is the reason you can't join them.

Martín Lorente

@danp said in This server is a different version to the master:

5.601

You are rigth, the problem was there. I didn´t found any package related to the schema version, but are rigth, so I've look into this. Here a problem like mine, and the key to resolv it. As my host0 was not updated, it was working with schema version 5.601. just a xe-tools-restart was enough to update the schema version to 5.602 and now they match.

Thanks!