OpenStack Compute (nova)

nova's VM stuck in build state when using quantum network manager

Bug #931788 reported by Yapeng Wu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned
devstack
Invalid
Undecided
Unassigned
neutron
Invalid
Undecided
Unassigned

Bug Description

When trying devstack, I found that the latest nova code could not spawn instance using quantum network manager.
The nova version is taking from master branch.

Tags: nova quantum
Yapeng Wu (yapengwu)
no longer affects: ubuntu
Revision history for this message
Dean Troyer (dtroyer) wrote :

Is this still a problem with E4 or current trunk (soon to be essex-RC1, to be cut tomorrow, 3/13)? If so, we need some specifics on the configuration and error. Please include (via pastebin) the output of DevStack's tools/info.sh at a minimum.

Changed in devstack:
status: New → Incomplete
Revision history for this message
Yapeng Wu (yapengwu) wrote :

It has been solved in E-4.
Please mark it invalid. Thanks.

Ying Chun Guo (daisy-ycguo)
Changed in nova:
status: New → Invalid
Revision history for this message
Gary Kotton (garyk) wrote :

Does this still happen with the current devstack installation. I am able to deploy instances using Quantum linuxbridge and OVS plugins.
Please clarify.

Changed in quantum:
status: New → Incomplete
Revision history for this message
dan wendlandt (danwent) wrote :

Given the age of this bug, i'm marking as invalid, as tons of stuff has changed since then. Any issues with master can be filed as a new bug.

Changed in quantum:
status: Incomplete → Invalid
Changed in devstack:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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