"Server didn't become active" in Devstack Gate Exercises

Bug #1101147 reported by Julien Danjou
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
High
Unassigned
devstack
Invalid
Undecided
Unassigned

Bug Description

Some tempest tests are failling because the instance didn't become active:

http://logs.openstack.org/19377/2/check/gate-tempest-devstack-vm-quantum/1585/console.html

James E. Blair (corvus)
no longer affects: openstack-ci
Revision history for this message
Andrew Laski (alaski) wrote :

Can you provide some more information that would help to reproduce this issue? Is something taking too long, not set up correctly, an exception being thrown...? Are you seeing this on every run of a certain patchset?

Changed in devstack:
status: New → Incomplete
Changed in nova:
status: New → Incomplete
Revision history for this message
James E. Blair (corvus) wrote :
Revision history for this message
Sean Dague (sdague) wrote :

This happens periodically, often what I see when looking at the devstack logs is that the instance came up, but the network didn't

Changed in nova:
status: Incomplete → Confirmed
importance: Undecided → Critical
Revision history for this message
Sean Dague (sdague) wrote :

Never mind the last comment, the network issue is a different bug

summary: - Instance didn't become active
+ Instance didn't become active in Devstack Gate Exercises
summary: - Instance didn't become active in Devstack Gate Exercises
+ "Instance didn't become active" in Devstack Gate Exercises
Changed in nova:
status: Confirmed → Triaged
importance: Critical → Medium
milestone: none → grizzly-rc1
importance: Medium → High
Revision history for this message
Russell Bryant (russellb) wrote : Re: "Instance didn't become active" in Devstack Gate Exercises

I'm going to move this to grizzly-rc-potential since it seems like something that should be on the "nice to have" list and shouldn't block grizzly-rc1.

Changed in nova:
milestone: grizzly-rc1 → none
tags: added: grizzly-rc-potential
Hans Lindgren (hanlind)
summary: - "Instance didn't become active" in Devstack Gate Exercises
+ "Server didn't become active" in Devstack Gate Exercises
Revision history for this message
Thierry Carrez (ttx) wrote :

Doesn't look like there is a clear way forward here... so probably not a good RC suggestion.

Changed in nova:
status: Triaged → Confirmed
tags: removed: grizzly-rc-potential
Revision history for this message
Jian Wen (wenjianhn) wrote :

Like bug 1101142, I think the reason is the poor performance of the devstack vm.

How many devstack vms were running on the host?
What was the load of the host machine?

Revision history for this message
Clark Boylan (cboylan) wrote :

We run all of our devstack gate host VMs on HPCloud currently (and have in the past also run them on Rackspace). For this reason it is not possible for us to know how many VMs were running on the hypervisor or to know what the load of that machine was at the time.

James E. Blair (corvus)
no longer affects: openstack-ci
Revision history for this message
Masayuki Igawa (igawa) wrote :
Revision history for this message
Ray Chen (chenrano2002) wrote :
Revision history for this message
Ray Chen (chenrano2002) wrote :

nova bug, devstack test works well

Changed in devstack:
status: Incomplete → Invalid
Revision history for this message
Joe Gordon (jogo) wrote :

There are many reasons why this can happen, this bug itself is too vague.

Changed in nova:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.