In case `ovn` is part of the SCENARIO, tempest will be told to test `ovn`
provider for it's scenario test.
Change-Id: Ifb184f586f282bc4341d1429330a245244dfb648
When generating inventory first check that is done, if user has defined
a container/management network. However, this logic ignores
is_management_address / is_container_address keys.
At the same time it expects another key - `address_prefix` which can or
should be set to `container` or `management`.
Change-Id: I49ebd1e0925a4b088b42bdf875b5f0b2dcc7eeae
Current behaviour may treat git+file combination as one being Zuul-treated
as when zuul_src_path is an empty string, path is still be located
and added as `zuul_item` while deployer might want it to be as local git
repo.
This patch adds another verification to ensure zuul_src_path
is defined and we're in CI before doing adjustments
Change-Id: I0acd3a14faf57d6c1bd64af9f36105df8b27b714
Changes in oslo.messaging for 2023.1 exposed a known race
condition in RabbitMQ when dealing with non-HA classic queues.
When a RMQ cluster member is taken down, clients failing over
to other members may erroneously be told a queue exists when it
is in the process of being deleted. This can cause them to
permanently sit waiting for messages from a queue that no longer
exists until their services are restarted.
Making the reply queues HA resolves this issue, at the expense
of a x3 increase in reply queues across the cluster. My
assumption is that reply queues were previously excluded from HA
policy as a performance gain given their link to the number of
compute nodes in an OpenStack deployment.
Context: https://bugs.launchpad.net/oslo.messaging/+bug/2031512
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/916042
Change-Id: Iee6b5f8cc1ad04988c8634f8b6e026e2f8c75b52
Task vars are higher precedence than inventory group vars so
cannot be overidden except in user_variables (ansible extra vars)
which then become a global setting, which is almost certainly
incorrect for this case.
Change-Id: Ie43e339df50adbe8240ffe43159c28f132e50000
This patch converts the container setup from a task include
to a role in the plugins repo so that the container setup
code can be re-used when extending openstack-ansible through
further use of ansible collections.
Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/900529
Change-Id: Idc8ece17ca334a6b46fa18446218a38b2c85c32b
Due to CVE-2023-5764 conditional statements should not include
jinja2 templating anymore and result in warnings/failures
This patch replaces Jinja tags with slightly different format that leads to the
same result/logic.
Change-Id: I049ac770b32152866194190e54f5947fe7589b39
At the moment Cloudkitty is targeted at all LXC hosts along with containers
which is not needed nor intended.
Unfortunatelly there's no really good compatible fix exist, so action from operator is required to handle transition to new naming for
the service.
Change-Id: I9360495e3b3347568969e36e0e96bb1325efd59f
Zuul
OpenStack Release Bot