Running bifrost on Ubuntu 14.04 LTS results in segmentation fault

Bug #1459801 reported by Julia Kreger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bifrost
Fix Released
Critical
Unassigned

Bug Description

Encountering a segmentation fault running the test script on 14.04LTS upon the step where shade installation is taking place with a -I parameter on the command forcing re-installation.

19:31 < TheJulia> cinerama: Your on 14.04LTS right?
19:31 < cinerama> TheJulia: yep
19:31 < cinerama> TheJulia: so the thing that breaks it is including "-I"
19:31 < cinerama> TheJulia: if i run it with --no-cache-dir i'm good
19:32 < cinerama> TheJulia: it complains about ownership of ~/.cache/pip/http and exits 139 without that

Changed in bifrost:
status: New → Confirmed
importance: Undecided → Critical
Revision history for this message
Stephane Miller (stephaneeee) wrote :

I've experimented with this a bit trying to drill down to the bug. It appears to be a problem with decoding the json containing the output of the command run, which happens at /opt/stack/ansible/lib/ansible/utils/__init__.py line 547. Unfortunately I was not able to isolate what in particular is going wrong.

Running pip either without the "-I" option or with "--no-cache-dir" seems to resolve the issue. Since supplying "-I" is slowing down our run Julia and I agreed that the best way to get things in order would be to omit it.

In the medium term, I'd like to look at using ansible's pip module rather than using command to run pip.

Revision history for this message
Stephane Miller (stephaneeee) wrote :

Also, for the record, pip install -I runs fine by itself - it's just causing ansible-playbook to segfault.

Revision history for this message
Stephane Miller (stephaneeee) wrote :

https://review.openstack.org/#/c/186626/ which has been merged closes this issue.

Changed in bifrost:
status: Confirmed → Fix Committed
Changed in bifrost:
milestone: none → 0.0.1
status: Fix Committed → Fix Released
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.