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 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.
>

Please open a bz on ovirt-vmconsole.

> >
> >
> > 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
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users