XCP-ng 8.3 betas and RCs feedback 🚀
-
can't install zabbix on 8.3.
yum install -y zabbix-agent2 zabbix-agent2-plugin-* Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Resolving Dependencies --> Running transaction check ---> Package zabbix-agent2.x86_64 0:7.0.3-release1.el7 will be installed --> Processing Dependency: libpcre2-8.so.0()(64bit) for package: zabbix-agent2-7.0.3-release1.el7.x86_64 ---> Package zabbix-agent2-plugin-ember-plus.x86_64 0:7.0.3-release1.el7 will be installed ---> Package zabbix-agent2-plugin-mongodb.x86_64 0:7.0.3-release1.el7 will be installed ---> Package zabbix-agent2-plugin-mssql.x86_64 0:7.0.3-release1.el7 will be installed ---> Package zabbix-agent2-plugin-postgresql.x86_64 0:7.0.3-release1.el7 will be installed --> Finished Dependency Resolution Error: Package: zabbix-agent2-7.0.3-release1.el7.x86_64 (zabbix) Requires: libpcre2-8.so.0()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
at 8.2 i only need to enable more repos, but 8.3 already use it own Vates mirror for Centos.
yum install pcre2 --enablerepo=epel,base,sources Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * epel: ftp-stud.hs-esslingen.de No package pcre2 available. Error: Nothing to do
-
@ph7 I don't see much changes which may lead to this result at first sight.
-
@Tristis-Oris said in XCP-ng 8.3 betas and RCs feedback :
yum install pcre2 --enablerepo=epel,base,sources
It is indeed missing. I must have missed something when I replicated the repository from CentOS vault.
-
Ok, I'm feeling dumb. I just mounted the guest tools ISO (hosts -> hostname -> console -> "select disk(s)" pulldown, select "guest-tools.iso") and I'm seeing kinda old versions of xe-guest-utilities (-2 instead of -12).
: || lvd@vm42 ~ [1023] ; ls -l /media/Linux/xe-guest-utilities*rpm
-r--r--r--. 1 root root 985556 Dec 11 2023 /media/Linux/xe-guest-utilities-7.30.0-2.i386.rpm
-r--r--r--. 1 root root 985384 Dec 11 2023 /media/Linux/xe-guest-utilities-7.30.0-2.legacy.i386.rpm
-r--r--r--. 1 root root 1246820 Dec 11 2023 /media/Linux/xe-guest-utilities-7.30.0-2.legacy.x86_64.rpm
-r--r--r--. 1 root root 1247000 Dec 11 2023 /media/Linux/xe-guest-utilities-7.30.0-2.x86_64.rpmWhen I do the same on my production 8.2.1 pool I see
: || lvd@chipmunkdev ~ [1000] ; ls -l /media/Linux/xe-guest-utilities*rpm
-r--r--r--. 1 root root 985488 Feb 7 2024 /media/Linux/xe-guest-utilities-7.30.0-12.i386.rpm
-r--r--r--. 1 root root 985308 Feb 7 2024 /media/Linux/xe-guest-utilities-7.30.0-12.legacy.i386.rpm
-r--r--r--. 1 root root 1246760 Feb 7 2024 /media/Linux/xe-guest-utilities-7.30.0-12.legacy.x86_64.rpm
-r--r--r--. 1 root root 1246948 Feb 7 2024 /media/Linux/xe-guest-utilities-7.30.0-12.x86_64.rpmShould I be looking somewhere else for the most recent xe-guest-utilities?
-
@stormi said in XCP-ng 8.3 betas and RCs feedback :
@ph7 I don't see much changes which may lead to this result at first sight.
Same alert today with commit 63a88
Should I report this in Home / Xen Orchestra / Backup ? -
@ph7 If you can test with an older version of XO and see if the issue is still present, this might help understanding whether it's an XO issue or not. But I think you can also already create a dedicated topic where XO devs can tell if they see what this could be.
-
@nomad Good point!
So, they are the same tools (8.2 got the update later, based on that of 8.3), but the version is defined in a peculiar way (based on the release of the RPM, which I mistakingly re-initialized to 1 on XCP-ng 8.3). I'll fix this, but you can already use them if you need them.
-
@stormi If it's the exact same thing just with a different version number I can wait for a future update. I already have the -12 RPM in my yum repo for automatic install on all VMs.
I was looking to see if there was any notable changes from what we already had as well to see if an icon for AlmaLinux would show up in the home -> VMs list (everything else has an icon showing the OS running on the VM, just poor Alma is left all alone at the display ball.)
-
@nomad There are two key players in this icon thing: the guest tools who report the OS name (this already works), and then Xen Orchestra matching this to an icon. In Xen Orchestra 5, the icon set is not easy to expand, so the developers said this would be done in XO 6.
-
@stormi I'm glad to know I was slightly right about some of the way it works anyway.