Fresh CentOS 7 kickstart, yum update fails after subscribing

Support
1

Problem: I install a fresh system with kickstart from DVD iso. The system is not internet facing. When the installation is done, I register the system to my Foreman server, remove the /etc/yum.repos.d/CentOS* and do a yum -y update. I get all kinds of messages like this:

Error: Package: libreport-web-2.1.11-53.el7.centos.x86_64 (@anaconda)
Requires: /sbin/ldconfig
Removing: glibc-2.17-317.el7.x86_64 (@anaconda)
Not found
Updated By: glibc-2.17-324.el7_9.x86_64 (CBS_CentOS_CentOS_7_Updates)
Not found
Error: Package: libtasn1-4.10-1.el7.x86_64 (@anaconda)
Requires: /sbin/ldconfig
Removing: glibc-2.17-317.el7.x86_64 (@anaconda)
Not found
Updated By: glibc-2.17-324.el7_9.x86_64 (CBS_CentOS_CentOS_7_Updates)
Not found
Error: Package: GeoIP-1.5.0-14.el7.x86_64 (@anaconda)
Requires: /sbin/ldconfig
Removing: glibc-2.17-317.el7.x86_64 (@anaconda)
Not found
Updated By: glibc-2.17-324.el7_9.x86_64 (CBS_CentOS_CentOS_7_Updates)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

For some reason yum can’t find the packages needed. When I download the needed packages which cause the dependency issues and install them manually with rpm -Uvh, everything looks fine and yum update works as expected.

This leads me to believe there must be something wrong with the metadata, but I tried everything possible (complete syncing of the repo’s, publishing metadata, etc.)

Expected outcome: Register system, remove original .repo files from kickstart, yum update -y should give an updated system.

Foreman and Proxy versions: 2.5.2-1

Foreman and Proxy plugin versions:

Distribution and version:

Other relevant data:

2

Katello 4.1.1 has a serious bug due to which it doesn’t import filelists from the rpms. See topic Cannot update puppet-agent to 6.24.0 on foreman servers Your errors look a lot like that. There is already a patch and a repair script available but it’s not yet in Katello updates…

3

Thank you for your quick response, however, this looks weird doesn’t it?

[root@hostname ~]# yum provides /sbin/ldconfig
Loaded plugins: fastestmirror, langpacks, product-id, search-disabled-repos, subscription-manager
Loading mirror speeds from cached hostfile
glibc-2.17-317.el7.x86_64 : The GNU libc libraries
Repo : @anaconda
Matched from:
Filename : /sbin/ldconfig

[root@hostname ~]#

4

I don’t see anything weird. You have glibc from the kickstart (anaconda) installed, which provides /sbin/ldconfig. What did you expect?

5

I’d expect to see the the repo CBS_CentOS_CentOS_7_Updates as well.

6

Please read my first response and the linked topic. As I wrote before: there is a bug in Katello 4.1.1 which prevents filelists from rpms to be synced/imported. Read the other topic and verify if it’s the same problem…

7

I’ve downloaded filelists.xml too and mine is quite empty. None of the files are in this .xml, just names and versions of packages.

<?xml version="1.0" encoding="UTF-8"?>
<filelists xmlns="http://linux.duke.edu/metadata/filelists" packages="2542">
<package pkgid="6838d1704d6089791d6b3d53de842f0901465128bc97227e71cbfb2073418234" name="fence-agents-intelmodular" arch="x86_64">
  <version epoch="0" ver="4.2.1" rel="41.el7_9.4"/>
</package>
<package pkgid="ddcaa350e33d1c8dbffab5d04b8b98a223178542f0bbbc0bffdae33e41b18241" name="libsss_nss_idmap-devel" arch="x86_64">
  <version epoch="0" ver="1.16.5" rel="10.el7_9.6"/>
</package>
<package pkgid="0c9cd97e333e5ea85907e92483ef91dbdb08349b7e29916dcf5c08061c74f836" name="libexif-doc" arch="x86_64">
  <version epoch="0" ver="0.6.22" rel="2.el7_9"/>
</package>
<package pkgid="37356ac1734506c064e4fdf1e87d69a442a12767a7e98626e8c9c571fb460198" name="fence-agents-vmware-rest" arch="x86_64">
  <version epoch="0" ver="4.2.1" rel="41.el7_9.4"/>
</package>
<package pkgid="2f0b2cb6eb70e8325b1e26082c9f953fa3bbe383a04e9bad22161bf475931cd5" name="libsss_certmap" arch="i686">
  <version epoch="0" ver="1.16.5" rel="10.el7_9.7"/>
</package>

primary.xml looks good in my case too, so guess it’s the same bug. Thanks for your time! I’ll wait for the patch then.