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

Change-Id: I7df734cf15eba1af4da92f9c4ef12cc761442ca1

Collections version taken from official Ansible 7 package [1]
and limited to the same major version.

[1]: https://github.com/ansible-community/ansible-build-data/blob/main/7/ansible-7.7.0.yaml

Change-Id: I0f1ea9717397adc2d2c3215d74ec3759f351a57a

Skyline is a new service for dashboard.
This patch adds a CI scenario which tests Skyline deployment.

Depends-On: https://review.opendev.org/c/openstack/kolla/+/826948
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/828464

Implements: blueprint skyline
Change-Id: I48488a24d6c8a03cd129929347b1bdac25f198b0

This avoids the need to use a proxy, or some other means, to connect to
Prometheus. This is disabled by default and can be enabled by setting
enable_prometheus_server_external to true.

Change-Id: Ia0af044ff436c2a204b357750a16ff49fcdfec45

This allows us to share variables between jobs without inheriting any
of the pre-run, post-run or cleanup playbooks of the parent job. These
run due to the zuul inheritance rules, see:

https://zuul-ci.org/docs/zuul/latest/config/job.html#job



Signed-off-by: Will Szumski <will@stackhpc.com>
Change-Id: Id0a34778accafdc62ebe916e81d69f31c6274d4c

Add support for automatic provisioning and renewal of HTTPS
certificates via LetsEncrypt.

Spec is available at:
https://etherpad.opendev.org/p/kolla-ansible-letsencrypt-https

Depends-On: https://review.opendev.org/c/openstack/kolla/+/887347


Co-Authored-By: Michal Arbet <michal.arbet@ultimum.io>
Implements: blueprint letsencrypt-https
Change-Id: I35317ea0343f0db74ddc0e587862e95408e9e106

Enable the jobboard feature for the Octavia amphora provider. This
requires Redis as a dependency, a precheck is added to ensure proper
configuration.

https://docs.openstack.org/octavia/latest/install/install-amphorav2.html

Change-Id: Iec3c8a4b4e257557dc8ec995c41d0ad7e88e13e2

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

Depends-On: https://review.opendev.org/c/openstack/kolla/+/899465
Change-Id: I876536263865077b7ecb2288ad95061292babcce

In order to drop docker pip package from requirements.txt in Kolla
we need to start installing that here.

Change-Id: Ifd3b86afb65760c3b3ce7f26feebdaf0789fb525

This change adds basic deployment based on Podman
container manager as an alternative to Docker.

Signed-off-by: Ivan Halomi <i.halomi@partner.samsung.com>
Signed-off-by: Martin Hiner <m.hiner@partner.samsung.com>
Signed-off-by: Petr Tuma <p.tuma@partner.samsung.com>
Change-Id: I2b52964906ba8b19b8b1098717b9423ab954fa3d
Depends-On: Ie4b4c1cf8fe6e7ce41eaa703b423dedcb41e3afc

This reverts commit d3c4ff8b.

Reason for revert: workaround is present

Change-Id: I40f794ce5f401a7357099dff10f7f8e05e1c4826

Change-Id: I5df9cf14f16a7c08cccf053302bbda227526a4a8

Change-Id: I7b1a5bef0cb1dc1dfad1c6c4ca486e6ead847f12

It seems latest ansible-core 2.14 and 2.15 breaks a filter
in kolla-ansible - let's pin for now and fix the issue in a
separate patchset.

Change-Id: I200ad775094230e4bf8bb40988c12ea03471008f

Change-Id: Ic153a91beb30daa334ccbb0430ce8340bd6c480f

Following Monasca initial removal in [1]

[1]: I6fc7842bcda18e417a3fd21c11e28979a470f1cf

Change-Id: I94d6f102e8da3882f37f3007639b917c49f907a9

Closes-Bug: #2036741

Change-Id: Ib448d04e43dff78e344064161beadae917c41206

Initially Ubuntu/Debian used /var/run/openvswitch as default OVN run dir,
it seems it has changed long time ago - but we haven't picked that up on latest
OVN DB refactor.

Adding in OVN and OVN upgrade Debian jobs to enhance coverage.

Closes-Bug: #2035584

Change-Id: I78967c4499269578ac921ad9a553946b65e1293f

it is already in test_openstack_logged function

Change-Id: I2d092b4cf6dc6527d1c3c5e172349e480c2366d3

Change-Id: If9636aaa76a7dc094223c3f096d96c96ecd0c8e7

This reverts commit 2524ec42.

Reason for revert: I don't think we need it anymore

Change-Id: I9f2871cf3de1a09952fc5c236da2f78e4d930bf5

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

Change-Id: Ia982df80d688522dbaa5fc3e462c1a009d512cb6

Sets the variable ``om_enable_rabbitmq_high_availability`` to ``true``
by default. An upgrade will therefore require some manual steps to
migrate from transient to durable queues. Note that this will be
caught by this precheck:
https://review.opendev.org/c/openstack/kolla-ansible/+/880274

Also updates the CI upgrade jobs to perform this migration. This will
need to be removed in Caracal.

Related-Bug: #2031294

Change-Id: I26a70d4722aaa4663eced5f5337840474c7b961c

MariaDB bootstrap has a phase where the first MariaDB container
is running with Galera bootstrap - after a check that WSREP
is synced is successful - we restart the container.

The bootstrap container is named mariadb and running with
docker_restart_policy: "no" - the restarted container should be running
in systemd.

Before this patch the code created a systemd unit but it was initially
stopped - so stopping was always a success - and the container would be
killed with SIGKILL on removal (which obviously breaks MariaDB).

This patch also improves docker/systemd stops by waiting for real
unit/container stop and adds failing CI for containers that are
killed with signal 9.

Closes-Bug: #2029613

Change-Id: I0a03e509ce228a50e081fcab44d2b4831251190c

Change-Id: I4c5ade2d687684f37df83b44a852d88c77067680

Change-Id: I7b998b34881084a68669dc9351ea1937c61534fa

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

Ansible 2.14.3 introduced a change that broke the method used for
restarting MariaDB and RabbitMQ serially [1][2]. In
I57425680a4cdbf0daeb9b2cc35920f1b933aa4a8 we limited to 2.14.2 to work
around this. Ansible upstream claim this behaviour was unintentional,
and will not fix it.

This change moves to a different approach where we use separate plays
with a 'serial' keyword to execute the restart.

This change also removes the restriction on the maximum supported
version of 2.14.2 on ansible-core - any 2.14 release is now supported.

[1] https://github.com/ansible/ansible/commit/65366f663de7d044f42ae6dd53368fd4c1f88b35
[2] https://github.com/ansible/ansible/issues/80848

Depends-On: https://review.opendev.org/c/openstack/kolla/+/884208

Change-Id: I5a12670d07077d24047aaff57ce8d33ccf7156ff

The kolla-genpwd, kolla-mergepwd, kolla-readpwd and kolla-writepwd
commands now creates or updates passwords.yml with correct
permissions. Also they display warning message about incorrect
permissions.

Closes-Bug: #2018338
Change-Id: I4b50053ced9150499d1d09fd4a0ec2e243cf938b
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>

Setting the CONTAINER_ENGINE env var was missed in one spot in [0].

[0] I395d2bdb0dfb4b325b6ad197c8893c8a0f768324

Change-Id: I29868d59cbef2bd5707ab20d2c30a2d8f6d6060e

Depends-On: https://review.opendev.org/c/openstack/neutron/+/878535
Change-Id: I05d8b29b59a7de76da488f68775547a8f0f11d0f

We limit to 2.14.2 due to a regression in ansible-core [1] that breaks
conditional include_task loops in handlers. This is used for controlled
restarts of MariaDB and RabbitMQ.

[1]: https://github.com/ansible/ansible/commit/65366f663de7d044f42ae6dd53368fd4c1f88b35



Change-Id: I57425680a4cdbf0daeb9b2cc35920f1b933aa4a8
Co-Authored-By: Michal Nasiadka <michal@stackhpc.com>