Change-Id: I96f00721c173cf095463424c0ca8779c54943591

We are seeing the following issue since 2.15.7 was released:

    Pattern and root_dir should be of the same type, not <class
    'ansible.utils.unsafe_proxy.AnsibleUnsafeText'> and <class 'str'>

Change-Id: I5cb458132133d171037f8697072e6bd8858db01a

Change-Id: I57fe9a6a5037adc341617bd35d3df83c81acc5b0
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>

We no longer use these variables since we switched to the kolla Ansible
collection.

TrivialFix

Change-Id: I50238dd694edc7ee02be4bfdc56ebf3a603e05d2

Switch all dependencies to use the OpenStack 2023.2 release.

This commit should be reverted on the master branch once the
Kayobe stable/2023.2 branch has been cut and RC1 released.

Change-Id: I749a1ac30fa15cf7faa456fcb90c4ddbbef77cc9

Change-Id: I5cd9dacea10f0e00b3d481704f0949b6f5c4a69e

This variable was configuring enable_host_ntp in kolla-ansible, which
was removed in the Xena release.

Change-Id: I737598d3bbe40b933b4b727eccc3b2a76ed97cdb

Adds support for configuring vGPUs on NVIDIA hardware.

Closes-Bug: #2028843
Change-Id: I4c8481f7429dbf50d51e26bd7acee24e16ee6c79

The docker Python package was dropped from kolla requirements [1], but
we still need to install it to build container images.

[1] https://review.opendev.org/c/openstack/kolla/+/896644

Change-Id: I241884497f4fb707385eb12d5fcc187ed839f754

If inline Ansible vault encryption is used to define an encrypted
variable in kayobe-config, running 'kayobe configuration dump -l <host>'
fails with the following:

  Failed to decode config dump YAML file /tmp/tmp_fg1bv_j/localhost.yml:
  ConstructorError(None, None, "could not determine a constructor for
  the tag '!vault'", <yaml.error.Mark object at 0x7f1e5c7404c0>)

This change fixes the error by using the Ansible YAML loader which
supports the vault tag. Any vault encrypted variables are sanitised in
the dump output. Note that variables in vault encrypted files are not
sanitised.

Change-Id: I4830500d3c927b0689b6f0bca32c28137916420b
Closes-Bug: #2031390

Since using the to_bool function in more places in
I3a5a43fef9c3d68d0db02be12b9f892c437e513d, we are now more strict about
the result of the variable dump. If there are no controllers in the
inventory, the result will not be a valid boolean and the to_bool
function will exit non-zero.

This change fixes the issue by running against localhost, which should
always be in the inventory.

Change-Id: Idcfd9d335f11f6c4d676033128d207f62b363ee9

This fix was added when upgrading from CentOS Linux 8.2 to 8.3. This is
likely not required on currently supported operating systems.

Change-Id: Ic2c47ae4514d98ff18c5d17ba62b50c47f3929c1

Change-Id: I73fad29af6a57b29afea46947d1ae90546253a2a

I missed this when I refactored the code to fallback
to templating. We need to deduplicate before picking
the strategy for the fallback to work for symlinked files.

Change-Id: Iddd6c90a6daa41e1d1cdaa6b598491792c13394d
Closes-Bug: #2042689

Change-Id: I06b0bd4634ebb8b78baa23656c891333fd96b88b

Change-Id: Id80e7d28c20b1f9ecc52473013c78c28d2ab5532

Change-Id: I2577245440d510ab19f48915479a8e3575b996b7

Updating requirements.yml with latest os-networks role

Following up:
Ia3550644e5fc3e83f792e46d42b4c35d5eec4705

Change-Id: I9cb1b4c5329dc9db8562cf317616101d35f13edb