10:19 a.m.
--=_bcf7df549bf9b0ecceb7d9f8d77a9c96
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Hi, This is the whole message. Here you get the whole output of the proc=
ess. I runned these commands on the node hosting the engine vm. But if t=
here is a more efficient workflow, I am interrested in it ! # yum -y u=
pdate Modules complmentaires chargs : fastestmirror=0Abase | 3.6 kB 00:0=
0:00 =0Acentos-sclo-rh-release | 2.9 kB 00:00:00 =0Aextras | 3.4 kB 00:0=
0:00 =0Aovirt-4.2 | 3.0 kB 00:00:00 =0Aovirt-4.2-centos-gluster312 | 2.9=
kB 00:00:00 =0Aovirt-4.2-centos-opstools | 2.9 kB 00:00:00 =0Aovirt-4.2=
-centos-ovirt42 | 2.9 kB 00:00:00 =0Aovirt-4.2-centos-qemu-ev | 2.9 kB 0=
0:00:00 =0Aovirt-4.2-epel/x86_64/metalink | 26 kB 00:00:00 =0Aovirt-4.2-=
virtio-win-latest | 3.0 kB 00:00:00 =0Aupdates | 3.4 kB 00:00:00 =0ALoad=
ing mirror speeds from cached hostfile=0A * base: fr.mirror.babylon.netw=
ork=0A * extras: ftp.ciril.fr=0A * ovirt-4.2: mirror.slu.cz=0A * ovirt-4=
.2-epel: mirror.uv.es=0A * updates: mirror.plusserver.com=0ANo packages=
marked for update=0A# hosted-engine --upgrade-appliance =0A[ INFO ] Sta=
ge: Initializing=0A[ INFO ] Stage: Environment setup=0A During customiza=
tion use CTRL-D to abort.=0A=0A =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A Welco=
me to the oVirt Self Hosted Engine setup/Upgrade tool.=0A=0A Please refe=
r to the oVirt install guide:=0A https://www.ovirt.org/documentation/how=
-to/hosted-engine/#fresh-install=0A Please refer to the oVirt upgrade gu=
ide:=0A https://www.ovirt.org/documentation/how-to/hosted-engine/#upgrad=
e-hosted-engine=0A =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A Continuing will u=
pgrade the engine VM running on this hosts deploying and configuring a n=
ew appliance.=0A If your engine VM is already based on el7 you can also=
simply upgrade the engine there.=0A This procedure will create a new di=
sk on the hosted-engine storage domain and it will backup there the cont=
ent of your current engine VM disk.=0A 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.=0A Y=
ou will be asked to take a backup of the running engine and copy it to t=
his host.=0A The engine backup will be automatically injected and recove=
red on the new appliance.=0A Are you sure you want to continue? (Yes, No=
)[Yes]: Yes=0A Configuration files: []=0A Log file: /var/log/ovirt-hoste=
d-engine-setup/ovirt-hosted-engine-setup-20180212090846-pse285.log=0A Ve=
rsion: otopi-1.7.5 (otopi-1.7.5-1.el7.centos)=0A[ INFO ] Detecting avail=
able oVirt engine appliances=0A[ INFO ] Stage: Environment packages setu=
p=0A[ INFO ] Stage: Programs detection=0A[ INFO ] Stage: Environment set=
up=0A[ INFO ] Checking maintenance mode=0A[ INFO ] The engine VM is runn=
ing on this host=0A[ INFO ] Stage: Environment customization=0A=0A --=3D=
=3D STORAGE CONFIGURATION =3D=3D--=0A=0A[ INFO ] Answer file successfull=
y loaded=0A[ INFO ] Acquiring internal CA cert from the engine=0A[ INFO=
] The following CA certificate is going to be used, please immediately=
interrupt if not correct:=0A[ INFO ] Issuer: C=3DUS, O=3Dpfm-ad.pfm.loc=
, CN=3Dpfm-ovirt-engine.pfm-ad.pfm.loc.60769, Subject: C=3DUS, O=3Dpfm-a=
d.pfm.loc, CN=3Dpfm-ovirt-engine.pfm-ad.pfm.loc.60769, Fingerprint (SHA-=
1): 2815C0CB4D6E05B7503917173F0D65B452C9D3DC=0A=0A --=3D=3D HOST NETWORK=
CONFIGURATION =3D=3D--=0A=0A[ INFO ] Checking SPM status on this host=
=0A[ INFO ] Connecting to Engine=0A Enter engine admin username [admin@i=
nternal]: =0A Enter engine admin password: =0A[ INFO ] Connecting to Eng=
ine=0A[ INFO ] This upgrade tool is running on the SPM host=0A[ INFO ] B=
ridge ovirtmgmt already created=0A[WARNING] Unable to uniquely detect th=
e interface where Bridge ovirtmgmt has been created on, [u'bond0', u'vne=
t0', u'vnet1', u'vnet2'] appear to be valid alternatives=0A=0A
--=3D=3D=
VM CONFIGURATION =3D=3D--=0A=0A The following appliance have been found=
on your system:=0A [1] - The oVirt Engine Appliance image (OVA) - 4.2-2=
0171219.1.el7.centos=0A [2] - Directly select an OVA file=0A Please sele=
ct an appliance (1, 2) [1]: 1=0A[ INFO ] Verifying its sha1sum=0A[ INFO=
] Checking OVF archive content (could take a few minutes depending on a=
rchive size)=0A[ INFO ] Checking OVF XML content (could take a few minut=
es depending on archive size)=0A Please specify the size of the VM disk=
in GB: [50]: =0A[ INFO ] Connecting to Engine=0A[ INFO ] The hosted-eng=
ine storage domain has enough free space to contain a new backup disk.=
=0A[ INFO ] Checking version requirements=0A[ INFO ] Checking metadata a=
rea=0A[ INFO ] Hosted-engine configuration is at a compatible level=0A[=
INFO ] Connecting to Engine=0A[ ERROR ] Cluster PROD is at version 4.2=
which is not supported by this upgrade flow. Please fix it before upgra=
ding.=0A[ ERROR ] Failed to execute stage 'Environment customization': U=
nsupported cluster level=0A[ INFO ] Stage: Clean up=0A[ INFO ] Stage: Pr=
e-termination=0A[ INFO ] Stage: Termination=0A[ ERROR ] Hosted Engine up=
grade failed=0A=0A Le 12-Feb-2018 08:06:43 +0100, jbelka(a)redhat.com a cr=
it: =0A> This option relevant only for the upgrade from 3.6 to 4.0(engin=
e had=0A > different OS major versions), it all other cases the upgrade=
flow very=0A > similar to upgrade flow of standard engine environment.=
=0A > =0A > =0A > 1. Put hosted-engine environment to GlobalMaintenance(=
you can do it via=0A > UI)=0A > 2. Update engine packages(# yum update -=
y)=0A > 3. Run engine-setup=0A > 4. Disable GlobalMaintenance=0A >=0A >=
Could someone explain me at least what "Cluster PROD is at version 4.2=
which=0A > is not supported by this upgrade flow. Please fix it before=
upgrading."=0A > means ? As far as I know 4.2 is the most recent branch=
available, isn't it ?=0A=0A I have no idea where did you get=0A=0A "Clu=
ster PROD is at version 4.2 which is not supported by this upgrade flow.=
Please fix it before upgrading."=0A=0A Please do not cut output and pro=
vide exact one.=0A=0A IIUC you should do 'yum update ovirt\*setup\*' and=
then 'engine-setup'=0A and only after it would finish successfully you=
would do 'yum -y update'.=0A Maybe that's your problem?=0A=0A Jiri =0A=
=0A---------------------------------------------------------------------=
----------------------------=0AFreeMail powered by mail.fr
--=_bcf7df549bf9b0ecceb7d9f8d77a9c96
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<div><span style=3D"font-family: arial, helvetica, sans-serif; font-size=
: 10pt; color: #000000;">Hi,</span></div>=0A<div><span
style=3D"font-fam=
ily: arial, helvetica, sans-serif; font-size: 10pt; color: #000000;">Thi=
s is the whole message.</span></div>=0A<div><span
style=3D"font-family:=
arial, helvetica, sans-serif; font-size: 10pt; color: #000000;">Here yo=
u get the whole output of the process. I runned these commands on the no=
de hosting the engine vm.</span></div>=0A<div><span
style=3D"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></di=
v>=0A<div> </div>=0A<div># yum -y
update</div>=0A<div><span style=
=3D"font-family: arial, helvetica, sans-serif; font-size: 10pt; color: #=
000000;">Modules complémentaires chargés :
fastestmir=
ror<br
/>base  =
;  =
;  =
;  =
;  =
;  =
;  =
;
| 3.6 kB 0=
0:00:00 <br
/>centos-sclo-rh-release =
=
=
=
=
=
| 2.9=
kB 00:00:00 <br
/>extras  =
;  =
;  =
;  =
;  =
;  =
;  =
;  =
; | 3.4 kB 00:00:00
<br />ovir=
t-4.2 &=
nbsp; &=
nbsp; &=
nbsp; &=
nbsp; &=
nbsp; &=
nbsp; &=
nbsp; | 3.0 kB 00:00:00
<br />=
ovirt-4.2-centos-gluster312 &nb=
sp; &nb=
sp; &nb=
sp; &nb=
sp; &nb=
sp; &nb=
sp; | 2.9 kB 00:00:00 <br
/>ovirt-4.2-cent=
os-opstools &=
nbsp; &=
nbsp; &=
nbsp; &=
nbsp; &=
nbsp; =
| 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 &nbs=
p; &nbs=
p; &nbs=
p; &nbs=
p; &nbs=
p; &nbs=
p; | 2.9 kB 00:00:00 <br
/>ovirt-4.2-epel/=
x86_64/metalink &nb=
sp; &nb=
sp; &nb=
sp; &nb=
sp; &nb=
sp; | 26
kB 00:00:=
00 <br
/>ovirt-4.2-virtio-win-latest =
=
=
=
=
=
| 3.0 kB
00:00:00 =
<br
/>updates &nbs=
p; &nbs=
p; &nbs=
p; &nbs=
p; &nbs=
p; &nbs=
p; &nbs=
p; | 3.4
kB 00:00:=
00 <br />Loading mirror speeds from cached
hostf=
ile<br /> * base: fr.mirror.babylon.network<br /> * extras:
ft=
p.ciril.fr<br /> * ovirt-4.2: mirror.slu.cz<br /> *
ovirt-4.2-=
epel: mirror.uv.es<br /> * updates: mirror.plusserver.com<br />No p=
ackages marked for update<br /># hosted-engine --upgrade-appliance <br /=
[ INFO ] Stage: Initializing<br />[ INFO ]
Stage: Environme=
nt setup<br
/>
Dur=
ing customization use CTRL-D to abort.<br
/> &nbs=
p; <br
/> &nb=
sp; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br
/> =
Welcome to the oVirt Self Hosted Engine
s=
etup/Upgrade tool.<br
/>  =
;<br
/>
Please ref=
er to the oVirt install guide:<br
/> =
https://www.ovirt.org/documentation/how-to/hosted-eng=
ine/#fresh-install<br
/> =
Please refer to the oVirt upgrade guide:<br
/> &=
nbsp;
https://www.ovirt.org/documentation/=
how-to/hosted-engine/#upgrade-hosted-engine<br
/>  =
;
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br />&nb=
sp;
Continuing will upgr=
ade 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 t=
he engine there.<br
/> &n=
bsp; 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 d=
isk.<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
/> &nbs=
p; You will be asked to take a backup of the running engine and co=
py it to this host.<br
/>  =
; The engine backup will be automatically injected and recovered o=
n the new appliance.<br
/> &nbs=
p; Are you sure you want to continue? (Yes, No)[Yes]: Yes<br />&nb=
sp;
Configuration files:=
[]<br
/>
Log file=
: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-201802120=
90846-pse285.log<br
/> &n=
bsp; 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 detectio=
n<br />[ INFO ] Stage: Environment setup<br />[ INFO ]
Check=
ing maintenance mode<br />[ INFO ] The engine VM is running on thi=
s host<br />[ INFO ] Stage: Environment customization<br
/> &=
nbsp; <br
/> =
--=3D=3D STORAGE CONFIGURATION
=3D=3D--<b=
r />
<br />[ INFO =
] Answer file successfully loaded<br />[ INFO ] Acquiring interna=
l CA cert from the engine<br />[ INFO ] The following CA certifica=
te is going to be used, please immediately interrupt if not correct:<br=
/>[ INFO ] Issuer: C=3DUS, O=3Dpfm-ad.pfm.loc, CN=3Dpfm-ovirt-eng=
ine.pfm-ad.pfm.loc.60769, Subject: C=3DUS, O=3Dpfm-ad.pfm.loc, CN=3Dpfm-=
ovirt-engine.pfm-ad.pfm.loc.60769, Fingerprint (SHA-1): 2815C0CB4D6E05B7=
503917173F0D65B452C9D3DC<br
/> =
<br
/>
--=
=3D=3D HOST NETWORK CONFIGURATION =3D=3D--<br
/> =
<br />[ INFO ] Checking SPM
status on thi=
s host<br />[ INFO ] Connecting to Engine<br
/> &=
nbsp; Enter engine admin username
[admin@i=
nternal]: <br
/>
E=
nter engine admin password: <br />[ INFO ] Connecting to Engine<br=
/>[ INFO ] This upgrade tool is running on the SPM host<br />[ IN=
FO ] Bridge ovirtmgmt already created<br />[WARNING] Unable to uni=
quely 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 /> =
--=3D=3D VM
CONFIGURATION =3D=
=3D--<br />
<br /> =
The
following appliance=
have been found on your system:<br
/> &nbs=
p; [1] - The oVirt Engine
Appliance=
image (OVA) - 4.2-20171219.1.el7.centos<br
/> &n=
bsp; [2] - Directly
select an=
OVA file<br
/>
Pl=
ease 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 />&=
nbsp;
Please specify the=
size of the VM disk in GB: [50]: <br />[ INFO ] Connecting to Eng=
ine<br />[ INFO ] The hosted-engine storage domain has enough free=
space to contain a new backup disk.<br />[ INFO ] Checking versio=
n requirements<br />[ INFO ] Checking metadata area<br />[
INFO&nb=
sp; ] Hosted-engine configuration is at a compatible level<br />[ INFO&n=
bsp; ] Connecting to Engine<br />[ ERROR ] Cluster PROD is at version 4.=
2 which is not supported by this upgrade flow. Please fix it before upgr=
ading.<br />[ ERROR ] Failed to execute stage 'Environment customization=
': Unsupported cluster level<br />[ INFO ] Stage: Clean up<br
/>[=
INFO ] Stage: Pre-termination<br />[ INFO ] Stage: Terminat=
ion<br />[ ERROR ] Hosted Engine upgrade failed<br
/></span></div>=0A<p>=
<br /><br /> Le 12-Feb-2018 08:06:43 +0100, jbelka(a)redhat.com a é=
crit:</p>=0A<blockquote style=3D"margin-left: 0; padding-left: 5px; bord=
er-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 flo=
w 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
whic=
h 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>=
=0A <br/><hr>FreeMail powered by <a
href=3D"https://m=
ail.fr" target=3D"_blank">mail.fr</a>=0A
--=_bcf7df549bf9b0ecceb7d9f8d77a9c96--