nova-compute logging exception when waiting on nova-conductor to start
Bug #1137994 reported by
Russell Bryant
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Russell Bryant | ||
oslo-incubator |
Fix Released
|
Medium
|
Russell Bryant | ||
Grizzly |
Fix Released
|
Medium
|
Russell Bryant |
Bug Description
When nova-compute starts up, it loops around waiting for nova-conductor to respond before it proceeds with its startup process. If nova-conductor doesn't respond to a ping request, it results in an exception in the log. This is an expected type of failure that should be handled gracefully and not make a mess in the log. Here is an example:
http://
Changed in nova: | |
assignee: | nobody → Russell Bryant (russellb) |
importance: | Undecided → Medium |
status: | New → Confirmed |
milestone: | none → grizzly-rc1 |
Changed in oslo: | |
milestone: | none → grizzly-rc1 |
Changed in oslo: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-rc1 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/23295
Review: https:/