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

Bug Description

/new is just totally empty:

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?

Tags: gate-failure
Revision history for this message
clayg (clay-gerrard) wrote :

Another instance of the initial smoke tests failing during a grenade upgrade:

The ER fingerprint identified this failure as

... but it actually looks more like

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?

Jeremy Stanley (fungi)
Changed in openstack-ci:
status: New → Triaged
importance: Undecided → Medium
tags: added: gate-failure
Revision history for this message
Clark Boylan (cboylan) wrote :

Added grenade as grenaders may have better insight into fixing this or if it is still an issue.

Revision history for this message
Sean Dague (sdague) wrote :

This grenade bug was last updated over 180 days ago, as grenade
is a fast moving project and we'd like to get the tracker down to
currently actionable bugs, this is getting marked as Invalid. If the
issue still exists, please feel free to reopen it.

Changed in grenade:
status: New → Invalid
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.