+CC Jiri as our libvirt expert.

On Wed, Jun 9, 2021 at 10:12 AM Eduardo Lima <el...@redhat.com> wrote:

>
>
> On Wed, Jun 9, 2021 at 11:06 AM Eduardo Lima <el...@redhat.com> wrote:
>
>>
>>
>> On Wed, Jun 9, 2021 at 4:33 AM Sandro Bonazzola <sbona...@redhat.com>
>> wrote:
>>
>>> thanks for the report, looping in +Eduardo Lima <etru...@redhat.com>
>>>  and +Danilo Cesar Lemes de Paula <ddepa...@redhat.com> .
>>> Eduardo, Danilo, can you get selinux policy quickly fixed? If not it's
>>> probably better to retire the libvirt build to avoid further breakages.
>>>
>>>
>> I donĀ“t  think so, as it is not a problem with our packages.
>> Unfortunately this is something that is expected right? As far as I
>> remember this is one of the major complaints with the CentOS Stream model,
>> breakage can happen every now and then. There is no way to ensure stability
>> of the packages there. For the tested and stable versions, we have the
>> CentOS Virt SIG.
>>
>>
> By the way, it does look like downgrading libvirt version will solve the
> problem, as discussed on the bug:
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1966842
>
>
>>
>>> Eduardo, next time please wait to get test results before tagging to
>>> release:
>>> Tue Jun  8 14:47:42 2021 libvirt-7.4.0-1.el8s tagged into
>>> virt8s-advancedvirt-common-candidate by etrunko [still active]
>>> Tue Jun  8 16:21:14 2021 libvirt-7.4.0-1.el8s tagged into
>>> virt8s-advancedvirt-common-testing by etrunko [still active]
>>> Tue Jun  8 16:21:17 2021 libvirt-7.4.0-1.el8s tagged into
>>> virt8s-advancedvirt-common-release by etrunko [still active]
>>>
>>> we can get you feedback in few hours from oVirt CI consuming the test
>>> builds
>>>
>>>
>> Okay, I will send you guys a heads up whenever I have a new build out. I
>> usually run CentOS Stream SIG updates on Fridays.
>>
>>
>>
>>>
>>>
>>> Il giorno mar 8 giu 2021 alle ore 21:15 Klaas Demter <
>>> klaasdem...@gmail.com> ha scritto:
>>>
>>>> Hi,
>>>>
>>>> I updated packages on my system today and ovirt is no longer starting,
>>>> turns out this is happening because of a selinux denial for a new
>>>> feature of libvirt-7.4.0-1.el8s.x86_64
>>>>
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1966842
>>>>
>>>> a workaround is suggested in the ticket or you can set selinux to
>>>> permissive until selinux-policy is updated.
>>>>
>>>>
>>>> Greetings
>>>>
>>>> Klaas
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list -- users@ovirt.org
>>>> To unsubscribe send an email to users-le...@ovirt.org
>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>>> oVirt Code of Conduct:
>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/OK4SLP7DC27FOKRHTHMTXLTB4BABRIMB/
>>>>
>>>
>>>
>>> --
>>>
>>> Sandro Bonazzola
>>>
>>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>>>
>>> Red Hat EMEA <https://www.redhat.com/>
>>>
>>> sbona...@redhat.com
>>> <https://www.redhat.com/>
>>>
>>> *Red Hat respects your work life balance. Therefore there is no need to
>>> answer this email out of your office hours.*
>>>
>>>
>>> As Eduardo said: this is not a libvirt issue.
It's also affecting the development internally. As far as I understand, if
we didn't update libvirt this week we would still have the issue.

Anway, just follow BZ#1966842
<https://bugzilla.redhat.com/show_bug.cgi?id=1966842> for a heads up on a
solution. Personally, I'm also blocked by this.

-- 
Danilo Cesar Lemes de Paula
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HBKD2OB53A5REJOZZVAPMVKTSD7Y2LPS/

Reply via email to