12:48 p.m.
Hi List,
is there a special upgrade procedure to get from 3.6 to 4.0 of oVirt?
Or it is just a normal upgrade procedure?
I'm currently running oVirt 3.6.7 on CentOS 7.
Best regards and thank you for the answer.
Christoph
3:37 p.m.
On Sun, Jul 3, 2016 at 7:48 PM, <ovirt(a)timmi.org> wrote:
Hi List,
is there a special upgrade procedure to get from 3.6 to 4.0 of oVirt?
Depends on your current system.
Or it is just a normal upgrade procedure?
It is in some cases.
I'm currently running oVirt 3.6.7 on CentOS 7.
If not hosted-engine, normal upgrade.
For hosted-engine please see a recent thread on this list with
subject line "upgrade hosted-engine os ( not hosts )".
For an engine on el6, in-place direct upgrade to el7 is not
supported. You can use backup/restore migration:
https://bugzilla.redhat.com/1318580
Best,
Best regards and thank you for the answer.
Christoph
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Didi
1:15 a.m.
Hi,
in my setup I have two servers on CentOS7. One of these servers is also
running the engine.
From your email I understood that in such case there is not special
procedure for me right?
Best regards
Christoph
Am 03.07.2016 um 21:37 schrieb Yedidyah Bar David:
On Sun, Jul 3, 2016 at 7:48 PM, <ovirt(a)timmi.org> wrote:
> Hi List,
>
> is there a special upgrade procedure to get from 3.6 to 4.0 of oVirt?
Depends on your current system.
> Or it is just a normal upgrade procedure?
It is in some cases.
> I'm currently running oVirt 3.6.7 on CentOS 7.
If not hosted-engine, normal upgrade.
For hosted-engine please see a recent thread on this list with
subject line "upgrade hosted-engine os ( not hosts )".
For an engine on el6, in-place direct upgrade to el7 is not
supported. You can use backup/restore migration:
https://bugzilla.redhat.com/1318580
Best,
> Best regards and thank you for the answer.
> Christoph
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
3:12 a.m.
Yes, this is correct.
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: ydary(a)redhat.com
IRC : ydary
On Jul 4, 2016 08:15, <ovirt(a)timmi.org> wrote:
Hi,
in my setup I have two servers on CentOS7. One of these servers is also
running the engine.
From your email I understood that in such case there is not special
procedure for me right?
Best regards
Christoph
Am 03.07.2016 um 21:37 schrieb Yedidyah Bar David:
> On Sun, Jul 3, 2016 at 7:48 PM, <ovirt(a)timmi.org> wrote:
>
>> Hi List,
>>
>> is there a special upgrade procedure to get from 3.6 to 4.0 of oVirt?
>>
> Depends on your current system.
>
> Or it is just a normal upgrade procedure?
>>
> It is in some cases.
>
> I'm currently running oVirt 3.6.7 on CentOS 7.
>>
> If not hosted-engine, normal upgrade.
>
> For hosted-engine please see a recent thread on this list with
> subject line "upgrade hosted-engine os ( not hosts )".
>
> For an engine on el6, in-place direct upgrade to el7 is not
> supported. You can use backup/restore migration:
>
> https://bugzilla.redhat.com/1318580
>
> Best,
>
> Best regards and thank you for the answer.
>> Christoph
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
4:45 a.m.
This is a multi-part message in MIME format.
--------------AB5682F750EE9BC31ED74D89
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Thank you for the quick answer.
Best regards
Christoph
Am 04.07.2016 um 09:12 schrieb Yaniv Dary:
Yes, this is correct.
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: ydary(a)redhat.com <mailto:ydary@redhat.com>
IRC : ydary
On Jul 4, 2016 08:15, <ovirt(a)timmi.org <mailto:ovirt@timmi.org>> wrote:
Hi,
in my setup I have two servers on CentOS7. One of these servers
is also running the engine.
From your email I understood that in such case there is not
special procedure for me right?
Best regards
Christoph
Am 03.07.2016 um 21:37 schrieb Yedidyah Bar David:
On Sun, Jul 3, 2016 at 7:48 PM, <ovirt(a)timmi.org
<mailto:ovirt@timmi.org>> wrote:
Hi List,
is there a special upgrade procedure to get from 3.6 to
4.0 of oVirt?
Depends on your current system.
Or it is just a normal upgrade procedure?
It is in some cases.
I'm currently running oVirt 3.6.7 on CentOS 7.
If not hosted-engine, normal upgrade.
For hosted-engine please see a recent thread on this list with
subject line "upgrade hosted-engine os ( not hosts )".
For an engine on el6, in-place direct upgrade to el7 is not
supported. You can use backup/restore migration:
https://bugzilla.redhat.com/1318580
Best,
Best regards and thank you for the answer.
Christoph
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
--------------AB5682F750EE9BC31ED74D89
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Thank you for the quick answer.</p>
<p>Best regards<br>
Christoph<br>
</p>
<br>
<div class="moz-cite-prefix">Am 04.07.2016 um 09:12 schrieb Yaniv
Dary:<br>
</div>
<blockquote
cite="mid:CACKMAy_qVJ_=Dy-j6LC1YwGXoScfeuAse4ftesUkQ5DvV4Y5Lg@mail.gmail.com"
type="cite">
<p dir="ltr">Yes, this is correct. </p>
<p dir="ltr">Yaniv Dary<br>
Technical Product Manager<br>
Red Hat Israel Ltd.<br>
34 Jerusalem Road<br>
Building A, 4th floor<br>
Ra'anana, Israel 4350109</p>
<p dir="ltr">Tel : +972 (9) 7692306<br>
8272306<br>
Email: <a moz-do-not-send="true"
href="mailto:ydary@redhat.com">ydary@redhat.com</a><br>
IRC : ydary</p>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Jul 4, 2016 08:15, <<a
moz-do-not-send="true"
href="mailto:ovirt@timmi.org"><a
class="moz-txt-link-abbreviated"
href="mailto:ovirt@timmi.org">ovirt@timmi.org</a></a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
in my setup I have two servers on CentOS7. One of these
servers is also running the engine.<br>
<br>
From your email I understood that in such case there is not
special procedure for me right?<br>
<br>
Best regards<br>
<br>
Christoph<br>
<br>
<br>
<br>
Am 03.07.2016 um 21:37 schrieb Yedidyah Bar David:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On Sun, Jul 3, 2016 at 7:48 PM, <<a
moz-do-not-send="true" href="mailto:ovirt@timmi.org"
target="_blank"><a
class="moz-txt-link-abbreviated"
href="mailto:ovirt@timmi.org">ovirt@timmi.org</a></a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi List,<br>
<br>
is there a special upgrade procedure to get from 3.6 to
4.0 of oVirt?<br>
</blockquote>
Depends on your current system.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Or it is just a normal upgrade procedure?<br>
</blockquote>
It is in some cases.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm currently running oVirt 3.6.7 on CentOS 7.<br>
</blockquote>
If not hosted-engine, normal upgrade.<br>
<br>
For hosted-engine please see a recent thread on this list
with<br>
subject line "upgrade hosted-engine os ( not hosts )".<br>
<br>
For an engine on el6, in-place direct upgrade to el7 is
not<br>
supported. You can use backup/restore migration:<br>
<br>
<a moz-do-not-send="true"
href="https://bugzilla.redhat.com/1318580"
rel="noreferrer"
target="_blank">https://bugzilla.redhat.com/1318580</a>...
<br>
Best,<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Best regards and thank you for the answer.<br>
Christoph<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@ovirt.org"
target="_blank">Users(a)ovirt.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users"
rel="noreferrer"
target="_blank">http://lists.ovirt.org/mailman/listinfo/user...
</blockquote>
<br>
<br>
</blockquote>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@ovirt.org"
target="_blank">Users(a)ovirt.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users"
rel="noreferrer"
target="_blank">http://lists.ovirt.org/mailman/listinfo/user...
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>
--------------AB5682F750EE9BC31ED74D89--
5:11 a.m.
Il 04/Lug/2016 09:12, "Yaniv Dary" <ydary(a)redhat.com> ha scritto:
Yes, this is correct.
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: ydary(a)redhat.com
IRC : ydary
On Jul 4, 2016 08:15, <ovirt(a)timmi.org> wrote:
>
> Hi,
>
> in my setup I have two servers on CentOS7. One of these servers is also
running the engine.
>
> From your email I understood that in such case there is not special
procedure
for me right?
>
> Best regards
>
> Christoph
>
Is it the same in case of single host with CentOS 7 and hosted engine?
Any caveat in this scenario?
5:25 a.m.
Hi,
I am also interested to upgrade my system from centos 7 ovirt 3.6.7 to
ovirt4, are there any preferable order to upgrade? Host then engine? or
engine then host?
thanks,
Arman.
***********************************************************
Dr. Arman Khalatyan eScience -SuperComputing
Leibniz-Institut für Astrophysik Potsdam (AIP)
An der Sternwarte 16, 14482 Potsdam, Germany
***********************************************************
On Mon, Jul 4, 2016 at 11:11 AM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
Il 04/Lug/2016 09:12, "Yaniv Dary" <ydary(a)redhat.com> ha scritto:
>
> Yes, this is correct.
>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306
> 8272306
> Email: ydary(a)redhat.com
> IRC : ydary
>
>
> On Jul 4, 2016 08:15, <ovirt(a)timmi.org> wrote:
>>
>> Hi,
>>
>> in my setup I have two servers on CentOS7. One of these servers is
also running the engine.
>>
>> From your email I understood that in such case there is not special
procedure for me right?
>>
>> Best regards
>>
>> Christoph
>>
Is it the same in case of single host with CentOS 7 and hosted engine?
Any caveat in this scenario?
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
6:59 a.m.
This is a multi-part message in MIME format.
--------------030201010904060806030005
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
alse I am interested.
Nicola
Il 04/07/2016 11:25, Arman Khalatyan ha scritto:
Hi,
I am also interested to upgrade my system from centos 7 ovirt 3.6.7 to
ovirt4, are there any preferable order to upgrade? Host then engine?
or engine then host?
thanks,
Arman.
***********************************************************
Dr. Arman Khalatyan eScience -SuperComputing
Leibniz-Institut für Astrophysik Potsdam (AIP)
An der Sternwarte 16, 14482 Potsdam, Germany
***********************************************************
On Mon, Jul 4, 2016 at 11:11 AM, Gianluca Cecchi
<gianluca.cecchi(a)gmail.com <mailto:gianluca.cecchi@gmail.com>> wrote:
Il 04/Lug/2016 09:12, "Yaniv Dary" <ydary(a)redhat.com
<mailto:ydary@redhat.com>> ha scritto:
>
> Yes, this is correct.
>
> Yaniv Dary
> Technical Product Manager
> Red Hat Israel Ltd.
> 34 Jerusalem Road
> Building A, 4th floor
> Ra'anana, Israel 4350109
>
> Tel : +972 (9) 7692306 <tel:%2B972%20%289%29%207692306>
> 8272306
> Email: ydary(a)redhat.com <mailto:ydary@redhat.com>
> IRC : ydary
>
>
> On Jul 4, 2016 08:15, <ovirt(a)timmi.org <mailto:ovirt@timmi.org>>
wrote:
>>
>> Hi,
>>
>> in my setup I have two servers on CentOS7. One of these servers
is also running the engine.
>>
>> From your email I understood that in such case there is not
special procedure for me right?
>>
>> Best regards
>>
>> Christoph
>>
Is it the same in case of single host with CentOS 7 and hosted engine?
Any caveat in this scenario?
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--------------030201010904060806030005
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">alse I am interested.<br>
<br>
Nicola<br>
<br>
Il 04/07/2016 11:25, Arman Khalatyan ha scritto:<br>
</div>
<blockquote
cite="mid:CAAqDm6bJTxFbcC3j1Bw2UHy3=kr7vj5qwRPD+oLRop5cMXQ3hQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>Hi,<br>
</div>
I am also interested to upgrade my system from centos 7
ovirt 3.6.7 to ovirt4, are there any preferable order to
upgrade? Host then engine? or engine then host?<br>
</div>
thanks,<br>
</div>
Arman.<br>
<br>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature"
data-smartmail="gmail_signature">***********************************************************<br>
<br>
Dr. Arman Khalatyan eScience -SuperComputing <br>
Leibniz-Institut für Astrophysik Potsdam (AIP) <br>
An der Sternwarte 16, 14482 Potsdam, Germany <br>
<br>
***********************************************************</div>
</div>
<br>
<div class="gmail_quote">On Mon, Jul 4, 2016 at 11:11 AM,
Gianluca Cecchi <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:gianluca.cecchi@gmail.com"
target="_blank">gianluca.cecchi(a)gmail.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">
<p dir="ltr"><br>
Il 04/Lug/2016 09:12, "Yaniv Dary" <<a
moz-do-not-send="true"
href="mailto:ydary@redhat.com"
target="_blank"><a
class="moz-txt-link-abbreviated"
href="mailto:ydary@redhat.com">ydary@redhat.com</a></a>>
ha scritto:<br>
><br>
> Yes, this is correct.<br>
><br>
> Yaniv Dary<br>
> Technical Product Manager<br>
> Red Hat Israel Ltd.<br>
> 34 Jerusalem Road<br>
> Building A, 4th floor<br>
> Ra'anana, Israel 4350109<br>
><br>
> Tel : <a moz-do-not-send="true"
href="tel:%2B972%20%289%29%207692306"
value="+97297692306" target="_blank">+972 (9)
7692306</a><br>
> 8272306<br>
> Email: <a moz-do-not-send="true"
href="mailto:ydary@redhat.com"
target="_blank">ydary(a)redhat.com</a><br>
> IRC : ydary<br>
><br>
><br>
> On Jul 4, 2016 08:15, <<a
moz-do-not-send="true"
href="mailto:ovirt@timmi.org"
target="_blank">ovirt(a)timmi.org</a>&gt;
wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> in my setup I have two servers on CentOS7. One
of these servers is also running the engine.<br>
>><br>
>> From your email I understood that in such case
there is not special procedure for me right?<br>
>><br>
>> Best regards<br>
>><br>
>> Christoph<br>
>></p>
</span>
<p dir="ltr">Is it the same in case of single host with
CentOS 7 and hosted engine?<br>
Any caveat in this scenario? </p>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users"
rel="noreferrer"
target="_blank">http://lists.ovirt.org/mailman/listinfo/user...
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</pre>
</blockquote>
<br>
</body>
</html>
--------------030201010904060806030005--
7:56 a.m.
about a n hour ago I just tested to setup ovirt 3.6, then upgrade it, 2
nodes: host and ovirt on separated machines.
very smoothly upgraded, first engine upgrade then host upgrade.
The only trouble on hosts is that some pacages are still reffering to
ovirt-3.6 repository even ovirt-4.0 is there.
it is simple to fix: yum list installed| grep ovirt-3.6 then removing all
possible packages
next reinstall host from GUI.
Thats it.
***********************************************************
Dr. Arman Khalatyan eScience -SuperComputing
Leibniz-Institut für Astrophysik Potsdam (AIP)
An der Sternwarte 16, 14482 Potsdam, Germany
***********************************************************
On Mon, Jul 4, 2016 at 12:59 PM, nicola.gentile.to <
nicola.gentile.to(a)gmail.com> wrote:
alse I am interested.
Nicola
Il 04/07/2016 11:25, Arman Khalatyan ha scritto:
Hi,
I am also interested to upgrade my system from centos 7 ovirt 3.6.7 to
ovirt4, are there any preferable order to upgrade? Host then engine? or
engine then host?
thanks,
Arman.
***********************************************************
Dr. Arman Khalatyan eScience -SuperComputing
Leibniz-Institut für Astrophysik Potsdam (AIP)
An der Sternwarte 16, 14482 Potsdam, Germany
***********************************************************
On Mon, Jul 4, 2016 at 11:11 AM, Gianluca Cecchi <
gianluca.cecchi(a)gmail.com> wrote:
>
> Il 04/Lug/2016 09:12, "Yaniv Dary" <
<ydary@redhat.com>ydary(a)redhat.com>
> ha scritto:
> >
> > Yes, this is correct.
> >
> > Yaniv Dary
> > Technical Product Manager
> > Red Hat Israel Ltd.
> > 34 Jerusalem Road
> > Building A, 4th floor
> > Ra'anana, Israel 4350109
> >
> > Tel : +972 (9) 7692306
> > 8272306
> > Email: ydary(a)redhat.com
> > IRC : ydary
> >
> >
> > On Jul 4, 2016 08:15, <ovirt(a)timmi.org> wrote:
> >>
> >> Hi,
> >>
> >> in my setup I have two servers on CentOS7. One of these servers is
> also running the engine.
> >>
> >> From your email I understood that in such case there is not special
> procedure for me right?
> >>
> >> Best regards
> >>
> >> Christoph
> >>
>
> Is it the same in case of single host with CentOS 7 and hosted engine?
> Any caveat in this scenario?
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
_______________________________________________
Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
4:25 a.m.
On Mon, Jul 4, 2016 at 1:56 PM, Arman Khalatyan <arm2arm(a)gmail.com> wrote:
about a n hour ago I just tested to setup ovirt 3.6, then upgrade it,
2
nodes: host and ovirt on separated machines.
very smoothly upgraded, first engine upgrade then host upgrade.
The only trouble on hosts is that some pacages are still reffering to
ovirt-3.6 repository even ovirt-4.0 is there.
it is simple to fix: yum list installed| grep ovirt-3.6 then removing all
possible packages
next reinstall host from GUI.
Thats it.
For the repo part I posted a question for clarification:
http://lists.ovirt.org/pipermail/users/2016-July/040910.html
see there for follow ups
In my case for single host environment with both host and hosted engine
(deployed as appliance) on CentOS 7.2 and storage domains on NFS served by
the host itself, this is the flow I followed to bring a 3.6.5 environment
to 4.0.
Problem still here is inability to upgrade the only existing cluster to 4.0
and then the datacenter to 4.0
Currently not possible due to :
https://bugzilla.redhat.com/show_bug.cgi?id=1351533
To update I kept valid what explained in the thread started here:
http://lists.ovirt.org/pipermail/users/2016-June/040649.html
yum update doesn't propose ovirt 4.0 packages
So I installed ovirt 4.0 repo (as in clean install description) and
disabled 3.6 ones.
yum update "ovirt-engine-setup*"
gives
Dependencies Resolved
===============================================================================================================
Package Arch Version
Repository Size
===============================================================================================================
Updating:
ovirt-engine-setup noarch
4.0.0.6-1.el7.centos ovirt-4.0 8.6 k
ovirt-engine-setup-base noarch
4.0.0.6-1.el7.centos ovirt-4.0 95 k
ovirt-engine-setup-plugin-ovirt-engine noarch
4.0.0.6-1.el7.centos ovirt-4.0 161 k
ovirt-engine-setup-plugin-ovirt-engine-common noarch
4.0.0.6-1.el7.centos ovirt-4.0 80 k
ovirt-engine-setup-plugin-vmconsole-proxy-helper noarch
4.0.0.6-1.el7.centos ovirt-4.0 27 k
ovirt-engine-setup-plugin-websocket-proxy noarch
4.0.0.6-1.el7.centos ovirt-4.0 26 k
Installing for dependencies:
antlr-tool noarch 2.7.7-30.el7
base 357 k
apache-commons-collections noarch 3.2.1-22.el7_2
updates 509 k
bea-stax noarch 1.2.0-9.el7
base 176 k
dom4j noarch 1.6.1-20.el7
base 277 k
hsqldb noarch
1:1.8.1.3-13.el7 base 950 k
isorelax noarch
1:0-0.15.release20050331.el7 base 75 k
jaxen noarch 1.1.3-11.el7
base 204 k
jdom noarch 1.1.3-6.el7
base 174 k
msv-msv noarch
1:2013.5.1-6.el7 base 3.7 M
msv-xsdlib noarch
1:2013.5.1-6.el7 base 1.1 M
ovirt-engine-dwh noarch
4.0.0-2.git38f5db5.el7.centos ovirt-4.0 2.1 M
ovirt-engine-dwh-setup noarch
4.0.0-2.git38f5db5.el7.centos ovirt-4.0 69 k
postgresql-jdbc noarch 9.2.1002-5.el7
base 447 k
relaxngDatatype noarch 1.0-11.el7
base 15 k
ws-jaxme noarch 0.5.2-10.el7
base 1.1 M
xpp3 noarch 1.1.3.8-11.el7
base 336 k
Updating for dependencies:
otopi noarch
1.5.0-1.el7.centos ovirt-4.0 160 k
otopi-java noarch
1.5.0-1.el7.centos ovirt-4.0 25 k
ovirt-engine-lib noarch
4.0.0.6-1.el7.centos ovirt-4.0 28 k
Transaction Summary
===============================================================================================================
Install ( 16 Dependent packages)
Upgrade 6 Packages (+ 3 Dependent packages)
engine-setup brings in the DWH database that I didn't have in 3.6 and now
seems to be required (probably for dashboard?).
[root@ractorshe ~]# engine-setup
...
--== DATABASE CONFIGURATION ==--
Where is the DWH database located? (Local, Remote) [Local]:
Setup can configure the local postgresql server automatically for
the DWH to run. This may conflict with existing applications.
Would you like Setup to automatically configure postgresql and
create DWH database, or prefer to perform that manually? (Automatic,
Manual) [Automatic]:
...
DWH database secured connection : False
DWH database host : localhost
DWH database user name : ovirt_engine_history
DWH database name : ovirt_engine_history
DWH database port : 5432
DWH database host name validation : False
...
DWH installation : True
Configure local DWH database : True
...
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ INFO ] Execution of setup completed successfully
[root@ractorshe ~]#
try connect admin portal --> ok (btw: no problems with certificates)
try user portal --> ok
shutdown engine vm --> ok
exit global maintenance --> ok engine vm starts automatically and I'm able
to connect to portals
again global maintenance, then
on engine vm
yum update
Dependencies Resolved
===============================================================================================================
Package Arch Version
Repository Size
===============================================================================================================
Installing:
kernel x86_64 3.10.0-327.22.2.el7
updates 33 M
python2-paramiko noarch 1.16.1-1.el7
epel 257 k
replacing python-paramiko.noarch 1.15.1-1.el7
Updating:
NetworkManager x86_64 1:1.0.6-30.el7_2
updates 2.0 M
NetworkManager-glib x86_64 1:1.0.6-30.el7_2
updates 385 k
NetworkManager-libnm x86_64 1:1.0.6-30.el7_2
updates 498 k
NetworkManager-team x86_64 1:1.0.6-30.el7_2
updates 132 k
NetworkManager-tui x86_64 1:1.0.6-30.el7_2
updates 212 k
chkconfig x86_64 1.3.61-5.el7_2.1
updates 173 k
device-mapper x86_64 7:1.02.107-5.el7_2.5
updates 252 k
device-mapper-event x86_64 7:1.02.107-5.el7_2.5
updates 167 k
device-mapper-event-libs x86_64 7:1.02.107-5.el7_2.5
updates 169 k
device-mapper-libs x86_64 7:1.02.107-5.el7_2.5
updates 305 k
device-mapper-multipath x86_64 0.4.9-85.el7_2.5
updates 119 k
device-mapper-multipath-libs x86_64 0.4.9-85.el7_2.5
updates 222 k
dracut x86_64 033-360.el7_2.1
updates 311 k
dracut-config-rescue x86_64 033-360.el7_2.1
updates 50 k
dracut-network x86_64 033-360.el7_2.1
updates 90 k
epel-release noarch 7-7
epel 14 k
firefox x86_64 45.2.0-1.el7.centos
updates 76 M
glibc x86_64 2.17-106.el7_2.6
updates 3.6 M
glibc-common x86_64 2.17-106.el7_2.6
updates 11 M
httpd x86_64 2.4.6-40.el7.centos.1
updates 2.7 M
httpd-tools x86_64 2.4.6-40.el7.centos.1
updates 82 k
iscsi-initiator-utils x86_64 6.2.0.873-33.el7_2.1
updates 418 k
iscsi-initiator-utils-iscsiuio x86_64 6.2.0.873-33.el7_2.1
updates 82 k
java-1.8.0-openjdk x86_64 1:1.8.0.91-1.b14.el7_2
updates 219 k
java-1.8.0-openjdk-headless x86_64 1:1.8.0.91-1.b14.el7_2
updates 31 M
kernel-tools x86_64 3.10.0-327.22.2.el7
updates 2.4 M
kernel-tools-libs x86_64 3.10.0-327.22.2.el7
updates 2.3 M
kpartx x86_64 0.4.9-85.el7_2.5
updates 60 k
libgudev1 x86_64 219-19.el7_2.11
updates 66 k
libndp x86_64 1.2-6.el7_2
updates 31 k
libtevent x86_64 0.9.26-1.el7_2.1
updates 33 k
libxml2 x86_64 2.9.1-6.el7_2.3
updates 668 k
libxml2-python x86_64 2.9.1-6.el7_2.3
updates 247 k
lvm2 x86_64 7:2.02.130-5.el7_2.5
updates 1.0 M
lvm2-libs x86_64 7:2.02.130-5.el7_2.5
updates 873 k
mod_ssl x86_64 1:2.4.6-40.el7.centos.1
updates 103 k
nfs-utils x86_64 1:1.3.0-0.21.el7_2.1
updates 371 k
ntpdate x86_64 4.2.6p5-22.el7.centos.2
updates 84 k
openssl x86_64 1:1.0.1e-51.el7_2.5
updates 712 k
openssl-libs x86_64 1:1.0.1e-51.el7_2.5
updates 952 k
ovirt-engine-sdk-python noarch 3.6.7.0-1.el7.centos
ovirt-4.0 480 k
ovirt-engine-webadmin-portal-debuginfo noarch 4.0.0.6-1.el7.centos
ovirt-4.0 39 M
ovirt-log-collector noarch 4.0.0-1.el7.centos
ovirt-4.0 49 k
ovirt-setup-lib noarch 1.0.2-1.el7.centos
ovirt-4.0 18 k
pcre x86_64 8.32-15.el7_2.1
updates 420 k
polkit x86_64 0.112-7.el7_2
updates 166 k
python-perf x86_64 3.10.0-327.22.2.el7
updates 2.4 M
python-websockify noarch 0.8.0-1.el7
centos-ovirt40-candidate 68 k
python2-boto noarch 2.40.0-1.el7
epel 1.7 M
rpcbind x86_64 0.2.0-33.el7_2.1
updates 58 k
selinux-policy noarch 3.13.1-60.el7_2.7
updates 376 k
selinux-policy-targeted noarch 3.13.1-60.el7_2.7
updates 3.9 M
systemd x86_64 219-19.el7_2.11
updates 5.1 M
systemd-libs x86_64 219-19.el7_2.11
updates 358 k
systemd-sysv x86_64 219-19.el7_2.11
updates 53 k
tzdata noarch 2016e-1.el7
updates 442 k
tzdata-java noarch 2016e-1.el7
updates 180 k
Transaction Summary
===============================================================================================================
Install 2 Packages
Upgrade 57 Packages
Total download size: 229 M
shutdown engine vm
exit global maintenance --> all ok
shutdown all vms but hosted engine
on host, to update it to 4.0 and then at reboot let starts all components,
I executed:
systemctl stop ovirt-ha-agent
systemctl stop ovirt-ha-broker
shutdown engine vm
on host again:
systemctl stop vdsmd
systemctl stop sanlock
systemctl stop wdmd
in messages
Jul 4 17:05:47 ractor wdmd[1258]: test failed rem 26 now 804 ping 760
close 770 renewal 697 expire 777 client 1285
sanlock_2025c2ea-6205-4bc1-b29d-745b47f8f806:1
Jul 4 17:05:48 ractor wdmd[1258]: test failed rem 25 now 805 ping 760
close 770 renewal 697 expire 777 client 1285
sanlock_2025c2ea-6205-4bc1-b29d-745b47f8f806:1
Jul 4 17:05:49 ractor wdmd[1258]: test failed rem 24 now 806 ping 760
close 770 renewal 697 expire 777 client 1285
sanlock_2025c2ea-6205-4bc1-b29d-745b47f8f806:1
Jul 4 17:05:50 ractor wdmd[1258]: test failed rem 23 now 807 ping 760
close 770 renewal 697 expire 777 client 1285
sanlock_2025c2ea-6205-4bc1-b29d-745b47f8f806:1
Jul 4 17:05:51 ractor wdmd[1258]: test failed rem 22 now 808 ping 760
close 770 renewal 697 expire 777 client 1285
sanlock_2025c2ea-6205-4bc1-b29d-745b47f8f806:1
Jul 4 17:05:51 ractor systemd[1]: wdmd.service stop-sigterm timed out.
Killing.
Jul 4 17:05:51 ractor systemd[1]: wdmd.service: main process exited,
code=killed, status=9/KILL
Jul 4 17:05:51 ractor systemd[1]: Stopped Watchdog Multiplexing Daemon.
Jul 4 17:05:51 ractor systemd[1]: Unit wdmd.service entered failed state.
Jul 4 17:05:51 ractor systemd[1]: wdmd.service failed.
PROBLEM: automatic reboot of node....
I asked for clarification here:
http://lists.ovirt.org/pipermail/users/2016-July/040912.html
In the mean time I manually let start the host in single user mode enabling
then only rsyslog, networking and ssh and
yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm
disable ovirt-3.6 repos
yum update --exclude=ovirt-hosted-engine-setup,ovirt-engine-appliance
(otherwise getting error on dependencies)
Dependencies Resolved
===============================================================================================================
Package Arch Version
Repository Size
===============================================================================================================
Installing:
kernel x86_64 3.10.0-327.22.2.el7
updates 33 M
python2-ecdsa noarch 0.13-4.el7
ovirt-4.0-epel 83 k
replacing python-ecdsa.noarch 0.11-3.el7.centos
Updating:
NetworkManager x86_64 1:1.0.6-30.el7_2
updates 2.0 M
NetworkManager-libnm x86_64 1:1.0.6-30.el7_2
updates 498 k
NetworkManager-team x86_64 1:1.0.6-30.el7_2
updates 132 k
NetworkManager-tui x86_64 1:1.0.6-30.el7_2
updates 212 k
chkconfig x86_64 1.3.61-5.el7_2.1
updates 173 k
device-mapper x86_64 7:1.02.107-5.el7_2.5
updates 252 k
device-mapper-event x86_64 7:1.02.107-5.el7_2.5
updates 167 k
device-mapper-event-libs x86_64 7:1.02.107-5.el7_2.5
updates 169 k
device-mapper-libs x86_64 7:1.02.107-5.el7_2.5
updates 305 k
device-mapper-multipath x86_64 0.4.9-85.el7_2.5
updates 119 k
device-mapper-multipath-libs x86_64 0.4.9-85.el7_2.5
updates 222 k
dracut x86_64 033-360.el7_2.1
updates 311 k
dracut-config-rescue x86_64 033-360.el7_2.1
updates 50 k
dracut-network x86_64 033-360.el7_2.1
updates 90 k
firefox x86_64 45.2.0-1.el7.centos
updates 76 M
glibc x86_64 2.17-106.el7_2.6
updates 3.6 M
glibc-common x86_64 2.17-106.el7_2.6
updates 11 M
glusterfs x86_64 3.7.12-2.el7
ovirt-4.0-centos-gluster37 482 k
glusterfs-api x86_64 3.7.12-2.el7
ovirt-4.0-centos-gluster37 85 k
glusterfs-cli x86_64 3.7.12-2.el7
ovirt-4.0-centos-gluster37 179 k
glusterfs-client-xlators x86_64 3.7.12-2.el7
ovirt-4.0-centos-gluster37 857 k
glusterfs-fuse x86_64 3.7.12-2.el7
ovirt-4.0-centos-gluster37 130 k
glusterfs-libs x86_64 3.7.12-2.el7
ovirt-4.0-centos-gluster37 352 k
ioprocess x86_64 0.16.1-1.el7
ovirt-4.0 28 k
iscsi-initiator-utils x86_64 6.2.0.873-33.el7_2.1
updates 418 k
iscsi-initiator-utils-iscsiuio x86_64 6.2.0.873-33.el7_2.1
updates 82 k
kernel-tools x86_64 3.10.0-327.22.2.el7
updates 2.4 M
kernel-tools-libs x86_64 3.10.0-327.22.2.el7
updates 2.3 M
kpartx x86_64 0.4.9-85.el7_2.5
updates 60 k
libgudev1 x86_64 219-19.el7_2.11
updates 66 k
libguestfs x86_64 1:1.28.1-1.55.el7.centos.4
updates 1.7 M
libguestfs-tools-c x86_64 1:1.28.1-1.55.el7.centos.4
updates 2.2 M
libndp x86_64 1.2-6.el7_2
updates 31 k
libsss_idmap x86_64 1.13.0-40.el7_2.9
updates 103 k
libsss_nss_idmap x86_64 1.13.0-40.el7_2.9
updates 103 k
libtevent x86_64 0.9.26-1.el7_2.1
updates 33 k
libvirt-client x86_64 1.2.17-13.el7_2.5
updates 4.3 M
libvirt-daemon x86_64 1.2.17-13.el7_2.5
updates 585 k
libvirt-daemon-config-nwfilter x86_64 1.2.17-13.el7_2.5
updates 122 k
libvirt-daemon-driver-interface x86_64 1.2.17-13.el7_2.5
updates 162 k
libvirt-daemon-driver-network x86_64 1.2.17-13.el7_2.5
updates 302 k
libvirt-daemon-driver-nodedev x86_64 1.2.17-13.el7_2.5
updates 161 k
libvirt-daemon-driver-nwfilter x86_64 1.2.17-13.el7_2.5
updates 185 k
libvirt-daemon-driver-qemu x86_64 1.2.17-13.el7_2.5
updates 571 k
libvirt-daemon-driver-secret x86_64 1.2.17-13.el7_2.5
updates 155 k
libvirt-daemon-driver-storage x86_64 1.2.17-13.el7_2.5
updates 328 k
libvirt-daemon-kvm x86_64 1.2.17-13.el7_2.5
updates 118 k
libvirt-lock-sanlock x86_64 1.2.17-13.el7_2.5
updates 167 k
libxml2 x86_64 2.9.1-6.el7_2.3
updates 668 k
libxml2-python x86_64 2.9.1-6.el7_2.3
updates 247 k
lvm2 x86_64 7:2.02.130-5.el7_2.5
updates 1.0 M
lvm2-libs x86_64 7:2.02.130-5.el7_2.5
updates 873 k
mom noarch 0.5.4-1.el7.centos
ovirt-4.0 119 k
net-snmp-libs x86_64 1:5.7.2-24.el7_2.1
updates 747 k
net-snmp-utils x86_64 1:5.7.2-24.el7_2.1
updates 197 k
nfs-utils x86_64 1:1.3.0-0.21.el7_2.1
updates 371 k
ntp x86_64 4.2.6p5-22.el7.centos.2
updates 544 k
ntpdate x86_64 4.2.6p5-22.el7.centos.2
updates 84 k
ntsysv x86_64 1.3.61-5.el7_2.1
updates 36 k
openssl x86_64 1:1.0.1e-51.el7_2.5
updates 712 k
openssl-libs x86_64 1:1.0.1e-51.el7_2.5
updates 952 k
otopi noarch 1.5.0-1.el7.centos
ovirt-4.0 160 k
ovirt-engine-sdk-python noarch 3.6.7.0-1.el7.centos
ovirt-4.0 480 k
ovirt-host-deploy noarch 1.5.0-1.el7.centos
ovirt-4.0 99 k
ovirt-hosted-engine-ha noarch 2.0.0-1.el7.centos
ovirt-4.0 296 k
ovirt-setup-lib noarch 1.0.2-1.el7.centos
ovirt-4.0 18 k
ovirt-vmconsole noarch 1.0.3-1.el7.centos
ovirt-4.0 29 k
ovirt-vmconsole-host noarch 1.0.3-1.el7.centos
ovirt-4.0 16 k
pcre x86_64 8.32-15.el7_2.1
updates 420 k
polkit x86_64 0.112-7.el7_2
updates 166 k
python-ioprocess noarch 0.16.1-1.el7
ovirt-4.0 25 k
python-perf x86_64 3.10.0-327.22.2.el7
updates 2.4 M
rpcbind x86_64 0.2.0-33.el7_2.1
updates 58 k
selinux-policy noarch 3.13.1-60.el7_2.7
updates 376 k
selinux-policy-targeted noarch 3.13.1-60.el7_2.7
updates 3.9 M
spice-server x86_64 0.12.4-15.el7_2.1
updates 381 k
sssd-client x86_64 1.13.0-40.el7_2.9
updates 158 k
systemd x86_64 219-19.el7_2.11
updates 5.1 M
systemd-libs x86_64 219-19.el7_2.11
updates 358 k
systemd-python x86_64 219-19.el7_2.11
updates 99 k
systemd-sysv x86_64 219-19.el7_2.11
updates 53 k
tzdata noarch 2016e-1.el7
updates 442 k
vdsm x86_64 4.18.4.1-0.el7.centos
ovirt-4.0 685 k
vdsm-cli noarch 4.18.4.1-0.el7.centos
ovirt-4.0 67 k
vdsm-hook-vmfex-dev noarch 4.18.4.1-0.el7.centos
ovirt-4.0 6.5 k
vdsm-infra noarch 4.18.4.1-0.el7.centos
ovirt-4.0 12 k
vdsm-jsonrpc noarch 4.18.4.1-0.el7.centos
ovirt-4.0 25 k
vdsm-python noarch 4.18.4.1-0.el7.centos
ovirt-4.0 565 k
vdsm-xmlrpc noarch 4.18.4.1-0.el7.centos
ovirt-4.0 24 k
vdsm-yajsonrpc noarch 4.18.4.1-0.el7.centos
ovirt-4.0 27 k
virt-v2v x86_64 1:1.28.1-1.55.el7.centos.4
updates 12 M
Installing for dependencies:
NetworkManager-config-server x86_64 1:1.0.6-30.el7_2
updates 122 k
PyYAML x86_64 3.10-11.el7
base 153 k
libyaml x86_64 0.1.4-11.el7_0
base 55 k
openvswitch x86_64 2.5.0-2.el7
centos-ovirt40-candidate 2.3 M
ovirt-imageio-common noarch
0.3.0-0.201606191345.git9f3d6d4.el7.centos
ovirt-4.0 22 k
ovirt-imageio-daemon noarch
0.3.0-0.201606191345.git9f3d6d4.el7.centos
ovirt-4.0 22 k
python-webob noarch 1.2.3-6.el7
base 202 k
vdsm-api noarch 4.18.4.1-0.el7.centos
ovirt-4.0 52 k
Transaction Summary
===============================================================================================================
Install 2 Packages (+8 Dependent packages)
Upgrade 91 Packages
Total download size: 185 M
Is this ok [y/d/N]:
Then I put in place vdsm.conf.rpmnew changing inside it
[addresses]
management_ip = 0.0.0.0
This is necessary because I have disabled ipv6 at system os level and this
setting forces vdsmd to listen on IPV4, that is not the default.
Other settings I had in 3.6 vdsm.conf (put in by initial installation) were
not explicitly inserted because they already are the default ones. they are:
ssl=true
and
management_port = 54321
reboot host
after some minutes engine vm starts ok
Wait for stabilization.
All seems up and I'm able to boot and connect to my VMs.
At the beginning the host results as needing for upgrades, but after couple
of minutes the engine detects that it is ok, from a components version
point of view.
In webadmin portal I still see the host with exclamation mark on side of it
because of course I've not configured power management in this single host
environment.
Only thing I don't understand is that I also see an icon on side of host (I
don't understand its graphic; it seems a crown, or a tower ) and when I
mouse over it I see the tooltip
Action Items
But I don't understand how should I manage it...
see image here:
https://drive.google.com/file/d/0BwoPbcrMv8mvRzZCcDA0OG9HaGs/view?usp=sha...
HIH,
Gianluca
4:30 a.m.
Two final steps I've done that are only necessary in my environment, where
the host itslef is providing the NFS service for storage domains:
After install you have to make a dependency so that VDSM Broker starts
after NFS Server
In /usr/lib/systemd/system/ovirt-ha-broker.service
Added in section [Unit] the line:
After=nfs-server.service
Also, for vdsmd service, in file vdsmd.service changed from:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service
to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service \
nfs-server.service
NOTE: the files will be overwritten by future updates, so you have to keep
in mind...
7:30 a.m.
This is a multi-part message in MIME format.
--------------C481890A6712B40D0C0D5327
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
Two final steps I've done that are only necessary in my
environment,
where the host itslef is providing the NFS service for storage domains:
After install you have to make a dependency so that VDSM Broker starts
after NFS Server
In /usr/lib/systemd/system/ovirt-ha-broker.service
Added in section [Unit] the line:
After=nfs-server.service
Also, for vdsmd service, in file vdsmd.service changed from:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service
to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service \
nfs-server.service
NOTE: the files will be overwritten by future updates, so you have to
keep in mind...
Hi,
I try to upgrade from ovirt 3.6.7 to 4.0.1.
I follow this steps:
1. Update repository for 4.0.1
2. Disable old repository 3.6.7
3. run: yum update "ovirt-engine-setup*"
now an error occured:
yum update "ovirt-engine-setup*"
Plugin abilitati:fastestmirror, langpacks, versionlock
Repository centos-ovirt36 is listed more than once in the configuration
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
* base: artfiles.org
* extras: ba.mirror.garr.it
* ovirt-4.0: ftp.nluug.nl
* ovirt-4.0-epel: epel.besthosting.ua
* updates: ba.mirror.garr.it
Risoluzione dipendenze
--> Esecuzione del controllo di transazione
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato
per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos
settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos
settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos
per il pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
--> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il
pacchetto:
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il
pacchetto: otopi-java-1.4.2-1.el7.centos.noarch
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos
settato per essere aggiornato
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos
settato per essere un aggiornamento
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato
per essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere
un aggiornamento
--> Analisi conflitto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch va in conflitto con
ovirt-engine-reports-setup < 4.0.0
--> Risoluzione delle dipendenze completata
Errore: ovirt-engine-setup-base conflicts with
ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
Si può provare ad usare --skip-broken per aggirare il problema
** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check' è:
bash-4.2.46-20.el7_2.x86_64 è un duplicato di bash-4.2.46-19.el7.x86_64
1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di 1:dbus-1.6.12-13.el7.x86_64
1:dbus-libs-1.6.12-14.el7_2.x86_64 è un duplicato di
1:dbus-libs-1.6.12-13.el7.x86_64
glibc-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-2.17-106.el7_2.6.x86_64
glibc-common-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-common-2.17-106.el7_2.6.x86_64
glibc-headers-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-headers-2.17-106.el7_2.6.x86_64
gssproxy-0.4.1-8.el7_2.x86_64 è un duplicato di gssproxy-0.4.1-7.el7.x86_64
1:java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato di
1:java-1.7.0-openjdk-1.7.0.101-2.6.6.1.el7_2.x86_64
1:java-1.7.0-openjdk-headless-1.7.0.111-2.6.7.2.el7_2.x86_64 è un
duplicato di 1:java-1.7.0-openjdk-headless-1.7.0.101-2.6.6.1.el7_2.x86_64
libblkid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libblkid-2.23.2-26.el7_2.2.x86_64
libmount-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libmount-2.23.2-26.el7_2.2.x86_64
libsss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_idmap-1.13.0-40.el7_2.9.x86_64
libsss_nss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_nss_idmap-1.13.0-40.el7_2.9.x86_64
libuuid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libuuid-2.23.2-26.el7_2.2.x86_64
2:microcode_ctl-2.1-12.el7_2.1.x86_64 è un duplicato di
2:microcode_ctl-2.1-12.el7.x86_64
systemd-219-19.el7_2.12.x86_64 è un duplicato di
systemd-219-19.el7_2.11.x86_64
systemd-libs-219-19.el7_2.12.x86_64 è un duplicato di
systemd-libs-219-19.el7_2.11.x86_64
systemd-sysv-219-19.el7_2.12.x86_64 è un duplicato di
systemd-sysv-219-19.el7_2.11.x86_64
util-linux-2.23.2-26.el7_2.3.x86_64 è un duplicato di
util-linux-2.23.2-26.el7_2.2.x86_64
What can I do to solve the problem?
Regards
Nicola
--------------C481890A6712B40D0C0D5327
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Il 05/07/2016 10:30, Gianluca Cecchi ha
scritto:<br>
</div>
<blockquote
cite="mid:CAG2kNCw=ZZZL7yGMJ86v1Nqig2E41wdhsZmKaaTFdsUXxyMHRA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="font-size:12.8px">Two final steps I've done that
are
only necessary in my environment, where the host itslef is
providing the NFS service for storage domains:</div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">After install you have to make a
dependency so that VDSM Broker starts after NFS Server</div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">In
/usr/lib/systemd/system/ovirt-ha-broker.<span
class="">service</span></div>
<div style="font-size:12.8px">
<div><br>
</div>
<div>Added in section [Unit] the line:</div>
<div><br>
</div>
<div>After=nfs-server.<span
class="">service</span></div>
</div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">Also, for vdsmd service, in
file <span
class="">vdsmd</span>.<span
class="">service</span> changed
from:<br>
</div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">
<div>After=multipathd.<span
class="">service</span> libvirtd.<span
class="">service</span> iscsid.<span
class="">service</span> rpcbind.<span
class="">service</span> \</div>
<div> supervdsmd.<span
class="">service</span> sanlock.<span
class="">service</span> vdsm-network.<span
class="">service</span> </div>
<div><br>
</div>
<div>to:</div>
<div>After=multipathd.<span
class="">service</span> libvirtd.<span
class="">service</span> iscsid.<span
class="">service</span> rpcbind.<span
class="">service</span> \</div>
<div> supervdsmd.<span
class="">service</span> sanlock.<span
class="">service</span> vdsm-network.<span
class="">service</span> \</div>
<div> nfs-server.<span
class="">service</span></div>
</div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">NOTE: the files will be
overwritten by future updates, so you have to keep in mind...<br>
</div>
<div><br>
</div>
</div>
</blockquote>
<p>Hi, <br>
</p>
<p>I try to upgrade from ovirt 3.6.7 to 4.0.1.</p>
<p>I follow this steps:</p>
<p>1. Update repository for 4.0.1</p>
<p>2. Disable old repository 3.6.7</p>
<p>3. run: yum update "ovirt-engine-setup*"</p>
<p>now an error occured:</p>
<p>yum update "ovirt-engine-setup*"<br>
Plugin abilitati:fastestmirror, langpacks, versionlock<br>
Repository centos-ovirt36 is listed more than once in the
configuration<br>
Repository virtio-win-stable is listed more than once in the
configuration<br>
Loading mirror speeds from cached hostfile<br>
* base: artfiles.org<br>
* extras: ba.mirror.garr.it<br>
* ovirt-4.0: <a class="moz-txt-link-abbreviated"
href="ftp://ftp.nluug.nl">ftp.nluug.nl</a><br>
* ovirt-4.0-epel: epel.besthosting.ua<br>
* updates: ba.mirror.garr.it<br>
Risoluzione dipendenze<br>
--> Esecuzione del controllo di transazione<br>
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos
settato per essere aggiornato<br>
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos
settato per essere un aggiornamento<br>
---> Pacchetto ovirt-engine-setup-base.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato<br>
---> Pacchetto ovirt-engine-setup-base.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento<br>
--> Elaborazione dipendenza: ovirt-engine-lib >=
4.0.1.1-1.el7.centos per il pacchetto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch<br>
--> Elaborazione dipendenza: otopi >= 1.5.0 per il
pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch<br>
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato<br>
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento<br>
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0
per il pacchetto:
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch<br>
---> Pacchetto
ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato<br>
---> Pacchetto
ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento<br>
---> Pacchetto
ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato<br>
---> Pacchetto
ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento<br>
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato<br>
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento<br>
--> Esecuzione del controllo di transazione<br>
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per
essere aggiornato<br>
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il
pacchetto: otopi-java-1.4.2-1.el7.centos.noarch<br>
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per
essere un aggiornamento<br>
---> Pacchetto ovirt-engine-dwh-setup.noarch
0:3.6.6-1.el7.centos settato per essere aggiornato<br>
---> Pacchetto ovirt-engine-dwh-setup.noarch
0:4.0.1-1.el7.centos settato per essere un aggiornamento<br>
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos
settato per essere aggiornato<br>
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos
settato per essere un aggiornamento<br>
--> Esecuzione del controllo di transazione<br>
---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato
per essere aggiornato<br>
---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato
per essere un aggiornamento<br>
--> Analisi conflitto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch va in
conflitto con ovirt-engine-reports-setup < 4.0.0<br>
--> Risoluzione delle dipendenze completata<br>
Errore: ovirt-engine-setup-base conflicts with
ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch<br>
Si può provare ad usare --skip-broken per aggirare il problema<br>
** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum
check' è:<br>
bash-4.2.46-20.el7_2.x86_64 è un duplicato di
bash-4.2.46-19.el7.x86_64<br>
1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di
1:dbus-1.6.12-13.el7.x86_64<br>
1:dbus-libs-1.6.12-14.el7_2.x86_64 è un duplicato di
1:dbus-libs-1.6.12-13.el7.x86_64<br>
glibc-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-2.17-106.el7_2.6.x86_64<br>
glibc-common-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-common-2.17-106.el7_2.6.x86_64<br>
glibc-headers-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-headers-2.17-106.el7_2.6.x86_64<br>
gssproxy-0.4.1-8.el7_2.x86_64 è un duplicato di
gssproxy-0.4.1-7.el7.x86_64<br>
1:java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato
di 1:java-1.7.0-openjdk-1.7.0.101-2.6.6.1.el7_2.x86_64<br>
1:java-1.7.0-openjdk-headless-1.7.0.111-2.6.7.2.el7_2.x86_64 è un
duplicato di
1:java-1.7.0-openjdk-headless-1.7.0.101-2.6.6.1.el7_2.x86_64<br>
libblkid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libblkid-2.23.2-26.el7_2.2.x86_64<br>
libmount-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libmount-2.23.2-26.el7_2.2.x86_64<br>
libsss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_idmap-1.13.0-40.el7_2.9.x86_64<br>
libsss_nss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_nss_idmap-1.13.0-40.el7_2.9.x86_64<br>
libuuid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libuuid-2.23.2-26.el7_2.2.x86_64<br>
2:microcode_ctl-2.1-12.el7_2.1.x86_64 è un duplicato di
2:microcode_ctl-2.1-12.el7.x86_64<br>
systemd-219-19.el7_2.12.x86_64 è un duplicato di
systemd-219-19.el7_2.11.x86_64<br>
systemd-libs-219-19.el7_2.12.x86_64 è un duplicato di
systemd-libs-219-19.el7_2.11.x86_64<br>
systemd-sysv-219-19.el7_2.12.x86_64 è un duplicato di
systemd-sysv-219-19.el7_2.11.x86_64<br>
util-linux-2.23.2-26.el7_2.3.x86_64 è un duplicato di
util-linux-2.23.2-26.el7_2.2.x86_64<br>
</p>
<p>What can I do to solve the problem?</p>
<p>Regards</p>
<p>Nicola<br>
</p>
</body>
</html>
--------------C481890A6712B40D0C0D5327--
7:42 a.m.
On Wed, Aug 3, 2016 at 2:30 PM, nicola.gentile.to
<nicola.gentile.to(a)gmail.com> wrote:
Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
Two final steps I've done that are only necessary in my environment, where
the host itslef is providing the NFS service for storage domains:
After install you have to make a dependency so that VDSM Broker starts after
NFS Server
In /usr/lib/systemd/system/ovirt-ha-broker.service
Added in section [Unit] the line:
After=nfs-server.service
Also, for vdsmd service, in file vdsmd.service changed from:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service
to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service \
nfs-server.service
NOTE: the files will be overwritten by future updates, so you have to keep
in mind...
Hi,
I try to upgrade from ovirt 3.6.7 to 4.0.1.
I follow this steps:
1. Update repository for 4.0.1
2. Disable old repository 3.6.7
3. run: yum update "ovirt-engine-setup*"
now an error occured:
yum update "ovirt-engine-setup*"
Plugin abilitati:fastestmirror, langpacks, versionlock
Repository centos-ovirt36 is listed more than once in the configuration
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
* base: artfiles.org
* extras: ba.mirror.garr.it
* ovirt-4.0: ftp.nluug.nl
* ovirt-4.0-epel: epel.besthosting.ua
* updates: ba.mirror.garr.it
Risoluzione dipendenze
--> Esecuzione del controllo di transazione
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per il
pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
--> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il pacchetto:
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
otopi-java-1.4.2-1.el7.centos.noarch
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
per essere un aggiornamento
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
--> Analisi conflitto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
va in conflitto con ovirt-engine-reports-setup < 4.0.0
--> Risoluzione delle dipendenze completata
Errore: ovirt-engine-setup-base conflicts with
ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
Si può provare ad usare --skip-broken per aggirare il problema
** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check' è:
bash-4.2.46-20.el7_2.x86_64 è un duplicato di bash-4.2.46-19.el7.x86_64
1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di 1:dbus-1.6.12-13.el7.x86_64
1:dbus-libs-1.6.12-14.el7_2.x86_64 è un duplicato di
1:dbus-libs-1.6.12-13.el7.x86_64
glibc-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-2.17-106.el7_2.6.x86_64
glibc-common-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-common-2.17-106.el7_2.6.x86_64
glibc-headers-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-headers-2.17-106.el7_2.6.x86_64
gssproxy-0.4.1-8.el7_2.x86_64 è un duplicato di gssproxy-0.4.1-7.el7.x86_64
1:java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato di
1:java-1.7.0-openjdk-1.7.0.101-2.6.6.1.el7_2.x86_64
1:java-1.7.0-openjdk-headless-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato
di 1:java-1.7.0-openjdk-headless-1.7.0.101-2.6.6.1.el7_2.x86_64
libblkid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libblkid-2.23.2-26.el7_2.2.x86_64
libmount-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libmount-2.23.2-26.el7_2.2.x86_64
libsss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_idmap-1.13.0-40.el7_2.9.x86_64
libsss_nss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_nss_idmap-1.13.0-40.el7_2.9.x86_64
libuuid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libuuid-2.23.2-26.el7_2.2.x86_64
2:microcode_ctl-2.1-12.el7_2.1.x86_64 è un duplicato di
2:microcode_ctl-2.1-12.el7.x86_64
systemd-219-19.el7_2.12.x86_64 è un duplicato di
systemd-219-19.el7_2.11.x86_64
systemd-libs-219-19.el7_2.12.x86_64 è un duplicato di
systemd-libs-219-19.el7_2.11.x86_64
systemd-sysv-219-19.el7_2.12.x86_64 è un duplicato di
systemd-sysv-219-19.el7_2.11.x86_64
util-linux-2.23.2-26.el7_2.3.x86_64 è un duplicato di
util-linux-2.23.2-26.el7_2.2.x86_64
What can I do to solve the problem?
Reports is not packaged nor supported in 4.0.
If you don't need it, you can try:
yum remove ovirt-engine-reports\*
If you do, you might be able to set up Reports 3.6 to
work with your 4.0 engine/dwh.
On a side note, it's recommended to remove your 3.6 repos
only after you finished upgrading to 4.0 - if you remove them
before, engine-setup will not be able to rollback in case of
a problem.
Best,
--
Didi
7:51 a.m.
This is a multi-part message in MIME format.
--------------731C0208BAD02396D2DA4474
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Il 03/08/2016 13:42, Yedidyah Bar David ha scritto:
On Wed, Aug 3, 2016 at 2:30 PM, nicola.gentile.to
<nicola.gentile.to(a)gmail.com> wrote:
> Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
>
> Two final steps I've done that are only necessary in my environment, where
> the host itslef is providing the NFS service for storage domains:
>
> After install you have to make a dependency so that VDSM Broker starts after
> NFS Server
>
> In /usr/lib/systemd/system/ovirt-ha-broker.service
>
> Added in section [Unit] the line:
>
> After=nfs-server.service
>
> Also, for vdsmd service, in file vdsmd.service changed from:
>
> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
> supervdsmd.service sanlock.service vdsm-network.service
>
> to:
> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
> supervdsmd.service sanlock.service vdsm-network.service \
> nfs-server.service
>
> NOTE: the files will be overwritten by future updates, so you have to keep
> in mind...
>
> Hi,
>
> I try to upgrade from ovirt 3.6.7 to 4.0.1.
>
> I follow this steps:
>
> 1. Update repository for 4.0.1
>
> 2. Disable old repository 3.6.7
>
> 3. run: yum update "ovirt-engine-setup*"
>
> now an error occured:
>
> yum update "ovirt-engine-setup*"
> Plugin abilitati:fastestmirror, langpacks, versionlock
> Repository centos-ovirt36 is listed more than once in the configuration
> Repository virtio-win-stable is listed more than once in the configuration
> Loading mirror speeds from cached hostfile
> * base: artfiles.org
> * extras: ba.mirror.garr.it
> * ovirt-4.0: ftp.nluug.nl
> * ovirt-4.0-epel: epel.besthosting.ua
> * updates: ba.mirror.garr.it
> Risoluzione dipendenze
> --> Esecuzione del controllo di transazione
> ---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
> essere aggiornato
> ---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
> essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
> per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
> per essere un aggiornamento
> --> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per il
> pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> --> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
> ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> --> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il pacchetto:
> ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
> --> Esecuzione del controllo di transazione
> ---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
> aggiornato
> --> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
> otopi-java-1.4.2-1.el7.centos.noarch
> ---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
> aggiornamento
> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
> per essere aggiornato
> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
> per essere un aggiornamento
> ---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
> essere aggiornato
> ---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
> essere un aggiornamento
> --> Esecuzione del controllo di transazione
> ---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
> aggiornato
> ---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere un
> aggiornamento
> --> Analisi conflitto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
> va in conflitto con ovirt-engine-reports-setup < 4.0.0
> --> Risoluzione delle dipendenze completata
> Errore: ovirt-engine-setup-base conflicts with
> ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
> Si può provare ad usare --skip-broken per aggirare il problema
> ** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check'
è:
> bash-4.2.46-20.el7_2.x86_64 è un duplicato di bash-4.2.46-19.el7.x86_64
> 1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di 1:dbus-1.6.12-13.el7.x86_64
> 1:dbus-libs-1.6.12-14.el7_2.x86_64 è un duplicato di
> 1:dbus-libs-1.6.12-13.el7.x86_64
> glibc-2.17-106.el7_2.8.x86_64 è un duplicato di
> glibc-2.17-106.el7_2.6.x86_64
> glibc-common-2.17-106.el7_2.8.x86_64 è un duplicato di
> glibc-common-2.17-106.el7_2.6.x86_64
> glibc-headers-2.17-106.el7_2.8.x86_64 è un duplicato di
> glibc-headers-2.17-106.el7_2.6.x86_64
> gssproxy-0.4.1-8.el7_2.x86_64 è un duplicato di gssproxy-0.4.1-7.el7.x86_64
> 1:java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato di
> 1:java-1.7.0-openjdk-1.7.0.101-2.6.6.1.el7_2.x86_64
> 1:java-1.7.0-openjdk-headless-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato
> di 1:java-1.7.0-openjdk-headless-1.7.0.101-2.6.6.1.el7_2.x86_64
> libblkid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
> libblkid-2.23.2-26.el7_2.2.x86_64
> libmount-2.23.2-26.el7_2.3.x86_64 è un duplicato di
> libmount-2.23.2-26.el7_2.2.x86_64
> libsss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
> libsss_idmap-1.13.0-40.el7_2.9.x86_64
> libsss_nss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
> libsss_nss_idmap-1.13.0-40.el7_2.9.x86_64
> libuuid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
> libuuid-2.23.2-26.el7_2.2.x86_64
> 2:microcode_ctl-2.1-12.el7_2.1.x86_64 è un duplicato di
> 2:microcode_ctl-2.1-12.el7.x86_64
> systemd-219-19.el7_2.12.x86_64 è un duplicato di
> systemd-219-19.el7_2.11.x86_64
> systemd-libs-219-19.el7_2.12.x86_64 è un duplicato di
> systemd-libs-219-19.el7_2.11.x86_64
> systemd-sysv-219-19.el7_2.12.x86_64 è un duplicato di
> systemd-sysv-219-19.el7_2.11.x86_64
> util-linux-2.23.2-26.el7_2.3.x86_64 è un duplicato di
> util-linux-2.23.2-26.el7_2.2.x86_64
>
> What can I do to solve the problem?
Reports is not packaged nor supported in 4.0.
If you don't need it, you can try:
yum remove ovirt-engine-reports\*
If you do, you might be able to set up Reports 3.6 to
work with your 4.0 engine/dwh.
On a side note, it's recommended to remove your 3.6 repos
only after you finished upgrading to 4.0 - if you remove them
before, engine-setup will not be able to rollback in case of
a problem.
Best,
I remove ovirt-engine-reports package and then I can upgrade.
In the documentation
"http://www.ovirt.org/documentation/how-to/reports/reports/" says that "
== oVirt Engine Reports & DWH included in oVirt >= 3.5 ==". This means
that I do not install nothing after upgrade?
Regards
Nicola
--------------731C0208BAD02396D2DA4474
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Il 03/08/2016 13:42, Yedidyah Bar David
ha scritto:<br>
</div>
<blockquote
cite="mid:CAHRwYXup4R6Y9j5Rv=xNMTir8Z_bVPR-jjTZiJDeD1cyj=Wyyg@mail.gmail.com"
type="cite">
<pre wrap="">On Wed, Aug 3, 2016 at 2:30 PM, nicola.gentile.to
<a class="moz-txt-link-rfc2396E"
href="mailto:nicola.gentile.to@gmail.com"><nicola.gentile.to@gmail.com></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
Two final steps I've done that are only necessary in my environment, where
the host itslef is providing the NFS service for storage domains:
After install you have to make a dependency so that VDSM Broker starts after
NFS Server
In /usr/lib/systemd/system/ovirt-ha-broker.service
Added in section [Unit] the line:
After=nfs-server.service
Also, for vdsmd service, in file vdsmd.service changed from:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service
to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service \
nfs-server.service
NOTE: the files will be overwritten by future updates, so you have to keep
in mind...
Hi,
I try to upgrade from ovirt 3.6.7 to 4.0.1.
I follow this steps:
1. Update repository for 4.0.1
2. Disable old repository 3.6.7
3. run: yum update "ovirt-engine-setup*"
now an error occured:
yum update "ovirt-engine-setup*"
Plugin abilitati:fastestmirror, langpacks, versionlock
Repository centos-ovirt36 is listed more than once in the configuration
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
* base: artfiles.org
* extras: ba.mirror.garr.it
* ovirt-4.0: <a class="moz-txt-link-abbreviated"
href="ftp://ftp.nluug.nl">ftp.nluug.nl</a>
* ovirt-4.0-epel: epel.besthosting.ua
* updates: ba.mirror.garr.it
Risoluzione dipendenze
--> Esecuzione del controllo di transazione
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per
il
pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
--> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il
pacchetto:
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
otopi-java-1.4.2-1.el7.centos.noarch
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
per essere un aggiornamento
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
--> Analisi conflitto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
va in conflitto con ovirt-engine-reports-setup < 4.0.0
--> Risoluzione delle dipendenze completata
Errore: ovirt-engine-setup-base conflicts with
ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
Si può provare ad usare --skip-broken per aggirare il problema
** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check' è:
bash-4.2.46-20.el7_2.x86_64 è un duplicato di bash-4.2.46-19.el7.x86_64
1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di 1:dbus-1.6.12-13.el7.x86_64
1:dbus-libs-1.6.12-14.el7_2.x86_64 è un duplicato di
1:dbus-libs-1.6.12-13.el7.x86_64
glibc-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-2.17-106.el7_2.6.x86_64
glibc-common-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-common-2.17-106.el7_2.6.x86_64
glibc-headers-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-headers-2.17-106.el7_2.6.x86_64
gssproxy-0.4.1-8.el7_2.x86_64 è un duplicato di gssproxy-0.4.1-7.el7.x86_64
1:java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato di
1:java-1.7.0-openjdk-1.7.0.101-2.6.6.1.el7_2.x86_64
1:java-1.7.0-openjdk-headless-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato
di 1:java-1.7.0-openjdk-headless-1.7.0.101-2.6.6.1.el7_2.x86_64
libblkid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libblkid-2.23.2-26.el7_2.2.x86_64
libmount-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libmount-2.23.2-26.el7_2.2.x86_64
libsss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_idmap-1.13.0-40.el7_2.9.x86_64
libsss_nss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_nss_idmap-1.13.0-40.el7_2.9.x86_64
libuuid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libuuid-2.23.2-26.el7_2.2.x86_64
2:microcode_ctl-2.1-12.el7_2.1.x86_64 è un duplicato di
2:microcode_ctl-2.1-12.el7.x86_64
systemd-219-19.el7_2.12.x86_64 è un duplicato di
systemd-219-19.el7_2.11.x86_64
systemd-libs-219-19.el7_2.12.x86_64 è un duplicato di
systemd-libs-219-19.el7_2.11.x86_64
systemd-sysv-219-19.el7_2.12.x86_64 è un duplicato di
systemd-sysv-219-19.el7_2.11.x86_64
util-linux-2.23.2-26.el7_2.3.x86_64 è un duplicato di
util-linux-2.23.2-26.el7_2.2.x86_64
What can I do to solve the problem?
</pre>
</blockquote>
<pre wrap="">
Reports is not packaged nor supported in 4.0.
If you don't need it, you can try:
yum remove ovirt-engine-reports\*
If you do, you might be able to set up Reports 3.6 to
work with your 4.0 engine/dwh.
On a side note, it's recommended to remove your 3.6 repos
only after you finished upgrading to 4.0 - if you remove them
before, engine-setup will not be able to rollback in case of
a problem.
Best,
</pre>
</blockquote>
<p>I remove ovirt-engine-reports package and then I can upgrade. <br>
</p>
<p>In the documentation
<a class="moz-txt-link-rfc2396E"
href="http://www.ovirt.org/documentation/how-to/reports/reports/&quo...
says
that "
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
<span style="color: rgb(51, 51, 51); font-family: "Source
Sans Pro", "Open Sans", "Helvetica
Neue", Helvetica, Arial, sans-serif; font-size: 16px;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: 22.8571px; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important;
float: none; background-color: rgb(255, 255, 255);">== oVirt
Engine Reports & DWH included in oVirt >= 3.5 ==". This
means that I do not install nothing after upgrade?</span></p>
<p><span style="color: rgb(51, 51, 51); font-family: "Source
Sans Pro", "Open Sans", "Helvetica
Neue", Helvetica, Arial, sans-serif; font-size: 16px;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: 22.8571px; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important;
float: none; background-color: rgb(255, 255,
255);">Regards</span></p>
<p><span style="color: rgb(51, 51, 51); font-family: "Source
Sans Pro", "Open Sans", "Helvetica
Neue", Helvetica, Arial, sans-serif; font-size: 16px;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: 22.8571px; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important;
float: none; background-color: rgb(255, 255,
255);">Nicola</span></p>
<p><span style="color: rgb(51, 51, 51); font-family: "Source
Sans Pro", "Open Sans", "Helvetica
Neue", Helvetica, Arial, sans-serif; font-size: 16px;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: 22.8571px; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important;
float: none; background-color: rgb(255, 255, 255);"><br>
</span></p>
<p><br>
</p>
<p><br>
</p>
</body>
</html>
--------------731C0208BAD02396D2DA4474--
8:04 a.m.
On Wed, Aug 3, 2016 at 2:51 PM, nicola.gentile.to <
nicola.gentile.to(a)gmail.com> wrote:
Il 03/08/2016 13:42, Yedidyah Bar David ha scritto:
On Wed, Aug 3, 2016 at 2:30 PM, nicola.gentile.to<nicola.gentile.to(a)gmail.com>
<nicola.gentile.to(a)gmail.com> wrote:
Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
Two final steps I've done that are only necessary in my environment, where
the host itslef is providing the NFS service for storage domains:
After install you have to make a dependency so that VDSM Broker starts after
NFS Server
In /usr/lib/systemd/system/ovirt-ha-broker.service
Added in section [Unit] the line:
After=nfs-server.service
Also, for vdsmd service, in file vdsmd.service changed from:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service
to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service \
nfs-server.service
NOTE: the files will be overwritten by future updates, so you have to keep
in mind...
Hi,
I try to upgrade from ovirt 3.6.7 to 4.0.1.
I follow this steps:
1. Update repository for 4.0.1
2. Disable old repository 3.6.7
3. run: yum update "ovirt-engine-setup*"
now an error occured:
yum update "ovirt-engine-setup*"
Plugin abilitati:fastestmirror, langpacks, versionlock
Repository centos-ovirt36 is listed more than once in the configuration
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
* base: artfiles.org
* extras: ba.mirror.garr.it
* ovirt-4.0: ftp.nluug.nl
* ovirt-4.0-epel: epel.besthosting.ua
* updates: ba.mirror.garr.it
Risoluzione dipendenze
--> Esecuzione del controllo di transazione
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per il
pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
--> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il pacchetto:
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
otopi-java-1.4.2-1.el7.centos.noarch
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
per essere un aggiornamento
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
--> Analisi conflitto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
va in conflitto con ovirt-engine-reports-setup < 4.0.0
--> Risoluzione delle dipendenze completata
Errore: ovirt-engine-setup-base conflicts with
ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
Si può provare ad usare --skip-broken per aggirare il problema
** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check' è:
bash-4.2.46-20.el7_2.x86_64 è un duplicato di bash-4.2.46-19.el7.x86_64
1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di 1:dbus-1.6.12-13.el7.x86_64
1:dbus-libs-1.6.12-14.el7_2.x86_64 è un duplicato di
1:dbus-libs-1.6.12-13.el7.x86_64
glibc-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-2.17-106.el7_2.6.x86_64
glibc-common-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-common-2.17-106.el7_2.6.x86_64
glibc-headers-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-headers-2.17-106.el7_2.6.x86_64
gssproxy-0.4.1-8.el7_2.x86_64 è un duplicato di gssproxy-0.4.1-7.el7.x86_64
1:java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato di
1:java-1.7.0-openjdk-1.7.0.101-2.6.6.1.el7_2.x86_64
1:java-1.7.0-openjdk-headless-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato
di 1:java-1.7.0-openjdk-headless-1.7.0.101-2.6.6.1.el7_2.x86_64
libblkid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libblkid-2.23.2-26.el7_2.2.x86_64
libmount-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libmount-2.23.2-26.el7_2.2.x86_64
libsss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_idmap-1.13.0-40.el7_2.9.x86_64
libsss_nss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_nss_idmap-1.13.0-40.el7_2.9.x86_64
libuuid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libuuid-2.23.2-26.el7_2.2.x86_64
2:microcode_ctl-2.1-12.el7_2.1.x86_64 è un duplicato di
2:microcode_ctl-2.1-12.el7.x86_64
systemd-219-19.el7_2.12.x86_64 è un duplicato di
systemd-219-19.el7_2.11.x86_64
systemd-libs-219-19.el7_2.12.x86_64 è un duplicato di
systemd-libs-219-19.el7_2.11.x86_64
systemd-sysv-219-19.el7_2.12.x86_64 è un duplicato di
systemd-sysv-219-19.el7_2.11.x86_64
util-linux-2.23.2-26.el7_2.3.x86_64 è un duplicato di
util-linux-2.23.2-26.el7_2.2.x86_64
What can I do to solve the problem?
Reports is not packaged nor supported in 4.0.
If you don't need it, you can try:
yum remove ovirt-engine-reports\*
If you do, you might be able to set up Reports 3.6 to
work with your 4.0 engine/dwh.
On a side note, it's recommended to remove your 3.6 repos
only after you finished upgrading to 4.0 - if you remove them
before, engine-setup will not be able to rollback in case of
a problem.
Best,
I remove ovirt-engine-reports package and then I can upgrade.
In the documentation
"http://www.ovirt.org/documentation/how-to/reports/reports/"
<http://www.ovirt.org/documentation/how-to/reports/reports/> says that " ==
oVirt Engine Reports & DWH included in oVirt >= 3.5 ==". This means that I
do not install nothing after upgrade?
Sorry, this page is not updated for 4.0. Please see also:
http://lists.ovirt.org/pipermail/users/2016-June/040549.html
Regards
Nicola
--
Didi
8:11 a.m.
This is a multi-part message in MIME format.
--------------F4E802409E3ADBC63538B4A2
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Il 03/08/2016 14:04, Yedidyah Bar David ha scritto:
On Wed, Aug 3, 2016 at 2:51 PM, nicola.gentile.to
<http://nicola.gentile.to> <nicola.gentile.to(a)gmail.com
<mailto:nicola.gentile.to@gmail.com>> wrote:
Il 03/08/2016 13:42, Yedidyah Bar David ha scritto:
> On Wed, Aug 3, 2016 at 2:30 PM,nicola.gentile.to
<http://nicola.gentile.to>
> <nicola.gentile.to(a)gmail.com> <mailto:nicola.gentile.to@gmail.com>
wrote:
>> Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
>>
>> Two final steps I've done that are only necessary in my environment,
where
>> the host itslef is providing the NFS service for storage domains:
>>
>> After install you have to make a dependency so that VDSM Broker starts after
>> NFS Server
>>
>> In /usr/lib/systemd/system/ovirt-ha-broker.service
>>
>> Added in section [Unit] the line:
>>
>> After=nfs-server.service
>>
>> Also, for vdsmd service, in file vdsmd.service changed from:
>>
>> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
>> supervdsmd.service sanlock.service vdsm-network.service
>>
>> to:
>> After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
>> supervdsmd.service sanlock.service vdsm-network.service \
>> nfs-server.service
>>
>> NOTE: the files will be overwritten by future updates, so you have to keep
>> in mind...
>>
>> Hi,
>>
>> I try to upgrade from ovirt 3.6.7 to 4.0.1.
>>
>> I follow this steps:
>>
>> 1. Update repository for 4.0.1
>>
>> 2. Disable old repository 3.6.7
>>
>> 3. run: yum update "ovirt-engine-setup*"
>>
>> now an error occured:
>>
>> yum update "ovirt-engine-setup*"
>> Plugin abilitati:fastestmirror, langpacks, versionlock
>> Repository centos-ovirt36 is listed more than once in the configuration
>> Repository virtio-win-stable is listed more than once in the configuration
>> Loading mirror speeds from cached hostfile
>> * base:artfiles.org <http://artfiles.org>
>> * extras:ba.mirror.garr.it <http://ba.mirror.garr.it>
>> * ovirt-4.0:ftp.nluug.nl <ftp://ftp.nluug.nl>
>> * ovirt-4.0-epel:epel.besthosting.ua <http://epel.besthosting.ua>
>> * updates:ba.mirror.garr.it <http://ba.mirror.garr.it>
>> Risoluzione dipendenze
>> --> Esecuzione del controllo di transazione
>> ---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato
per
>> essere aggiornato
>> ---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato
per
>> essere un aggiornamento
>> ---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos
settato
>> per essere aggiornato
>> ---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos
settato
>> per essere un aggiornamento
>> --> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos
per il
>> pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
>> --> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
>> ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
>> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
>> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
>> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
>> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
>> --> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il
pacchetto:
>> ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
>> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
>> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
>> ---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
>> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
>> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
>> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
>> ---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
>> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
>> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
>> 0:3.6.7.5-1.el7.centos settato per essere aggiornato
>> ---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
>> 0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
>> --> Esecuzione del controllo di transazione
>> ---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
>> aggiornato
>> --> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
>> otopi-java-1.4.2-1.el7.centos.noarch
>> ---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
>> aggiornamento
>> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
>> per essere aggiornato
>> ---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
>> per essere un aggiornamento
>> ---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
>> essere aggiornato
>> ---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
>> essere un aggiornamento
>> --> Esecuzione del controllo di transazione
>> ---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
>> aggiornato
>> ---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere
un
>> aggiornamento
>> --> Analisi conflitto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
>> va in conflitto con ovirt-engine-reports-setup < 4.0.0
>> --> Risoluzione delle dipendenze completata
>> Errore: ovirt-engine-setup-base conflicts with
>> ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
>> Si può provare ad usare --skip-broken per aggirare il problema
>> ** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum
check' è:
>> bash-4.2.46-20.el7_2.x86_64 è un duplicato di bash-4.2.46-19.el7.x86_64
>> 1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di 1:dbus-1.6.12-13.el7.x86_64
>> 1:dbus-libs-1.6.12-14.el7_2.x86_64 è un duplicato di
>> 1:dbus-libs-1.6.12-13.el7.x86_64
>> glibc-2.17-106.el7_2.8.x86_64 è un duplicato di
>> glibc-2.17-106.el7_2.6.x86_64
>> glibc-common-2.17-106.el7_2.8.x86_64 è un duplicato di
>> glibc-common-2.17-106.el7_2.6.x86_64
>> glibc-headers-2.17-106.el7_2.8.x86_64 è un duplicato di
>> glibc-headers-2.17-106.el7_2.6.x86_64
>> gssproxy-0.4.1-8.el7_2.x86_64 è un duplicato di gssproxy-0.4.1-7.el7.x86_64
>> 1:java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato di
>> 1:java-1.7.0-openjdk-1.7.0.101-2.6.6.1.el7_2.x86_64
>> 1:java-1.7.0-openjdk-headless-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato
>> di 1:java-1.7.0-openjdk-headless-1.7.0.101-2.6.6.1.el7_2.x86_64
>> libblkid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
>> libblkid-2.23.2-26.el7_2.2.x86_64
>> libmount-2.23.2-26.el7_2.3.x86_64 è un duplicato di
>> libmount-2.23.2-26.el7_2.2.x86_64
>> libsss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
>> libsss_idmap-1.13.0-40.el7_2.9.x86_64
>> libsss_nss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
>> libsss_nss_idmap-1.13.0-40.el7_2.9.x86_64
>> libuuid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
>> libuuid-2.23.2-26.el7_2.2.x86_64
>> 2:microcode_ctl-2.1-12.el7_2.1.x86_64 è un duplicato di
>> 2:microcode_ctl-2.1-12.el7.x86_64
>> systemd-219-19.el7_2.12.x86_64 è un duplicato di
>> systemd-219-19.el7_2.11.x86_64
>> systemd-libs-219-19.el7_2.12.x86_64 è un duplicato di
>> systemd-libs-219-19.el7_2.11.x86_64
>> systemd-sysv-219-19.el7_2.12.x86_64 è un duplicato di
>> systemd-sysv-219-19.el7_2.11.x86_64
>> util-linux-2.23.2-26.el7_2.3.x86_64 è un duplicato di
>> util-linux-2.23.2-26.el7_2.2.x86_64
>>
>> What can I do to solve the problem?
> Reports is not packaged nor supported in 4.0.
>
> If you don't need it, you can try:
>
> yum remove ovirt-engine-reports\*
>
> If you do, you might be able to set up Reports 3.6 to
> work with your 4.0 engine/dwh.
>
> On a side note, it's recommended to remove your 3.6 repos
> only after you finished upgrading to 4.0 - if you remove them
> before, engine-setup will not be able to rollback in case of
> a problem.
>
> Best,
I remove ovirt-engine-reports package and then I can upgrade.
In the documentation
"http://www.ovirt.org/documentation/how-to/reports/reports/"
<http://www.ovirt.org/documentation/how-to/reports/reports/> says
that " == oVirt Engine Reports & DWH included in oVirt >= 3.5 ==".
This means that I do not install nothing after upgrade?
Sorry, this page is not updated for 4.0. Please see also:
http://lists.ovirt.org/pipermail/users/2016-June/040549.html
Regards
Nicola
--
Didi
thanks a lot for you support
Nicola
--------------F4E802409E3ADBC63538B4A2
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Il 03/08/2016 14:04, Yedidyah Bar David
ha scritto:<br>
</div>
<blockquote
cite="mid:CAHRwYXvXW8huj2cux2Skb7a4YaD9V1N4dgYjDvpcxhaYLTkT1Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Aug 3, 2016 at 2:51 PM, <a
moz-do-not-send="true" href="http://nicola.gentile.to"
target="_blank">nicola.gentile.to</a> <span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:nicola.gentile.to@gmail.com"
target="_blank">nicola.gentile.to(a)gmail.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>
<div>
<div>Il 03/08/2016 13:42, Yedidyah Bar David ha
scritto:<br>
</div>
<blockquote type="cite">
<pre>On Wed, Aug 3, 2016 at 2:30 PM, <a
moz-do-not-send="true" href="http://nicola.gentile.to"
target="_blank">nicola.gentile.to</a>
<a moz-do-not-send="true" href="mailto:nicola.gentile.to@gmail.com"
target="_blank">&lt;nicola.gentile.to(a)gmail.com&gt;</a> wrote:
</pre>
<blockquote type="cite">
<pre>Il 05/07/2016 10:30, Gianluca Cecchi ha scritto:
Two final steps I've done that are only necessary in my environment, where
the host itslef is providing the NFS service for storage domains:
After install you have to make a dependency so that VDSM Broker starts after
NFS Server
In /usr/lib/systemd/system/ovirt-ha-broker.service
Added in section [Unit] the line:
After=nfs-server.service
Also, for vdsmd service, in file vdsmd.service changed from:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service
to:
After=multipathd.service libvirtd.service iscsid.service rpcbind.service \
supervdsmd.service sanlock.service vdsm-network.service \
nfs-server.service
NOTE: the files will be overwritten by future updates, so you have to keep
in mind...
Hi,
I try to upgrade from ovirt 3.6.7 to 4.0.1.
I follow this steps:
1. Update repository for 4.0.1
2. Disable old repository 3.6.7
3. run: yum update "ovirt-engine-setup*"
now an error occured:
yum update "ovirt-engine-setup*"
Plugin abilitati:fastestmirror, langpacks, versionlock
Repository centos-ovirt36 is listed more than once in the configuration
Repository virtio-win-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
* base: <a moz-do-not-send="true" href="http://artfiles.org"
target="_blank">artfiles.org</a>
* extras: <a moz-do-not-send="true"
href="http://ba.mirror.garr.it"
target="_blank">ba.mirror.garr.it</a>
* ovirt-4.0: <a moz-do-not-send="true" href="ftp://ftp.nluug.nl"
target="_blank">ftp.nluug.nl</a>
* ovirt-4.0-epel: <a moz-do-not-send="true"
href="http://epel.besthosting.ua"
target="_blank">epel.besthosting.ua</a>
* updates: <a moz-do-not-send="true"
href="http://ba.mirror.garr.it"
target="_blank">ba.mirror.garr.it</a>
Risoluzione dipendenze
--> Esecuzione del controllo di transazione
---> Pacchetto ovirt-engine-setup.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-setup.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
---> Pacchetto ovirt-engine-setup-base.noarch 0:3.6.7.5-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-setup-base.noarch 0:4.0.1.1-1.el7.centos settato
per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-lib >= 4.0.1.1-1.el7.centos per
il
pacchetto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
--> Elaborazione dipendenza: otopi >= 1.5.0 per il pacchetto:
ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Elaborazione dipendenza: ovirt-engine-dwh-setup >= 4.0 per il
pacchetto:
ovirt-engine-setup-plugin-ovirt-engine-4.0.1.1-1.el7.centos.noarch
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-ovirt-engine-common.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:3.6.7.5-1.el7.centos settato per essere aggiornato
---> Pacchetto ovirt-engine-setup-plugin-websocket-proxy.noarch
0:4.0.1.1-1.el7.centos settato per essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
--> Elaborazione dipendenza: otopi = 1.4.2-1.el7.centos per il pacchetto:
otopi-java-1.4.2-1.el7.centos.noarch
---> Pacchetto otopi.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:3.6.6-1.el7.centos settato
per essere aggiornato
---> Pacchetto ovirt-engine-dwh-setup.noarch 0:4.0.1-1.el7.centos settato
per essere un aggiornamento
---> Pacchetto ovirt-engine-lib.noarch 0:3.6.7.5-1.el7.centos settato per
essere aggiornato
---> Pacchetto ovirt-engine-lib.noarch 0:4.0.1.1-1.el7.centos settato per
essere un aggiornamento
--> Esecuzione del controllo di transazione
---> Pacchetto otopi-java.noarch 0:1.4.2-1.el7.centos settato per essere
aggiornato
---> Pacchetto otopi-java.noarch 0:1.5.1-1.el7.centos settato per essere un
aggiornamento
--> Analisi conflitto: ovirt-engine-setup-base-4.0.1.1-1.el7.centos.noarch
va in conflitto con ovirt-engine-reports-setup < 4.0.0
--> Risoluzione delle dipendenze completata
Errore: ovirt-engine-setup-base conflicts with
ovirt-engine-reports-setup-3.6.5.1-1.el7.centos.noarch
Si può provare ad usare --skip-broken per aggirare il problema
** Trovati 19 problemi pre-esistenti nel rpmdb, l'output di 'yum check' è:
bash-4.2.46-20.el7_2.x86_64 è un duplicato di bash-4.2.46-19.el7.x86_64
1:dbus-1.6.12-14.el7_2.x86_64 è un duplicato di 1:dbus-1.6.12-13.el7.x86_64
1:dbus-libs-1.6.12-14.el7_2.x86_64 è un duplicato di
1:dbus-libs-1.6.12-13.el7.x86_64
glibc-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-2.17-106.el7_2.6.x86_64
glibc-common-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-common-2.17-106.el7_2.6.x86_64
glibc-headers-2.17-106.el7_2.8.x86_64 è un duplicato di
glibc-headers-2.17-106.el7_2.6.x86_64
gssproxy-0.4.1-8.el7_2.x86_64 è un duplicato di gssproxy-0.4.1-7.el7.x86_64
1:java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato di
1:java-1.7.0-openjdk-1.7.0.101-2.6.6.1.el7_2.x86_64
1:java-1.7.0-openjdk-headless-1.7.0.111-2.6.7.2.el7_2.x86_64 è un duplicato
di 1:java-1.7.0-openjdk-headless-1.7.0.101-2.6.6.1.el7_2.x86_64
libblkid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libblkid-2.23.2-26.el7_2.2.x86_64
libmount-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libmount-2.23.2-26.el7_2.2.x86_64
libsss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_idmap-1.13.0-40.el7_2.9.x86_64
libsss_nss_idmap-1.13.0-40.el7_2.12.x86_64 è un duplicato di
libsss_nss_idmap-1.13.0-40.el7_2.9.x86_64
libuuid-2.23.2-26.el7_2.3.x86_64 è un duplicato di
libuuid-2.23.2-26.el7_2.2.x86_64
2:microcode_ctl-2.1-12.el7_2.1.x86_64 è un duplicato di
2:microcode_ctl-2.1-12.el7.x86_64
systemd-219-19.el7_2.12.x86_64 è un duplicato di
systemd-219-19.el7_2.11.x86_64
systemd-libs-219-19.el7_2.12.x86_64 è un duplicato di
systemd-libs-219-19.el7_2.11.x86_64
systemd-sysv-219-19.el7_2.12.x86_64 è un duplicato di
systemd-sysv-219-19.el7_2.11.x86_64
util-linux-2.23.2-26.el7_2.3.x86_64 è un duplicato di
util-linux-2.23.2-26.el7_2.2.x86_64
What can I do to solve the problem?
</pre>
</blockquote>
<pre>Reports is not packaged nor supported in 4.0.
If you don't need it, you can try:
yum remove ovirt-engine-reports\*
If you do, you might be able to set up Reports 3.6 to
work with your 4.0 engine/dwh.
On a side note, it's recommended to remove your 3.6 repos
only after you finished upgrading to 4.0 - if you remove them
before, engine-setup will not be able to rollback in case of
a problem.
Best,
</pre>
</blockquote>
</div>
</div>
<p>I remove ovirt-engine-reports package and then I can
upgrade. <br>
</p>
<p>In the documentation <a moz-do-not-send="true"
href="http://www.ovirt.org/documentation/how-to/reports/reports/"
target="_blank">"http://www.ovirt.org/documentation/how...
says that " <span>== oVirt Engine Reports & DWH
included in oVirt >= 3.5 ==". This means that I
do not install nothing after upgrade?</span></p>
</div>
</blockquote>
<div><br>
</div>
<div>Sorry, this page is not updated for 4.0. Please see
also:<br>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/pipermail/users/2016-June/040549.html&q...
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p><span>Regards</span></p>
<span><font color="#888888">
<p><span>Nicola</span></p>
<p><span><br>
</span></p>
<p><br>
</p>
<p><br>
</p>
</font></span></div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div data-smartmail="gmail_signature">Didi<br>
</div>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>thanks a lot for you support</p>
<p>Nicola<br>
</p>
</body>
</html>
--------------F4E802409E3ADBC63538B4A2--
3067
days inactive
3098
days old
15 comments
6 participants
participants (6)
-
Arman Khalatyan -
Gianluca Cecchi -
nicola.gentile.to -
ovirt＠timmi.org -
Yaniv Dary -
Yedidyah Bar David