Issue #4354
closed
Pulp 2.19 master pulled epel django instead of pulp 2 django
Description
Problem¶
When running nightly rhel76-fips testing, there were 500 errors [0] on jenkins tests since 1/23 and issues in journalctl with django [1].
After talking with asmacdo and daviddavis, it appears this may be a django being pulled from EPEL and not from our Pulp 2 repos on build [2][3]
Testing¶
It was determined this was the result of EPEL django precedence over the pulp.repo version that was built. This issue has been seen before.
Forced installation of the python2-django-1.11.17-1 from the fedorapeople repo [3] and restart of services (or with a hammer of shutdown now -r) resulted in a functioning pulp install.
Actions¶
Pulp-dev determined this issue as a low priority issue where documentation exercise may happen as a result of this issue.
For QE, this is a critical breakage of CI as the ansible install fails on FIPS installation and puts the box into a non-testable state. QE will be opening a related Urgent test tracker to fix the issue in the pulp-ci installer to fix mission critical work.
References¶
[0] - https://paste.fedoraproject.org/paste/bPRtYPa4ZCLShrZ7VUMqMQ
[1] - https://pulp-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Pulp%202%20-%20Master/job/pulp-2-master-dev-rhel7-fips/228/
[2] - https://paste.fedoraproject.org/paste/6eHTS1Uc3NkC0hohvKe-TA [from the affected 2.19a1-nightly box under test
[3] - 2.11.17-1 https://repos.fedorapeople.org/repos/pulp/pulp/v2/testing/automation/2.19/stage/7Server/x86_64/
Related issues
.