kolla-ansible --limit option is broken when upgrading nova
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
it might be debatable if we want to support this use case (but I think it might be used in the wild).
regardless here is what doesn't work:
here we can see that "nova-status upgrade check" is run on the first host in group "nova-api", regardless which --limit option was used.
as the result is registered as a host var via the "register" keyword[0] it can not be accessed directly by other hosts, as a result the check for the result fails: https:/
a workaround might be to use set_fact or to document that we don't support ansibles --limit option.
This was tested on an upgrade from zed to 2023.1 with ubuntu based hosts.
kind regards
Sven
[0]: https:/
so the play was limited to a certain subset of compute nodes, which don't necessarily contain the nova-api nodes. the play then breaks in the next step, because the result is not set from the host var perspective.