Because of role retirement we need to drop them out of
zuul required projects. However this shouldn't influence role usage
outside of the CI as they are still required for services deployment.
Change-Id: Iac3a8eefcf231f735ff617d5605c6e1fda85b164
This reverts commit cee072a7a5.
There are a lot of jobs out there still set to run that depend on these.
Change-Id: I23ce4b56241364bf2bf5b2bdbcfcac9fc210bc4f
With the transition to OpenDev, we cannot rely on the old URLs
and this is a much cleaner solution that leverages the proposa-bot
user to get all the information we need.
Change-Id: Ie5dae335c12e178928186637b7b73f97c6a694ab
(cherry picked from commit 0f4872e823)
(cherry picked from commit 17a4ca8d83)
Disable CentOS gating to allow the galera_server percona-release fix
to merge[1].
openSUSE 42.3 gating is removed since it uses LXC containers and our
LXC build process is broken on 42.3, plus 42.3 is scheduled for EOL
soon.
[1] https://review.opendev.org/#/c/662107/
Change-Id: I82052e89d84beb31df41ee2cb8e89746ddf41150
Instances are failing to launch on OVH in Tempest runs with the following:
KVM: entry failed, hardware error 0x0
Octavia team reporting the same.
This reverts commit 0f29f9ae08.
Change-Id: I9d709135c2c0a8328a78cba16cd9fa709d997b32
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I59e59c7fc449bd2066d20926b952f1e162bfaa9c
Story: #2002586
Task: #24319
The nested virt issues we saw on OVH should be resolved now.
More information here: I980cdbc67d6e7b3a8a2520b2279ff3a1cdf68c4b
This reverts commit 748e3d2292.
Change-Id: If2adfc006ee9efb3f80e23d34311673b7c74d274
(cherry picked from commit a771ef5a03)
(cherry picked from commit 7961d67274)
Version 3.2 has a bug with it on some systems that can result in the
following stacktrace: [ http://paste.openstack.org/show/726064 ]. To
correct this issue the version of the get-pip script has been set to 3.3
which does not suffer from the same issue.
Change-Id: Ib551c8627351ba23d3c1a67a9631f58fdd2157a7
(cherry picked from commit 178506f624)
As get-pip.py evolves based on pip 10, while we're still using
pip 9, changes in the way it can be used are causing problems.
For example, the ability to use --download is no longer there.
As such, let's pin to a known good version and leave it at that
until we no longer need to use this script. Version 3.2 maps to
pip 7.1.2 which fulfills our needs.
Change-Id: I6aa297ee6e1ca3a76f016a6a0c3d4a735433a9b2
Closes-Bug: 1779534
(cherry picked from commit aa0a76ce9c)
Currently lint tests are failing due to ARA bringing in
extra packages unconstrained. Here we ensure that the
upper constraints are applied when installing ARA.
Change-Id: I35e3688ae632d5f7747f32dafc41d23883c033c5
(cherry picked from commit 2516484ffc)
There is absolutely no chance that zuul will be reverted
back to v2, so let's remove the extra code.
Change-Id: Ia3e4c5ea6514f9caeeea936afd10fac9a54a09c8
(cherry picked from commit 8908a96546)
Linters are extended to 15 minutes. A few jobs have been just
reaching the 10 minute deadline, so using 15 minutes should
leave plenty of wiggle room.
Change-Id: I1473d55498d72f5611ae09e0d2e7b709954bb363
(cherry picked from commit d515c1074a)
Lint rule to make sure no module argument looking like "password"
will get logged.
Change-Id: I180b77faf7aaab57d1c48fc993e43f08c4fb16f6
Closes-Bug: #1760878
(cherry picked from commit c00ecb858d)
We should not Set nova_virt_type.
This way detection steps in, and kvm is used.
However, we should use qemu for OVH hosts:
There seem to be a bug in some OVH hosts
causing 'hardware error 0x0' when trying to run with kvm.
This is a manual-cherry pick of the following commits:
Allow to run tests outside openstack infra:
I782bc40a6ce192b705d7d08a578fdf6275b9a13e
Run with KVM if we can in tests:
I4f679815ac55095000dc1017cebbd1a8bf0f6c5f
Use the right hypervisor name for ovh hosts:
Ib07a93db1d0f826701fd58f95243eb17ef017e4b
(cherry picked from commit 17439c210c)
(cherry picked from commit b3a5751048)
(cherry picked from commit 748e3d2292)
(cherry picked from commit 41c59c7908)
(cherry picked from commit 5d161fb731)
Change-Id: I7a5e15f84d4cd7b3a121a2275cd4ab7b961829f5
Combined backport of:
- https://review.openstack.org/557720
- https://review.openstack.org/558524
Given that tempest is in upper-constraints and its releases
are published to pip, we don't need to use developer mode
for our tests. Also, given that we're not really in a position
to closely track every move the QA team makes, perhaps it
makes better sense for us to just used the released versions
for our tests so that we only have to deal with those changes
whenever they release, implying the confidence that they have
completed their implementation changes.
Change-Id: Ibc191f6fc33ca9a1807c01a23f476c4dfe225f33
Right now, ARA is being setup when we are running functional tests.
However, we could use it for other type of tests such as the upgrade
ones. As such, we can setup ARA by default as part of the environment
preparation steps.
Change-Id: I49052809c4970592c40a394a31a4d8eca12116e5
(cherry picked from commit 6b127cb2bc)
To cater for the option of running a non-voting functional
test on ubuntu xenial, we add the job.
Change-Id: I95f084c26bc3c8c00a326a45d3aa94a0ee539df7
(cherry picked from commit ed22d7046c)
The custom ansible-lint rule APTRepositoryCacheUpdateRule was added in
67bfc90703, this change adds tests to
validate its functionality.
Includes fix from 44761d390b to ensure
unit tests only run against this repository.
Change-Id: Ie0642cc41c016fc016b2bc6fc6d04b6afdf2be2c
Partial-bug: 1750656
(cherry picked from commit cb435cea45)
This rule is designed to prevent the Ansible module `apt_repository`
from being used to update the APT cache. There is a bug [1] in
`apt_repository` that prevents cache updates from being performed
whenever the module is retried. If the cache update fails at the first
attempt, it is skipped on the subsequent attempt of the task causing the
task to always complete successfully. Until this bug is addressed this
rule should prevent it from being introduced into OpenStack-Ansible.
Partial-bug: 1750656
[1] https://github.com/ansible/ansible/issues/36605
Change-Id: If440ce129c31fb4e62a8e0ac5094195f4d4d7167
(cherry picked from commit 67bfc90703)
To make it easier to switch the upgrade job to non-voting
temporarily in the repositories which have it, have a
standard non-voting one to switch to.
Change-Id: I22623cb84aa9ad48be10bbeb53ba898e99b17371
(cherry picked from commit 1c3b36b320)
When copying the logs, the log shows all the files copied
which is unnecessary and just consumes console log space.
In this patch we do not show all the files copied, but we
still show errors which is informative enough without
wasting log lines.
Change-Id: Iffe4baad65d1d2a1812e62f78d54441ae8dbaff2
The current rabbitmq installation playbook assumes that there is
only a single rabbitmq container. While this works for most roles,
when more than one is desired in a test it requires a duplicated
playbook in the role which behaves differently.
This patch updates the playbook to make it more universal.
Change-Id: I372e0db39989ef412ab4301fcd5493efb48bdbe9
(cherry picked from commit 81a91a9604)
When doing the role upgrade, we run every playbook with current's
branch ansible. This is normal for the infrastructure bits (which
are running on current branch), but not for the installation of
the previous branch's role, which should use previous branch's
environment. This script already exists for some OSA roles to
facilitate upgrades but we are now moving it to the tests
repository so all roles can benefit from it.
(Original patch 91b7524603650edbef984fd9fe83e352b90604d2)
Link: https://github.com/ansible/ansible/pull/34790
Co-Authored-By: Jean-Philippe Evrard <jean-philippe@evrard.me>
Closes-Bug: #1741471
Change-Id: I7ebb045885dd645b820de2b7f75b46c755c015f6
(cherry picked from commit f51a22988d)
openSUSE mirros are now configurable in the
openstack-ansible-openstack-hosts role so we need to make sure we are
using the internal OpenStack ones when running in zuul. This patch also
modifies the code to check for /etc/nodepool instead of
/etc/nodepool/provider because the latter doesn't seem to exist anymore.
Change-Id: I6df997e13f678faaddac8b5d1818f2906bac08ec
(cherry picked from commit d5cda7aacc)
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I44f1889047b6ed65fd283b4ee4c4193567d42e03
Sometimes gzip log collection will fail because certain linked
log file are missing. This change notice those error and let the
test pass
Change-Id: I0720460dba3ec959429b577017713e1d5a209337
(cherry picked from commit 6c800b5170)
In order to decouple changes in the roles repositories from changes
needed in other repositories due to the ansible-lint test, the roles
repositories will skip all dependent roles when executing the lint test.
The roles can be updated in time as patches are submitted to those
repositories. In order to do that, we need to stop symlinking the
role into the same directory where its dependent roles are and place
it to its own directory so we can ignore the dependent roles in
ansible-lint.
Change-Id: I49c01fb63054e45bae5ae45a89cce986579959de
Closes-Bug: #1737310
(cherry picked from commit 4bb840d2de)
In order to facilitate providing additional parameters
to ansible-lint for any tests, we add an additional
environment variable for it.
We also add the printing out of any extra parameters
given to the lint test to ease troubleshooting.
Related-Bug: #1737310
Change-Id: If5746d35ee1b8ce5d6fd1a14a2abca16e29cb899
(cherry picked from commit fa828752c5)
We export many variables throughout the CI jobs so it's helpful to
collect them all as part of the job results.
Change-Id: Ic12bb7efa6e841108d56a9368917157c4e104c77
(cherry picked from commit db570376ec)
The ethtool command can fail when run against some devices in some
configurations. This change simply makes the test collections pass
no matter the interface configuration.
Change-Id: I4475e4dfe13acb4c88444f1f7aa88272bf87f6ee
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
(cherry picked from commit f0f9f32975)
This change updates our log collection script so that it is once again
grabbing logs from services and containers but this time far more
conservatively.
Backport combined with https://review.openstack.org/524881
Depends-On: I3c1b755e4bed6a209c127258b79d3ef557caf19e
Change-Id: Ifae67fa3bb3dd790f806bc73de5068f0998cb4e6
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>