n-cpu fails init on timeout calling n-cond-cell1
Bug #1789484 reported by
Sean McGinnis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Smith | ||
Queens |
Fix Committed
|
Medium
|
Matt Riedemann | ||
Rocky |
Fix Committed
|
Medium
|
Matt Riedemann |
Bug Description
We've seen several cases now where n-cpu fails to start in gate runs. It appears that during the service init it tries to call out to the cell1 conductor. Logs show n-cond-cell1 did start about 1 second before this, but maybe too soon to accept API calls. Traceback in the n-cpu log has the message:
"MessagingTimeout: Timed out waiting for a reply to message ID"
tags: | added: compute gate-failure |
To post a comment you must log in.
Better logstash query - http:// logstash. openstack. org/#/dashboard /file/logstash. json?query= message: %5C%22_ determine_ version_ cap%5C% 22%20AND% 20tags: %5C%22screen- n-cpu.txt% 5C%22&from= 7d