Can't upgrade python3.11-django to 4.2.16 on Satellite 6.15.4.2

Posted on

Context: I'm brand-new to Redhat Satellite (if you want a chuckle, check out my brief bio).

During our monthly security scans my Satellite Server was pinged with CVE-2024-45230 and CVE-2024-45231 (among a few others).

Essentially, python3.11-django is at version 4.2.15 and needs to move to 4.2.16, but literally nothing I have done has gotten my Satellite server to see or even acklowdge that the package (python3.11-django-4.2.16-.el8pc.noarch) is available. I can see the package on the Redhat website. I can see it in my (Satellite) web interface. I can even see (and download/install) it from other servers pointing to my Satellite server in the internal network repositories. But I can not see it in the operating system of the server that's hosting the Satellite application.

I've tried point to the Redhat repositories. I've tried unlocking the packages. I even tried pointing the server back at it's own repositories (since my other server can see it). Oddly enough, even though they are looking at the same respository, they are not getting the same content (using both dnf and satellite/foerman-maintain).... It's been about 3 days of my trying to sort this out with no success. I'm trying not to "side-load" the rpms since I did get them to download, but I don't know what else I can do....ChatGPT was no help.

Anyone run into this problem or maybe have some ideas?

Responses