Quantum service does not restart after reboot
Bug #1073999 reported by
Gary Kotton
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Undecided
|
Unassigned | ||
Folsom |
Fix Released
|
Critical
|
Eric Harney | ||
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
neutron |
Fix Released
|
Critical
|
Gary Kotton | ||
Folsom |
Fix Released
|
Critical
|
Gary Kotton | ||
oslo-incubator |
Fix Released
|
Critical
|
Gary Kotton | ||
Folsom |
Fix Committed
|
Undecided
|
Unassigned | ||
Grizzly |
Fix Released
|
Critical
|
Gary Kotton | ||
quantum (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi,
If the Quantum service starts before QPID then it does not listen on port 9696. The reason for is that the connection setup with the RPC hangs with the call: self.connection
Even when the qpidd service starts this does not work and Quantum is still waiting to get out of this function.
Thanks
Gary
Related branches
lp:~gandelman-a/ubuntu/quantal/quantum/2012.2.1
- Openstack Ubuntu Testers: Pending requested
-
Diff: 79 lines (+68/-0)1 file modifieddebian/changelog (+68/-0)
Changed in quantum: | |
importance: | Undecided → Critical |
tags: | added: folsom-backport-potential |
Changed in nova: | |
status: | New → Invalid |
Changed in oslo: | |
status: | New → Fix Committed |
tags: |
added: in-stable-folsom removed: folsom-backport-potential |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in oslo: | |
importance: | Undecided → Critical |
assignee: | nobody → Gary Kotton (garyk) |
Changed in oslo: | |
milestone: | none → grizzly-1 |
status: | Fix Committed → Fix Released |
Changed in quantum (Ubuntu): | |
status: | New → Fix Released |
Changed in quantum (Ubuntu Quantal): | |
status: | New → Confirmed |
tags: | removed: in-stable-folsom |
Changed in quantum: | |
milestone: | grizzly-1 → 2013.1 |
Changed in cinder: | |
status: | New → Incomplete |
status: | Incomplete → Invalid |
To post a comment you must log in.
The problem is also reproducible with nova-network.
Simple reproduction:
- shut down qpidd
- restart nova-network