Python3.5 test for
* monasca-persister,
* monasca-statsd,
* python-monascaclient
are passing.
Making gates voting for those projects.
Change-Id: I9ce5a82f14f256328da86bc832cb45800a87bf14
The Horizon integrated test suite is a lost cause, has
been non-voting for quite some time and is never going
to be fixed and maintained.
Change-Id: Ie7b538757a71ddd7aa9070ae93d3d05d5657bd17
Because openswan is not available on xenial.
Probably we should start testing libreswan driver instead, but it would be
a work for another day.
Partial-Bug: #1649574
Change-Id: I084c1db44cc94e50890c4bd9553a8f4c896b2484
With the switch to Xenial, we can cleanup a few repos:
* almanach: Has only stable branch, remove unused py34 job
* anchor: Has only stable branch, remove unused py34 job, make
py35 voting since it passes - example
https://review.openstack.org/#/c/380554/
* anvil: Has no current stable branches (only essex,folsom,grizzly).
Remove trusty jobs, they are never run.
* app-catalog-ui: Has only master branch, remove trusty jobs.
* bandit: has only master and stable/17.0.0 branch, remove py34 job.
* bilean: has only master branch. Remove voting py34 job, make py35
voting since it passes - see https://review.openstack.org/#/c/379164/
* blazar-nova: has only master branch, remove trusty jobs.
* castellan: has only master branch. remove voting py34 job, make py35
voting since it passes, see https://review.openstack.org/#/c/409887/
* cathead: has only master branch, remove trusty jobs
Change-Id: Iad4a66bc673a51a71c0fc98888796ec52249073c
Somewhere in the consolidation of the OSA zuul job cleanup, CentOS 7
jobs were re-enabled for the openstack-ansible-security role in
Liberty/Mitaka. The role didn't support CentOS 7 in those branches
and this patch should disable those tests.
Change-Id: I85d5f85a6b78d945b635c7ec42f741bb77e2fb64
These repos had a condition to make the py34 jobs non-voting - but we
had no py34 jobs enabled for them. Remove the extra condition.
We do not yet add a py35 job, the repos are not ready.
Change-Id: I1828b60dab2190548cb560cab8c94c3fa594db77
Volume backups are failing when magnum is enabled. While we figure that
out, turn the magnum job into a non-voting job.
Change-Id: Idc4691d52e2275aadf938412a47be794746f95d7
This patch is making the
gate-tempest-dsvm-ironic-pxe_ipmitool-virtualbmc-src-ubuntu-xenial
voting. This job is running for some time already and is green.
Change-Id: Ibfd32f443cd09c8d08085c38c5f313e8172303fc
The missing-services test works! Except we told it that the keystone job
has designate and it doesn't. Also, remove the plugin references since
they don't work with this config.
Change-Id: I53da84b3cf548f2a3b551f4ea8b52081f7febae7
Awhile ago heat was removed from devstack [1] tree and now
it is disabled in mangum rally jobs.
[1] https://review.openstack.org/#/c/317618/
Change-Id: Ib7d4aba4a0823823046b138f0aa495291d7ae8ea
A Cinder live upgrade from Liberty to Mitaka should work, but we weren't
gating on that back in Mitaka timeframe and the feature was considered
experimental. There's no need to gate on that in stable/mitaka. Moreover
the job is currently constanly failing due to PyMSQL not being installed
on the subnode.
This commit disables the job for Cinder's stable/mitaka and unblocks
the gate.
Closes-Bug: 1647672
Change-Id: I362d1306d201f5f239b228d6df2108349517295e
Python 34 jobs should only run on liberty or mitaka stable branches, do
some cleanups:
vmware-nsx:
Remove python34, those jobs will never run.
app-catalog: Repo has only master branch, replace py34 with py35.
congress, designate, mistral, python-muranoclient, tacker repos, and some more:
Fix branch.
sahara-dashboard: Remove python34, the jobs was set to run on newer than
mitaka.
trove, trove-dashboard: Remove python34, jobs was set to run only on newer branches.
Add python35-nv to trove-dashboard instead of the non-voting python34.
murano, murano-agent: Remove 34 job, it was set to run only on newer branches.
Change-Id: Ied8b9d15c87d4e9ef49675a9ef3cbf94bda0426a
All functional jobs don't need a full devstack vm
but only some packages to be installed
So we can leverage the bindeps.txt feature to just install
our package requirements.
This change adds new jobs to use a non-dsvm.
Once the new jobs are working we will switch them to voting
and remove the dsvm one.
Change-Id: I9a1a997299f33f9c7dc2b8683b03081781a2d5d6
The py35 job runs without error on the project Nova,
therefore we can safely enabling voting. Reference patch:
https://review.openstack.org/#/c/403548/
This patch also drops py34 voting job.
Change-Id: I8a1293e78e6e7ac3d454e3043840173c2ba049ec
This job was introduced a while ago as non-voting and was green.
Relevantly recently a change landed that broke it. Lets make it voting
to prevent that from happening.
Also given that it's voting add it to the gate pipeline also.
Change-Id: I0612e2b1ebc87932b85b0b4dfc4f3fe46da22609
For projects that only have master branch, remove python34 and trusty
jobs since those will never be run.
Additional changes:
germqtt: Use python35 instead of python34.
openstackid: Add voting docs job to gate as well.
reviewstats: Use python35-nv instead of python34 job.
storyboard: Make python35 jobs voting, they pass like in
https://review.openstack.org/#/c/408297/
infra-publish-jobs template: We do not need the trusty jobs here.
Change-Id: I8249391541b799fbcbbbf609948af0525675a46d
The changed repos have no stable branches, so we can remove all trusty
jbos that are run on them including python34-jobs.
While this change removes job, the jobs run on any change stays the
same.
Change-Id: I71dbf88a9c7b9bbf9c6e6723f0253d31a2c069e3