openstack/kayobe
Code Issues Proposed changes

Clean up release notes

Browse Source 
This is a partial cherry-pick since only some changes were backported.

Change-Id: I96f00721c173cf095463424c0ca8779c54943591
(cherry picked from commit 99d03686936dd1378e0d50289dd0ab8f0badcd8d)
(cherry picked from commit 5bff84f80fb51c43fe0821e23d49741b849485f8)
This commit is contained in:
Pierre Riteau 2023-12-07 21:06:15 +01:00
parent f30dd43802
commit eb8ff22f6b
2 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
releasenotes/notes/honor-ssh-args-for-bootstrap-ba894df14ba58167.yaml
View File

@ -2,12 +2,12 @@
fixes: fixes:
- | - |
When determining whether or not a host needs bootstrapping, we attempt to When determining whether or not a host needs bootstrapping, we attempt to
connect to the host using ansible_user, if the login fails, we then assume connect to the host using ``ansible_user``, if the login fails, we then
that the host needs bootstrapping. In previous releases we used a manually assume that the host needs bootstrapping. In previous releases we used a
crafted ``ssh`` command. This did respect any customisations to the SSH manually crafted ``ssh`` command. This did not respect any customisations
arguments made through ansible configuration. We now use the raw module so to the SSH arguments made through Ansible configuration. We now use the raw
that these customisations are used when connecting to the host. One module so that these customisations are used when connecting to the host.
possible use case is to configure a jump host between the control host and One possible use case is to configure a jump host between the control host
the target hosts. If bootstrapping was needed, hosts will now show as and the target hosts. If bootstrapping was needed, hosts will now show as
unreachable in the summary stats at the end of the run. This can safely be unreachable in the summary stats at the end of the run. This can safely be
ignored. ignored.

8
releasenotes/notes/kolla-passwords-overrides-065fd6bb8eb9689d.yaml
View File

@ -6,9 +6,9 @@ fixes:
``kolla_ansible_default_custom_passwords`` and own dictionary with custom ``kolla_ansible_default_custom_passwords`` and own dictionary with custom
passwords in configuration files. Now passwords in configuration files. Now
``kolla_ansible_extra_custom_passwords`` should provide only user custom ``kolla_ansible_extra_custom_passwords`` should provide only user custom
passwords to add or override in the passwords.yml. passwords to add or override in ``kolla/passwords.yml``.
upgrade: upgrade:
- | - |
Now no need to combine ``kolla_ansible_default_custom_passwords`` and Introduces a new variable ``kolla_ansible_extra_custom_passwords`` to avoid
``kolla_ansible_custom_passwords`` in your custom configuration. Just use the need to combine ``kolla_ansible_default_custom_passwords`` and
``kolla_ansible_extra_custom_passwords`` to add or override passwords. ``kolla_ansible_custom_passwords`` when adding or overriding passwords.