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: 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

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

Default timeout is 5 and we're often hitting that on our poor man's
Ceph.

Change-Id: Ide92b3c32150c0045b0723155f94b21ea9cdce66

etcd is flakey and complaining over slow disk

Change-Id: I1f5191015b53bdb218cfeaa43586ecf2d71a161e

Change-Id: I246b14c9b547c6a0ff0be68ad57e723839cc3275

Change Ib7f72b2663199ef80844a412bc436c6ef09322cc
disabled horizon testing. This patch enabling
horizon tests again.

Change-Id: Iff670525c91c8adbcf2a01288b12456cb4a31809

This patch adds tests for neutron and designate DNS
integration.

Tests are based on scenarios described below in [1][2].

[1] https://docs.openstack.org/neutron/latest/admin/config-dns-int.html
[2] https://docs.openstack.org/neutron/latest/admin/config-dns-int-ext-serv.html

Change-Id: I3953f760458285e5c9a818599492c6176e857dde

Change-Id: I3501e6bf17ccb94adfcdb62956dceba9d67b0881

The version that we were capping to is no longer compatible with latest
upper-constraints.txt, so let us free float again.

The resulting linting errors are included for now to unblock the gate,
these will still need to be discussed or fixed later.

NOTE(kevko): Temporarily disabling horizon deployment, as it's not
possible to unblock gates without it

Co-Authored-By: Michal Arbet <michal.arbet@ultimum.io>
Change-Id: Ib7f72b2663199ef80844a412bc436c6ef09322cc

This reverts commit 94a74f58.

Reason for revert: Zun/Kuryr-libnetwork has switched to "local" scope which doesn't require docker 20 anymore. It should work for latest docker version. Related patches:
https://review.opendev.org/c/openstack/zun/+/903884

Change-Id: Ieb545ae5a5917322f599728587c3f04ea8356126

In Kolla CI K-A upgrade job needs docker_custom_config override
as docker_registry var is being used both for docker daemon
config - for kolla images build, and kolla-ansible container images
sources - where we're using quay.io mirror.
docker_custom_config gets precedence in docker daemon
configuration.

docker_custom_config was removed in [1].

[1] https://review.opendev.org/c/openstack/kolla-ansible/+/904067

Change-Id: I1e890223faf25b1169a49e22a9529f90806d2f3a

This adds an extra resize operation to core OpenStack tests. This should
be fast since we are only increasing the number of cores of the VM and
could help catch additional errors in CI tests.

Change-Id: Ia61b995dbffcda4f1e6494548df457231cb67bd7

HAProxy exposes a Prometheus metrics endpoint, it just needs to be
enabled. Enable this and remove configuration for
prometheus-haproxy-exporter. Remaining prometheus-haproxy-exporter
containers will automatically be removed.

Change-Id: If6e75691d2a996b06a9b95cb0aae772db54389fb
Co-Authored-By: Matt Anson <matta@stackhpc.com>

Change-Id: Id25b4407a8170f69e4cd7278e0aff64c609ace7d

Change-Id: I552fea9f9b461e57611f1d2aa5c767a1f4043ff8

Change-Id: I4d09018f4e921e90cbe7457c1f7fb025ef3acfa8

Change-Id: Id5c53b63e88502c999b89cbc62405bb8953fef3a

Adds a precheck to fail if non-quorum queues are found in RabbitMQ.

Currently excludes fanout and reply queues, pending support in
oslo.messaging [1].

[1]: https://review.opendev.org/c/openstack/oslo.messaging/+/888479

Closes-Bug: #2045887
Change-Id: Ibafdcd58618d97251a3405ef9332022d4d930e2b

Change-Id: I46c05a54171cbf43a51594998561db94af7d17e6

Change-Id: I373f6d13809674c521155ca51962785a8b1ac598

Similar to [1].

[1]: https://review.opendev.org/c/openstack/openstack-ansible/+/851426

Change-Id: I254f71d607353e0cf4d3d5ebafd6813287c4fa9f

Change-Id: I54f94c383ae5a1185b364495422e1ab79cbd1afb

This implements a global toggle `om_enable_rabbitmq_quorum_queues`
to enable quorum queues for each service in RabbitMQ, similar to
what was done for HA[0].

Quorum Queues are enabled by default.

Quorum queues are more reliable, safer, simpler and faster than
replicated mirrored classic queues[1].

Mirrored classic queues are deprecated and scheduled for removal
in RabbitMQ 4.0[2].

Notice, that we do not need a new policy in the RabbitMQ definitions
template, because their usage is enabled on the client side and can't
be set using a policy[3].

Notice also, that quorum queues are not yet enabled in oslo.messaging
for the usage of reply_ and fanout_ queues (transient queues).
This will change once[4] is merged.

[0]: https://review.opendev.org/c/openstack/kolla-ansible/+/867771
[1]: https://www.rabbitmq.com/quorum-queues.html
[2]: https://blog.rabbitmq.com/posts/2021/08/4.0-deprecation-announcements/
[3]: https://www.rabbitmq.com/quorum-queues.html#declaring
[4]: https://review.opendev.org/c/openstack/oslo.messaging/+/888479



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

Change-Id: Ie3963f5ed20f7fb61ef2e03f0cf12a4ea1c87c9c

This dependency was added to podman-py in version 4.8.0, but not added
properly to their requirements. Install it explicitly for our tox
and integration testing as a workaround.

[0] https://github.com/containers/podman-py/issues/350

Change-Id: I61a5fdfc4e505f2577185f0c0f1297cf2709be2c

Change-Id: Ia1de6d9452e2c900169e9b4ccb7dfc1280283909

This commit addresses a few shortcomings in the etcd service:
  * Adding or removing etcd nodes required manual intervention.

  * The etcd service would have brief outages during upgrades or
    reconfigures because restarts weren't always serialised.

This makes the etcd service follow a similar pattern to mariadb:
  * There is now a distiction between bootstrapping the cluster
    and adding / removing another member.

  * This more closely follows etcd's upstream bootstrapping
    guidelines.

  * The etcd role now serialises restarts internally so the
    kolla_serial pattern is no longer appropriate (or necessary).

This does not remove the need for manual intervention in all
failure modes: the documentation has been updated to address the
most common issues.

Note that there's repetition in the container specifications: this
is somewhat deliberate. In a future cleanup, it's intended to reduce
the duplication.

Change-Id: I39829ba0c5894f8e549f9b83b416e6db4fafd96f

This reverts commit b86c304a.

Reason for revert: We want to enable Quorum Queues by default in Caracal, without requiring two queue migrations between releases. See etherpad for details: https://etherpad.opendev.org/p/kolla-ansible-rmq-quorum-queues-proposal

Change-Id: Ia19ab97f538125475297976347c5da332a7fdda7

Change-Id: Id6ca24c058fabf0c68bcb5b6d1e58175aaf531eb

Changes name of ansible module kolla_docker to
kolla_container.

Change-Id: I13c676ed0378aa721a21a1300f6054658ad12bc7
Signed-off-by: Martin Hiner <m.hiner@partner.samsung.com>

docker_restart_policy: no causes systemd units to not get created
and we use it in CI to disable restarts on services.

Introducing oneshot policy to not create systemd unit for oneshot
containers (those that are running bootstrap tasks, like db
bootstrap and don't need a systemd unit), but still create systemd
units for long lived containers but with Restart=No.

Change-Id: I9e0d656f19143ec2fcad7d6d345b2c9387551604

Copy cat of I2cfd2667abb1ae8988b7a7fd9761b75c20a0eaa4

Co-Authored-By: Pierre Riteau <pierre@stackhpc.com>
Change-Id: If4feec0a86f9a50ed43920ecf4d0da8875c71f4e

Octavia now requires redis - see [1].

[1]: Iec3c8a4b4e257557dc8ec995c41d0ad7e88e13e2

Change-Id: I5aa489209984974b2345b1f5f7608db022a1405e