The upgrade tests are very noisy since Ansible verbosity is set too
high. This makes debugging problems very painful so drop the verbosity
level and let users increase it if desired.
Change-Id: Id256efff664c58d62aaf7b9e23c7df6953032573
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.
Depends-On: I7ebb045885dd645b820de2b7f75b46c755c015f6
Change-Id: I7069c906395b37e8af20db82d88d8a069faf5f79
Related-Bug: #1741471
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Ifff40bdf0aaf9020d3b3e44cfb15055f2824266e
In the previous patch removing the virtualenv-tools, we've updated
paths to the proper binaries, but we don't reset the virtualenv
like what we used to do.
Change-Id: I33906abc0e145dc671c2781924c4c20e9df3ba48
Partial-Bug: #1741634
openstacksdk was updated to 0.10.0 which has a different
connection.Connection object, which doesn't take our auth_url.
We should respect the constraints, install the tooling in a venv,
and restrict to a known version of the sdk until more robust code
is written.
Change-Id: Ibcfe3d69705833b0c743e6303feb351a464abdcf
virtualenv-tools has a bug which gets triggered in gates: it can't
change the shebang of a virtualenv python bin/ files if they
were generated with a virtualenv script whose shebang ends with
python2 instead of python.
Because we can't modify virtualenv-tools, we use shell scripts
instead.
Change-Id: I2dc9a507162fcd2323e19a3a2daa97c6db9cdcdb
Partial-Bug: #1741634
We are already collecting logs as part of the post-run playbook so we
don't need to do that as part of the exit trap. This avoid collecting
and compressing the logs twice.
Change-Id: Iacbdd102e8889ae09ee2c93e300a87ba4ffc4842
With addition of pip_install on every node, we don't
need to have pip_install as a meta dependency.
Depends-On: If3412bb888ebb854874bbc43eb76bfcb3e4a7868
Depends-On: I79ff70c438b44753be2a93f004ebbc46de0a963d
Change-Id: I2a59d22cd7d073fbc4af711aa6d9be92a2c07e54
The systemd module doesn't support the sleep option and this patch
removes it from the handlers.
Closes-Bug: 1735786
Change-Id: Ida1d83903dc4d3cd85029735a0882bf342d21dca
This patch removes Jinja2 delimiters from when clauses and fixes the
capitalization of task names to match the other tasks in the file.
Closes-Bug: 1735785
Change-Id: I16334a11c551026c593b1872a44ed68f786719a5
This is the time of the cycle where we update all the static
elements in the roles. PyPy has a static file version, so we
bump it.
Change-Id: I15c21c177c32dcae0a7f2710b50f91829be09586
Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.
Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
.
Change-Id: I7df0385b62d118b535179dd42d7aa576897815ca
We need to add openstack ansible information in the role
metadata to be able to track role maturity. With it,
we can create a role maturity table and take decisions about
role deprecations.
Change-Id: Iafdf127465e9c5c5bfd60fa6951ef12f76864a22
Until the bug #1729263 is resolved, we should move back to
non-voting centos, to avoid an useless series of rechecks.
Change-Id: I930a0458c10625e2f795f4fba76675f5b93a6f7d
Swift fails to deploy when using >1 storage node. The fact `need_sync`
was being set using information from ansible_local in an effort to
support rolling uprades sometime in the future. Sadly this variable
causes storage nodes to be removed from the key sync which results in a
failed build. If we decide serialized rolling uprades are required for
swift we can revisit this however until then we need to remove this
constraint and ensure we're allowing successfule deployments and
upgrades of swift.
This reverts commit 176452bebf7e1ceabd2cf72a89c558c0fc7f1420.
Change-Id: I21318d7c737c2415ef760b46176c3f9b372bb634
Initially the intent for adding this was to better test
any patches for roles together before they merge, but it
has had the unintended side-effect of causing patches to
take much longer to merge (because they all get lined up
in a single queue, rather than independent queues) and
a lot more infra resources are used (because a patch
that fails at the top of the queue will result in all
subsequent patches restarting all their tests).
As discussed in the channel, we'd prefer to revert back
to the previous independent queue method of testing. It
has served us well.
Change-Id: I717e111e8cc85f8396bddf317a2a27969a5728e7
Currently the linters test is in the project-config
repository, but those are meant to be used for standard
jobs which do not require any repository other than the
one given. Our lint tests use the 'openstack-ansible-tests'
repository, so we should rather use our own job definition.
Change-Id: Ie7416e87851463e94bc11147faa277b5bf60e106
Depends-On: I0391ec310c4eede436011a48490e3c524c8ddf4d
This changes the a-r-r with the proper version, and fixes
the repo path for role upgrades:
The role will, during test-upgrade-pre, have its current branch
checked out, and will deploy the current branch infrastructure,
including the generation of the constraints.
Then, the installation of previous branch of the role will use
the constraints for its previous version, but will have no
constraints for it, and fail.
We need to generate the constraints for the previous version too.
This should do it.
This patch also implements an initial set of jobs intended to
match the current job execution method. It does not intend to
improve how the jobs are executed - only to replicate what is
currently in openstack-infra/openstack-zuul-jobs and provide
the platform to iterate on.
Change-Id: I4aa7591c931501490e706b9d61ba0bc12c006baa
Ansible throws warnings when we use rsync with the command
module. This patch suppresses those warnings.
Change-Id: I42652318f128120b1ecec4781066c89ee9023636
This patch contains five combined improvements.
1) Remove RabbitMQ from the gate
RabbitMQ is only needed in the swift gate if the ceilometer
middleware is being deloyed. This isn't enabled in the gate
job, so let's save some time and deploy memcached/galera
without RabbitMQ.
2) Bindep pyOpenSSL change
This commit also includes the pyOpenSSL bindep change in the
hopes that we can get the swift gate moving along again. ;)
3) Disable erasure code test for CentOS
Due to #1707220 we are running into issues with CentOS 7 running Erasure
Code storage policies on RAX hardware.
This patch temoprarily disables EC testing for CentOS 7, but we can
re-enable that once the package is backported to stable/ocata branch.
4) Pass packages as a list
This patch passes a list of packages to the package module
rather than using "with_items" and it should speed up the
package installation process.
5) Set package state to present
Change-Id: Ic7b13853ce00b0f8ac2181e46e2bd8dea5ce377e
Co-Authored-By: Andy McCrae <andy.mccrae@gmail.com>