[ovirt-users] Upgrade hypervisor to 4.1.1.1

[eric stam]

All,

Problem solved.

I executed the “ restorecon -Rv /etc/ “ command. and the problem is solved.
The other question, execute "semodule -DB “ will give no return of any massage.

Everything is up an running again.

Regards,
Eric


On 10 Apr 2017, 16:10 +0200, Ryan Barry <rbarry at redhat.com>, wrote:
> Hey Eric -
>
> It's possible that there are some silent denials in some policy. Can you please try "semodule -DB" to see if anything pops up?
>
> I'll also try to reproduce this...
>
> > On Mon, Apr 10, 2017 at 5:11 AM, eric stam <estam at indm.nl> wrote:
> > > We are on the good way.
> > > I first put SELinux in permissive mode, and now it is possible to start virtual machine's.
> > >
> > >
> > > I will test the "restorecon" next.
> > >
> > > Regards,
> > > Eric
> > >
> > > > 2017-04-10 14:00 GMT+02:00 Yuval Turgeman <yuvalt at redhat.com>:
> > > > > restorecon on virtlogd.conf would be enough
> > > > >
> > > > > > On Apr 10, 2017 2:51 PM, "Misak Khachatryan" <kmisak at gmail.com> wrote:
> > > > > > > Is it node setup? Today i tried to upgrade my one node cluster, after that VM's fail to start, it turns out that selinux prevents virtlogd to start.
> > > > > > >
> > > > > > > ausearch -c 'virtlogd' --raw | audit2allow -M my-virtlogd
> > > > > > > semodule -i my-virtlogd.pp
> > > > > > > /sbin/restorecon -v /etc/libvirt/virtlogd.conf
> > > > > > >
> > > > > > > fixed things for me, YMMV.
> > > > > > >
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Misak Khachatryan
> > > > > > >
> > > > > > > > On Mon, Apr 10, 2017 at 2:03 PM, Sandro Bonazzola <sbonazzo at redhat.com> wrote:
> > > > > > > > > Can you please provide a full sos report from that host?
> > > > > > > > >
> > > > > > > > > > On Sun, Apr 9, 2017 at 8:38 PM, Sandro Bonazzola <sbonazzo at redhat.com> wrote:
> > > > > > > > > > > Adding node team.
> > > > > > > > > > >
> > > > > > > > > > > > Il 09/Apr/2017 15:43, "eric stam" <estam at indm.nl> ha scritto:
> > > > > > > > > > > > > Yesterday I executed an upgrade on my hypervisor to version 4.1.1.1
> > > > > > > > > > > > > After the upgrade, it is impossible to start a virtual machine on it.
> > > > > > > > > > > > > The messages I found: Failed to connect socket to '/var/run/libvirt/virtlogd-sock': Connection refused
> > > > > > > > > > > > >
> > > > > > > > > > > > > [root at vm-1 log]# hosted-engine --vm-status | grep -i engine
> > > > > > > > > > > > > Engine status                      : {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "down"}
> > > > > > > > > > > > > state=EngineUnexpectedlyDown
> > > > > > > > > > > > >
> > > > > > > > > > > > > The redhead version: CentOS Linux release 7.3.1611 (Core)
> > > > > > > > > > > > >
> > > > > > > > > > > > > Is this a known problem?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Regards, Eric
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > > Users mailing list
> > > > > > > > > > > > > Users at ovirt.org
> > > > > > > > > > > > > http://lists.ovirt.org/mailman/listinfo/users
> > > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > SANDRO BONAZZOLA
> > > > > > > > > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
> > > > > > > > > Red Hat EMEA
> > > > > > > > > TRIED. TESTED. TRUSTED.
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > Users mailing list
> > > > > > > > > Users at ovirt.org
> > > > > > > > > http://lists.ovirt.org/mailman/listinfo/users
> > > > > > > > >
> > > > > > >
> > >
> > >
> > >
> > > --
> > > Gr. Eric Stam
> > > Mob.: 06-50278119
>
>
>
> --
> RYAN BARRY
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR
> Red Hat NA
> rbarry at redhat.com    M: +1-651-815-9306     IM: rbarry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170410/f0ab7e1e/attachment.html>