@rev164: nova-api ImportError: No module named compute_req_id

Bug #1501924 reported by Ryan Beisner on 2015-10-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nova-compute (Juju Charms Collection)
Critical
Chris Glass

Bug Description

I believe lp:nova-compute/next rev164 has broken nova-api for Precise-Icehouse.

From amulet test:
nova-compute/0 `pidof -x nova-api` returned 1 ERROR subprocess encountered error code 1

From nova-compute/0 nova-api log:
2015-10-01 21:32:53.684 20347 CRITICAL nova [-] ImportError: No module named compute_req_id

The automated test for this merge proposal reported back after the branch was already merged. That test says the nova-api service didn't start on the nova-compute/0 unit for the Precise-Icehouse deployment:

https://code.launchpad.net/~tribaal/charms/trusty/nova-compute/enable-api-rate-limiting/+merge/272884
charm_amulet_test #6926 nova-compute-next for tribaal mp272884
    AMULET FAIL: amulet-test failed

AMULET Results (max last 2 lines):
make: *** [test] Error 1
ERROR:root:Make target returned non-zero.

Full amulet test output: http://paste.ubuntu.com/12633828/
Build: http://10.245.162.77:8080/job/charm_amulet_test/6926/

...

Last known good nova-compute/next amulet test:

rev163
lp:~openstack-charmers/charms/trusty/nova-compute/next

Sept 29
http://10.245.162.77:8080/view/Dashboards/view/Amulet/job/charm_amulet_test/6881/
 -or-
http://paste.ubuntu.com/12634611/

Related branches

Ryan Beisner (1chb1n) wrote :

FYI:

I re-ran the nova-compute/next amulet Precise test from rev163, confirmed success (in my bastion host).

I re-ran the nova-compute/next amulet Precise test from rev164, confirmed failure (in my bastion host).

Chris Glass (tribaal) wrote :

Reverting this change.

Changed in nova-compute (Juju Charms Collection):
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Chris Glass (tribaal)
Changed in nova-compute (Juju Charms Collection):
milestone: none → 15.10
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers