OpenVZ Forum


Home » General » Support » almaconvert8 no longer converts to almalinux
almaconvert8 no longer converts to almalinux [message #53878] Sat, 08 March 2025 17:58 Go to next message
wsap is currently offline  wsap
Messages: 81
Registered: March 2018
Location: Halifax, NS
Member
I have no idea if any of the Virtuozzo devs even look here anymore, but on the off chance they do (and since we can no longer report bugs to the OpenVZ bug tracker):

The almaconvert8 utility no longer successfully converts to AlmaLinux - it takes the container to Virtuozzo Linux 8, and upgrades all vl8 packages, and stops there Sad

This is when running it with the following environment:

- Freshly installed CentOS 7 from ez template on a totally new test container
- Host Node running OpenVZ release 7.0.22 (123) [all packages updated]
- Kernel: 3.10.0-1160.105.1.vz7.214.3
- vzdeploy8-1.1.6-2.vz7.noarch


Re: almaconvert8 no longer converts to almalinux [message #53879 is a reply to message #53878] Sun, 09 March 2025 15:35 Go to previous message
wsap is currently offline  wsap
Messages: 81
Registered: March 2018
Location: Halifax, NS
Member
From what I have gathered, /bin/almadeploy8_ct is supposed to remove vzlinux-release then install almalinux-release via vzpkg (line 134) however either almalinux-release is now aliased TO vzlinux-release or it's falling back to it because vzpkg no longer has almalinux packages available to it (perhaps because the 8.9 repos are now replaced by 8.10 and they haven't synced them?).

The solution is running what is essentially the same changes as above manually *after* almaconvert8 switches the container from centos7 to vzlinux8:

            vzctl exec $CTID rpm -e vzlinux-release --nodeps
            vzctl exec $CTID rpm -Uvh http://mirror.its.dal.ca/almalinux/8.10/BaseOS/x86_64/os/Packages/almalinux-release-8.10-1.el8.x86_64.rpm
            vzctl exec $CTID yum -y update
            # Swap all vl8 packages for al8 packages
            vzctl exec $CTID yum -y distro-sync --disablerepo=epel

Note: you probably want to replace that mirror URL with one closer to you.

Unrelated, but odd: almadeploy8_ct also has a call to a non-existent binary on line 140: /usr/bin/almadeploy8

I suspect devs never noticed because the conditional never branches to there, but I attempted to run it without nonetwork, and that's why I hit it. Obviously it doesn't do anything because the binary it calls does not exist.
Previous Topic: Openvz7 Ubuntu 24 template
Next Topic: Unable to migrate container
Goto Forum:
  


Current Time: Fri May 09 07:21:10 GMT 2025

Total time taken to generate the page: 0.05290 seconds