Follow up email, just to confirm that the rolling pool upgrade was successful on my 3 hosts. On each host, the procedure provided by Yvan was repeated and the host detected the previous installation and carried out the upgrade
thanks again. On Sun, Oct 14, 2012 at 2:50 PM, Black Bird <[email protected]> wrote: > Hi Yvan > > I've tried your patch and it does work. The existing installation is > recognised. I'll now attempt the rolling pool upgrade. > > Thanks for your help. > > On Fri, Oct 12, 2012 at 2:29 AM, karmouta yvan < > [email protected]> wrote: > >> Hello all >> >> I have a pool of 3 vanilla XCP 1.1.0-50674c hosts. I have attempted an >>> upgrade of one of the hosts which is currently unloaded with VMs (not >>> the master) just to verify that an upgrade is possible, prior to >>> commencing a rolling pool upgrade (starting from the master). >>> >>> I am using the latest XCP-1.6-beta-61002c.iso. I added the keys >>> PLATFORM_VERSION=1.1.0 and PLATFORM_NAME=XCP to /etc/xensource-inventory >>> as directed by >>> http://wiki.xen.org/wiki/XCP_**1.6_test_instructions<http://wiki.xen.org/wiki/XCP_1.6_test_instructions>. >>> The >>> file contents is now: >>> >>> [root@xen3v3 ~]# cat /etc/xensource-inventory >>> BUILD_NUMBER='50674c' >>> CURRENT_INTERFACES='xapi10 xapi13 xapi5 xapi12 xapi8 xapi14 xapi6 xapi16 >>> xapi11 xapi7 xapi3 xapi15 xenbr0 xapi4 xapi2 xapi9' >>> DOM0_MEM='752' >>> PRODUCT_BRAND='XCP' >>> INSTALLATION_UUID='**aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa**aa' >>> KERNEL_VERSION='2.6.32.12-0.7.**1.xs1.1.0.327.170596xen' >>> DEFAULT_SR_PHYSDEVS='/dev/**sda3' >>> CONTROL_DOMAIN_UUID='**bbbbbbbbbbbbbbbbbbbbbbbbbbbbbb**bbbb' >>> PRIMARY_DISK='/dev/disk/by-id/**scsi-SATA_ST2000DM001-9YN_**Z1E0V06V' >>> XEN_VERSION='3.4.2' >>> BACKUP_PARTITION='/dev/disk/**by-id/scsi-SATA_ST2000DM001-**9YN_Z1E0V06V-part2' >>> >>> PRODUCT_NAME='xcp' >>> INSTALLATION_DATE='2012-10-09 05:24:44.725360' >>> PRODUCT_VERSION='1.1.0' >>> PLATFORM_VERSION=1.1.0 >>> PLATFORM_NAME=XCP >>> MANAGEMENT_INTERFACE='xapi9' >>> >>> The ISO boots normally. After going through the keyboard selection and >>> disk selection, the installer reports "Only product installations that >>> cannot be upgraded have been detected". >>> >> >> I bumped into the same issue yesterday, I have resolved this by modifying >> the file "/opt/xensource/installer/**upgrade.py" at the ligne 53 >> >> diff upgrade_bad.py upgrade.py >> 54c54 >> < return (cls.upgrades_product == product and >> --- >> > return (cls.upgrades_product.upper() == product.upper() and >> >> during install, you just have to go on the console, apply the patch and >> kill the python init process and relaunch it whith "python >> /opt/xensource/installer/init"**. >> >> Afterward everything goes smoothly and I have a shiny new XCP 1.6 running >> with all my VMs and my configuration upgraded ! >> >> Note : that test was carried on a standalone server, I'll try the cluster >> rolling upgrade in the next few days. >> >> Cheers and thanks for the great work! >> >> Yvan >> >> >> >> >> >>> At this point I stop as I want to do an upgrade, not a clean >>> installation. >>> >>> Do I need to provide different keys in /etc/xensource-inventory or carry >>> out some other steps? >>> >>> >>> >> >
_______________________________________________ Xen-api mailing list [email protected] http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
