Andrew Bonney b0073df505 Fix lack of constraints for ironic-inspector ... OSA playbooks only call this role once for all Ironic containers (API and inspector). As a result, the wheel builds only happen once. If the first host (which is responsible for wheel builds) is an API container, these vars would prevent Ironic inspector requirements being accounted for, and as such no matching constraints will be generated. When the venv is deployed to the Ironic inspector container, the lack of constraints can cause dependencies which are too new to be installed, causing the service to fail. Alternatively this role could be called twice by the playbook for differing container/host roles, but as inspector is expected to be merged into ironic at some point this feels equally valid. Change-Id: I3952a4e5514824381410d87ed6d535f13ec40498 (cherry picked from commit a665f45a69) (cherry picked from commit d700ff19af)		2023-08-22 09:54:28 +00:00
..
debian.yml	Pass CA pass to Swift CLI	2022-11-25 10:56:59 +01:00
main.yml	Fix lack of constraints for ironic-inspector	2023-08-22 09:54:28 +00:00
redhat.yml	Pass CA pass to Swift CLI	2022-11-25 10:56:59 +01:00