pip_install failing on apt packages task

Bug #1705615 reported by Logan V
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Invalid
Undecided
Unassigned

Bug Description

Beginning this afternoon, pip_install is failing in a project where I consume it outside of OSA. I have not tested OSA yet, but this seems like an apt packages update has broken pip_install, because I had pip_install pinned since 7/12 to 7cab63d3aa187c740b3a1d5878ca26af193433d5. It began failing today on that SHA, so I bumped to the current master HEAD dd087128104b41e2e65720b611eabd2eb5b4cf99, and now it is continuing to fail with the below message:

TASK [pip_install : Install packages] ******************************************
FAILED - RETRYING: Install packages (5 retries left).
FAILED - RETRYING: Install packages (4 retries left).
FAILED - RETRYING: Install packages (3 retries left).
FAILED - RETRYING: Install packages (2 retries left).
FAILED - RETRYING: Install packages (1 retries left).
fatal: [test-1-sql1]: FAILED! => {"attempts": 5, "cache_update_time": 1500608157, "cache_updated": false, "changed": false, "failed": true, "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\" install 'gcc' 'python-dev' 'libffi-dev' 'libssl-dev' 'python3-dev'' failed: E: Unable to correct problems, you have held broken packages.\n", "rc": 100, "stderr": "E: Unable to correct problems, you have held broken packages.\n", "stderr_lines": ["E: Unable to correct problems, you have held broken packages."], "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nSome packages could not be installed. This may mean that you have\nrequested an impossible situation or if you are using the unstable\ndistribution that some required packages have not yet been created\nor been moved out of Incoming.\nThe following information may help to resolve the situation:\n\nThe following packages have unmet dependencies:\n python-dev : Depends: libpython-dev (= 2.7.11-1) but it is not going to be installed\n Depends: python2.7-dev (>= 2.7.11-1~) but it is not going to be installed\n python3-dev : Depends: libpython3-dev (= 3.5.1-3) but it is not going to be installed\n Depends: python3.5-dev (>= 3.5.1-2~) but it is not going to be installed\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "Some packages could not be installed. This may mean that you have", "requested an impossible situation or if you are using the unstable", "distribution that some required packages have not yet been created", "or been moved out of Incoming.", "The following information may help to resolve the situation:", "", "The following packages have unmet dependencies:", " python-dev : Depends: libpython-dev (= 2.7.11-1) but it is not going to be installed", " Depends: python2.7-dev (>= 2.7.11-1~) but it is not going to be installed", " python3-dev : Depends: libpython3-dev (= 3.5.1-3) but it is not going to be installed", " Depends: python3.5-dev (>= 3.5.1-2~) but it is not going to be installed"]}

Testing the install from inside the container shell:
root@test-1-sql1:~# apt-get install 'gcc' 'python-dev' 'libffi-dev' 'libssl-dev' 'python3-dev'
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python-dev : Depends: libpython-dev (= 2.7.11-1) but it is not going to be installed
              Depends: python2.7-dev (>= 2.7.11-1~) but it is not going to be installed
 python3-dev : Depends: libpython3-dev (= 3.5.1-3) but it is not going to be installed
               Depends: python3.5-dev (>= 3.5.1-2~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Revision history for this message
Logan V (loganv) wrote :

Switched apt mirrors and it seems to fix the issue, so I think this is a transient mirror issue on my end.

Changed in openstack-ansible:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.