@rev164: nova-api ImportError: No module named compute_req_id
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nova-compute (Juju Charms Collection) |
Fix Released
|
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:/
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://
Build: http://
...
Last known good nova-compute/next amulet test:
rev163
lp:~openstack-charmers/charms/trusty/nova-compute/next
Sept 29
http://
-or-
http://
Related branches
- Billy Olsen: Approve
-
Diff: 246 lines (+1/-182)5 files modifiedconfig.yaml (+0/-10)
hooks/nova_compute_context.py (+0/-9)
hooks/nova_compute_utils.py (+0/-5)
templates/api-paste.ini (+0/-141)
tests/basic_deployment.py (+1/-17)
| Ryan Beisner (1chb1n) wrote | #1 |
| Chris Glass (tribaal) wrote | #2 |
| 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 |
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).