failing update ovirt-engine on centos 7
--Apple-Mail=_9190D383-816A-4168-8F45-9E5CFD2D7429 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I have an dedicated machin to run ovirt-engine (not hosted). It's an up = to date centos 7.2.1511 I installed ovirt 3.6.6 a few weeks ago (May 10 17:56:44 tells me = yum.log) Now, I'm trying a full yum update and getting : # yum update .... Error: Package: ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch = (@ovirt-3.6) Requires: ovirt-engine-tools-backup =3D 3.6.5.3-1.el7.centos Removing: = ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) ovirt-engine-tools-backup =3D 3.6.5.3-1.el7.centos Updated By: = ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6) ovirt-engine-tools-backup =3D 3.6.6.2-1.el7.centos rpm -qi ovirt-engine-tools says : Version : 3.6.5.3 Release : 1.el7.centos ... Build Date : Mon Apr 11 23:45:30 2016 Build Host : el7-vm02.phx.ovirt.org and : rpm -qi ovirt-engine-tools-backup says: Name : ovirt-engine-tools-backup Version : 3.6.5.3 Release : 1.el7.centos ... Build Date : Mon Apr 11 23:45:30 2016 Build Host : el7-vm02.phx.ovirt.org yum update ovirt-engine-tools-backup ovirt-engine-tools fails in the = same way. but: yum list ovirt-engine-tools-backup ovirt-engine-tools Loaded plugins: etckeeper, fastestmirror, versionlock Loading mirror speeds from cached hostfile Installed Packages ovirt-engine-tools.noarch = 3.6.5.3-1.el7.centos = @ovirt-3.6 ovirt-engine-tools-backup.noarch = 3.6.5.3-1.el7.centos = @ovirt-3.6 Available Packages ovirt-engine-tools-backup.noarch = 3.6.6.2-1.el7.centos = ovirt-3.6=20 So no ovirt-engine-tools to update. and indeed : yum update ovirt-engine-tools Loaded plugins: etckeeper, fastestmirror, versionlock Loading mirror speeds from cached hostfile No packages marked for update I have disable ovirt-3.6-epel, because I already use epel, is it the = problem ? What should I do ? I don't think removing ovirt-engine-tools is a = option. --Apple-Mail=_9190D383-816A-4168-8F45-9E5CFD2D7429 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space;" class=3D"">I have an dedicated = machin to run ovirt-engine (not hosted). It's an up to date centos = 7.2.1511<br class=3D""><br class=3D"">I installed ovirt 3.6.6 a few = weeks ago (May 10 17:56:44 tells me yum.log)<br class=3D""><br = class=3D"">Now, I'm trying a full yum update and getting :<div = class=3D""><font face=3D"Menlo" style=3D"font-size: 11px;" class=3D""># = yum update</font></div><div class=3D""><font face=3D"Menlo" = style=3D"font-size: 11px;" class=3D"">....</font></div><div = class=3D""><font face=3D"Menlo" style=3D"font-size: 11px;" class=3D""><br = class=3D""></font></div><div class=3D""><font face=3D"Menlo" = style=3D"font-size: 11px;" class=3D"">Error: Package: = ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6)<br = class=3D""> Requires: = ovirt-engine-tools-backup =3D 3.6.5.3-1.el7.centos<br class=3D""> = Removing: = ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6)<br = class=3D""> = ovirt-engine-tools-backup =3D 3.6.5.3-1.el7.centos<br = class=3D""> Updated By: = ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6)<br = class=3D""> = ovirt-engine-tools-backup =3D 3.6.6.2-1.el7.centos<br class=3D""><br= class=3D""></font></div><div class=3D""><br class=3D""></div><div = class=3D""><font face=3D"Menlo" style=3D"font-size: 11px;" class=3D"">rpm = -qi ovirt-engine-tools says :</font></div><div class=3D""><font = face=3D"Menlo" style=3D"font-size: 11px;" class=3D"">Version = : 3.6.5.3<br class=3D"">Release : 1.el7.centos<br = class=3D"">...</font></div><font face=3D"Menlo" style=3D"font-size: = 11px;" class=3D"">Build Date : Mon Apr 11 23:45:30 2016<br = class=3D""></font><div class=3D""><font face=3D"Menlo" style=3D"font-size:= 11px;" class=3D"">Build Host : <a = href=3D"http://el7-vm02.phx.ovirt.org" = class=3D"">el7-vm02.phx.ovirt.org</a><br class=3D""><br = class=3D""></font></div><div class=3D""><br class=3D""></div><div = class=3D"">and :</div><div class=3D""><font face=3D"Menlo" = style=3D"font-size: 11px;" class=3D"">rpm -qi ovirt-engine-tools-backup = says:</font></div><div class=3D""><font face=3D"Menlo" style=3D"font-size:= 11px;" class=3D"">Name : = ovirt-engine-tools-backup<br class=3D"">Version : = 3.6.5.3<br class=3D"">Release : = 1.el7.centos</font></div><div class=3D""><font face=3D"Menlo" = style=3D"font-size: 11px;" class=3D"">...<br class=3D"">Build Date = : Mon Apr 11 23:45:30 2016<br class=3D"">Build Host : <a = href=3D"http://el7-vm02.phx.ovirt.org" = class=3D"">el7-vm02.phx.ovirt.org</a><br class=3D""><br = class=3D""></font></div><div class=3D"">yum update = ovirt-engine-tools-backup ovirt-engine-tools fails in the same way.<br = class=3D""></div><div class=3D""><br class=3D""></div><div = class=3D"">but:</div><div class=3D""><br class=3D""></div><div = class=3D""><font face=3D"Menlo" style=3D"font-size: 11px;" class=3D"">yum = list ovirt-engine-tools-backup ovirt-engine-tools<br class=3D"">Loaded = plugins: etckeeper, fastestmirror, versionlock<br class=3D"">Loading = mirror speeds from cached hostfile<br class=3D"">Installed Packages<br = class=3D"">ovirt-engine-tools.noarch = = = 3.6.5.3-1.el7.centos = = = @ovirt-3.6<br class=3D"">ovirt-engine-tools-backup.noarch = = = 3.6.5.3-1.el7.centos = = = @ovirt-3.6<br class=3D"">Available Packages<br = class=3D"">ovirt-engine-tools-backup.noarch = = = 3.6.6.2-1.el7.centos = = = ovirt-3.6 <br class=3D""></font><br class=3D""></div><div = class=3D"">So no ovirt-engine-tools to update.</div><div = class=3D""><br class=3D""></div><div class=3D"">and indeed :</div><div = class=3D""><font face=3D"Menlo" style=3D"font-size: 11px;" class=3D"">yum = update ovirt-engine-tools<br class=3D"">Loaded plugins: etckeeper, = fastestmirror, versionlock<br class=3D"">Loading mirror speeds from = cached hostfile<br class=3D"">No packages marked for update<br = class=3D""><br class=3D""></font></div><div class=3D"">I have = disable ovirt-3.6-epel, because I already use epel, is it the = problem ?</div><div class=3D""><br class=3D""></div><div class=3D"">What = should I do ? I don't think removing ovirt-engine-tools is a = option.</div><div class=3D""><br class=3D""></div><div class=3D""><br = class=3D""></div><div class=3D""><br class=3D""></div></body></html>= --Apple-Mail=_9190D383-816A-4168-8F45-9E5CFD2D7429--
This is a multi-part message in MIME format. --------------C70F218DBA72DAF73EE7ABBC Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 25/05/16 17:59, Fabrice Bacchella wrote:
I have an dedicated machin to run ovirt-engine (not hosted). It's an up to date centos 7.2.1511
I installed ovirt 3.6.6 a few weeks ago (May 10 17:56:44 tells me yum.log)
Now, I'm trying a full yum update and getting : # yum update ....
Error: Package: ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) Requires: ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Removing: ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Updated By: ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6) ovirt-engine-tools-backup = 3.6.6.2-1.el7.centos
Follow 3.6.6 release notes to update: https://www.ovirt.org/release/3.6.6/ |yum install ||http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm| yum update ovirt\*setup\* and then run engine-setup to update the rest of the packages. G --------------C70F218DBA72DAF73EE7ABBC 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 bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 25/05/16 17:59, Fabrice Bacchella wrote:<br> </div> <blockquote cite="mid:3E15656C-06C7-4A7D-B03B-8BB58509B5A0@icloud.com" type="cite">I have an dedicated machin to run ovirt-engine (not hosted). It's an up to date centos 7.2.1511<br class=""> <br class=""> I installed ovirt 3.6.6 a few weeks ago (May 10 17:56:44 tells me yum.log)<br class=""> <br class=""> Now, I'm trying a full yum update and getting : <div class=""><font style="font-size: 11px;" class="" face="Menlo"># yum update</font></div> <div class=""><font style="font-size: 11px;" class="" face="Menlo">....</font></div> <div class=""><font style="font-size: 11px;" class="" face="Menlo"><br class=""> </font></div> <div class=""><font style="font-size: 11px;" class="" face="Menlo">Error: Package: ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6)<br class=""> Requires: ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos<br class=""> Removing: ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6)<br class=""> ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos<br class=""> Updated By: ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6)<br class=""> ovirt-engine-tools-backup = 3.6.6.2-1.el7.centos<br class=""> <br class=""> </font></div> <div class=""><br class=""> </div> </blockquote> <br> <font face="Menlo">Follow 3.6.6 release notes to update:<br> <a class="moz-txt-link-freetext" href="https://www.ovirt.org/release/3.6.6/">https://www.ovirt.org/release/3.6.6/</a><br> <br> </font><br> <font face="Menlo"><code>yum install </code><a href="http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm"><code><a class="moz-txt-link-freetext" href="http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm">http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm</a></code></a><br> yum update ovirt\*setup\*<br> and then run<br> engine-setup to update the rest of the packages.<br> <br> G<br> </font> </body> </html> --------------C70F218DBA72DAF73EE7ABBC--
Il 25/Mag/2016 17:25, "Kapetanakis Giannis" <bilias@edu.physics.uoc.gr> ha scritto:
On 25/05/16 17:59, Fabrice Bacchella wrote:
I have an dedicated machin to run ovirt-engine (not hosted). It's an up
to date centos 7.2.1511
I installed ovirt 3.6.6 a few weeks ago (May 10 17:56:44 tells me
yum.log)
Now, I'm trying a full yum update and getting : # yum update ....
Error: Package: ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch
(@ovirt-3.6)
Requires: ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Removing:
ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6)
ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Updated By:
ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6)
ovirt-engine-tools-backup = 3.6.6.2-1.el7.centos
Follow 3.6.6 release notes to update: https://www.ovirt.org/release/3.6.6/
+1 karma point +virtual medal "I read the docs" (We should start doing something like this and keep track)
yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm yum update ovirt\*setup\* and then run engine-setup to update the rest of the packages.
G
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_D678C2CC-BD61-4E4E-B7C7-04BA144FE6B1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252
Le 25 mai 2016 =E0 17:25, Kapetanakis Giannis = <bilias@edu.physics.uoc.gr> a =E9crit : =20 On 25/05/16 17:59, Fabrice Bacchella wrote:
I have an dedicated machin to run ovirt-engine (not hosted). It's an = up to date centos 7.2.1511 =20 I installed ovirt 3.6.6 a few weeks ago (May 10 17:56:44 tells me = yum.log) =20 Now, I'm trying a full yum update and getting : # yum update .... =20 Error: Package: ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch = (@ovirt-3.6) Requires: ovirt-engine-tools-backup =3D = 3.6.5.3-1.el7.centos Removing: = ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) ovirt-engine-tools-backup =3D 3.6.5.3-1.el7.centos Updated By: = ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6) ovirt-engine-tools-backup =3D 3.6.6.2-1.el7.centos =20 =20 =20 Follow 3.6.6 release notes to update: https://www.ovirt.org/release/3.6.6/ = <https://www.ovirt.org/release/3.6.6/> =20 =20 yum install = <http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm>http://resour= ces.ovirt.org/pub/yum-repo/ovirt-release36.rpm = <http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm> yum update ovirt\*setup\* and then run engine-setup to update the rest of the packages.
I have seen this doc. It updates a few components and what about the others ? The readme talk = about running engine-setup, but not that it will updates other packages. = I thought that ovirt-engine is for engine setup, not upgrading. --Apple-Mail=_D678C2CC-BD61-4E4E-B7C7-04BA144FE6B1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div = class=3D"">Le 25 mai 2016 =E0 17:25, Kapetanakis Giannis <<a = href=3D"mailto:bilias@edu.physics.uoc.gr" = class=3D"">bilias@edu.physics.uoc.gr</a>> a =E9crit :</div><br = class=3D"Apple-interchange-newline"><div class=3D""> =20 <meta content=3D"text/html; charset=3Dwindows-1252" = http-equiv=3D"Content-Type" class=3D""> =20 <div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D""> <div class=3D"moz-cite-prefix">On 25/05/16 17:59, Fabrice Bacchella wrote:<br class=3D""> </div> <blockquote = cite=3D"mid:3E15656C-06C7-4A7D-B03B-8BB58509B5A0@icloud.com" type=3D"cite"= class=3D"">I have an dedicated machin to run ovirt-engine (not hosted). It's an up to date centos 7.2.1511<br class=3D""> <br class=3D""> I installed ovirt 3.6.6 a few weeks ago (May 10 17:56:44 tells me yum.log)<br class=3D""> <br class=3D""> Now, I'm trying a full yum update and getting : <div class=3D""><font style=3D"font-size: 11px;" class=3D"" = face=3D"Menlo"># yum update</font></div> <div class=3D""><font style=3D"font-size: 11px;" class=3D"" = face=3D"Menlo">....</font></div> <div class=3D""><font style=3D"font-size: 11px;" class=3D"" = face=3D"Menlo"><br class=3D""> </font></div> <div class=3D""><font style=3D"font-size: 11px;" class=3D"" = face=3D"Menlo">Error: Package: ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6)<br class=3D""> Requires: = ovirt-engine-tools-backup =3D 3.6.5.3-1.el7.centos<br class=3D""> Removing: ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6)<br class=3D""> = ovirt-engine-tools-backup =3D 3.6.5.3-1.el7.centos<br class=3D""> Updated By: ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6)<br class=3D""> = ovirt-engine-tools-backup =3D 3.6.6.2-1.el7.centos<br class=3D""> <br class=3D""> </font></div> <div class=3D""><br class=3D""> </div> </blockquote> <br class=3D""> <font face=3D"Menlo" class=3D"">Follow 3.6.6 release notes to = update:<br class=3D""> <a class=3D"moz-txt-link-freetext" = href=3D"https://www.ovirt.org/release/3.6.6/">https://www.ovirt.org/releas= e/3.6.6/</a><br class=3D""> <br class=3D""> </font><br class=3D""> <font face=3D"Menlo" class=3D""><code = class=3D"">yum install </code><a = href=3D"http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm" = class=3D""><code class=3D""></code></a><code class=3D""><a = class=3D"moz-txt-link-freetext" = href=3D"http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm">http:= //resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm</a></code><br = class=3D""> yum update ovirt\*setup\*<br class=3D""> and then run<br class=3D""> engine-setup to update the rest of the packages.<br = class=3D""></font></div></div></blockquote><br class=3D""></div><div>I = have seen this doc.</div><div><br class=3D""></div><div>It updates a few = components and what about the others ? The readme talk about = running <span style=3D"color: inherit; font-family: Menlo, Monaco, = Consolas, 'Courier New', monospace; font-size: inherit; white-space: = pre-wrap; line-height: 1.42857143;" class=3D"">engine-setup, but not = that it will updates other packages. I thought that ovirt-engine is for = engine setup, not upgrading.</span></div><br class=3D""></body></html>= --Apple-Mail=_D678C2CC-BD61-4E4E-B7C7-04BA144FE6B1--
On Wed, May 25, 2016 at 9:11 PM, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Le 25 mai 2016 à 17:25, Kapetanakis Giannis <bilias@edu.physics.uoc.gr> a écrit :
On 25/05/16 17:59, Fabrice Bacchella wrote:
I have an dedicated machin to run ovirt-engine (not hosted). It's an up to date centos 7.2.1511
I installed ovirt 3.6.6 a few weeks ago (May 10 17:56:44 tells me yum.log)
Now, I'm trying a full yum update and getting : # yum update ....
Error: Package: ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) Requires: ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Removing: ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Updated By: ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6) ovirt-engine-tools-backup = 3.6.6.2-1.el7.centos
Follow 3.6.6 release notes to update: https://www.ovirt.org/release/3.6.6/
yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm yum update ovirt\*setup\* and then run engine-setup to update the rest of the packages.
I have seen this doc.
It updates a few components and what about the others ? The readme talk about running engine-setup, but not that it will updates other packages. I thought that ovirt-engine is for engine setup, not upgrading.
Right. After engine-setup finishes, you should 'yum update' to update the rest. And BTW, this specific issue about tools-backup was fixed in [1]. So a future 'yum update' should not emit this error - although the update sequence is still the same - add repos, update setup packages, engine-setup, update the rest. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 -- Didi
I had an issue with updating to 3.6.6. There were errors during engine-setup: [ ERROR ] Yum Non-fatal POSTUN scriptlet failure in rpm package ovirt-vmconsole-1.0.0-1.el7.centos.noarch [ ERROR ] Yum Transaction close failed: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 778, in endTransaction self.processTransaction() File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 1064, in processTransaction _('One or more elements within Yum transaction failed') RuntimeError: One or more elements within Yum transaction failed ovirt-vmconsole has the following uninstall script: postuninstall scriptlet (using /bin/sh): if [ "$1" -ge "1" ]; then semodule -i "/usr/share/selinux/packages/ovirt-vmconsole/ovirt_vmconsole.pp" fi In other words you can't update if you have SELINUX disabled. The workaround is the following: ln -fs /bin/true /usr/sbin/semodule On 26/05/16 08:43, "users-bounces@ovirt.org on behalf of Yedidyah Bar David" <users-bounces@ovirt.org on behalf of didi@redhat.com> wrote:
On Wed, May 25, 2016 at 9:11 PM, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Le 25 mai 2016 à 17:25, Kapetanakis Giannis <bilias@edu.physics.uoc.gr> a écrit :
On 25/05/16 17:59, Fabrice Bacchella wrote:
I have an dedicated machin to run ovirt-engine (not hosted). It's an up to date centos 7.2.1511
I installed ovirt 3.6.6 a few weeks ago (May 10 17:56:44 tells me yum.log)
Now, I'm trying a full yum update and getting : # yum update ....
Error: Package: ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) Requires: ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Removing: ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Updated By: ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6) ovirt-engine-tools-backup = 3.6.6.2-1.el7.centos
Follow 3.6.6 release notes to update: https://www.ovirt.org/release/3.6.6/
yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm yum update ovirt\*setup\* and then run engine-setup to update the rest of the packages.
I have seen this doc.
It updates a few components and what about the others ? The readme talk about running engine-setup, but not that it will updates other packages. I thought that ovirt-engine is for engine setup, not upgrading.
Right.
After engine-setup finishes, you should 'yum update' to update the rest.
And BTW, this specific issue about tools-backup was fixed in [1]. So a future 'yum update' should not emit this error - although the update sequence is still the same - add repos, update setup packages, engine-setup, update the rest.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 -- Didi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Thu, May 26, 2016 at 1:21 PM, Pavel Gashev <Pax@acronis.com> wrote:
I had an issue with updating to 3.6.6. There were errors during engine-setup:
[ ERROR ] Yum Non-fatal POSTUN scriptlet failure in rpm package ovirt-vmconsole-1.0.0-1.el7.centos.noarch
[ ERROR ] Yum Transaction close failed: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 778, in endTransaction self.processTransaction() File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 1064, in processTransaction _('One or more elements within Yum transaction failed') RuntimeError: One or more elements within Yum transaction failed
ovirt-vmconsole has the following uninstall script: postuninstall scriptlet (using /bin/sh): if [ "$1" -ge "1" ]; then semodule -i "/usr/share/selinux/packages/ovirt-vmconsole/ovirt_vmconsole.pp" fi
In other words you can't update if you have SELINUX disabled.
The workaround is the following: ln -fs /bin/true /usr/sbin/semodule
Thanks for the report. Adding Francesco.
On 26/05/16 08:43, "users-bounces@ovirt.org on behalf of Yedidyah Bar David" <users-bounces@ovirt.org on behalf of didi@redhat.com> wrote:
On Wed, May 25, 2016 at 9:11 PM, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Le 25 mai 2016 à 17:25, Kapetanakis Giannis <bilias@edu.physics.uoc.gr> a écrit :
On 25/05/16 17:59, Fabrice Bacchella wrote:
I have an dedicated machin to run ovirt-engine (not hosted). It's an up to date centos 7.2.1511
I installed ovirt 3.6.6 a few weeks ago (May 10 17:56:44 tells me yum.log)
Now, I'm trying a full yum update and getting : # yum update ....
Error: Package: ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) Requires: ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Removing: ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Updated By: ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6) ovirt-engine-tools-backup = 3.6.6.2-1.el7.centos
Follow 3.6.6 release notes to update: https://www.ovirt.org/release/3.6.6/
yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm yum update ovirt\*setup\* and then run engine-setup to update the rest of the packages.
I have seen this doc.
It updates a few components and what about the others ? The readme talk about running engine-setup, but not that it will updates other packages. I thought that ovirt-engine is for engine setup, not upgrading.
Right.
After engine-setup finishes, you should 'yum update' to update the rest.
And BTW, this specific issue about tools-backup was fixed in [1]. So a future 'yum update' should not emit this error - although the update sequence is still the same - add repos, update setup packages, engine-setup, update the rest.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 -- Didi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi
Il 26/Mag/2016 12:50, "Yedidyah Bar David" <didi@redhat.com> ha scritto:
On Thu, May 26, 2016 at 1:21 PM, Pavel Gashev <Pax@acronis.com> wrote:
I had an issue with updating to 3.6.6. There were errors during
[ ERROR ] Yum Non-fatal POSTUN scriptlet failure in rpm package
ovirt-vmconsole-1.0.0-1.el7.centos.noarch
[ ERROR ] Yum Transaction close failed: Traceback (most recent call
last): File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 778, in endTransaction self.processTransaction() File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 1064, in
engine-setup: processTransaction _('One or more elements within Yum transaction failed') RuntimeError: One or more elements within Yum transaction failed
ovirt-vmconsole has the following uninstall script: postuninstall scriptlet (using /bin/sh): if [ "$1" -ge "1" ]; then semodule -i
"/usr/share/selinux/packages/ovirt-vmconsole/ovirt_vmconsole.pp"
fi
In other words you can't update if you have SELINUX disabled.
The workaround is the following: ln -fs /bin/true /usr/sbin/semodule
Thanks for the report. Adding Francesco.
On 26/05/16 08:43, "users-bounces@ovirt.org on behalf of Yedidyah Bar
David" <users-bounces@ovirt.org on behalf of didi@redhat.com> wrote:
On Wed, May 25, 2016 at 9:11 PM, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Le 25 mai 2016 à 17:25, Kapetanakis Giannis <bilias@edu.physics.uoc.gr>
a
écrit :
On 25/05/16 17:59, Fabrice Bacchella wrote:
I have an dedicated machin to run ovirt-engine (not hosted). It's an up to date centos 7.2.1511
I installed ovirt 3.6.6 a few weeks ago (May 10 17:56:44 tells me yum.log)
Now, I'm trying a full yum update and getting : # yum update ....
Error: Package: ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) Requires: ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Removing: ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Updated By: ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6) ovirt-engine-tools-backup = 3.6.6.2-1.el7.centos
Follow 3.6.6 release notes to update: https://www.ovirt.org/release/3.6.6/
yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm yum update ovirt\*setup\* and then run engine-setup to update the rest of the packages.
I have seen this doc.
It updates a few components and what about the others ? The readme talk about running engine-setup, but not that it will updates other
Please open a bz on ovirt-vmconsole. packages. I
thought that ovirt-engine is for engine setup, not upgrading.
Right.
After engine-setup finishes, you should 'yum update' to update the rest.
And BTW, this specific issue about tools-backup was fixed in [1]. So a future 'yum update' should not emit this error - although the update sequence is still the same - add repos, update setup packages, engine-setup, update the rest.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 -- Didi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 26 May 2016, at 18:17, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il 26/Mag/2016 12:50, "Yedidyah Bar David" <didi@redhat.com> ha scritto:
On Thu, May 26, 2016 at 1:21 PM, Pavel Gashev <Pax@acronis.com> wrote:
I had an issue with updating to 3.6.6. There were errors during
[ ERROR ] Yum Non-fatal POSTUN scriptlet failure in rpm package
ovirt-vmconsole-1.0.0-1.el7.centos.noarch
[ ERROR ] Yum Transaction close failed: Traceback (most recent call
last): File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 778, in endTransaction self.processTransaction() File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 1064, in
engine-setup: processTransaction _('One or more elements within Yum transaction failed') RuntimeError: One or more elements within Yum transaction failed
ovirt-vmconsole has the following uninstall script: postuninstall scriptlet (using /bin/sh): if [ "$1" -ge "1" ]; then semodule -i
"/usr/share/selinux/packages/ovirt-vmconsole/ovirt_vmconsole.pp"
fi
In other words you can't update if you have SELINUX disabled.
The workaround is the following: ln -fs /bin/true /usr/sbin/semodule
Thanks for the report. Adding Francesco.
Please open a bz on ovirt-vmconsole.
Running with selinux disabled is not recommended nor supported. It should be easy to skip over that problem, but in general this is not something you should hit in normal environment Thanks, michal
On 26/05/16 08:43, "users-bounces@ovirt.org on behalf of Yedidyah Bar
David" <users-bounces@ovirt.org on behalf of didi@redhat.com> wrote:
On Wed, May 25, 2016 at 9:11 PM, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Le 25 mai 2016 à 17:25, Kapetanakis Giannis <bilias@edu.physics.uoc.gr>
écrit :
On 25/05/16 17:59, Fabrice Bacchella wrote:
I have an dedicated machin to run ovirt-engine (not hosted). It's an up to date centos 7.2.1511
I installed ovirt 3.6.6 a few weeks ago (May 10 17:56:44 tells me yum.log)
Now, I'm trying a full yum update and getting : # yum update ....
Error: Package: ovirt-engine-tools-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) Requires: ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Removing: ovirt-engine-tools-backup-3.6.5.3-1.el7.centos.noarch (@ovirt-3.6) ovirt-engine-tools-backup = 3.6.5.3-1.el7.centos Updated By: ovirt-engine-tools-backup-3.6.6.2-1.el7.centos.noarch (ovirt-3.6) ovirt-engine-tools-backup = 3.6.6.2-1.el7.centos
Follow 3.6.6 release notes to update: https://www.ovirt.org/release/3.6.6/
yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm yum update ovirt\*setup\* and then run engine-setup to update the rest of the packages.
I have seen this doc.
It updates a few components and what about the others ? The readme talk about running engine-setup, but not that it will updates other
a packages. I
thought that ovirt-engine is for engine setup, not upgrading.
Right.
After engine-setup finishes, you should 'yum update' to update the rest
Running with selinux disabled is not recommended nor supported. It should be easy to skip over that problem, but in general this is not something you should hit in normal environment
That's very theorical recommandation. selinux is very very often disabled, because nobody really understand it.
On 30 May 2016, at 14:57, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Running with selinux disabled is not recommended nor supported. It should be easy to skip over that problem, but in general this is not something you should hit in normal environment
That's very theorical recommandation. selinux is very very often disabled, because nobody really understand it.
It is not theoretical, it’s mandatory. there is an assumption it is enabled, after bare OS installation it is enabled, so when you disable it it is an explicit decision done by the admin for some reason. What did you find not working? Did you really encounter anything not being solved by setting Permissive mode instead disabling completely? Thanks, michal
Le 30 mai 2016 à 15:01, Michal Skrivanek <michal.skrivanek@redhat.com> a écrit :
On 30 May 2016, at 14:57, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Running with selinux disabled is not recommended nor supported. It should be easy to skip over that problem, but in general this is not something you should hit in normal environment
That's very theorical recommandation. selinux is very very often disabled, because nobody really understand it.
It is not theoretical, it’s mandatory. there is an assumption it is enabled, after bare OS installation it is enabled, so when you disable it it is an explicit decision done by the admin for some reason. What did you find not working? Did you really encounter anything not being solved by setting Permissive mode instead disabling completely?
What's the purpose of permissive ? if everything is allowed, what selinux is good for ? Instead of having something that run doing nothing, I shutdown it, and selinux is part of that generic policy. What is a bad practice is switching selinux on and off. So my installation setup is done with selinux down and stay so for the whole server life of the server. I never met a product that requisite selinux. And more, I just have a look at your administration guide (http://www.ovirt.org/documentation/admin-guide/administration-guide/) and quickstart guide (http://www.ovirt.org/documentation/quickstart/quickstart-guide/). selinux is never declared as mandatory. There is just a few tips about the problem that one can have with selinux.
On 30 May 2016, at 15:22, Fabrice Bacchella <fabrice.bacchella@icloud.com> wrote:
Le 30 mai 2016 à 15:01, Michal Skrivanek <michal.skrivanek@redhat.com> a écrit :
On 30 May 2016, at 14:57, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Running with selinux disabled is not recommended nor supported. It should be easy to skip over that problem, but in general this is not something you should hit in normal environment
That's very theorical recommandation. selinux is very very often disabled, because nobody really understand it.
It is not theoretical, it’s mandatory. there is an assumption it is enabled, after bare OS installation it is enabled, so when you disable it it is an explicit decision done by the admin for some reason. What did you find not working? Did you really encounter anything not being solved by setting Permissive mode instead disabling completely?
What's the purpose of permissive ? if everything is allowed, what selinux is good for ? Instead of having something that run doing nothing, I shutdown it, and selinux is part of that generic policy.
there is a difference between “no support for selinux” and “allowing everything”. Functionally it is different as e.g. labelling is not getting done when selinux is disabled, that’s why typically when you disable selinux, and install/change something those files do not have set up the context properly and when you enable selinux again things break completely (this bug is a different case)
What is a bad practice is switching selinux on and off. So my installation setup is done with selinux down and stay so for the whole server life of the server.
I never met a product that requisite selinux.
I’m not going to start a flamewar on selinux, there are plenty of those out there:) But oVirt is built with security in mind on a RHEL-based distro, so it uses SELinux. All I can say is that disabling SELinux is discouraged for security as well as functionality reasons.
And more, I just have a look at your administration guide (http://www.ovirt.org/documentation/admin-guide/administration-guide/) and quickstart guide (http://www.ovirt.org/documentation/quickstart/quickstart-guide/). selinux is never declared as mandatory. There is just a few tips about the problem that one can have with selinux.
yes, most things tend to work…until they don’t. You’ve just encountered the situation when it doesn’t work. It shall be fixed, but it is not at the moment. Thanks, michal
In my case oVirt is running in an OpenVZ container. Since selinux doesn't support namespaces, it's disabled. I don't want to fuel the holy war stopdisablingselinux.com vs selinuxsucks.com. Just please allow us to choose. Thanks. On 30/05/16 16:01, "users-bounces@ovirt.org on behalf of Michal Skrivanek" <users-bounces@ovirt.org on behalf of michal.skrivanek@redhat.com> wrote:
On 30 May 2016, at 14:57, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Running with selinux disabled is not recommended nor supported. It should be easy to skip over that problem, but in general this is not something you should hit in normal environment
That's very theorical recommandation. selinux is very very often disabled, because nobody really understand it.
It is not theoretical, it’s mandatory. there is an assumption it is enabled, after bare OS installation it is enabled, so when you disable it it is an explicit decision done by the admin for some reason. What did you find not working? Did you really encounter anything not being solved by setting Permissive mode instead disabling completely?
Thanks, michal
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 30 May 2016, at 15:35, Pavel Gashev <Pax@acronis.com> wrote:
In my case oVirt is running in an OpenVZ container. Since selinux doesn't support namespaces, it's disabled.
I don't want to fuel the holy war stopdisablingselinux.com vs selinuxsucks.com. Just please allow us to choose. Thanks.
yep, I guess it’s fair in experimental cases like yours. And you can skip over the ovirt-vmconsole deployment in engine-setup completely, so even when the bug is still here it shouldn’t affect you at all. It’s not about a choice, it’s about supportability and reasonable verification. Thanks, michal
On 30/05/16 16:01, "users-bounces@ovirt.org on behalf of Michal Skrivanek" <users-bounces@ovirt.org on behalf of michal.skrivanek@redhat.com> wrote:
On 30 May 2016, at 14:57, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Running with selinux disabled is not recommended nor supported. It should be easy to skip over that problem, but in general this is not something you should hit in normal environment
That's very theorical recommandation. selinux is very very often disabled, because nobody really understand it.
It is not theoretical, it’s mandatory. there is an assumption it is enabled, after bare OS installation it is enabled, so when you disable it it is an explicit decision done by the admin for some reason. What did you find not working? Did you really encounter anything not being solved by setting Permissive mode instead disabling completely?
Thanks, michal
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Mon, May 30, 2016 at 4:49 PM, Michal Skrivanek <michal.skrivanek@redhat.com> wrote:
On 30 May 2016, at 15:35, Pavel Gashev <Pax@acronis.com> wrote:
In my case oVirt is running in an OpenVZ container. Since selinux doesn't support namespaces, it's disabled.
I don't want to fuel the holy war stopdisablingselinux.com vs selinuxsucks.com. Just please allow us to choose. Thanks.
yep, I guess it’s fair in experimental cases like yours. And you can skip over the ovirt-vmconsole deployment in engine-setup completely, so even when the bug is still here it shouldn’t affect you at all. It’s not about a choice, it’s about supportability and reasonable verification.
I'll just note that generally speaking, we do fix such bugs, see e.g. [1]. So please open one and eventually it will be handled. Thanks. That said, we do work hard to make everything work with selinux enabled. If something in ovirt fails for you when it's enabled, and works if you disable selinux, that's a much higher priority bug. [1] https://bugzilla.redhat.com/show_bug.cgi?id=980042
Thanks, michal
On 30/05/16 16:01, "users-bounces@ovirt.org on behalf of Michal Skrivanek" <users-bounces@ovirt.org on behalf of michal.skrivanek@redhat.com> wrote:
On 30 May 2016, at 14:57, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
Running with selinux disabled is not recommended nor supported. It should be easy to skip over that problem, but in general this is not something you should hit in normal environment
That's very theorical recommandation. selinux is very very often disabled, because nobody really understand it.
It is not theoretical, it’s mandatory. there is an assumption it is enabled, after bare OS installation it is enabled, so when you disable it it is an explicit decision done by the admin for some reason. What did you find not working? Did you really encounter anything not being solved by setting Permissive mode instead disabling completely?
Thanks, michal
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi
participants (7)
-
Fabrice Bacchella -
Fabrice Bacchella -
Kapetanakis Giannis -
Michal Skrivanek -
Pavel Gashev -
Sandro Bonazzola -
Yedidyah Bar David