Hi,
today i updated und install some new XEN Server SP2.
After update to SP2 i have version 39265p
Full install will give me version 47101p.

with that "bug" you cannot add new insatlled XEN Server to a poll with updated XEN Server, because there are different versions...

in the moment there is realy no fun to use citrix xen server...

greetings
roger

I have exactly the same problem. 3 of 4 XenServers were updated via the Update Package without a problem. The fourth XenServer was freshly installed via the 5.6.1 SP2 ISO Image.

I can't join the freshly installed XenServer into the Pool because the build IDs don't match with the upgraded XenServers...

Same here :(

Volkan

Same here....

Same problem here...

I had that problem, too.

The Update from FP1 to SP2 was a success on Master Server (SP2 but with old build number),
but fails on Slave Server.
Slave Machine Interface told me it is already updated (shows SP2) but told me to "Apply Uploaded Update"
again and again. (No success to fix this with xe patch clean and delete of Update folder)
So I made a fresh install of the Slave but could not join the Pool (Version Mismatch).

Solution:
Update Version: 5.6.100-39265p vs. Fresh Install Version: 5.6.100-47101p

Force join the Pool (merge your VMs if needed and change the Master of the Pool) and then make a fresh install of the "old build Number" Machine.

Same problem here what is the story ??

> grep BUILD_NUMBER /etc/xensource-inventory
Please execute this command on all servers and compare results.
Sorry for my question, but if the results are the same, are you sure you upgraded this host with different build number,
This KB CTX122443 is not updated with SP2 yet but check if you number is the same like XS 5.6 FP1 number.

Radek.

Ran commands on both systems - both identical results with build # 39265p

I have ran this command on 5.6.1 FP1 running in a production environment and 5.6.1 SP2 (upgraded from FP1) within a test environment.

The test environment server running the SP2 patch (which installed successfully) clearly states SP2 in the top left corner of the console root screen.

Regards

I have reproduced the problem on clean install of 5.6 fp1 with Linux and latest Dell management packs, upgrade using SP2 XenCenter console, rebooted and build number has failed to increment but xsconsole reports SP2 in top corner.

Second server clean build using 5.6 fp1 sp2 media with Linux and latest Dell management packs, build number has incremented correctly.

Had to force join the pool then rebuild original server.

Same problem here. Using XenCenter 5.6 SP2, I upgraded host "xenserver1" running XS 5.6 FP1 with +XS56ESP2.xsupdate+, and I did a clean install on "xenserver3" using +XenServer-5.6.100-SP2-install-cd.iso+. I get this error when trying to add xenserver3 to the pool:
!addserver.png!

See attached addserver.log.bz2+ for the +xensource.log from attempting to add the server. Here's more info about the hosts:

+uname -a+ from upgrade:
> Linux xenserver1 2.6.32.12-0.7.1.xs5.6.100.323.170596xen #1 SMP Fri Apr 8 07:25:07 EDT 2011 i686 i686 i386 GNU/Linux
From clean install:
> Linux xenserver3 2.6.32.12-0.7.1.xs5.6.100.323.170596xen #1 SMP Fri Apr 8 07:25:07 EDT 2011 i686 i686 i386 GNU/Linux
+cat /etc/redhat-release+ from upgrade:
> XenServer release 5.6.100-39215p (xenenterprise)
From clean install:
> XenServer release 5.6.100-46766p (xenenterprise)
+grep BUILD_NUMBER /etc/xensource-inventory+ from upgrade:
> BUILD_NUMBER='39265p'
From clean install:
> BUILD_NUMBER='47101p'
XenCenter info from from upgrade:
!xenserver1.png!
From clean install:
!xenserver3.png!

___
{color:#555555}Kirk Kosinski{color} !http://www.linkedin.com/favicon.ico!
{color:#999999}MCITP: EA / VA / EDA7, VCP 4, CCA{color}

Kirk, can you try to make a copy of original /etc/xensource-inventory+ file and change the +BUILD_NUMBER+, set it to the same value. I guess +/etc/redhat-release is not really important here. This looks to me like some kind of upgrade limitation, you have to do upgrade in the same way or simply like some kind of bug.

Radek.

That worked. On the freshly installed host I changed:
> BUILD_NUMBER='47101p'
To:
> BUILD_NUMBER='39265p'

And successfully added it to the pool (with the upgraded host).

___
{color:#555555}Kirk Kosinski{color} !http://www.linkedin.com/favicon.ico!
{color:#999999}MCITP: EA / VA / EDA7, VCP 4, CCA{color}

So you simply changed BUILD_NUMBER to the same value which is already on master?

Do I have to spent 5000$ for this error ? :D Come on Citrix... More beta testing.

As well I CANT install linux pack to host which was upgraded through XenCenter.

Citrix please, if you release the new version of XenServer is it SO hard to take care of version numbers ??

Now we have to do a magic with damned xeninvetory file. Mess.

> So you simply changed BUILD_NUMBER to the same value which is already on master?
Yes, exactly.

___
{color:#555555}Kirk Kosinski{color} !http://www.linkedin.com/favicon.ico!
{color:#999999}MCITP: EA / VA / EDA7, VCP 4, CCA{color}

I have a support ticket open for this issue and have been informed that Citrix are aware of the issue.

Hmm..has nobody at Citrix checked if an upgrade runs succesful and also if you add the slaves to the upgraded pool?

I am experience the same problem with Service Pack 2.

Alberto