Check only things we build into collection.
Ignore sanity files from full CI jobs.
Add queens to gate because it's voting.
Add files to ignoring when building collection.
Remove non-required lines from ignorign sanity files.
Change-Id: I0dde756efa133cf75b67d072af78a1f8307ce932
This is separate from the previous patch - it's just the results
of running the script so we can review the two a little independently.
We should probably squash them.
Change-Id: I838f15cf4a32455a5be20033c8ddc27db6ca15c0
The 2.10 transition has a routing.yml file that points each
individual module from ansible/ansible to a new location. That means
we can put:
os_server:
redirect: openstack.cloud.server
into lib/ansible/config/routing.yml in ansible/ansible and have
the result be the end user's playbooks still working with the
old names while providing new names that are less ugly.
This adds a routing file to our collection repo, as well as the
script used to generate the new mapping.
Change-Id: Ia5d18282b14ad0d86a347343be8bb477ae47130a
We can't run linters in an install because installs expand
symlinks to regular files so the ansible-test code that detects
symlinks can't work so it looks at docs for symlink aliases
as if they were real.
Change-Id: I0a5659a1f693261a21a5b29528f950b846205f2e
Prior to this change, the os_server_action module could not rebuild
servers, because it passed no arguments to the "rebuild" object.
The imageRef parameter is mandatory. If the client does not specify
imageRef, Nova takes no action to rebuild the server.
Change-Id: I0edbdb634feb90d4c54476a4089fcb014c0b83b2
As per the REST Networking API v2.0 (Subnet) docs, if subnets pools
are not specified, OpenStack networking automatically allocates pools
covering all IP addresses in the CIDR.
In custom vendor specific environments, subnets can be created without
allocation pools via UI due to which subnets will not have any existing
allocation pools. Under this scenario, module throws an
"IndexError: list index out of range" error.
Also, allow to add more allocation pools on top of existing allocation
pools.
Change-Id: Ib8becf5e958f1bc8e5c9fd76f1722536bf1c9f1a
Keystone supports setting custom properties for projects. This changes add
properties to os_project to enable setting of custom properties.
Depends-On: https://review.opendev.org/715255
Change-Id: I23e2834d6b9d40ce86db4b32a0ed8bf76b3d9879
In addition to running ansible-test from stable it's helpful to run
ansible-test from 'devel' where new sanity tests will land. These
sanity tests are generally applicable to existing modules, but aren't
back-ported.
Change-Id: I8df3dd43cbc4cba643d7860e77a1089c15f5f092
Depends-On: https://review.opendev.org/717118
Pass SDK version to ansible roles so we can skip testing of modules
which are not supported for current SDK version
Change-Id: I5d25c0a6827536434a8f17b2a0f7de0db4c78301
Galaxy shows the README, which currently shows a "failing" badge
pointing at github actions. That's obviously not right for us.
Update this by using the zuul:gated badge and pointing to the
builds for the repo in the Zuul Dashboard.
Change-Id: I7f1254f882486514cd29a52bf05ebf5a972da490
Add rocky and stein jobs to check and gate
and remove non voting jobs of ansible devel from gates.
Change-Id: Ib231a50fa5e8427ef39077bc49ac806aa0a5732e
Use the openstacksdk base functional test instead of going all
the way back to devstack for our base. Also - defining a job
starting with openstacksdk in this repo is not ok - but that
probably just came from the original copy-pasta coming from the
sdk repo.
Use tox-siblings more and stop doing tox requirements of ../
things. The system is there and we can use it.
Add jobs to test against released openstacksdk and ansible, as well
as a non-voting to test against ansible devel branch.
Add openstacksdk to the test-requirements because it's super
required.
Move zuul.yaml to .zuul.yaml. This isn't a zuul jobs repo so
we should just make it a hidden file rather than a non-hidden.
Change-Id: I658bd1728629cd358bc17a7f00d282d04530d8fe
