This reverts commit 94a74f58c7.
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
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>
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
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
Copy cat of I2cfd2667abb1ae8988b7a7fd9761b75c20a0eaa4
Co-Authored-By: Pierre Riteau <pierre@stackhpc.com>
Change-Id: If4feec0a86f9a50ed43920ecf4d0da8875c71f4e
When the kolla-ansible project has a cross dependency on
the kolla project, CI have to build an image from that change
locally. However, Podman refuses to push to localhost, so it is
necessary to set the local repo as insecure for the test.
Change-Id: I786b22ff0cd581f90ba4bec08842651a6509a745
Up till now the ARA plugin has been pinned to a very old version,
and is no longer functional.
This installs a much newer version of ARA and adds a README file
to guide developers on how to view the sqlite file.
The ARA plugin is installed by default, but not activated. This
is intended to catch a small amount of regressions and
integration failures.
Developers can enable the plugin by adding the string `#ara`
to their commit message. This avoids extra load on the CI.
Change-Id: Id8328e374c9590b1363026fa2b2b24e191183987
It's not needed anymore, since both Ceph and ansible-collection-kolla
are setting that by default.
Also fix test-core-openstack so it doesn't delete a server before
volume attachment test.
Change-Id: I20bd352479ee5562514084d0d11063e45e8b956a
We've seen issues in CI when keepalived haproxy check script returns
an error and keepalived is switching to backup and then again to primary
on a single node environment.
Closes-Bug: #2025219
Change-Id: Iba62e76b3cf83f3ade6df81288d2d77129ffc725