Jim, Thanks for reaching out. Epel recently started shipping a newer version than what’s in Pulp and newer than what we support in Pulp. This newer version of celery is automatically being installed since yum tries to use the latest version. This problem isn’t strictly limited to 2.18 but it’s likely users will encounter it during yum upgrades.
We have since fixed the problem by bumping up the epoch of our celery version that we ship in Pulp, which should mean that if you upgrade to 2.18.1, yum/dnf will consider our versions as newer and download it. Let us know if upgrading to 2.18.1 doesn’t fix the issue. David On Thu, Mar 28, 2019 at 12:47 PM Jim Davis <[email protected]> wrote: > In order to get to 2.18 I had to add this to my epel.repo (remove the > incompatible python2-celery and reinstall it from the pulp repo): > > > > exclude=python2-celery-4.0.2 > > > > To remove the OS supplied pkg I did: > > > > rpm -e --nodeps python2-celery > > > > Somehow I think this needs to be added to the upgrade notes. I didn’t like > the pulp-list talked about priority plugin solution. This seems to have > worked for me – no errors since. > > > > jim > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
