995c539491
This reverts commit a645fa4ffb3c819f38ce1c66e83eb409c587c55d. It is really devstack causing problems here; it was removing the python-virtualenv package & re-installing using pip (see depends-on). This failed because the pip-install we did here removed the egg-file that rpm expected to be there, so rpm bailed out on the removal. But even if it worked, this just leads you back down the path of the original problem; that the system packaged version can be re-installed and overwrites the pip installed version. Thus I still believe this is the correct thing to do in the dib element. Note it is not a common problem (devstack aside); most jobs don't touch python-virtualenv & related packages (the one we did notice this on was being brought over from travisci where it was required for some reason). Change-Id: I82acb865378a0fa5903a6267bfcee0e2962eced0 Depends-On: Ib0edf6c4ee8a510e9d671213de35d787f56acfed
pip-and-virtualenv
This element installs pip and virtualenv in the image. If the package installtype is used then these programs are installed from distribution packages. If the source installtype is used these programs are installed from get-pip.py and pip (respectively).
To install pip and virtualenv from package:
export DIB_INSTALLTYPE_pip_and_virtualenv=package