Hi,

just for info, recently I have migrated two ovirt 4.4.8 installations to Rocky Linux 8.5. Everything went smoothly and it was as simple as

curl https://raw.githubusercontent.com/rocky-linux/rocky-tools/main/migrate2rocky/migrate2rocky.sh -o migrate2rocky.sh
chmod u+x migrate2rocky.sh
./migrate2rocky.sh -r

on hosts and after that the same on HE (in my case also with upgrade to 4.4.9)

One of these systems was HCI and everything looks good.

Happy new year to all of oVirt (and Gluster, CentOS, Rocky,...) teams ;-)

Cheers, Jiri


On 11/9/21 09:46, Jiří Sléžka wrote:
Hi,

On 11/8/21 21:38, Christoph Timm wrote:
Hi Gianluca,

I have a self hosted platform with plain CentOS 8.4 host. Also my engine is currently running CentOS 8.4.
I updated my whole system from 4.4.7 to 4.4.9.

As 4.4.9 does not support CentOS hosts I had to migrate them to CentOS Stream 8 as well. Due to dependency issues I have put the host into maintenance mode and did the rest through CLI.

# dnf swap centos-linux-repos centos-stream-repos
# dnf update ovirt-release44
# dnf distro-sync
# reboot
Done

Thanks for this. I think this should be documented better because it confuses me a bit.

I run small HCI cluster on CentOS8.4 hosts and would like to know valid migration paths. Sure, one is CentOS Strem. Is onother one RHEL 8.4? It looks like not (from release notes for 4.4.9: "This release is available now for Red Hat Enterprise Linux 8.5 Beta (or similar) and CentOS Stream"). Did anybody even try migrate CentOS hosts to Rocky Linux?

In this case I prefer to migrate to stabe RHEL clone distro and stay a bit behind oVirt releases.

What is your opinion, does it make sense?

Thanks in advance,

Jiri


I did not change the engine OS aa CentOS 8.4 is still supported here.

Also I did the update in multiple steps over a couple of days which did not cause any issue on my side.

Hope this helps.

Best regards
Christoph

Am 08.11.21 um 13:41 schrieb Gianluca Cecchi:
I have a lab with an environment based on 4.4.8.6-1, with 3 CentOS Linux 8.4 hosts and a CentOS 8.4 external engine system (that is a VM on vSphere, so that I can leverage a snapshot methodology for the process...). I would like to pass to 4.4.9 and retain a full plain OS on hosts for the moment, without going through oVirt nodes, but standing the repo problems and CentOS 8.x going through EOL this is what I'm planning to do:

1. stop engine service on engine system

2. convert engine to CentOS Stream
This step needs some confirmation.
Could you provide an official link about the process?
I'm not able to find it again. Is it a problem of mine or all (CentOS website, RHEL website) seem to point only to conversion from CentOS Linux to RHEL?? Apart external websites provided workflows, I was only able to find a mid January youtube video, when CentOS was based on 8.3, with these steps:
yum install centos-release-stream
yum swap centos-{linux,stream}-repos
yum repolist
yum distro-sync
reboot
The video link is here:
https://www.youtube.com/watch?v=Ba2ytp_8x7s

No mention at
https://www.redhat.com/en/blog/faq-centos-stream-updates

And on CentOS page I only found this:
https://centos.org/distro-faq/
with Q7 containing only the two instructions:
dnf swap centos-linux-repos centos-stream-repos
dnf distro-sync

What to use safely?
Is it possible to include some sort of documentation or links on oVirt page, to migrate from CentOS Linux to CentOS Stream for oVirt upgrade purposes?

3. After reboot implied, I think, in step 2., use the usual steps to update engine to 4.4.9

4. update the first out of three hosts from CentOS Linux to CentOS Stream and to 4.4.9.

4.a follow the same approach of engine (when defined) and pass it to Stream retaining the 4.4.8.
4.b upgrade from the web admin gui to 4.4.9

5. Do the same for second host and third hosts

Any hints, comments, limitations in having mixed 4.4.8 and 4.4.9 hosts for a while and such?

Thanks,
Gianluca



_______________________________________________
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-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/L3CRTNR2IUGNRZNVQMROQABHHBKMEYPP/


_______________________________________________
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/RGF6HG7LSJOYTV3AVYK4VP7HPQ4UAK2A/



_______________________________________________
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/V6CZM33TTWB6ZFML4JN67MG3KQ455FNB/


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
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/DRGINS7I55FX77UGXRWIVPLHNE6U7HLK/

Reply via email to