When running kolla-ansible upgrade with a host limit that does not
include controllers, the neutron upgrade fails.
Change-Id: I7125a6ef1f180db6997026ff27e84feb04ee239d
Closes-Bug: #1939691
Continuing fixing CI after [1], this patch fixes the other branch
that [2] has not previously included.
[1] https://review.opendev.org/c/openstack/kolla-ansible/+/805449
[2] 02e07a0860e8ca8bc1d6d7716e44bd2888591ecd
Change-Id: I44014a93b92b5a8782e34cf394881dec74cdeea1
As a result of https://review.opendev.org/c/openstack/kolla-ansible/+/805449
CI is failing, because we don't have a TLS certificate on our registry.
This workaround will get our CI to be green while a proper patch
(TLS certs for registry) can be worked out.
Change-Id: Ia45c8a764a1f87d1c44717c4da3b9a3f94cdc967
Currently only operations done with default kolla_toolbox user are logged
to /var/log/kolla/ansible.log.
In order to fix logging, permissions to ansible.log must allow writing
for other users in kolla group - and then a separate patch will follow
to make custom ansible.cfg file usable by other toolbox users.
Partial-Bug: #1942846
Change-Id: I1be60ac7647b1a838e97f05f15ba5f0e39e8ae3c
This is required for libvirtd with cgroupsv2 (Debian Bullseye and
soon others).
Otherwise, device attachments simply fail.
The warning message suggests filtering will be disabled but it
actually just fails the action entirely.
Change-Id: Id1fbd49a31a6e6e51b667f646278b93897c05b21
Closes-Bug: #1941940
This is useful for iterative work with docs as it avoids trashing
results from previous builds and thus saves time.
Change-Id: Ic4f710725cbc2d85c28ca4e00c3a32a00a72c2da
Streamline all actions to behave the same (start with clean
env).
Additionally:
- doc envs do not require k-a to be (re)installed (skip_install)
- this change turns on nitpicky mode to catch reference issues
early
Change-Id: I8ae8a1ca5f6f77ea498573e343889611559b5c97
Just like I added Cinder volume upgrade testing before, let's
also test similarly for Nova and Neutron. :-)
More robust debugging and refactor included.
Related-Bug: #1941706
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/806476
Change-Id: Id79df44254603f9b37ce7da2bfc796fc0b1ac91f
It was removed in [1] as part of cgroupsv2 cleanup.
However, the testing did not catch the fact that the legacy
cgroups behaviour was actually still breaking despite latest
Docker and setting to use host's cgroups namespace.
[1] 286a03bad20955aa4d3f7009cef5856d328b76f1
Closes-Bug: #1941706
Change-Id: I629bb9e70a3fd6bd1e26b2ca22ffcff5e9e8c731
In some situations it may be helpful to populate the fact cache on
demand. The 'kolla-ansible gather-facts' command may be used to do this.
One specific case where this may be helpful is when running kolla-ansible
with a --limit argument, since in that case hosts that match the limit
will gather facts for hosts that fall outside the limit. In the extreme
case of a limit that matches only one host, it will serially gather
facts for all other hosts. To avoid this issue, run 'kolla-ansible
gather-facts' without a limit to populate the fact cache in parallel
before running the required command with a limit.
Change-Id: I79db9bca23aa1bd45bafa7e7500a90de5a684593
When running without that option, the list of servers might be empty,
resulting in leftover instances on the host that is about to be
migrated.
Change-Id: I85915f0f86655f3a1eb5f54911d24e4e0e75f340
To follow best security practices and help fellow operators.
More details inline and in the linked bug report.
Closes-Bug: #1940547
Change-Id: Ide9e9009a6e272f20a43319f27d257efdf315f68
For now role haproxy is maintaining haproxy
and keepalived. In follow-up changes there is also
proxysql added.
This patch is *only* renaming/moving stuff to more
prominent role loadbalancer, and moving also specific
templates to subdirectory.
This was done only to better diff in follow-up
changes.
Change-Id: I1d39d5bcaefc4016983bf267a2736b742cc3a555
Sometimes, the registries may intermittently fail to deliver the
images. This is often seen in the CI, though it also happens with
production deployments, even those with internal registries and/or
registry mirrors - due to sheer load when trying to pull the
images from many hosts.
This patchs adds two new vars to control retry behaviour.
The default has been set to make users happier by default. :-)
Change-Id: I81ad7d8642654f8474f11084c6934aab40243d35
It seems to have been mistakenly introduced by
de00bf491dfbabc8e11009fce4410bce5c2110ed
"Simplify handler conditionals"
Change-Id: I65b6e322fa11a870f32099bbfd62150cbea4feb5
This change enables the use of Docker healthchecks for
keystone-fernet container. It checks if "key 0" has
right permissions, and if rsync is able to distribute
keys to other keystones.
Implements: blueprint container-health-check
Change-Id: I17bea723d4109e869cd05d211f6f8e4653f46e17
Manila has changed from using subfolders to subvolumes.
We need a bit of a tidy up to prevent deploy errors.
This change also adds the ability to specify the ceph FS
Manila uses instead of relying on the default "first found".
Closes-Bug: #1938285
Closes-Bug: #1935784
Change-Id: I1d0d34919fbbe74a4022cd496bf84b8b764b5e0f
