grenade upgrade fails to start any services in new
Bug #1317399 reported by
clayg
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Core Infrastructure |
Triaged
|
Medium
|
Unassigned | ||
| grenade |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
/new is just totally empty:
http://
I guess the initial setup get's smoke tests run against it before the upgrade - and they just failed?
This is the last sane thing n-cpu seemed to have to say about the node before the test cleanup came through and blew away the timed out task:
Not sure how to find the cause on that failure though... maybe libvirt?
Revision history for this message
| clayg (clay-gerrard) wrote | #1 |
| Changed in openstack-ci: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: gate-failure |
Revision history for this message
| Clark Boylan (cboylan) wrote | #2 |
Revision history for this message
| Sean Dague (sdague) wrote | #3 |
| Changed in grenade: | |
| status: | New → Invalid |
To post a comment you must log in.
Another instance of the initial smoke tests failing during a grenade upgrade:
http://
The ER fingerprint identified this failure as https:/
... but it actually looks more like https:/
http://
I'm not sure if this bug is actually the right place to track all of these, since the problem doesn't really seem to be that the upgrade failed, and just that smoke tests failed against the original deploy (best I can tell) - but I suppose each of these initial test failures is actually going to have it's own root cause for the real failure.
Which *may* be a libvirt issue?
http://
http://