compute agent gives up discovery if it receives a HTTP 503 from nova-api
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Triaged
|
Low
|
Unassigned |
Bug Description
If the ceilometer-agent on the compute node is started before the Nova API is quite ready to receive requests and subsequently receives a HTTP 503 error, it gives up discovery and goes into a indefinite loop doing nothing.
The end user will have to identify this and manually restart the ceilometer-agent on the compute nodes to have meters updating.
ceilometer-agent should keep retrying discovery until it succeeds.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
2016-11-23 08:01:44.659 1862 ERROR ceilometer.
i don't know if we should retry until it succeeds but i understand the bug. maybe it's better to just let the service die after retrying for set time.
can you confirm what code branch you see this error on?