Re: [ovirt-users] Upgrade hypervisor to 4.1.1.1
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 , 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 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 :
> > > > > restorecon on virtlogd.conf would be enough
> > > > >
> > > > > > On Apr 10, 2017 2:51 PM, "Misak Khachatryan"
> > > > > > 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
> > > > > > > > wrote:
> > > > > > > > > Can you please provide a full sos report from that host?
> > > > > > > > >
> > > > > > > > > > On Sun, Apr 9, 2017 at 8:38 PM, Sandro Bonazzola
> > > > > > > > > > wrote:
> > > > > > > > > > > Adding node team.
> > > > > > > > > > >
> > > > > > > > > > > > Il 09/Apr/2017 15:43, "eric stam" 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
> rba...@redhat.com M: +1-651-815-9306 IM: rbarry
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade hypervisor to 4.1.1.1
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 :
> restorecon on virtlogd.conf would be enough
>
> On Apr 10, 2017 2:51 PM, "Misak Khachatryan" 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
>> wrote:
>>
>>> Can you please provide a full sos report from that host?
>>>
>>> On Sun, Apr 9, 2017 at 8:38 PM, Sandro Bonazzola
>>> wrote:
>>>
Adding node team.
Il 09/Apr/2017 15:43, "eric stam" 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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade hypervisor to 4.1.1.1
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 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 :
>
>> restorecon on virtlogd.conf would be enough
>>
>> On Apr 10, 2017 2:51 PM, "Misak Khachatryan" 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
>>> wrote:
>>>
Can you please provide a full sos report from that host?
On Sun, Apr 9, 2017 at 8:38 PM, Sandro Bonazzola
wrote:
> Adding node team.
>
> Il 09/Apr/2017 15:43, "eric stam" 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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade hypervisor to 4.1.1.1
On Mon, Apr 10, 2017 at 2:11 PM, eric stam 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 :
>
>> restorecon on virtlogd.conf would be enough
>>
>> On Apr 10, 2017 2:51 PM, "Misak Khachatryan" 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
>>> wrote:
>>>
Can you please provide a full sos report from that host?
On Sun, Apr 9, 2017 at 8:38 PM, Sandro Bonazzola
wrote:
> Adding node team.
>
> Il 09/Apr/2017 15:43, "eric stam" 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
>
--
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
Re: [ovirt-users] Upgrade hypervisor to 4.1.1.1
restorecon on virtlogd.conf would be enough
On Apr 10, 2017 2:51 PM, "Misak Khachatryan" 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
> wrote:
>
>> Can you please provide a full sos report from that host?
>>
>> On Sun, Apr 9, 2017 at 8:38 PM, Sandro Bonazzola
>> wrote:
>>
>>> Adding node team.
>>>
>>> Il 09/Apr/2017 15:43, "eric stam" 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
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade hypervisor to 4.1.1.1
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
wrote:
> Can you please provide a full sos report from that host?
>
> On Sun, Apr 9, 2017 at 8:38 PM, Sandro Bonazzola
> wrote:
>
>> Adding node team.
>>
>> Il 09/Apr/2017 15:43, "eric stam" 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
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Upgrade hypervisor to 4.1.1.1
Can you please provide a full sos report from that host?
On Sun, Apr 9, 2017 at 8:38 PM, Sandro Bonazzola
wrote:
> Adding node team.
>
> Il 09/Apr/2017 15:43, "eric stam" 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
Re: [ovirt-users] Upgrade hypervisor to 4.1.1.1
Adding node team.
Il 09/Apr/2017 15:43, "eric stam" 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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] 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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
