When ``resolv_is_managed`` is set, Kayobe templates resolv.conf. This
patch stops NetworkManager from overriding these changes.
Closes-Bug: #2044537
Change-Id: I90b61dfe03d53c58327d2b15e70b7b8489bdfb47
This reverts commit 99f5b64956b795d4d2ac3f04c51db5a108da3560.
Reason for revert: 2023.2 has been branched and released
Change-Id: I38fc5dcadda5103d63a11022825e8e167408677d
Fix a logic issue when seed SNAT is not enabled. In this circumstance
Bifrost was generating ConfigDrive data with the default gateway unset
even when one is available on the admin network. This regression was
introduced in Ib847d3420dee374cec067cd8af519b510be04120 [1].
[1] https://review.opendev.org/c/openstack/kayobe/+/898434
Closes-Bug: #2045926
Change-Id: Ifd9f9cd389ac09448fc91dba74f8f09595698b55
Add file to the reno documentation build to show release notes for
stable/2023.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.2.
Sem-Ver: feature
Change-Id: I9ab85dfddf3b4ae6ba593649ed4310ca8cbec0e2
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
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
This variable was configuring enable_host_ntp in kolla-ansible, which
was removed in the Xena release.
Change-Id: I737598d3bbe40b933b4b727eccc3b2a76ed97cdb
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
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
Updating requirements.yml with latest os-networks role
Following up:
Ia3550644e5fc3e83f792e46d42b4c35d5eec4705
Change-Id: I9cb1b4c5329dc9db8562cf317616101d35f13edb
