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
As PTI for 2023.1 Antelope release Ubuntu Jammy was set as a target
platform. Thus, we should update our functional jobs to reflect that.
With that we also clean-out projects.yaml from jobs that are currently
undefined among zuul jobs to prevent any zuul config failures.
Change-Id: I72b4bb7eddb37579f9d33d365ded982e5db0a9ac
In functional tests we don't ensure that wget exists. Also for Ubuntu
we ensure that curl is present only. So let's replace wget command with
curl and be consistent across repos.
Change-Id: If9106bd0a481079b9e676c5547e244a11a35fb73
With tox release of 4.0, some parameters were deprecated and are ignored now
which causes tox failures. One of the most spread issues we have is using
`whitelist_externals` isntead of `allowlist_externals`
Change-Id: Id2a4cb712b4099bff1c05c4d10502a7572517268
Add file to the reno documentation build to show release notes for
stable/zed.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/zed.
Sem-Ver: feature
Change-Id: Iabfa5f742744a9fc69ba296d8953359891832779
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
This must be python3.8 as we use this version in the integrated repo
and require it for ansible 2.12
Change-Id: Ia326d92c24b9cdfcf46011e0661a9b5081e11573
With sphinx release of 5.0.0, they changed default for language variable
to 'en' from None. With that current None valuable is not valid and should
not be used.
Change-Id: I3fc1dd06c176c7004974b9cd989208f4ba7a37f2
Since OSA has trailing releases, we might want to override branch we're
testing. At the moment it's set based on the .gitreview file.
At same time we temporary override branch to yoga, as deploying from
master breaks installation.
Change-Id: Iacef9bec9ab8f2f15a56e3d95f71734277d7a8c7
Jobs are broken due to a release of setuptools 61.0 introducing
non-backwards compatible breaking changes [1]
Setting py_modules to an empty string here will disable autodiscovery
and should permit jobs to run as before.
[1] https://github.com/pypa/setuptools/issues/3197
Signed-off-by: Neil Hanlon <neil@shrug.pw>
Change-Id: I64c2850b6a414c68277270952676518aa7aaa85b
ipaddr filter has been moved from netcommon to utils collection [1]
Based on that we must add that collection to requirements.
[1] db4920ebf6
Change-Id: Ifb7a043ce7c6a12c413641dde61c170ae9327dc4
Ansible-lint prior to v5.3.1 has issue with reach version >=11.0.0.
In order to cherry-pick fix to stable branches we fix rich version.
We can't use requirements as rich is neither in blacklist nor in
global-requirements, so must be handled independently
This should be reverted with ansible-lint version bump.
Change-Id: I7ad62182178dd1eb285d6002b2852b457f678c7b
Remove job definitions for gentoo and bionic and any others which
are not used elsewhere in openstack-ansible.
Depends-On: Ic53886ee1833469daef0b31a46ea361e449d7697
Change-Id: I1fb55fd1f476139fcd4cc0b6c68b291454160132
It might be desired by deployer to remove already applied policy.
For that policy state should be explicitly passeda as absent
for the module.
Change-Id: I0db1e23ca0edf65aa1b4c8ca20153337044b6c4c
Once we've moved almost all repos to integrated linters jobs,
we shouldn't include linters inside functional tests template.
Change-Id: I890529cdd2fe3918e9d97e918da303c929dfe07d
Since role-name (106) test has been added metadata tag in
ansible-lint 5.0.9, we shouldn't exclude it explicitly.
Change-Id: I84f8a97ecce0eebf1f0fbb5c8a4fc433eedc34fd
ansible-lint 5.0.9 has merged our NoLogPasswordRule [1]
APTRepositoryCacheUpdateRule is not relevant since
ansible fix has been merged for several years now.
Also ansible-lint provides yamllint check.
This means, we shouldn't really carry custom lint
rules and can jsut use upstream ones.
We also update ansible and collections version to
match with the integrated repo.
[1] 8bef056d69
Change-Id: Ie85d6d0a17849bbc665a7f49644c38b5f6a96bb2
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I150f3362a3790ad6db4da443f582671e6d909f4b
Recent nova does not support libvirt version that is provided in
Debian Buster, so we setting job to not voting.
Change-Id: I2c0bcbcfe1f8b4bee60a6069e4b2417ad5f67cf6
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
There's a usecase, where all datasets might be the same, except
setup_hosts. For example, when we use isolated rabbitmq cluster for RPC
but shared one for notifications. And we have same set of users
and vhosts there. In current state setup won't be performed, since
vhosts and users are the same.
Change-Id: Ib5c44327d5f1edc25bace79fdd057adabb0b4c14