Discuss March 2024

discuss@lists.centos.org

9 participants
11 discussions

SSD for Centos SWAP /tmp & /var/ partition
by Keith Roberts 03 Sep '25

03 Sep '25

Has anyone actually used a SSD in a Centos setup? My little experiment with a s/h WD drive for /tmp and SWAP partitions kicked the bucket on Wednesday, when the poor WD drive caught the click-of-death. It was a s/h drive to start with and lasted about 4 months. But that was without the /var/log/ partition being written to it, as I mounted that back onto /var/log from the original drive. So I had to install another (WD) drive, and repartion it and rebuild my RPM package database, from the backed-up Packages file. That seems to be all OK now. I'm wondering if it would be a good idea to use a new SSD for moving all the disk i/o to, that Linux likes to do so often. Plus putting SWAP onto a decent SSD should speed things up somewhat. Here's a short video of a laptop fitted with a SSD drive booting macOS, compared to a similar laptop booting from the standard HDD. The laptop with the SSD boots and loads some apps in 28 seconds. The other one takes twice as long. http://eshop.macsales.com/shop/SSD/OWC/Mercury_Extreme_Pro_6G/?utm_source=t… Kind Regards, Keith Roberts ----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------

33 96

Problems with CentOS 8 kickstart
by Hooton, Gerard 23 Jun '25

23 Jun '25

Hi All, I am having problems with a kickstart install of CentOS 8 When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file. Then I see the following message "kickstart install Started cancel waiting for multipath siblings for nvme0n1" This is what I have in the kickstart file # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel autopart --nohome --type=lvm --fstype=xfs ================ When I install from a USB drive it works OK and I have the following in /dev/disk/by-id lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1 lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 lvm-pv-uuid-5Dg4mg-saHa-hJJ6-n5a8-MxBS-gdFi-5jPoNn -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part2 UNG_MZVL2512HCJQ-0-> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part2 -> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part2 -> ../../nvme0n1p2 drwxr-xr-x. 2 root root 400 Jul 5 10:28 . lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKtEdtLjwJQyIdxJcSvPv8TEAjwYGMv6yU -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKAooqrczySYJyiHvUAUji9oScPN2cVi7J -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-swap -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-root -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkK5HZXbR2ow5xKGuD7jVe4UPzZm2qRLLXI -> ../../dm-2 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-home -> ../../dm-2 It's looks like that I am not doing the disk drive stuff in the config file correctly. -- Gerard Hooton. Senior Technical Officer School of Engineering. University College Cork. College Road. Cork. Ireland. Loc8: WDR-04-60G Tel: +353 21 4902296 Mobile: +353 852813491

3 7

Issues booting centos7 [dracut is failing to enable centos/root, centos/swap LVs]
by Yannis Milios 01 Feb '25

01 Feb '25

Hello, I'm having a strange problem booting a new centos7 installation. Below some background on this. [I have attached the tech details at the bottom of this message] I started a new CentOS7 installation on a VM, so far all good, o/s boots fine. Then I decided to increase VM disk size (initially was 10G) to 13G. Powered off the VM, increased the vhd via the hypervisor, booted from CentOS livecd, selected "recover my centos installation". Then I used the following sequence of commands to make the new vhd size "visible" to the o/s ... - ran fdisk /dev/sda and deleted partition 2. (This is the LVM partition where the o/s is stored. The first partition is /boot [xfs] partition *non lvm*.) - created a new partition with same starting sector as before deleting it, but a different ending sector (to reflect to the increased space). - set partition type to 8e (lvm), saved settings and exit. - ran pvresize and lvresize to make new space visible to the o/s.All good, I can see the space increase on 'lvdisplay centos/root'. - ran 'mount /dev/mapper/centos-root /mnt/root' to temporarily mount the o/s partition. - ran 'xfs_growfs /mnt/root' to resize the o/s fs to the new size. It was successful and I could actually chroot to the o/s and verify new disk size. - rebooted and tried to boot from hdd this time. Grub menu shows up and loads default kernel (3.10.0-862.9.1.el7.x86_64). - after initial kernel boot up process, booting continues to initrd and then it's where the problem starts... - looks like dracut has issues locating/enabling /dev/mapper/centos-root (lv) and as a result it cannot boot to the 'real' root fs (/). - while in dracut shell, I execute the following command sequence: 1. lvm lvchange -ay /dev/centos/root 2. lvm lvchange -ay /dev/centos/swap 3. ln -s /dev/mapper/centos-root /dev/root 4. exit ...and the o/s boots fine...so looks like the pv,vg,lv is detected properly while in initrd, but somehow dracut has difficulties enabling the root,swap LVs ? - While in o/s, I rebuild initrd by using: 'dracut -f -v -a lvm' Note, I have to use '-a lvm' as for some reason, if don't, the lvm utils (lvm,lvm_scan) are not being included to the initrd, not sure why this happens. After rebooting, same thing happens, I have to manually boot the system via dracut shell. I'm a bit stuck at this point, any clues what I'm doing wrong in here ? As I previously said, this is a new installation, so I could simply reinstall the whole thing, but I would rather try to find out some answer to why is this happening ... :-) [curiosity] Some additional details: ================== I've attached /run/initramfs/rdsosreport.txt file [generated while in inird] here: https://privatebin.net/?fdc4052c0c402884#gdB/QYR3IeR55SxUbjfrkZPQfJ7jMxiUxq… o/s ver=CentOS Linux release 7.5.1804 (Core) [root@localhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 13G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 12.5G 0 part ├─centos-root 253:0 0 11.5G 0 lvm / └─centos-swap 253:1 0 1G 0 lvm [SWAP] [root@localhost ~]# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rd.shell rhgb" GRUB_DISABLE_RECOVERY="true"

4 11

No suspend after update
by Michael B Allen 22 May '24

22 May '24

Just updated CentOS 9 Stream on a Lenovo T17 Gen 4 Intel and not it won't suspend with the following error: [ 52.604998] Restarting kernel threads ... done. [ 52.605111] OOM killer enabled. [ 52.605111] Restarting tasks ... done. [ 52.606604] random: crng reseeded on system resumption [ 52.616014] thermal thermal_zone9: failed to read out thermal zone (-61) [ 52.791625] PM: suspend exit [ 52.791733] PM: suspend entry (s2idle) [ 52.797260] Filesystems sync: 0.005 seconds [ 52.797579] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 52.799127] OOM killer disabled. [ 52.799128] Freezing remaining freezable tasks ... [ 72.805437] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): [ 72.805450] task:NFSv4 callback state:I stack:0 pid:2191 ppid:2 flags:0x00004000 [ 72.805453] Call Trace: [ 72.805454] <TASK> [ 72.805456] __schedule+0x21b/0x550 [ 72.805463] schedule+0x2d/0x70 [ 72.805466] nfs41_callback_svc+0x186/0x190 [nfsv4] [ 72.805508] ? __pfx_autoremove_wake_function+0x10/0x10 [ 72.805512] ? __pfx_nfs41_callback_svc+0x10/0x10 [nfsv4] [ 72.805536] kthread+0xdd/0x100 [ 72.805538] ? __pfx_kthread+0x10/0x10 [ 72.805539] ret_from_fork+0x29/0x50 [ 72.805543] </TASK> Kernel: 5.14.0-404.el9.x86_64 How do I boot the previous kernel? Holding Shift down does nothing. Pressing escape brings up some kind of emergency screen that has no options other than to "Press any key to exit". Is CentOS 9 Stream considered stable enough to use as an everyday desktop? Mike

3 7

Problem 1: package resteasy-3.0.26-6.module_el8.4.0+595+e59c9af2.noarch from @System requires pki-servlet-4.0-api, but none of the providers can be installed
by Jelle de Jong 30 Apr '24

30 Apr '24

Dear CentOS members, Does someone know how to resolve this package conflict, it is creating security issues with freeipa dependencies. [root@freeipa01 ~]# yum update --refresh CentOS Stream 8 - AppStream 102 kB/s | 4.4 kB 00:00 CentOS Stream 8 - BaseOS 18 kB/s | 3.9 kB 00:00 CentOS Stream 8 - Extras 55 kB/s | 2.9 kB 00:00 CentOS Stream 8 - Extras common packages 15 kB/s | 3.0 kB 00:00 Extra Packages for Enterprise Linux 8 - x86_64 367 kB/s | 28 kB 00:00 Extra Packages for Enterprise Linux 8 - Next - x86_64 75 kB/s | 35 kB 00:00 Error: Problem 1: package resteasy-3.0.26-6.module_el8.4.0+595+e59c9af2.noarch from @System requires pki-servlet-4.0-api, but none of the providers can be installed - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from @System - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-1.module_el8.4.0+595+e59c9af2.noarch from appstream - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from appstream - cannot install the best update candidate for package resteasy-3.0.26-6.module_el8.4.0+595+e59c9af2.noarch - cannot install the best update candidate for package pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch Problem 2: cannot install the best update candidate for package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch - both package tomcat-el-3.0-api-1:9.0.62-30.el8.noarch from appstream and tomcat-lib-1:9.0.62-30.el8.noarch from appstream obsolete pki-servlet-engine <= 1:9.0.50 - package tomcat-1:9.0.62-30.el8.noarch from appstream requires tomcat-lib = 1:9.0.62-30.el8, but none of the providers can be installed - package tomcat-jsp-2.3-api-1:9.0.62-30.el8.noarch from appstream requires tomcat-servlet-4.0-api = 1:9.0.62-30.el8, but none of the providers can be installed - package tomcat-lib-1:9.0.62-30.el8.noarch from appstream requires tomcat-servlet-4.0-api = 1:9.0.62-30.el8, but none of the providers can be installed - package tomcatjss-7.7.1-1.module_el8.6.0+1038+e795ee4b.noarch from @System requires pki-servlet-engine >= 1:9.0.7, but none of the providers can be installed - package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from @System requires pki-servlet-4.0-api = 1:9.0.30-3.module_el8.5.0+854+e1c92b81, but none of the providers can be installed - package pki-servlet-engine-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from appstream requires pki-servlet-4.0-api = 1:9.0.30-3.module_el8.5.0+854+e1c92b81, but none of the providers can be installed - package pki-servlet-engine-1:9.0.30-1.module_el8.4.0+595+e59c9af2.noarch from appstream requires pki-servlet-4.0-api = 1:9.0.30-1.module_el8.4.0+595+e59c9af2, but none of the providers can be installed - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from @System - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-1.module_el8.4.0+595+e59c9af2.noarch from appstream - package tomcat-servlet-4.0-api-1:9.0.62-30.el8.noarch from appstream obsoletes pki-servlet-4.0-api <= 1:9.0.50 provided by pki-servlet-4.0-api-1:9.0.30-3.module_el8.5.0+854+e1c92b81.noarch from appstream - cannot install the best update candidate for package tomcatjss-7.7.1-1.module_el8.6.0+1038+e795ee4b.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

2 1

CentOS 7/8s EOL : infrastructure impacts (please read)
by Fabian Arrotin 02 Apr '24

02 Apr '24

Hi all, As you're all aware (we sent multiple mails in the last year about this), CentOS 7 and Stream 8 will go EOL soon : https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-an… Let's lists some things that will happen on the CentOS Infrastructure as we'll be approching (or passed) these dates : # CentOS 7/8s content itself Usual process : content will be archived to https://vault.centos.org and removed from mirror.centos.org completely, with just a simple readme file dropped here (for example http://mirror.centos.org/centos/8/readme for already EOL'ed version). Worth knowing that some SIGs are still building for RHEL8, still supported for SIGs through https://cbs.centos.org so such kind of content will continue to be available there as long as SIGs can build against/for it # CBS/koji (https://cbs.centos.org) No impact on CBS env itself ( not running centos 7 nor 8s for a long time now) but the various build tag reflecting centos 7 and 8s will be locked so that nobody would be able to build content anymore : that would even be impossible as content itself will have been removed from mirror.centos.org (internally used for cbs build tags) # CentOS Forums (https://forums.centos.org) : still running on centos 7 and even if that's easy to migrate to newer/supported EL version, it was decided to just shutdown the service (based on discussion with the actual moderation team). An option (to be announced on forums.centos.org ?) is to eventually start moving thread/discussions on Fedora discourse (There is already a CentOS category there : https://discussion.fedoraproject.org/c/neighbors/centos/71) So the plan is just to shutdown forums.centos.org and remove A/AAAA records from DNS # mirrorlist.centos.org service : Starting from Stream 9 (and above), deployed CentOS instance ares using Fedora infra mirrormanager instance for metalink= instead of mirrorlist= in .repo files. We'll just decommission our mirror crawler (also running with a mix of perl/python2 code), so not validating any mirror for legacy/EOL releases. mirrorlist.centos.org A/AAAA records will be removed in the following weeks after c7 will be EOL'ed. That means that people still running CentOS 7 or 8-stream will not have functional yum/dnf stack, except if they point to either vault or have internal mirror but at least people would be aware that distro itself is EOL and that they shouldn't expect to receive any update anymore # CentOS mailing-lists Currently running on mailman2 stack, on top of CentOS 7 linux : there is WIP to port everything to up2date mailman3 stack, actually packaged for EPEL9. We have successfully imported archives into mailman3 and same for lists config but let's start a different/separate thread to discuss changes (like renaming lists, see next coming thread) Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

2 4

unsubcribe
by Leonardo Cuyar Morales 30 Mar '24

30 Mar '24

-- Imagination is more important than knowledge

2 1

Out-Of-Office
by Sivaramakrishna Polepalli 30 Mar '24

30 Mar '24

Hello, I will be OOO traveling from 03/28 to 05/06 returning back on 06/07. Please expect delays in my email responses. Please contact Aurus support prodsupport(a)aurusinc.com / Yogesh Baviskar ybaviskar(a)aurusinc.com or any support needs. Thanks Siva Polepalli +1 575-404-3272

1 0

CentOS-announce Digest, Vol 218, Issue 2
by centos-announce-request＠centos.org 26 Mar '24

26 Mar '24

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEBA-2024:1277 CentOS 7 libX11 BugFix Update (Johnny Hughes) 2. CEBA-2024:1275 CentOS 7 lm_sensors BugFix Update (Johnny Hughes) 3. CEBA-2024:1276 CentOS 7 resource-agents BugFix Update (Johnny Hughes) 4. CESA-2024:1249 Important CentOS 7 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 25 Mar 2024 15:01:43 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2024:1277 CentOS 7 libX11 BugFix Update Message-ID: <20240325150143.GA5320(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2024:1277 Upstream details at : https://access.redhat.com/errata/RHBA-2024:1277 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3e22c1e91e6c946f60aaa437911042d67c7e9de92d77cf458a51d5660658186c libX11-1.6.7-5.el7_9.i686.rpm f79bf580272858f3f9343a97221fc561755bb908456a1beb77582f9310486ae1 libX11-1.6.7-5.el7_9.src.rpm 1f4f286b0441b2c508c416f72ee52c1b323a1ba12aae4579f986c007ecde653f libX11-1.6.7-5.el7_9.x86_64.rpm 70bbd71ba6462d9f6702322739a79ddf57ab8a23f41a3ae1e2c47feacb60d0d1 libX11-common-1.6.7-5.el7_9.noarch.rpm 1ef57080cad8889aa2a957bb771d161af38b61bf4aec83a7fcd19e2dfe510079 libX11-devel-1.6.7-5.el7_9.i686.rpm 374f721b5f41a11a081cd23537162130ab654a02ece3e8c55f3840ecd8f839a0 libX11-devel-1.6.7-5.el7_9.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Mon, 25 Mar 2024 15:01:57 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2024:1275 CentOS 7 lm_sensors BugFix Update Message-ID: <20240325150157.GA5446(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2024:1275 Upstream details at : https://access.redhat.com/errata/RHBA-2024:1275 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 88e82b5a11526a65b2ac8dcbe253868992a00064db1db424255bd509feb452cb lm_sensors-3.4.0-8.20160601gitf9185e5.el7_9.1.src.rpm be4cfd2a6f6ccca83e063fb2eccc0c3e16716ba370638be5de4deda72c80848a lm_sensors-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm 95d76c0c65f9a62fc846a490f4d2b19a993d7bfe3b29c8f5435e619d31f10fe5 lm_sensors-devel-3.4.0-8.20160601gitf9185e5.el7_9.1.i686.rpm 552d8f1a349abd352ed882be0cfbe9423589f98f6621627e58afa84d6c83599d lm_sensors-devel-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm 189cab5bc603286773946e73c42d38c539c7a0de2d36fdb6fa6aba0763c86a44 lm_sensors-libs-3.4.0-8.20160601gitf9185e5.el7_9.1.i686.rpm 0af4fa113704a011a3594459a6619542c384a68bce85aa250f90448e347431fe lm_sensors-libs-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm 60f10f4641f2dac4d689ad5b1ee25cc224768eadce58b7f0d64c3eecf32b94ff lm_sensors-sensord-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Mon, 25 Mar 2024 15:02:10 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2024:1276 CentOS 7 resource-agents BugFix Update Message-ID: <20240325150210.GA5582(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2024:1276 Upstream details at : https://access.redhat.com/errata/RHBA-2024:1276 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 619d5b89b88c559b235692c6c00c5d06cedd0d274f0132dc0732b25bc91bb93e resource-agents-4.1.1-61.el7_9.20.src.rpm 1f633f20c7b2aa6eafb4ac8894d9cd73727c40432189eee52f62aee11daf62e9 resource-agents-4.1.1-61.el7_9.20.x86_64.rpm 6d0aee209b29a68899270b50fbdb5657444b46017f3f4b39ff4652e77f30292c resource-agents-aliyun-4.1.1-61.el7_9.20.x86_64.rpm 639a97b21ae7b51141fd76f2777d2f3ea1bd758549e53130764657fafe2daf7a resource-agents-gcp-4.1.1-61.el7_9.20.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Mon, 25 Mar 2024 15:37:48 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2024:1249 Important CentOS 7 kernel Security Update Message-ID: <20240325153748.GA12778(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2024:1249 Important Upstream details at : https://access.redhat.com/errata/RHSA-2024:1249 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ebf604edce00a3a3778207eeaac06a3de226dbf62bfb987ed00584aa8d736ea1 bpftool-3.10.0-1160.114.2.el7.x86_64.rpm 4ea83e958a87df368396a4445d79a7047566af99a681051e97005b0c5b61aa05 kernel-3.10.0-1160.114.2.el7.src.rpm d4e1ed8394af297a574fede15b7e0b3dcc28d263998175257f45e728f22fca91 kernel-3.10.0-1160.114.2.el7.x86_64.rpm 18d2703d9432cd3d8353acf0fb1f852fe4c15301b3d49fffac3f0194c6a4aaa0 kernel-abi-whitelists-3.10.0-1160.114.2.el7.noarch.rpm fe01de01f7bcb863a54f276394f9ab097a0d29db56661a42eb33d27e4bef27f8 kernel-debug-3.10.0-1160.114.2.el7.x86_64.rpm cfde4230671763bf6a464de9ec8c191195c9ae864571afd92bc7bea8dfcbb11e kernel-debug-devel-3.10.0-1160.114.2.el7.x86_64.rpm 74dfc146e5e4ab219dba838033e3a2a983e2ad796cee5a175fda1b6c17653193 kernel-devel-3.10.0-1160.114.2.el7.x86_64.rpm b5a460913216927a863650ccef6d332b05a92836c9647e73a369720e9156fe84 kernel-doc-3.10.0-1160.114.2.el7.noarch.rpm 4aeb221b696dbe4b67c7b108b689cf26df6c7baa673fd4a529bd4df444eaf4fc kernel-headers-3.10.0-1160.114.2.el7.x86_64.rpm 2ba740802cbbc7ff23957b8b2a38c06b773a113b40708d05815b6081f7eecb19 kernel-tools-3.10.0-1160.114.2.el7.x86_64.rpm d4ce276deccf36c3cdff38a52ff6f73bd2c271d8df45463c61cc66cdd8dd7e18 kernel-tools-libs-3.10.0-1160.114.2.el7.x86_64.rpm bee03f8565ac02484c05292876b9c0976e9334dad12bbf643dd9f59526e9eb6d kernel-tools-libs-devel-3.10.0-1160.114.2.el7.x86_64.rpm 0af8a6a9e3b24968bed3be9b8de12ef658fbbfc2164edfd7186a7cced585e5ec perf-3.10.0-1160.114.2.el7.x86_64.rpm 850766245b53884b841d001909aa89898b167cf79a244d26c44c42dd775019c3 python-perf-3.10.0-1160.114.2.el7.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 218, Issue 2 ***********************************************

1 0

CentOS Virt SIG and packages' priority problems?
by Gianluca Cecchi 14 Mar '24

14 Mar '24

Hello, some days ago I followed these instructions https://sigs.centos.org/virt/tdx/host/ and after enabling the repo I installed the tdx necessary bits as indicated, with the command dnf install kernel-tdx qemu-kvm-tdx libvirt-tdx This gave me: libvirt 9.5.0-1.el9s qemu-kvm 8.0.0-15.el9s kernel 5.14.0-395.el9s But now if I run a usual "dnf update" I'm proposed "standard" libvirt and qemu-kvm sw stack, I think because of their version apparently greater (10 vs 9.5 and 8.2 vs 8.0): Upgrading: libvirt x86_64 10.0.0-4.el9 appstream 23 k libvirt-client x86_64 10.0.0-4.el9 appstream 438 k libvirt-client-qemu x86_64 10.0.0-4.el9 appstream 47 k libvirt-daemon x86_64 10.0.0-4.el9 appstream 213 k libvirt-daemon-common x86_64 10.0.0-4.el9 appstream 139 k libvirt-daemon-config-network x86_64 10.0.0-4.el9 appstream 29 k libvirt-daemon-config-nwfilter x86_64 10.0.0-4.el9 appstream 42 k libvirt-daemon-driver-interface x86_64 10.0.0-4.el9 appstream 219 k libvirt-daemon-driver-network x86_64 10.0.0-4.el9 appstream 260 k libvirt-daemon-driver-nodedev x86_64 10.0.0-4.el9 appstream 240 k libvirt-daemon-driver-nwfilter x86_64 10.0.0-4.el9 appstream 255 k libvirt-daemon-driver-qemu x86_64 10.0.0-4.el9 appstream 976 k libvirt-daemon-driver-secret x86_64 10.0.0-4.el9 appstream 216 k libvirt-daemon-driver-storage x86_64 10.0.0-4.el9 appstream 23 k libvirt-daemon-driver-storage-core x86_64 10.0.0-4.el9 appstream 276 k libvirt-daemon-driver-storage-disk x86_64 10.0.0-4.el9 appstream 38 k libvirt-daemon-driver-storage-iscsi x86_64 10.0.0-4.el9 appstream 35 k libvirt-daemon-driver-storage-logical x86_64 10.0.0-4.el9 appstream 39 k libvirt-daemon-driver-storage-mpath x86_64 10.0.0-4.el9 appstream 32 k libvirt-daemon-driver-storage-rbd x86_64 10.0.0-4.el9 appstream 43 k libvirt-daemon-driver-storage-scsi x86_64 10.0.0-4.el9 appstream 35 k libvirt-daemon-lock x86_64 10.0.0-4.el9 appstream 64 k libvirt-daemon-log x86_64 10.0.0-4.el9 appstream 69 k libvirt-daemon-plugin-lockd x86_64 10.0.0-4.el9 appstream 38 k libvirt-daemon-proxy x86_64 10.0.0-4.el9 appstream 211 k libvirt-libs x86_64 10.0.0-4.el9 appstream 4.9 M python3-libvirt x86_64 10.0.0-1.el9 appstream 339 k qemu-img x86_64 17:8.2.0-6.el9 appstream 2.5 M qemu-kvm x86_64 17:8.2.0-6.el9 appstream 68 k qemu-kvm-audio-pa x86_64 17:8.2.0-6.el9 appstream 81 k qemu-kvm-block-blkio x86_64 17:8.2.0-6.el9 appstream 84 k qemu-kvm-block-rbd x86_64 17:8.2.0-6.el9 appstream 86 k qemu-kvm-common x86_64 17:8.2.0-6.el9 appstream 685 k qemu-kvm-core x86_64 17:8.2.0-6.el9 appstream 4.3 M qemu-kvm-device-display-virtio-gpu x86_64 17:8.2.0-6.el9 appstream 92 k qemu-kvm-device-display-virtio-gpu-pci x86_64 17:8.2.0-6.el9 appstream 76 k qemu-kvm-device-display-virtio-vga x86_64 17:8.2.0-6.el9 appstream 77 k qemu-kvm-device-usb-host x86_64 17:8.2.0-6.el9 appstream 90 k qemu-kvm-device-usb-redirect x86_64 17:8.2.0-6.el9 appstream 95 k qemu-kvm-docs x86_64 17:8.2.0-6.el9 appstream 1.2 M qemu-kvm-tools x86_64 17:8.2.0-6.el9 appstream 584 k qemu-kvm-ui-egl-headless x86_64 17:8.2.0-6.el9 appstream 77 k qemu-kvm-ui-opengl x86_64 17:8.2.0-6.el9 appstream 84 k qemu-pr-helper x86_64 17:8.2.0-6.el9 appstream 497 k What is the best option to blacklist the packages in appstream and prioritize the tdx ones? I tried adding priority=1 to the tdx repo file, but now I get this when running "dnf update": Error: Problem: package python3-libvirt-10.0.0-1.el9.x86_64 from appstream requires libvirt.so.0(LIBVIRT_9.7.0)(64bit), but none of the providers can be installed - cannot install both libvirt-libs-10.0.0-2.el9.x86_64 from appstream and libvirt-libs-9.5.0-1.el9s.x86_64 from @System - cannot install both libvirt-libs-10.0.0-3.el9.x86_64 from appstream and libvirt-libs-9.5.0-1.el9s.x86_64 from @System - cannot install both libvirt-libs-10.0.0-4.el9.x86_64 from appstream and libvirt-libs-9.5.0-1.el9s.x86_64 from @System - cannot install both libvirt-libs-9.10.0-1.el9.x86_64 from appstream and libvirt-libs-9.5.0-1.el9s.x86_64 from @System - cannot install both libvirt-libs-9.9.0-1.el9.x86_64 from appstream and libvirt-libs-9.5.0-1.el9s.x86_64 from @System - cannot install the best update candidate for package python3-libvirt-9.3.0-1.el9.x86_64 - cannot install the best update candidate for package libvirt-libs-9.5.0-1.el9s.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) # Currently I have python3-libvirt-9.3.0-1.el9.x86_64 installed. Thanks for any advise Gianluca

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss March 2024