unsupported centos release 'CentOS Stream release 8' (with fix)

adreyer

New Member
Oct 13, 2020
2
0
1
The LXC hook scripts do not recognize the numbering scheme for Stream releases. There is a simple fix:

Code:
root@pve:~# pveversion
pve-manager/6.2-12/b287dd27 (running kernel: 5.4.65-1-pve)


Perl:
root@pve:~# diff -u /usr/share/perl5/PVE/LXC/Setup/CentOS.pm{.orig,}
--- /usr/share/perl5/PVE/LXC/Setup/CentOS.pm.orig       2020-09-22 08:54:10.000000000 +0000
+++ /usr/share/perl5/PVE/LXC/Setup/CentOS.pm    2020-10-13 11:04:59.980313071 +0000
@@ -19,7 +19,7 @@
 
     my $version;
 
-    if ($release =~ m/release\s+(\d+\.\d+)(\.\d+)?/) {
+    if ($release =~ m/release\s+(\d+)(\.\d+)?(\.\d+)?/) {
        if ($1 >= 5 && $1 <= 9) {
            $version = $1;
        }
 
History:
I had some LXC containers build with CentOS8, added the Stream repositories and updated all packages. Rebooted the container from within and everything was running fine for quite some time.
I have updated proxmox/PVE a few times without rebooting the host or the containers. Today I had a power outage and when trying to start up all containers, those running CentOS Stream (release 8) failed to start. Digging into it I found that the Stream release was not detected and a look at the code showed that only release numbers with one or two dots are recognized as valid. However, Stream releases only have the major version number.

Patch sent to the devel list.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!