gate: change ansible to run in virtual environment
Bug #1431324 reported by
Jesse Pretorius
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Wishlist
|
Kevin Carter |
Bug Description
Currently gate-check-commit builds an AIO. The AIO bootstraps ansible on the same server that also runs all the playbooks, resulting in the compute and storage roles running on the same host as is used for running ansible.
This introduces some differences to the way things happen in the real world - specifically related to the ansible requirements which are installed on the server. As a result we are possibly missing out on catching some bugs related to differing pip versions or other conflicts introduced by the ansible pip requirements.
I suggest that we install ansible in a seperated python virtual environment to try and isolate this effect.
no longer affects: | openstack-ansible/juno |
no longer affects: | openstack-ansible/kilo |
no longer affects: | openstack-ansible/trunk |
Changed in openstack-ansible: | |
assignee: | Jesse Pretorius (jesse-pretorius) → nobody |
tags: | added: low-hanging-fruit |
Changed in openstack-ansible: | |
assignee: | nobody → Hector Gonzalez (theizaakk) |
Changed in openstack-ansible: | |
assignee: | Hector Gonzalez (theizaakk) → nobody |
Changed in openstack-ansible: | |
assignee: | nobody → Kevin Carter (kevin-carter) |
milestone: | none → newton-1 |
Changed in openstack-ansible: | |
status: | Triaged → In Progress |
To post a comment you must log in.
Is this suggestion just for AIOs?
Also, how would this affect projects embedding os-ansible- deployment?