kolla-ansible unconditionally configures ironic-inspector with rabbitmq transport
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
In Progress
|
Medium
|
Sven Kieske | ||
Antelope |
In Progress
|
Medium
|
Unassigned | ||
Bobcat |
In Progress
|
Medium
|
Unassigned | ||
Caracal |
In Progress
|
Medium
|
Sven Kieske | ||
Yoga |
In Progress
|
Medium
|
Unassigned | ||
Zed |
In Progress
|
Medium
|
Unassigned |
Bug Description
Hi,
a user reported issues in #openstack-ironic deploying kolla-ansible with ironic-inspector in HA fashion on three controllers.
in the discussion it was brought to light, that we always configure a rabbitmq transport, even if ironic-inspector is not deployed HA, which is not necessary (instead we should use "transport_
back in the day the rabbitmq support was conditional on the fact if TLS was enabled, but this was changed in: https:/
I thus suggest that we therefore implement a precheck if ironic-inspector is deployed HA, and if it is not, we set the transport url accordingly.
relevant ironic specs (unfortunately there seem to be no more detailed docs about this):
https:/
I was also told that running ironic-inspector in HA mode is still considered experimental. I have no personal experience myself if there are any known bugs or if we should disallow HA deployments for this component (I guess we can't do the latter, because it was already possible in the past to do so).
Notice, this is only about ironic-inspector, not about ironic itself or other sub components of ironic.
Going forward, if we reach consensus, I would go on implementing the above mentioned solution.
Thanks.
description: | updated |
Changed in kolla-ansible: | |
assignee: | nobody → Sven Kieske (s-kieske) |
So it seems this is not really stable in an HA environment because of issues with the rabbitmq transport, see these error logs from the user:
https:/ /paste. opendev. org/show/ bscQiIEnqqfwzW2 Vv3yx/
https:/ /paste. opendev. org/show/ bTfJ1XRpmkqDw2J isoZr/
this was on stable/2023.2
relevant error snippet:
2024-02-22 12:57:03.472 7 ERROR ironic_ inspector. main oslo_messaging. exceptions. MessagingTimeou t: Timed out waiting for a reply to message ID 4abead957e784d1 8b3a98e38b6d83e 48
ironics (dtantsur) suggestion is, to always use the "fake://" transport and start only one copy of inspector until the upstream HA work is done and merged (see the second spec)