<div><span style="font-family: arial, helvetica, sans-serif; font-size: 10pt; color: #000000;">Hi,</span></div>
<div><span style="font-family: arial, helvetica, sans-serif; font-size: 10pt; color: #000000;">This is the whole message.</span></div>
<div><span style="font-family: arial, helvetica, sans-serif; font-size: 10pt; color: #000000;">Here you get the whole output of the process. I runned these commands on the node hosting the engine vm.</span></div>
<div><span style="font-family: arial, helvetica, sans-serif; font-size: 10pt; color: #000000;">But if there is a more efficient workflow, I am interrested in it !</span></div>
<div> </div>
<div># yum -y update</div>
<div><span style="font-family: arial, helvetica, sans-serif; font-size: 10pt; color: #000000;">Modules complémentaires chargés : fastestmirror<br />base | 3.6 kB 00:00:00 <br />centos-sclo-rh-release | 2.9 kB 00:00:00 <br />extras | 3.4 kB 00:00:00 <br />ovirt-4.2 | 3.0 kB 00:00:00 <br />ovirt-4.2-centos-gluster312 | 2.9 kB 00:00:00 <br />ovirt-4.2-centos-opstools | 2.9 kB 00:00:00 <br />ovirt-4.2-centos-ovirt42 | 2.9 kB 00:00:00 <br />ovirt-4.2-centos-qemu-ev | 2.9 kB 00:00:00 <br />ovirt-4.2-epel/x86_64/metalink | 26 kB 00:00:00 <br />ovirt-4.2-virtio-win-latest | 3.0 kB 00:00:00 <br />updates | 3.4 kB 00:00:00 <br />Loading mirror speeds from cached hostfile<br /> * base: fr.mirror.babylon.network<br /> * extras: ftp.ciril.fr<br /> * ovirt-4.2: mirror.slu.cz<br /> * ovirt-4.2-epel: mirror.uv.es<br /> * updates: mirror.plusserver.com<br />No packages marked for update<br /># hosted-engine --upgrade-appliance <br />[ INFO ] Stage: Initializing<br />[ INFO ] Stage: Environment setup<br /> During customization use CTRL-D to abort.<br /> <br /> ==================================================================================<br /> Welcome to the oVirt Self Hosted Engine setup/Upgrade tool.<br /> <br /> Please refer to the oVirt install guide:<br /> https://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install<br /> Please refer to the oVirt upgrade guide:<br /> https://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-engine<br /> ==================================================================================<br /> Continuing will upgrade the engine VM running on this hosts deploying and configuring a new appliance.<br /> If your engine VM is already based on el7 you can also simply upgrade the engine there.<br /> This procedure will create a new disk on the hosted-engine storage domain and it will backup there the content of your current engine VM disk.<br /> The new el7 based appliance will be deployed over the existing disk destroying its content; at any time you will be able to rollback using the content of the backup disk.<br /> You will be asked to take a backup of the running engine and copy it to this host.<br /> The engine backup will be automatically injected and recovered on the new appliance.<br /> Are you sure you want to continue? (Yes, No)[Yes]: Yes<br /> Configuration files: []<br /> Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20180212090846-pse285.log<br /> Version: otopi-1.7.5 (otopi-1.7.5-1.el7.centos)<br />[ INFO ] Detecting available oVirt engine appliances<br />[ INFO ] Stage: Environment packages setup<br />[ INFO ] Stage: Programs detection<br />[ INFO ] Stage: Environment setup<br />[ INFO ] Checking maintenance mode<br />[ INFO ] The engine VM is running on this host<br />[ INFO ] Stage: Environment customization<br /> <br /> --== STORAGE CONFIGURATION ==--<br /> <br />[ INFO ] Answer file successfully loaded<br />[ INFO ] Acquiring internal CA cert from the engine<br />[ INFO ] The following CA certificate is going to be used, please immediately interrupt if not correct:<br />[ INFO ] Issuer: C=US, O=pfm-ad.pfm.loc, CN=pfm-ovirt-engine.pfm-ad.pfm.loc.60769, Subject: C=US, O=pfm-ad.pfm.loc, CN=pfm-ovirt-engine.pfm-ad.pfm.loc.60769, Fingerprint (SHA-1): 2815C0CB4D6E05B7503917173F0D65B452C9D3DC<br /> <br /> --== HOST NETWORK CONFIGURATION ==--<br /> <br />[ INFO ] Checking SPM status on this host<br />[ INFO ] Connecting to Engine<br /> Enter engine admin username [admin@internal]: <br /> Enter engine admin password: <br />[ INFO ] Connecting to Engine<br />[ INFO ] This upgrade tool is running on the SPM host<br />[ INFO ] Bridge ovirtmgmt already created<br />[WARNING] Unable to uniquely detect the interface where Bridge ovirtmgmt has been created on, [u'bond0', u'vnet0', u'vnet1', u'vnet2'] appear to be valid alternatives<br /> <br /> --== VM CONFIGURATION ==--<br /> <br /> The following appliance have been found on your system:<br /> [1] - The oVirt Engine Appliance image (OVA) - 4.2-20171219.1.el7.centos<br /> [2] - Directly select an OVA file<br /> Please select an appliance (1, 2) [1]: 1<br />[ INFO ] Verifying its sha1sum<br />[ INFO ] Checking OVF archive content (could take a few minutes depending on archive size)<br />[ INFO ] Checking OVF XML content (could take a few minutes depending on archive size)<br /> Please specify the size of the VM disk in GB: [50]: <br />[ INFO ] Connecting to Engine<br />[ INFO ] The hosted-engine storage domain has enough free space to contain a new backup disk.<br />[ INFO ] Checking version requirements<br />[ INFO ] Checking metadata area<br />[ INFO ] Hosted-engine configuration is at a compatible level<br />[ INFO ] Connecting to Engine<br />[ ERROR ] Cluster PROD is at version 4.2 which is not supported by this upgrade flow. Please fix it before upgrading.<br />[ ERROR ] Failed to execute stage 'Environment customization': Unsupported cluster level<br />[ INFO ] Stage: Clean up<br />[ INFO ] Stage: Pre-termination<br />[ INFO ] Stage: Termination<br />[ ERROR ] Hosted Engine upgrade failed<br /></span></div>
<p><br /><br /> Le 12-Feb-2018 08:06:43 +0100, jbelka@redhat.com a écrit:</p>
<blockquote style="margin-left: 0; padding-left: 5px; border-left: 2px solid navy;">> This option relevant only for the upgrade from 3.6 to 4.0(engine had<br /> > different OS major versions), it all other cases the upgrade flow very<br /> > similar to upgrade flow of standard engine environment.<br /> > <br /> > <br /> > 1. Put hosted-engine environment to GlobalMaintenance(you can do it via<br /> > UI)<br /> > 2. Update engine packages(# yum update -y)<br /> > 3. Run engine-setup<br /> > 4. Disable GlobalMaintenance<br /> ><br /> > Could someone explain me at least what "Cluster PROD is at version 4.2 which<br /> > is not supported by this upgrade flow. Please fix it before upgrading."<br /> > means ? As far as I know 4.2 is the most recent branch available, isn't it ?<br /><br /> I have no idea where did you get<br /><br /> "Cluster PROD is at version 4.2 which is not supported by this upgrade flow. Please fix it before upgrading."<br /><br /> Please do not cut output and provide exact one.<br /><br /> IIUC you should do 'yum update ovirt\*setup\*' and then 'engine-setup'<br /> and only after it would finish successfully you would do 'yum -y update'.<br /> Maybe that's your problem?<br /><br /> Jiri</blockquote>
<br/><hr>FreeMail powered by <a href="https://mail.fr" target="_blank">mail.fr</a>