bootstrap-ansible fails in stable newton
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | openstack-ansible |
Critical
|
Jesse Pretorius | ||
Bug Description
Today I got issues with a fresh ubuntu 14.04 install of osa, branch stable/newton.
See the log below.
I suspect an update of the ansible install source changed ansible requirements which would be conflicting with our pins. It's just a gut feeling, so worth checking in more details!
| description: | updated |
| summary: |
- bootstrap-ansible fails in stable/newton + bootstrap-ansible fails in stable newton |
| Changed in openstack-ansible: | |
| assignee: | nobody → Jesse Pretorius (jesse-pretorius) |
| status: | New → In Progress |
| Changed in openstack-ansible: | |
| importance: | Undecided → Critical |
Fix proposed to branch: stable/mitaka
Review: https:/
| Jesse Pretorius (jesse-pretorius) wrote : | #3 |
Patches submitted to resolve this issue:
master (ocata): https:/
newton: https:/
mitaka: https:/
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 253ea10d266f5ce
Author: Matthew Thode <email address hidden>
Date: Mon Jan 23 12:33:49 2017 -0600
Apply global-pins as constraints to ensure complete pinning
The current pinning method for pip/setuptools/
initial setup of a host or python venv. However, when a python
package which has one of these in its requirements is installed
onto the host or into the venv and the '--upgrade' option is given
to pip, the package will be upgraded to the latest version available
within the given constraints.
As OpenStack's requirements management process does not cater for
the pip, setuptools or wheel packages we need to ensure that all
python install tasks prior to the repo being built use our global
pins as a constraint in addition to the OpenStack uppser constraints.
As pip's --constraints option can only take a file as an argument
we have to copy the global pins file to the target which will use
it. This file can be removed from the host once the repo is built.
Related-Bug: #1658773
Closes-Bug: #1658948
Change-Id: Iccbb2e4a126a1c
| Changed in openstack-ansible: | |
| status: | In Progress → Fix Released |
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit c640fcf7d972749
Author: Matthew Thode <email address hidden>
Date: Mon Jan 23 12:33:49 2017 -0600
Apply global-pins as constraints to ensure complete pinning
The current pinning method for pip/setuptools/
initial setup of a host or python venv. However, when a python
package which has one of these in its requirements is installed
onto the host or into the venv and the '--upgrade' option is given
to pip, the package will be upgraded to the latest version available
within the given constraints.
As OpenStack's requirements management process does not cater for
the pip, setuptools or wheel packages we need to ensure that all
python install tasks prior to the repo being built use our global
pins as a constraint in addition to the OpenStack uppser constraints.
As pip's --constraints option can only take a file as an argument
we have to copy the global pins file to the target which will use
it. This file can be removed from the host once the repo is built.
Related-Bug: #1658773
Closes-Bug: #1658948
Change-Id: Iccbb2e4a126a1c
(cherry picked from commit 253ea10d266f5ce
| tags: | added: in-stable-mitaka |
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit 3859663a6bb4b15
Author: Matthew Thode <email address hidden>
Date: Mon Jan 23 12:33:49 2017 -0600
Apply global-pins as constraints to ensure complete pinning
The current pinning method for pip/setuptools/
initial setup of a host or python venv. However, when a python
package which has one of these in its requirements is installed
onto the host or into the venv and the '--upgrade' option is given
to pip, the package will be upgraded to the latest version available
within the given constraints.
As OpenStack's requirements management process does not cater for
the pip, setuptools or wheel packages we need to ensure that all
python install tasks prior to the repo being built use our global
pins as a constraint in addition to the OpenStack uppser constraints.
As pip's --constraints option can only take a file as an argument
we have to copy the global pins file to the target which will use
it. This file can be removed from the host once the repo is built.
Combined backport of:
- https:/
- https:/
Closes-Bug: #1658773
Closes-Bug: #1658948
Change-Id: Iccbb2e4a126a1c
(cherry picked from commit 253ea10d266f5ce
| tags: | added: in-stable-newton |
| OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible 15.0.0.0b3 | #7 |
This issue was fixed in the openstack/
This issue was fixed in the openstack/
Sadly, the feature add attchment doesn't work today, and I want to cleanup the gist above.
Here was its content:
root@evrardjp-
+ export HTTP_PROXY=
+ HTTP_PROXY=
+ export HTTPS_PROXY=
+ HTTPS_PROXY=
+ export ANSIBLE_
+ ANSIBLE_
+ export ANSIBLE_
+ ANSIBLE_
+ export SSH_DIR=/root/.ssh
+ SSH_DIR=/root/.ssh
+ export DEBIAN_
+ DEBIAN_
++ awk '/requirements_
+ export 'UPPER_
+ UPPER_CONSTRAIN
+ export ANSIBLE_
+ ANSIBLE_
+ VIRTUALENV_
++ dirname scripts/
+ cd scripts/..
+ info_block 'Checking for required libraries.'
+ source scripts/
++ LINE=--
++ MAX_RETRIES=5
++ ANSIBLE_
+++ date +%s
++ STARTTIME=
++ PIP_INSTALL_
++ COMMAND_
++ '[' -z '' ']'
+++ grep -c '^processor' /proc/cpuinfo
++ CPU_NUM=8
++ '[' 8 -lt 10 ']'
++ ANSIBLE_FORKS=8
++ trap 'exit_fail 273 0 '\''Received STOP Signal'\''' SIGHUP SIGINT SIGTERM
++ trap 'exit_fail 274 0' ERR
+++ id -u
++ '[' 0 '!=' 0 ']'
++ '[' '!' -d etc -a '!' -d scripts -a '!' -d playbooks ']'
++ export PATH=/usr/
++ PATH=/usr/
++ export HOME=/root
++ HOME=/root
++ [[ -f /usr/local/
+ info_block 'Bootstrapping System with Ansible'
+ echo -------
-------
+ print_info 'Bootstrapping System with Ansible'
+ PROC_NAME='- [ Bootstrapping System with Ansible ] -'
+ printf '\n%s%s\n' '- [ Bootstrapping System with Ansible ] -' -------
- [ Bootstrapping System with Ansible ] -------
+ echo -------
-------
++ pwd
+ export OSA_CLONE_
+ OSA_CLONE_
++ readlink -f ansible-
+ ANSIBLE_
| description: | updated |
This issue was fixed in the openstack/
http://
holds packaging===16.8
while current stable/newton holds (http://
When the requirements sha bump will be done it's gonna be fixed.