ironic-conductor does not retry to connect to rpc if connection failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
High
|
Galyna Zholtkevych |
Bug Description
If Ironic Conductor can't connect to AMQP, it won't loop to try again later, like it's done in many other OpenStack services, and the process will fail.
See:
Ironic Conductor tries to start:
http://
But RabbitMQ resources for Ironic are created after:
http://
Ironic Conductor fails to start:
http://
And never try again. That's a bug because other OpenStack services use to loop again.
Changed in ironic: | |
assignee: | nobody → Haomeng,Wang (whaom) |
Changed in ironic: | |
status: | Incomplete → Confirmed |
importance: | Undecided → High |
Changed in ironic: | |
assignee: | Haomeng,Wang (whaom) → nobody |
Changed in ironic: | |
assignee: | nobody → Vadim Hmyrov (vhmyrov) |
Changed in ironic: | |
assignee: | nobody → Galyna Zholtkevych (gzholtkevych) |
Changed in ironic: | |
status: | In Progress → Incomplete |
I found the root cause is "AccessRefused: (0, 0): (403) ACCESS_REFUSED", do you make sure other openstack service will try again for such access refused case, can you share the logs if you have.
And I checked nova rpc starting code[1], did not find any loop logic for such rpc start fail case, so can you provide more details? Just want to see what behavior for other services.
[1] https:/ /github. com/openstack/ nova/blob/ master/ nova/service. py#L231