Upgrade hypervisor to 4.1.1.1
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@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
Adding node team. Il 09/Apr/2017 15:43, "eric stam" <estam@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Can you please provide a full sos report from that host? On Sun, Apr 9, 2017 at 8:38 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Adding node team.
Il 09/Apr/2017 15:43, "eric stam" <estam@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
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@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@redhat.com> wrote:
Adding node team.
Il 09/Apr/2017 15:43, "eric stam" <estam@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
restorecon on virtlogd.conf would be enough On Apr 10, 2017 2:51 PM, "Misak Khachatryan" <kmisak@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@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@redhat.com> wrote:
Adding node team.
Il 09/Apr/2017 15:43, "eric stam" <estam@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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@redhat.com>:
restorecon on virtlogd.conf would be enough
On Apr 10, 2017 2:51 PM, "Misak Khachatryan" <kmisak@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@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@redhat.com> wrote:
Adding node team.
Il 09/Apr/2017 15:43, "eric stam" <estam@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Gr. Eric Stam *Mob*.: 06-50278119
On Mon, Apr 10, 2017 at 2:11 PM, eric stam <estam@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.
the strange thing here is that the sosreport Eric provided showed no selinux denials in ausearch -m avc output. If it's selinux, it's tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1434816
Regards, Eric
2017-04-10 14:00 GMT+02:00 Yuval Turgeman <yuvalt@redhat.com>:
restorecon on virtlogd.conf would be enough
On Apr 10, 2017 2:51 PM, "Misak Khachatryan" <kmisak@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@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@redhat.com> wrote:
Adding node team.
Il 09/Apr/2017 15:43, "eric stam" <estam@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Gr. Eric Stam *Mob*.: 06-50278119
-- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
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@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@redhat.com>:
restorecon on virtlogd.conf would be enough
On Apr 10, 2017 2:51 PM, "Misak Khachatryan" <kmisak@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@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@redhat.com> wrote:
Adding node team.
Il 09/Apr/2017 15:43, "eric stam" <estam@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@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
_______________________________________________ Users mailing list Users@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 <https://www.redhat.com/> rbarry@redhat.com M: +1-651-815-9306 IM: rbarry <https://red.ht/sig>
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@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@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@redhat.com>:
restorecon on virtlogd.conf would be enough
On Apr 10, 2017 2:51 PM, "Misak Khachatryan" <kmisak@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@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@redhat.com> wrote: > > > > > Adding node team. > > > > > > > > > > > Il 09/Apr/2017 15:43, "eric stam" <estam@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@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@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@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@redhat.com M: +1-651-815-9306 IM: rbarry
participants (5)
-
eric stam -
Misak Khachatryan -
Ryan Barry -
Sandro Bonazzola -
Yuval Turgeman