its been a few months since i last built a new CentOS7 system via my spacewalk 
server, but this past week i tried to build a new one over PXE and now i am 
getting strange errors.

if i use my existing profiles (which include other child channels like updates, 
EPEL7, etc) it hangs with this error in the packaging log:


14:17:53,301 WARN packaging: 1:NetworkManager-1.12.0-8.el7_6.x86_64 requires 
glib2 >= 2.56.1
14:17:53,301 WARN packaging: systemd-219-62.el7_6.3.x86_64 requires 
libcryptsetup.so.12(CRYPTSETUP_2.0)(64bit)
14:17:53,301 WARN packaging: policycoreutils-2.5-29.el7_6.1.x86_64 requires 
libselinux-utils >= 2.5-14
14:17:53,301 WARN packaging: systemd-219-62.el7_6.3.x86_64 requires 
libcryptsetup.so.12()(64bit)
14:17:53,301 WARN packaging: policycoreutils-2.5-29.el7_6.1.x86_64 requires 
libsemanage >= 2.5-14
14:17:53,301 WARN packaging: policycoreutils-2.5-29.el7_6.1.x86_64 requires 
libsepol >= 2.5-10
14:17:53,301 WARN packaging: selinux-policy-3.13.1-229.el7_6.9.noarch requires 
libsemanage >= 2.5-13
14:17:53,302 WARN packaging: kernel-3.10.0-957.5.1.el7.x86_64 requires 
linux-firmware >= 20180911-68
14:17:53,302 WARN packaging: nss-util-3.36.0-1.1.el7_6.x86_64 requires nspr >= 
4.19.0-1
14:17:53,302 WARN packaging: nss-3.36.0-7.1.el7_6.x86_64 requires 
nss-softokn(x86-64) >= 3.36.0-1
14:17:53,302 WARN packaging: nss-3.36.0-7.1.el7_6.x86_64 requires nspr >= 4.19.0


upon verifying packages in both the package search in the spacewalk gui as well 
as double checking files in the file system on the spacewalk server, the 
package at a higher revision is there.  i made a new test profile which only 
included base and updates, and got the same error.  if i remove the updates 
channel, it tries to proceed, then hangs with


Error populating transaction and fails 10 times, in this case trying to find 
3.10.0-862.el7 when in fact the kernel in the repo for the base install is 
3.10.0-957.el7.

in troubleshooting i have deleted all my existing centos repo files (but not 
the actual channels) and re-run spacewalk-repo-sync, but it seems like anaconda 
is pulling some really old package list that is no longer current to the 
physical rpm files that are there.

i have googled and googled, but have not found the solution i need.  i am sure 
this will turn out to be something simple, but i just cant place my finger on 
it.

thanks for any help,

Jonathan
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to