The ironic-conductor service creates with ansible /var/lib/ironic/httpboot and seems to configure other things to that directory, so it's possible that the content of that directory changes while the container is being configured. It is problematic if at the same time the ironic inspector container is also being configured; and the config volume removed.
It would be safer to use the same config volumes both these containers.
I think I found the reason.
Both container- puppet- ironic and container- puppet- ironic_ inspector run at the same time:
ironic 01:56:21.141861229 - 01:56:51.610467343
ironic_inspector 01:56:24.338754035 - 01:56:43.509309933
And don't have the same config_volume parameter; so the code that prevents the config_volumes to be archived at the same time can't happen: /github. com/openstack/ tripleo- ansible/ blob/master/ tripleo_ ansible/ ansible_ plugins/ modules/ container_ puppet_ config. py#L204- L230
https:/
The ironic-conductor service creates with ansible /var/lib/ ironic/ httpboot and seems to configure other things to that directory, so it's possible that the content of that directory changes while the container is being configured. It is problematic if at the same time the ironic inspector container is also being configured; and the config volume removed.
It would be safer to use the same config volumes both these containers.