I can confirm that all of the repos work for Rocky now. I was a little worried when I saw 98 packages to be updated, but then I looked at the versions and most were just changing the package tag from .el8 to .el8s. collectd was the only thing actually updated to a new version.

I do worry about the long term with stream repos, it seems like there could be compatibility issues down the road when stream is closer to 8.6 than 8.5.

Just for the record, I haven't tried to do a clean install on Rocky yet, just converted existing hosts from CentOS. I suppose if the installation is still broken, I can always install CentOS, install the host, and then convert it to Rocky.

On Tue, 1 Feb 2022, Lev Veyde 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 <[email protected]> wrote:


Il giorno lun 31 gen 2022 alle ore 21:17 Thomas Hoberg
<[email protected]> 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&gt; wrote:
      _______________________________________________
      Users mailing list -- [email protected]
      To unsubscribe send an email to [email protected]
      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/[email protected]/message/MZTD4JSDLSVQ7
      XBSRCQF4PFRPHJYCVQT/



--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

[email protected]   

[logo--200.png]
Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.


_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/D7KAW7Q45PJYW
SHWBKBGTSNQYOUDESPQ/



--

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel

[email protected] | [email protected]

[logo-red-hat-black.png] TRIED. TESTED. TRUSTED.

_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/S3SQG7AHGJRNB2RSAAJ5AOSQPSI2DM4P/

Reply via email to