Those have been failing for long time and Masakari is deprecated
in Kolla (not mentioning the state of the project itself).
Change-Id: I06d32f8f4921b2025fd176be1198dc0cbcfa5f3b
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
Starting with ansible-core 2.13, list concatenation format is changed
and does not support concatenation operations outside of the jinja template.
The format change:
"[1] + {{ [2] }}" -> "{{ [1] + [2] }}"
This affects the horizon role that iterates over existing policy files to
override and concatenate them into a single variable.
Co-Authored-By: Dr. Jens Harbott <harbott@osism.tech>
Closes-Bug: #2045660
Change-Id: I91a2101ff26cb8568f4615b4cdca52dcf09e6978
This allows us to continue execution until a certain proportion of hosts
to fail. This can be useful at scale, where failures are common, and
restarting a deployment is time-consuming.
The default max failure percentage is 100, keeping the default
behaviour. A global max failure percentage may be set via
kolla_max_fail_percentage, and individual services may define a max
failure percentage via <service>_max_fail_percentage.
Note that all hosts in the inventory must be reachable for fact
gathering, even those not included in a --limit.
Closes-Bug: #1833737
Change-Id: I808474a75c0f0e8b539dc0421374b06cea44be4f
Add file to the reno documentation build to show release notes for
stable/2023.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.2.
Sem-Ver: feature
Change-Id: I96140b1e3be06b60909f3eed739f1a944e119c7e
If a file {{ node_custom_config }}/magnum/kubeconfig exists, it is
copied to /var/lib/magnum/.kube/config in all Magnum Service Containers.
At this location, the vexxhost/magnum-cluster-api will loo for the Kubeconfig
configuration file to control the Cluster API Control Plane. If the
vexxhost/magnum-cluster-api is installed in the Magnum container images,
control of a cluster API control plane can then take place via the Magnum API.
Depends-On: https://review.opendev.org/c/openstack/kolla/+/902101
Change-Id: I986c5192fe96b9c480a2d8fa87d719a50ce78186
* Updates etcd to v3.4
* Updated the config to use v3.4's logging mechanism
* Deprecated etcd CA parameters aren't used, so we are not affected
by their removal.
* Note that we are not currently guarding against skip-version updates for
etcd.
Notable non-voting jobs exercising some of this:
* kolla-ansible-ubuntu-upgrade-cephadm (cinder->tooz->etcd3gw->etcd)
* kolla-ansible-ubuntu-zun (see
https://review.opendev.org/c/openstack/openstack-ansible/+/883194 )
Depends-On: https://review.opendev.org/c/openstack/kolla/+/890464
Change-Id: I086e7bbc7db64421445731a533265e7056fbdb43
* etcd service containers usually have a set of
environment parameters required to boot the container.
* The short-lived etcd bootstrap containers pass extra
ETCD_INITIAL_* environment variables, but still need to
pass the ones that the service containers use.
* This uses ansible's `combine` filter to cut down on the
duplication.
* This is intended to be just a straightforward refactor.
Change-Id: I04e95f92a8f365553afd618d58b99de595d48312
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
