[SOLVED] [BUG] Problems with LXC after CentOS update to 8.4

rickyo

Active Member
Oct 21, 2015
25
17
43
Hi,

this is another shoutout to make you aware of problems after an OS-upgrade.


It seems CentOS 8 replaces the centos-release file when upgrading to 8.4.

Package Architecture Version Repository Size
========================================================================================================================================================================
Installing:
centos-stream-release noarch 8.4-1.el8 Stream-BaseOS 21 k
replacing centos-release.x86_64 8.2-2.2004.0.1.el8
replacing centos-release-stream.x86_64 8.3-3.2006.0.1.el8
replacing centos-repos.x86_64 8.2-2.2004.0.1.el8


Installing dependencies:
centos-stream-repos noarch 8-1.el8 Stream-BaseOS 19 k

The problem is that /etc/redhat-release changes from the format 8.x to "CentOS Stream release 8",

In /usr/share/perl5/PVE/LXC/Setup/CentOS.pm the release-check is for 8.x and without a dot in the versionnumber it bugs out and don't want to start the container.

my $version;


if ($release =~ m/release\s+(\d+\.\d+)(\.\d+)?/) {
if ($1 >= 5 && $1 <= 9) {
$version = $1;
}
}


die "unsupported centos release '$release'\n" if !$version;

Now, either we stop using the /etc/redhat-release file for versioning and use /etc/os-release, which should be common to all major distros now, or we will continue having the same problems more or less with them all.

BTW, the quick fix is to add ".4" after the 8 in /etc/redhat-release.


Just my 2 cents!

Rickard Osser
 
Last edited:
Are you sure you run latest Proxmox VE?

Post your:

> pveversion -v
 
pveversion -v
proxmox-ve: 6.2-2 (running kernel: 5.4.65-1-pve)
pve-manager: 6.2-12 (running version: 6.2-12/b287dd27)
pve-kernel-5.4: 6.2-7
pve-kernel-helper: 6.2-7
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-23-pve: 4.15.18-51
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.17-1-pve: 4.15.17-9
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-9
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.0-1
proxmox-backup-client: 0.9.1-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.3-1
pve-cluster: 6.2-1
pve-container: 3.2-2
pve-docs: 6.2-6
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-1
pve-qemu-kvm: 5.1.0-3
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-15
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve2

And

pveversion -v
proxmox-ve: 6.2-2 (running kernel: 5.4.65-1-pve)
pve-manager: 6.2-15 (running version: 6.2-15/48bd51b6)
pve-kernel-5.4: 6.2-7
pve-kernel-helper: 6.2-7
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-7-pve: 4.15.18-27
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.17-1-pve: 4.15.17-9
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-9
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.0-1
proxmox-backup-client: 0.9.4-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.3-6
pve-cluster: 6.2-1
pve-container: 3.2-2
pve-docs: 6.2-6
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-4
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-18
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve2


Tested on both machines! :)


Best regards,
Rickard
 
Tom, I know...

This was an an LXC installed with the standard template and a regular "dnf update", it seems CentOS is moving all over to the rolling stream release by obsoleteing the old centos-release package.

Just happend the other day.

Name : centos-stream-release
Version : 8.4
Release : 1.el8
Architecture: noarch
Install Date: tor 19 nov 2020 15:16:21
Group : Unspecified
Size : 25312
License : GPLv2
Signature : RSA/SHA256, tor 29 okt 2020 20:12:52, Key ID 05b555b38483c65d
Source RPM : centos-stream-release-8.4-1.el8.src.rpm
Build Date : tor 29 okt 2020 20:10:17
Build Host : ppc64le-02.mbox.centos.org
Relocations : (not relocatable)
Packager : CentOS Buildsys <bugs@centos.org>
Vendor : CentOS
URL : https://centos.org
Summary : CentOS Stream release files

The following is an excerpt from the dnf.rpm.log:
2020-11-18T20:16:25Z SUBDEBUG Installed: centos-stream-release-8.4-1.el8.noarch
2020-11-18T20:16:25Z SUBDEBUG Installed: centos-stream-release-8.4-1.el8.noarch
2020-11-18T20:18:41Z SUBDEBUG Obsoleted: centos-release-stream-8.0-0.1905.0.9.el8.x86_64
2020-11-18T20:18:41Z SUBDEBUG Obsoleted: centos-release-stream-8.0-0.1905.0.9.el8.x86_64
2020-11-18T20:18:54Z SUBDEBUG Obsoleted: centos-release-8.0-0.1905.0.9.el8.x86_64
2020-11-18T20:18:54Z SUBDEBUG Obsoleted: centos-release-8.0-0.1905.0.9.el8.x86_64
2020-11-19T15:16:21Z SUBDEBUG Reinstall: centos-stream-release-8.4-1.el8.noarch
2020-11-19T15:16:21Z SUBDEBUG Reinstalled: centos-stream-release-8.4-1.el8.noarch

So you can see they are forcing centos-stream-release as an update to centos-release and centos-release-stream.x86_64 8.3-3.2006.0.1.el8 which are standard in
the template.

Best regards,

Ricakrd
 
Tom, I know...

This was an an LXC installed with the standard template and a regular "dnf update",
I just did a clean install of our template and a dnf update did NOT move to 8.4.
 
Tom,

You're right, I inherited the LXC and saw that the centos-release-stream package was installed as 7th command, I'm checking with my colleague why he did that.
Anyway, there is nothing wrong with supporting rolling-release version which is a full CentOS-release as well.

/etc/os-release is also a great idea to use as all distros use it to publish distro-info.

Just my 2 cents.

Thanks,

RIckard
 
Hi Tom,

it seem an update is pending that fixes this.

Thanks for your attention.

Rickard
 

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!