On 30.09.2023, "old" ansible galaxy(galaxy.ansible.com) was replaced
with "galaxy ng"[1].
There was a bug [2][3][4] that was fixed only in a supported
ansible-core versions, so:
- v2.12.8
- v2.13.3
- v2.14.0 (and all newer versions)
All openstack-ansible versions up to Yoga are using older ansible-core
versions.
As a result, bootstrap-ansible.sh script fails with an error:
```
Skipping Galaxy server https://galaxy.ansible.com/api/. Got an
unexpected error when getting available versions of collection
ansible.netcommon:
'/api/v3/plugin/ansible/content/published/collections/index/ansible/netcommon/versions/'
```
This patch bumps ansible-core version to 2.12.8 that includes required
fix.
[1] https://www.ansible.com/blog/new-ansible-galaxy
[2] https://github.com/ansible/ansible/issues/81830
[3] https://github.com/ansible/ansible/issues/77911
[4] https://github.com/ansible/ansible/pull/78325
Change-Id: I2c15c220ca8c6b6f0cbedbf0da8e802b7c0f5e2d
Currently TESTING_BRANCH serving 2 purposes - it controls over OSA
branch to use and services branch.
At the same time we need to have these separated from time to time, as
OSA is trailing.
Change-Id: Ib5ca8c7d3300f4e8efd81f87612c821594bebfac
In functional tests, comparing to the integrtion ones, dynamic inventroy
is not used. Thus, ``is_metal`` variable is not defined, and we rely on
it in some roles.
To cover the gap, we're setting a variable based on the ansible_facts for
functional tests only.
Change-Id: Ifc9bb5bb65d599a39f562faaaa14a0756e493ba1
With the new pip resolver, if a package is constrainted to two
different versions simultaneously then the package cannot be installed.
setuptools has a constraint in both OSA global-requirement-pins and
openstack upper-constraints, so the installation will fail with the
new resolver.
This patch removes any references to setuptools from openstack u-c
and allows the constraint from the OSA repo to be used.
Change-Id: Ib4c3592184973ba9908a1ba17d935a96448969a1
As we have mysql client and mysql config file on infra1 host
for all functional tests, we need to use it instead of the utility
host (since we don't have one for functional tests).
Needed-By: https://review.opendev.org/733443
Change-Id: If91bff7af39a8e465ac1086dcd3378b4e6de3ca7
After update of requirements_git_url to use releases.openstack.org
test_branch should be in format of "ussuri" instead of "stable/ussuri"
Change-Id: Ia3eae8c132b841797f887f1c82ff1ceb1145783a
We rely on mapping inside lxc-containers-create role while we have
a variable defined with correct version of lxc. So we can set key
correctly here.
Change-Id: Ic9c6287e43737fb2dc6f833dd6e2adff02066f10
As for U we don't support debian stretch, there is no need
in having stretch CI jobs. Buster ones should be used instead.
This also fixes ara report
Needed-by: https://review.opendev.org/706285
Change-Id: I554e512968718492ce6056b29b0612e450f0856b
This variable is used to conditionally include a task file which runs
the python_venv_build role. This means that the handler in the venv
build role is executed conditionally on tempest_use_tempestconf but in
the context of the outermost playbook, where this var is not in scope.
THis patch ensures that tempest_use_tempestconf is defined in the scope
of the top level test playbook.
Change-Id: I8cd5e5626ecc3cfa40315e2bdf62945b7bb1582b
For role tests to work, we need to pin nova to before the placement
removal. Once we're able to re-implement the role tests or remove
them we can remove this pin.
Change-Id: I58788af6f02a4b339a270dff69a86ce7cdea41d3
This patch adds support of rabbitmq policies configuration for mq_setup
and uses oslomsg_rpc_policies and oslomsg_notify_policies variables for
that. These variables are defined in group vars and provide HA mode.
It also adds ability to provide extra policies during include by
specifying _oslomsg_notify_policies and/or _oslomsg_rpc_policies
variables.
Depends-On: https://review.openstack.org/652186/
Change-Id: Id60b7ac62ff16af938577615ab001dd144f92c26
We may need to use some addresses on this subnet for interfaces and
bridges on the host, or containers. This patch defines the range
available to neutron where previously any IP in the subnet may have
been used.
Change-Id: I5a2f7351a6f08b37120f6299556fba1e810f3c9d
This play and the vars are no used anywhere but the
Sahara role, so we move them there instead.
Needed-By: https://review.openstack.org/583427
Change-Id: I830b6bf1d384f497bb0673822a910245463f824f
This overrides centos default values of printk logging
to a more "quiet" default, reducing IO in testing.
Change-Id: I62d2357152384b78d8371f2a714aa3313d77f3fd
There is no record for why we implement the MQ vhost/user creation
outside of the role in the playbook, when we could do it inside the
role.
Implementing it inside the role allows us to reduce the quantity of
group_vars duplicated from the role, and allows us to better document
the required variables in the role. The delegation can still be done
as it is done in the playbook too.
In this patch we remove the test-vars which were duplicated from the
role, and remove the MQ setup tasks as they are no longer required.
Change-Id: Ib515630c8fbf793258b40f15a4c9f2c18c4c7531
There is no record for why we implement the MQ vhost/user creation
outside of the role in the playbook, when we could do it inside the
role.
Implementing it inside the role allows us to reduce the quantity of
group_vars duplicated from the role, and allows us to better document
the required variables in the role. The delegation can still be done
as it is done in the playbook too.
In this patch we remove the test-vars which were duplicated from the
role, and remove the MQ setup tasks as they are no longer required.
We also remove the usage of a variable for the role name as that is
unnecessary legacy.
Depends-On: https://review.openstack.org/568517
Change-Id: I516e65e3b49f1722636d69f80c1bddc01c942a48
If we're testing a stable branch, it is best to use the stable
released Tempest version. However, when working in master, it
is possible that an OpenStack service change which has a
corresponding Tempest change would lead to things failing because
we're deploying master of the service but a tagged version of
Tempest which means the tests will fail.
In order to ensure stability of stable branches, we'll keep using
the tagged release but we'll use master Tempest for testing the
roles.
Change-Id: I347afd358850149b359ae64871a858701755d896
Do not use glance servers variable.
Specify the glance servers for all hosts.
Also add correct ironic variable.
Depends-On: I983a20d923384bf54cb0af924ec0a0f8ef4db191
Depends-On: I8dfd1904de36ca2b9f163bd5447bfa40ddf4ca3a
Change-Id: I7dcc8177e13b49f87e5ee4c9d2323074fee45179
Previously, we had a <service>_galera_address for every project,
however, it looks like the patches to move the creation of the
database inside the roles have worked great, but their testing
patches inside this repo. have dropped the usage of the address
which means that the service is configured with 127.0.0.1 (the
fallback if none is provided).
This patch fixes this by adding that variable so that everything
can go through smoothly. Therefore, the removal of future
<service>_galera_address variables will not affect things.
Change-Id: Ib180fc3a7cbae28b413094b444f7d528b584c9ed