just to be sure: Have you cleaned the dnf cache beforehand? (Some dnf variant of yum clean all)
I only had this behavior happen in two scenarios by now:
Package manager cache not updated
Yum versionlock plugin doing strange things (I don’t know if dnf has a versionlock plugin)
If that does not help, you could try rebuilding the CV/CCV metadata via Foreman UI. There is an option “regenerate repository metadata” on the CV Versions page, hidden behind the arrow next to the promote button. Try this for both the affected CV and CCV.
Hope this helps.
This is indeed very strange. After looking into this, it seems like that package was not even released in the version your client requests.
I don’t have a lot of experience with dnf, but my best guess would be that another package you are trying to upgrade might be depending on the wrong version of abrt-addon-ccpp? From how far my google-foo got me, you could try something like “dnf repoquery --whatdepends abrt-addon-ccpp”, check the depending packages and see how far that gets you.
Hm, interesting. According to fedora.pkgs.org, those abrt-* packages should also be available in version 2.14.
Could you check if those are available in your CV/CCV in 2.14 or if the newest version you have of those is in fact 2.13? If it is the latter, you might have hit two incomplete mirrors in a row. You might also want to check the mirrors you are using directly via your browser to see if the 2.14 packages are available there.
Have you resolved this by now?
If not, my last guess would be checking what the repos look like on the filesystem. I’m really poking in the dark here, though.
In your Pulp proxy/Foreman Server, the repos should be under /var/lib/pulp/published/yum/https/repos/bkg/Library/ccv_fedora_base/custom/Fedora/Fedora31_updates/
tbh, it somewhat looks like corrupted metadata to me, but that should have resolved itself by now. So I’m really out of ideas