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 patch fixes ovs-dpdk script as options
in DPDK changed and PCI whitelist config changed
from '-w' to '-a' as per [1].
[1] db27370b57
Closes-Bug: #2058372
Change-Id: Iae812a4a255c13a42b2d6a691e265922d220f4c8
This reverts commit 0b1a59dd8cc2b402b5a0ad9b02144edd1daf40ca.
Reason for revert: Upstream Fix available at https://github.com/containers/podman-py/pull/351
Change-Id: Iadb74ffb5a747bd16e6acebd6a9c22b3b7198fd0
support for jammy was added to yoga in:
https://review.opendev.org/c/openstack/kolla-ansible/+/869127
it should thus be perfectly fine to directly upgrade to jammy
and then upgrade to zed.
Signed-off-by: Sven Kieske <kieske@osism.tech>
Change-Id: Id77704f4386b48c9bfd7b684bee3fb47d2b4a93a
This way the playbooks won't try to set ipv6 systemctl options
unless ipv6 is available on the system.
Closes-bug: #1906306
Change-Id: Icccfc1c509179c3cfd59650b7917a637f9af9646
This patch fixes ovs-dpdk images pull by adding
the variable kolla_role_name to the ovs-dpdk vars, so
services-image-pull can work correctly.
Closes-Bug: #2041864
Change-Id: I2e799290a57ebfacbc0ff9a0b1ca3dc956c513df
Signed-off-by: German Espinoza <gespinoza@whitestack.com>
This patch fixes the creation of the openvswitch
bridge by fixing an ansible task that was rewritten
to use an ansible module, but unfortunately, its loop
was implemented incorrectly.
Closes-Bug: #2056332
Change-Id: Ia55a36c0f9b122b72d757ca973e7d8f76ae84344
Tooz 6.0.1 includes commit [1], which introduced
parsing the username from the Redis connection URL.
As a result, services started authenticating as admin
which, by the way, was incorrect even before, as either
a created user or the default one should have been used.
The reason it worked before is simply because the username
'admin' wasn't parsed anywhere.
This patch fixes the user being used and sets the correct
'default' one.
[1] https://review.opendev.org/c/openstack/tooz/+/907656
Closes-Bug: #2056667
Depends-On: https://review.opendev.org/c/openstack/kolla/+/911703
Change-Id: I5568dba15fa98e009ad4a9e41756aba0fa659371
there are currently known bugs in our interaction with the ansible
--limit option. document those and recommend not to use this like it
was agreed in the kolla meeting:
https://meetings.opendev.org/meetings/kolla/2024/kolla.2024-02-21-14.00.log.txt
Signed-off-by: Sven Kieske <kieske@osism.tech>
Change-Id: Iaeaa8c667ce7cd677b2b3dc2096ef4e52c1f651f
