Followup on Id4588f4529a4522e68e22ce58711cb927fa68a9d to fix the
place of the RabbitMQ configuration and there are not only the
rabbitmq.conf and rabbitmq-env.conf but also advanced.config which
also often customized and more other files.
Change-Id: Iff0b28b770753c81ac526afd1ce6f61d77fad25c
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
Change the etc-hosts role to run on the overcloud group, as using
``ansible_play_hosts_all`` would exclude hosts when running with a
limit.
Also change the gather-facts-delegated role to run on the overcloud
group. The delegated task needs to be included separately as the hostvar
``ansible_host`` cannot be set dynamically based on a loop item in one
task. We loop over the batch indices here so that the tasks are included
in parallel, rather than in series.
Closes-Bug: #2051714
Change-Id: I0465eafa9e4ff37c96064ea8395f0bd461035b40
On newer versions of util-linux, the ``wipe_disks`` role was not
properly configured due to the fact that ``lsblk -J`` returns a slightly
different output than what was previously returned. Previously the
output would contain a key called ``mountpoint``, however this has been
changed to ``mountpoints``. This has now been fixed by looking at the
new key as well as the old key.
Closes-bug: #2051859
Change-Id: I2a59f4eb3ae27f37fda38e05924315887cb04c41
Currently building OVN container images and OVS container images are
mutually exclusive.
This becomes problem when all container images are needed to be built
at the same time.
``kolla_build_neutron_ovs`` is added to let user to build OVS even if
OVN is enabled when it's explictly set to true.
Default value ensures regex mapping behaves normally when
``kolla_build_neutron_ovs`` is not given.
Release note is also added.
Change-Id: I7efe883fce4117a5167b6db4a711004d77a44f81
These are currently not included in the regex we generate so aren't
built as part of the complete set.
Change-Id: I4f79b1b0887df72b11b768593ba45d89e75ce0d6
Closes-Bug: #2052428
Supports calling custom Kolla Ansible commands directly after a
``kayobe control host bootstrap``.
Change-Id: I19f188cc002f8578618003e90c0a4a154b806e49
This has now been removed from upstream docker-ce packages.
```
the devicemapper storage-driver has been deprecated and removed
```
and has shown deprecation warnings for some time.
This change also includes some fixes necessary for CI to pass:
* update the Zuul previous_release variable to 2023.2
Closes-Bug: #2051233
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/906858
Change-Id: I263f59ea77e39accffe4febe0d47e56b35d9800e
Prompts the user to confirm before deprovisioning any overcloud hosts.
The user is given a list of hosts which will be deprovisioned. Automatic
confirmation can be achieved by setting ``confirm_deprovison`` to
``yes``.
Change-Id: I6eea5bb7c268912e6f39627f64c92715877311a3
Previously it was only possible to define custom playbook hooks in the
base configuration, and not in environments. This could be limiting in
cases where different environments require different hooks.
With this change it is now possible to define hooks both in the base
configuration and in environments.
Change-Id: Ic003c18402177318ac1aa4c2d851263893bd4e9f
When ``resolv_is_managed`` is set, Kayobe templates resolv.conf. This
patch stops NetworkManager from overriding these changes.
Closes-Bug: #2044537
Change-Id: I90b61dfe03d53c58327d2b15e70b7b8489bdfb47
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
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
This is a backwards compatability improvement, since it was previously
permitted to have a config file that templated to invalid yaml/ini.
Change-Id: I53a0894cc64e83c7342a82ad987b7e5a4696ece2
Closes-Bug: #2042690
Kayobe has fairly coarse-grained default groups - controller, compute,
etc, which work well in the majority of cases. Kolla Ansible allows much
more fine-grained placement on a per-service basis, e.g.
ironic-conductor. If the operator has taken advantage of this
fine-grained placement, then it is possible that some of the assumptions
in Kayobe may be incorrect. This is one downside of the split between
Kayobe and Kolla Ansible.
For example, Ironic conductor services may have been moved to a subset
of the top level 'controllers' group. In this case, we would not want
the Ironic networks to be mapped to all hosts in the controllers group -
only those running Ironic conductor services. The same argument can be
made if the loadbalancer services (HAProxy & keepalived) or Neutron
dataplane services (e.g. L3 & DHCP agents) have been separated from the
top level 'network' group.
This change abstracts the placement of Ironic conductor Ironic
inspector, loadbalancer and network services into separate variables,
rather than referencing the top level 'controllers' and 'network' groups
directly. These variables may be updated by the operator to match the
service placement.
Change-Id: Idbf181c795ee98ad653f11ae483f9dab4ef1b599
Fixes an issue when user forgot to combine
'kolla_ansible_custom_passwords',
'kolla_ansible_default_custom_passwords' and own dictionary with
custom passwords in configuration files. Now
'kolla_ansible_extra_custom_passwords' should provide only user
custom passwords to add or override in the passwords.yml.
Change-Id: I4813a1f6ab9cb566596e806bd0ada6dff342d119
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>