I am getting update failures for ovirt-node as well because of this.Is there any kind of work around or do I need to manually edit ovirt-4.4-dependencies.repo on every host to point to the vault?Thanks.Regards,Ryan Bullock_______________________________________________On Tue, Feb 1, 2022 at 5:19 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:_______________________________________________Il giorno mar 1 feb 2022 alle ore 13:45 Ayansh Rocks <shashank123rastogi@gmail.com> ha scritto:Thanks Lev, I hope it will work on Alma.It passes repository closure on Alma but we lack resources to actively testing it there.RegardsAyansh RocksOn Tue, Feb 1, 2022 at 4:01 PM Lev Veyde <lveyde@redhat.com> wrote:Hi,We just released a new version of the ovirt-release package that includes this temporary vault fix (4.4.10.1).Thanks in advance,On Tue, Feb 1, 2022 at 9:31 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:_______________________________________________Il giorno lun 31 gen 2022 alle ore 21:17 Thomas Hoberg <thomas@hoberg.net> ha scritto:> Hi Emilio,
>
> Yes, looks like the patch that should fix this issue is already here:
> https://github.com/oVirt/ovirt-release/pull/93 , but indeed it still hasn't
> been reviewed and merged yet.Hi, the patch has not been merged yet because the OpsTools repo for CentOS Stream has not been yet populated by the OpsTools SIG.I contacted the chair of the SIG last week but he was on PTO and returning only this week.As a temporary solution you can redirect the repositories to the vault: https://vault.centos.org/8.5.2111/>
> I hope that we'll have a fixed version very soon, but meanwhile you can try
> to simply apply the changes manually in your *testing* env.
So I did, but I can't help wondering: how well will code tested against "stream" work on RHEL, Alma, Rocky, Liberty, VzLinux?
How well will an engine evidently built on "stream" work with hosts based on RHEL etc.?
Shouldn't you in fact switch the engine to RHEL etc., too?
>
> Thanks in advance,
>
> On Mon, Jan 31, 2022 at 8:05 PM Emilio Del Plato <ehdeec(a)rit.edu> wrote:
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/MZTD4JSDLSVQ7XBSRCQF4PFRPHJYCVQT/
--Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/D7KAW7Q45PJYWSHWBKBGTSNQYOUDESPQ/
----Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/TLQY36AZGZZTZKG2OZDJOF6CTYX4F6Z2/
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/TSLID6S66IU5NOFGGVYMHLSKI6LWDX5T/