Having a pre installed Ansible in a different location causes AIO issues.

Bug #1681372 reported by Rick Box
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Won't Fix
Medium
Cam J. Loader

Bug Description

This is on Ubuntu Xenial 16.04. When Ansible is pre-installed before the deploy starts and it is in a different location than install inspects, it skips the install and then is not in the folder:

"/opt/ansible-runtime/bin/"

This means when it comes to use Ansible later, the install fails.

Having this folder pre-created and hard linked is a workaround for this problem.

Specifically in my case having ARA pre-installed is the trigger for this bug:

https://github.com/openstack/ara

When attempting to install the below script, the following line is the cause of this issue.

https://github.com/openstack/openstack-ansible/blob/master/scripts/bootstrap-ansible.sh#L125

The following errors occur, for comparison I have included the output of when this occurs and a working install on the same machine without anything pre-installed.

https://gist.github.com/boxrick/bdf492848f02c1f3d5ea4af4b7933729

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

Fair point, I think we should have (at least best effort) a way for users to have their own ansible.

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

However, if the deployer is using its own ansible, we should also assume that (s)he will make sure the roles are available, and the proper variables are used. So the bootstrap ansible shouldn't be used in that case IMO.

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

Also the link of your bug is, I think, incomplete.

Revision history for this message
Rick Box (rickbox-bbcrd) wrote :

How is it incomplete?

Considering the use case of ARA and the it simply being installed causes it all not work rather inelegantly, perhaps a useful output saying this will break. Or as mentioned in IRC a forced re-install within the PIP options would be the best option.

In this case, it simply was not working and took some effort to actually track the cause of the issue which could obviously be prevented in the future with some small improvements to this script.

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

The bug is not incomplete, I meant the first link is just a link to ARA, not a link to a bug there :)

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

Ok we need to adapt our bootstrap ansible script to be more resilient for that case, and add a test of the minimum ansible version required for our builds.

We could also express this issue in the docs to tell if you're using your own ansible, you could skip the bootstrap ansible script, but then need to circumvent the absence of our wrapper script and tools.

Cam J. Loader (cjloader)
Changed in openstack-ansible:
assignee: nobody → Cam J. Loader (cjloader)
Revision history for this message
Cam J. Loader (cjloader) wrote :

I just tested this against master and Queens, seems this issue has been resolved. Please re-open if you are seeing this again.

Changed in openstack-ansible:
status: Confirmed → Incomplete
Revision history for this message
Cam J. Loader (cjloader) wrote :

Also Newton is EOL.

Changed in openstack-ansible:
status: Incomplete → Won't Fix
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.