Project

Profile

Help

Task #2497

closed

Prevent vagrant from installing pulp-server rpm

Added by bmbouter over 7 years ago. Updated about 5 years ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 16
Quarter:

Description

vagrant up on the HEAD of pulp/devel:master will install the pulp-server rpm. To reproduce:

1. vagrant up as described above
2. show the pulp-server rpm with:

[vagrant@dev ~]$ sudo dnf list installed | grep pulp
pulp-selinux.noarch                2.11.1-0.1.alpha.git.4.329d557.fc24 @pulp-nightlies
pulp-server.noarch                 2.11.1-0.1.alpha.git.4.329d557.fc24 @pulp-nightlies
python-kombu.noarch                1:3.0.33-6.pulp.fc24                @pulp-2-stable
python-nectar.noarch               1.5.3-1.fc24                        @pulp-2-stable
python-pulp-common.noarch          2.11.1-0.1.alpha.git.4.329d557.fc24 @pulp-nightlies
python-pulp-repoauth.noarch        2.11.1-0.1.alpha.git.4.329d557.fc24 @pulp-nightlies
python-pulp-streamer.noarch        2.11.1-0.1.alpha.git.4.329d557.fc24 @pulp-nightlies

Two things are odd about this:

  • I expected only the pulp-nightlies to be providing packages, but pulp-2-stable provides some also. I expected pulp-2-stable to not be an available repo since it's subscribed to nightlies.
  • This is a devel checkout and yet rpms are being installed. The resulting environment does work, but this doesn't seem right because it seems it is mixing setuptools and rpm based installs of the same software. Mixing setuptools installed code and rpm installed code can cause strange/difficult problems at times.

Also available in: Atom PDF