Change-Id: I33a3ec11b0cdef94b08cd7551008284755824cb7

When cert generation during upgrade was fixed
it was omitted to also redirect stderr to the log file.

This commit fixes that.

Introduced-By: Ib257f8342c392b78e02ae31588ce5c6f8943f5b8
Closes-Bug: #2078364

Signed-off-by: Sven Kieske <kieske@osism.tech>
Change-Id: I43ca7d782bdcc53dcbc59dcf82ac1daa48e85ad5

There is a bug in current `tests/upgrade.sh`. If a
developer adds a new type of certificate i.e. for
RabbitMQ, it is not generated on upgrade because the
script does not run the `certificates` role.
This fix adds the `certificates` role to the script.

Change-Id: Ib257f8342c392b78e02ae31588ce5c6f8943f5b8

The prometheus-msteams project is no longer maintained [1]. As a result
support for deploying prometheus-msteams via kolla-ansible has been
dropped. Users are encouraged to migrate to the native Prometheus
Alertmanager integration with Microsoft Teams [2].

[1] https://github.com/prometheus-msteams/prometheus-msteams/issues/343
[2] https://prometheus.io/docs/alerting/latest/configuration/#msteams_config

Change-Id: I93d28ef138b4e784465f3a7eaa11101ea5877050

Library "distutils" is deprecated in Python 3.10:
https://peps.python.org/pep-0632/

The versions previously referenced using StrictVersion should be old
enough that they will not be used in a Dalmatian deployment:

- Ansible 2.11
- Docker API 1.42, included since Docker engine 23.0.0

Change-Id: Ie315004715a1cb5a91dd54bc64b0a8fd0af650ec

Change-Id: Ic87fb3e4c014d3090869d5631e02982829df6312

RabbitMQ uses quorum queues by default in both Dalmatian and Caracal, so
we don't need to run the migrations.

Change-Id: I1244f453af8f339cc3db7300951e366196e5291a

Change-Id: I2546d714d1e6a1b648a4c6242ece18a2108b9183

Closes-Bug: #2075966

Change-Id: I6ed82ecc7ca82c09aacb2a65254f794c72365188

Interface names with dashes can cause problems in Ansible since dashes
are replaced with underscores when referencing facts.

Change-Id: Ib15f81120d353ebcf8965dc0aaba90f3a9b0ec44
Related-Bug: #1927357

As our CI is ipv6 only and using cirros for tests.
Therefore we need to set force_config_drive = true.

Change-Id: I07058a4b30d0de1aaf8e82656024c5f6a99b290b

Closes-Bug: #2070051

Depends-On: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/923544

Change-Id: I221eb136e77c61aef39e8646b48b927352d1419d

There was a bug where setting the test command
for the health check to 'NONE' would throw an error
in podman_worker. This was problematic since K-A
uses 'NONE' as an indicator that the health check is not enabled.

Closes-Bug: #2071912
Change-Id: I3140bb79eace58b23f579be3da569c502c52c38c
Signed-off-by: Ivan Halomi <ivan.halomi@tietoevry.com>

ansible-core 2.16 and later requires python 3.10+ (see [1])

[1]: https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix

Change-Id: Id5e10872de413e7b476c5343360d73c109b9667a

When using short notations like `1g` or `512m` to define the
container dimensions, we are always getting the container to
being restarted in each kolla-ansible run, even with no real
changes in the container configs.

Change-Id: Ic8e2dd42b95a8f5c2141a820c55642a3ed7beabd
Closes-Bug: #2070494

Change-Id: I9a71da5a00a4580b491a9c10ca34094b6654b438

it is already in init-runonce in the previous release

Change-Id: I7edc1216d3e74e995ed2051e9fd3d93196014836

Change-Id: I517d9f078a4dbb34178c851c1bc8b51b738882da

This reverts commit 0ec71d87.

Reason for revert: fixed now

Change-Id: I33d62e910ff6151eb03c814ee7b8984c6f4e5308

Depends-On: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/920172

Change-Id: Ieba0baf154ead063a1bc244aaadd4ca53c814ad3

This reverts commit 5b431f0f.

Reason for revert: the any_errors_fatal play parameter is not templated
by Ansible (tested up to ansible-core 2.15.9). This behaviour is
demonstrated in [1].

This means that "{{ kolla_ansible_setup_any_errors_fatal }}" is always
interpreted as 'true', regardless of the value of
kolla_ansible_setup_any_errors_fatal.  This is particularly bad because
the default value of kolla_ansible_setup_any_errors_fatal is false.

We now have gather_facts_max_fail_percentage which can be set to 0 to
provide the same functionality.

[1] https://github.com/markgoddard/ansible-experiments/tree/master/15-fatal-errors

Change-Id: I2e0ea49701b5900eae26434bcdb6b1bb44507ee7

It was deprecated in Antelope cycle.

Change-Id: I499e69ec6db63e4067e49376e2a1f3e01e48fe62

It's inactive and hasn't produced a 2024.1 release [1].
In addition to that, there's a CVE that hasn't really been patched [2].

Also drop outward_rabbitmq that was used only with Murano.

[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects
[2]: https://lists.openstack.org/archives/list/openstack-announce@lists.openstack.org/thread/4FYM6GSIM5WZSJQIG4TT5Q3UBKQIHLWX/

Change-Id: I691205730b0e10a42ce61f3340cc39ee51bd1010

It's inactive and hasn't produced a 2024.1 release [1].

[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects

Change-Id: I217b3633f07e5b2c657e20b19aaa4fbb46535a97

It's inactive and hasn't produced a 2024.1 release [1].

[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects

Change-Id: I888963751b6e1ed080588297c2889e700431516c

It's inactive and hasn't produced a 2024.1 release [1].

[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects

Change-Id: Ic988295bc5b8acb19df008fe0d52a3bcc6de2135

It's inactive and hasn't produced a 2024.1 release [1].
There are some efforts to restore Freezer, but let's remove it for now.

[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects

Change-Id: Ie42012af9e5c64bca23a6e6826bfc4651fd194bd

Fix existing spelling errors

Change-Id: Ie689cf5a344aaa630a4860448b09242333a8e119

double the timeout from 5 to 10 seconds.
this should prevent errors like these:

https://zuul.opendev.org/t/openstack/build/547464fe844e4e8ba34faac33f615c92/log/primary/logs/ansible/test-core-openstack#1210



Change-Id: I47157973a8152154a264cc1914b6d2b55bc08cd1
Signed-off-by: Sven Kieske <kieske@osism.tech>

It's needed for Python3.12 support, because imp has been dropped [1].

Also shlex dropped s=None support [2].

[1]: https://docs.python.org/3/whatsnew/3.12.html
[2]: https://github.com/python/cpython/issues/94352

Change-Id: I23f37897ea08ac708f6df485f699122df647e552

this produces errors itself, e.g.:

```
 for container in $failed_containers
+ docker inspect prometheus_openstack_exporter
[]
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.45/containers/prometheus_openstack_exporter/json

": dial unix /var/run/docker.sock: connect: permission denied
```

Signed-off-by: Sven Kieske <kieske@osism.tech>
Change-Id: I280e2660d187d966098ae39df6392503b1aa5bdf

This reverts commit 0b1a59dd.

Reason for revert: Upstream Fix available at https://github.com/containers/podman-py/pull/351

Change-Id: Iadb74ffb5a747bd16e6acebd6a9c22b3b7198fd0

Some multinode jobs have been failing due to galera suspecting inactive nodes
Tweak it as per [1].

[1]: https://galeracluster.com/library/documentation/recovery.html

Change-Id: I5577ea2c23d6dbd440bd52899a30ea9531996256

Change-Id: I5b4a30e605bb143cf342f83f0c811c25046269ef

Change-Id: Iab40eb92c7e4a9092471bef9d4477a4fa34f1c85

Currently RMQ 3.13 fails on ipv6 multinode scenario, use 3.12 from 2023.1
until [1] gets resolved.

[1]: https://github.com/rabbitmq/rabbitmq-server/issues/10728

Change-Id: If11710e99cf2e340e558d68e2071c1bb16825e55

We replaced redis with etcd in that scenario, but GATE_IMAGES
are not updated.

Change-Id: Ie9d6642f8ce51bc2a35b800c6c149153c14378db

This is a CI level check that we are able to recover from one
node OVN NB/SB DB failure

Change-Id: I3185811fed50b2ab18f9493c6dc9f4afc970ab34

Ironic enabled secure RBAC with system scoped enforcement [1].

Some API calls, for instance 'baremetal:driver:get' needs system
scope role by design [2], even with elevated access project scope
service role [3].

[1] https://review.opendev.org/c/openstack/ironic/+/902009
[2] https://opendev.org/openstack/ironic/src/commit/8ec56066223301230ac0ed0f0c471a10d366b474/ironic/common/policy.py#L1349-L1357
[3] https://review.opendev.org/c/openstack/kolla-ansible/+/908007

Related-Bug: #2051837

Change-Id: Id6313d7dd343b82d4c9ccf7bf429d340ea0e93d1

The upgrade job needs the haproxy exporter group, which
was missing from the inventory.

Change-Id: Ie4ecf283a2f4ac056ace5e76f2acc4ba1a8fe0b4