Run script generate-gitmodules.py to sync with governace repository to
add new repositories and remove retired ones.
Change-Id: Ia42b717ad242958ba4a9689ac814c956f460712f
* Update devstack-gate from branch 'master'
- Merge "Convert testmatrix run to venv"
- Convert testmatrix run to venv
As part of our efforts to ship bare nodes, we want to install as
little as possible in any sort of pre-run jobs. Since all infra nodes
have python3 available, use venv to create this small environment for
the test matrix production, and avoid having to pull in any other
dependencies.
Change-Id: Ie8b09ab60841f9d1b15ae1a7afec51906cd89f95
* Update devstack-gate from branch 'master'
- Merge "Move stable branch gate job to stable/ussuri"
- Move stable branch gate job to stable/ussuri
We have stable/ussuri branch as latest stable and
d-g test only latest stable branch to make sure the compatibility
of legacy jobs.
This commit moves the legacy stable job testing to stable/ussuri.
Depends-On: https://review.opendev.org/#/c/723605/
Change-Id: Id57e5590a5b24c2d821381f52e1c445cbbd1105b
* Update devstack-gate from branch 'master'
- Set TOX_CONSTRAINTS_FILE
UPPER_CONSTRAINTS_FILE is deprecatedi[1], set the newer
TOX_CONSTRAINTS_FILE as well when interacting with other repos for the
transition.
[1] https://zuul-ci.org/docs/zuul-jobs/python-roles.html#rolevar-tox.tox_constraints_file
Change-Id: Ib02819e805d216ead178300df0b250f85f9f27b7
* Update devstack-gate from branch 'master'
- Set up stable/ussuri
* update the feature list
* add ussuri to allowed stable branch names list
Change-Id: Ia1de95b01da1007d6eef1f95cfba8fed15ffef2e
* Update devstack-gate from branch 'master'
- Fix virtualenv detection
This checks if the task failed; which it never does because of the
failed_when: false. What we want to check is the return value of that
check.
Change-Id: Ic975b53d60f44e8e743bcc31fc864cc8416b3a92
* Update devstack-gate from branch 'master'
- Merge "Do not gzip files under logs in job results"
- Do not gzip files under logs in job results
In zuul job results the 'logs' directory contains gzip'd files which are
now unbrowsable. This happened due to changes in swift behavior [1].
This patch removes unnecessary compression of files under logs
directory.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-January/011875.html
Change-Id: I1d0e7869d418612bb9a20fdf01da2641693ed8bb
* Update devstack-gate from branch 'master'
- Merge "Just use the pip from the virtualenv"
- Just use the pip from the virtualenv
There is only one python, so there is only one pip.
Change-Id: I31bc5a7bad603f3f58a3d2ac1501271935830cdd
* Update devstack-gate from branch 'master'
- Cap virtualenv to a version < 20
There are errors with the recently released
virtualenv 20 for example: https://github.com/pypa/virtualenv/issues/1551
It has been capped on devstack side also
I3b447557f013934719aa357efeffb093c7f6bd95
Let's use the lower version and we can move to
latest once issues are fixed.
Change-Id: I341437856c709e1e0e281357b96901ae6ef7cd00
* Update devstack-gate from branch 'master'
- Use stable constraints in Tempest tox till stable/rocky
Stable branches till stable/rocky is using python
version <py3.6. Tempest test those branch in venv
but Tempest tox use the master upper-constraint[1]
which block installation due to dependencies
require >=py3.6. For exmaple, oslo.concurrency 4.0.0
is not compatible for <py3.6.
As we pin Tempest for EM stable brach, we should be
able to use stable constraint for Tempest installation
as well as while running during run-tempest playbook.
tox.ini is hard coded to use master constraint[1] which force
legacy ocata job to use the master constraints and fail
- https://review.opendev.org/#/c/706161/
Devstack can set stable u-c to use via env var but this is
not enough as Tempest recreate the tox env with master u-c
when run test via devstack-gate.
All other branches have been fixed by fixing the run-tempest playbooks
in same way.
- https://review.opendev.org/#/c/705870/
Because stable/ocata and grenade job use devstack-gate, we need to fix this.
This is required to fix the grenade jobs on each stable branch to
get the other fixes in.
[1] bc9fe8eca8/tox.ini (L14)
Change-Id: Ibfc5c3d5e64e274fd674e6c42878d98bb194fa73
* Update devstack-gate from branch 'master'
- Drop peakmem_tracker service
When devstack reverted the pip cap in [0], it was necessary to disable
the peakmem_tracker service as there was no easy way to make it work in
that setup. So we need to delete it from the test-matrix here, too.
We could decide to add it only for older stable/branches, but as ds-gate
is to be obsoleted anyway, I'm not convinced that that is worth the
effort.
[0] https://review.opendev.org/561597
Change-Id: I9dd57d3bdb56c64377efbdd55429bd075223c746
* Update devstack-gate from branch 'master'
- Merge "nova: Enable n-cauth on stable/rocky for cells v1 jobs"
- nova: Enable n-cauth on stable/rocky for cells v1 jobs
Ia85ea5d338f07cb248f60de44b21826862d09d26 had enabled n-cauth again
correctly on branches prior to Rocky but missed that while deprecated it
is still required on stable/rocky for cells v1 jobs:
https://docs.openstack.org/nova/rocky/configuration/config.html#workarounds.enable_consoleauth
Change-Id: I74fd0ba8d2fb1ed25210576fabe957167dc6ca90
* Update devstack-gate from branch 'master'
- Use python3 for virtualenv if exists
Depends-On: https://review.opendev.org/#/c/702162/
Change-Id: Ib07ea45bf0a6e202751f6ddf7fcb159da310f5c8
* Update devstack-gate from branch 'master'
- nova: Renable n-net on stable/rocky|queens|pike|ocata
Following on from Ia85ea5d338f07cb248f60de44b21826862d09d26 n-net also
needs to be renabled on these older branches to allow cellsv1 testing.
Change-Id: I300a93142355517382c8ba55105ac7c1e88f29c8
* Update devstack-gate from branch 'master'
- Re-enable the n-cauth required service for stable/queens|pike|ocata
n-cauth serviec has been remvoed from nvoa in Ussuri and that is why
it was removed from default services[1]. But that is requried
for stable/queens|pike|ocata which still depends on text-matrix
for ENABLED_SERVICES. Since stable/rocky we have migrated the
service enable in devstack base job[2].
This commit fix the Tempest master and stable/queens|pike|ocata
gate by re-enable the n-cauth service for listed stable branches
only. Later we can discuss to remove the test-matrix dependency for
these branches also.
Related-Bug: 1858666
[1] https://review.opendev.org/#/c/700217/
[2] https://review.opendev.org/#/c/546765/
Change-Id: Ia85ea5d338f07cb248f60de44b21826862d09d26
* Update devstack-gate from branch 'master'
- Add a feature support matrix test for grenade subnode
test-features.sh wasn't testing anything for subnodes
so this adds a subnode feature support matrix test for
grenade. It also highlights that the grenade config
is applied to all nodes regardless of role so a TODO
is added to test_matrix.py in case someone needs to make
that per-role, per-config service override support at
some point (hopefully that never really happens and all
jobs are moved to zuulv3 by that point).
Change-Id: I485d76c1db5c3a4363c3e26fea204cc7782887f3
* Update devstack-gate from branch 'master'
- Disable c-bak and etcd3 in grenade jobs
Grenade only runs tempest smoke tests and there are no
cinder-backup service related smoke tests in the main
tempest repo so running the c-bak service on the primary
and subnode (in multinode jobs) is just a waste of resources
since it's not used in testing.
Similarly, etcd3 is really only interesting for cinder in
a multinode job but in grenade multinode jobs etcd3 is not
enabled on the subnode, so only the primary node cinder
services are configured to use etcd3, so again it's a waste
of resources.
There is a theory that bug 1844929 is failing primarily on
OVH nodes because they aggressively restrict iops so we're
running into swap issues [1]. Freeing up more resources on
the nodes used in grenade jobs might alleviate some of that
swap pressure.
To do this using the feature test matrix in devstack-gate
the test_matrix.py script has to be updated such that
services can be added/removed per config rather than per
feature because otherwise grenade says it wants cinder but
cannot remove cinder-specific services like c-bak.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010506.html
Change-Id: Ide146793053ae6b62f93a5af45c6130a21514e87
Related-Bug: #1844929
* Update devstack-gate from branch 'master'
- Add more logging to test_matrix.py
This is just to help with figuring out what's going on in
test_matrix.py when it runs.
Change-Id: I8c81cdc44c62719fea5becfb81f6bab17cbe658e
* Update devstack-gate from branch 'master'
- Add --verbose option to test_matrix.py
This allows getting the debug logging out of test_matrix.py
from the command line which is useful when you're trying to
debug what is wrong with entries in the feature test matrix.
Change-Id: I49aa3d7b60f4df4f32a0a3dbef9b13a97404dbf4
* Update devstack-gate from branch 'master'
- Remove 'cinder' service from feature test matrix
The cinder config is including the "cinder" devstack
service which would mean that anything removed explicitly,
like c-bak, is going to be trumped by the fact that 'cinder'
is in the enabled services list in a job.
This removes 'cinder' the service from cinder the config so
that cinder services have to be explicitly enabled/disabled
in the feature test matrix.
Change-Id: I857fbeba2af4a0f038fd2c2a19bb29c2767227a2
* Update devstack-gate from branch 'master'
- Modernize default services in the test matrix
Ceilometer is not installed by default in legacy jobs using
devstack-gate so we shouldn't be enabling it by default. Anything
that cares about testing with ceilometer should be using a zuulv3
based job with the ceilometer devstack plugin and explicitly
enabling the service. So ceilometer is removed from the default
list of enabled services.
This also removes some now-dead nova services (n-obj, ha).
Change-Id: If8237c94be2b1db210f83bc9871792af9c5c868f
* Update devstack-gate from branch 'master'
- Bump ANSIBLE_VERSION default to 2.7.14
devstack-gate is still used for grenade jobs and restricts
ara<1.0.0 and defaults ANSIBLE_VERSION=2.5.7.
ARA 0.16.6 dropped support for ansible < 2.6 [1]. As such,
grenade jobs are failing because ara 0.16.6 cannot be installed.
This bumps the ANSIBLE_VERSION default to 2.7.14 which is current
as of Ubuntu Xenial 16.04 which should be sufficient for the
branches still supported in upstream OpenStack CI (mainly Ocata+).
[1] 872ba818fb
Story: 2007028
Task: 37825
Change-Id: If7874f6e74606fe8a79fbff48abf764cc41c4a3b
* Update devstack-gate from branch 'master'
- Set tox basepython to python2
bashate isn't working under python3 so we pin to python2.
Change-Id: Idbff334bec75bdbb7f7e46a164d8904768ef5881
* Update devstack-gate from branch 'master'
- Merge "Add gate job for stable/train"
- Add gate job for stable/train
Now we have stable/train branch ready for devstack
and so does for all service projects.
This commit adds the stable/train job running for
d-g gate.
Change-Id: Ibf278cd21d1a0921f7122deb944e1ae18b7c07c1
* Update devstack-gate from branch 'master'
- Fix MySQL log collection
The mysql logs weren't being copied to logs and published.
Related-Bug: #1844929
Change-Id: I20740b468e4b310ac07e77f3930cae92026942fb
* Update devstack-gate from branch 'master'
- Prepare for stable branching in devstack-gate
This ensures the legacy devstack-gate can be used for train.
Change-Id: Id89df61fe53437a2d21354a46dc92e4654d03bc1
* Update devstack-gate from branch 'master'
- Merge "Add gate job for stable/stein"
- Add gate job for stable/stein
Now we have stable/stein branch ready for devstack
and so does for all service projects.
This commit adds the stable/stein job running for
d-g gate.
NOTE: Adding legacy job vesion of stable/stein because
only legacy jobs use devstack-gate which is what we need
to test.
This commit removes the all stable zuulv3 native jobs
which does not use devstack-gate and so does not required
to be tested here.
Change-Id: I546038fa4164a3085b33fa0ef30a51ec237bdc3f
* Update devstack-gate from branch 'master'
- Merge "Note status of CINDER_PERIODIC_INTERVAL setting"
- Note status of CINDER_PERIODIC_INTERVAL setting
Change I1ef1fe564123216b19582262726cdb1078b7650e in DevStack removes
the ability to set the Cinder periodic_interval config option via the
CINDER_PERIODIC_INTERVAL shell var.
The CINDER_PERIODIC_INTERVAL was introduced in DevStack in Havana as
a workaround for Bug #1180976. That bug, however, was fixed in such
a way that it does not require adjusting the periodic_interval in
Cinder, and the workaround was finally removed in Train.
Because devstack-gate is basically frozen as a legacy pre-zuul-v3
supporting infrastructure for DevStack jobs, this patch does not remove
setting the CINDER_PERIODIC_INTERVAL. It simply adds a note explaining
that it's a no-op when using a Train or later DevStack.
Depends-on: https://review.opendev.org/#/c/652711
Change-Id: I7e2cc815ad14036dbae94e73d118b2845ddf5c64
Partial-bug: #1824837
* Update devstack-gate from branch 'master'
- Pin ARA to <1.0.0
ARA 1.0 will be released in the near future and isn't backwards
compatible. Pin it so it doesn't break things unexpectedly.
Change-Id: If40616a433c32ce23eca3b06c27050950c62e250
- Replace git.openstack.org URLs with opendev.org URLs
Thorough replacement of git.openstack.org URLs with their opendev.org
counterparts.
Port of the present changes are needed to fix some errors in legacy jobs when
opendev.org is used as git base URL, as devstack-gate tries to clone
openstack-dev/devstack and it fails (the redirect works only when
git.openstack.org is used).
Change-Id: I81f6e00aa10ef7f93d0dead2f76369035a18a81b
- OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.htmlhttp://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
* Update devstack-gate from branch 'master'
- Merge "Replace openstack.org git:// URLs with https://"
- Replace openstack.org git:// URLs with https://
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Id82762087382b8bb72ea339e58e728be169000ba
* Update devstack-gate from branch 'master'
- Replace openstack.org git:// URLs with https://
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I59312b9ee70b4a3a7e9912a011de770d8df0f5a4
* Update devstack-gate from branch 'master'
- Merge "Enable process_stackviz function to be optional"
- Enable process_stackviz function to be optional
This patch keeps the proccess_stackviz function default to true, but
allow it to be optional called, if you set PROCESS_STACKVIZ to 0.
This is required because not all the projects run tempest in the same
way.
One of the examples is the tripleo project, that has a particular way
to run tempest (in undercloud) and it's being impossible to have the
stackviz results in the logs/stackviz because the cleanup process
overwrite the stackviz data there.
Change-Id: Idf4f360ecba618900ef939d94db2ffb73e16b11a
* Update devstack-gate from branch 'master'
- Replace deprecated ansible --sudo with --become
Solves annoying warnings and prevents code from breaking on newer
ansible which dropped --sudo.
The sudo command line option has been deprecated in
favor of the "become" command line arguments. This feature will be removed in
version 2.6. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
Change-Id: I0ec17d6bd6a1e3ada366c323ad67e864a7f1b5ed
* Update devstack-gate from branch 'master'
- Merge "Avoid failure to install zuul when venv exists"
- Include openstack/placement in PROJECTS starting in Stein
The openstack/placement repo is required for devstack/grenade
runs starting in Stein so this adds a conditional based on the
branch to include the openstack/placement repo in the default
PROJECTS list.
Needed by https://review.openstack.org/604454/
Depends-On: https://review.openstack.org/608266/
Change-Id: I71cffffc88c329052c4067d6a9406f42856c69c6
- Merge "Update grenade settings for stable/rocky"
- Update grenade settings for stable/rocky
Depends-On: https://review.openstack.org/600196/
Change-Id: I940a705d4b8269fbf3bec9f107f179e9191b5a42
- Bump ansible to latest 2.5 version
This is the same version run by zuul.
Update devstack callback for ansible 2.5.
Change-Id: Ic0d2559346570e60025838166b9bd0081eee331a
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
- Merge "Add gate job for stable/rocky"
- Import legacy-dg-hooks-dsvm job
This job is used only by devstack-gate, import it.
Rename it to devstack-gate-hooks following our naming policy.
Change-Id: Id01d7cda5cb28b6371bdcf8b85208135caa9e9b1
- Add gate job for stable/rocky
Now we have stable/rocky branch ready for devstack
and so does for all service projects.
This commit adds the stable/rocky job running for
d-g gate.
Depends-On: https://review.openstack.org/#/c/596279/
Change-Id: I7ab1b7042808cce0d89cb2bcfc87c718543718b4
- Merge "Remove support for devstack exercises"
- Avoid failure to install zuul when venv exists
Fixes case where a succesfull creation of the
virtualenv but failure to install zuul would
make the function useless as it would always
miss installing zull.
Change-Id: Ie5ef82765120094e8147b05443626e2012273fba
- add rocky branch to features.yaml
This patch adds the rocky branch to features.yaml so that rocky branch
patches can land, for example [1] that currently fails with:
ERROR: branch not allowed by features matrix: rocky
[1] https://review.openstack.org/#/c/584078/
Change-Id: I235c6c3ad81dff916a65cf8b97152621812fa102
- Remove support for devstack exercises
These seem to be not run for quite some time and they don't
succeed anymore - drop the code to avoid somebody accidentally
running it and wondering. A good example of "if it isn't tested
its broken".
Needed-By: https://review.openstack.org/#/c/581377/
Change-Id: I68d7099e6f5be502f8a578818b5e2e4c82889c15
- Dynamically determine overlay MTU
Some clouds we run on no longer have MTUs of 1500 on their interfaces
and are smaller. We dynamically determine the MTU we should use on the
overlay networks. List all "real" interfaces with a permament mac addr
then use the smallest MTU less 50 bytes for vxlan overhead.
We only consider "real" interfaces so that we can run this multiple
times for separate overlays without perpetually decreasing the MTU due
to finding the lower MTU we just configured.
Change-Id: If163bf211570e690e255cc3ef6888d9e0cba19b5
- Cap cmd2 to < 0.9.0
cmd2>=0.9.0 now require python3.4 or greater. We install ansible under
python2 (for now) so we need to cap the cmd2 install to make the ansible
installation function.
Upstream bug at https://github.com/python-cmd2/cmd2/issues/421
Change-Id: I5ec830e092646a3626cacea264de9ad81fcdd124
- Merge "Grant tempest user access to virt-filesystems"
- Remove retired tripleo-incubator from PROJECTS list
tripleo-incubator has been retired so we don't cache it on our images
but if it is in the PROJECTS list we will attempt to rsync it. Just
remove it as it is no longer used.
Change-Id: I3ad57d247a02881ba8a6757f2a058d03884eaf35
- Merge "Remove setting of ETCD_DOWNLOAD_URL"
- Remove setting of ETCD_DOWNLOAD_URL
Adding ETC binaries was a stop gap measure until packages were
available. With the impending release of bionic that'll be soon :)
Also using the mirror on tarballs.o.o was unreliable so these binaries
are cached in the nodepool images as described in[1]. Having this
setting in d-g makes more work than is needed in the near term.
Removing it does introduce a new failure mode if an etcd version is
used in devstack but not yet cacched in the image.
[1] http://lists.openstack.org/pipermail/openstack-infra/2018-March/005871.html
Change-Id: I2a6649ae3094ca65aa31798ee9bddf2fcdd49260
- Fix bashate "local hides exit status" warnings
Promote "local hides exit status" (E042) to error and fix issues found
(this is inline with what we do in devstack).
Change-Id: Idd784af066db80bb67792da3dd0aa0ae4c8475db
- Merge "Revert "Work around cffi install error""
- Merge "Add stable/pike Tempest bitrot job"
- Add stable/pike Tempest bitrot job
Replace the legacy stable/pike tempest bitrot job with the new
zuulv3 one. The removal part will be done in a separate patch
since it's in a different project.
Change-Id: I180cd65e934c15b33975e65a9ece1d1f48fd851c
- Add neutron-tempest-plugin-api job
The old tempest tests have been removed from the neutron repo, so
legacy-neutron-dsvm-api doesn't run anything at all anymore. Use the new
api job from the neutron-tempest-plugin repo instead.
Change-Id: I2d1854109474cee1923b9bffd75c3224a6f2b4bf
- Merge "Handle stestr execution for stackviz"
- Merge "Handle a stestr results directory"
- Merge "Add stable/queens integration checks"
- Return a proper boolean True instead of a 'True' string
The type here is important, returning anything other than a boolean
has unintended consequences such as breaking Ansible callbacks because
they are expecting the "changed" field to be nothing other than a bool
by contract.
Change-Id: Ia9b4a749f64adae8969fd9ad66304d013013e056
- Add stable/queens integration checks
New jobs for d-g can be defined in the local .zuul.yaml as opposed
to project-config. These jobs prevent ensure changes to d-g to not
break stable/queens.
Depends-on: https://review.openstack.org/521888/
Change-Id: I547591607a7726bdef3c3953df9e0bd1c67f3423
- Merge "Update grenade settings for stable/queens"
- Update grenade settings for stable/queens
Change-Id: I2709f5527552fd4fc406f870ef35c4b6e4b9dae9
- Check for virtualenv binary
The current check looks for a virtualenv package; but this isn't
portable to other platforms. In the gate we also have installed from
upstream (to ensure latest) and the package might be on hold, etc
which might mess up the detection.
I think the KISS thing to do is to check for virtualenv and fail with
a useful message.
Change-Id: Icf15ddd18ca52885f5c4a89a7d83622a70c811d5
- Zuul: Remove project name
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Ifd621431bfb925e8a6f0df013ddbe7cd7ed5c1e7
- Remove tempest-lib
tempest-lib was reintegrated into tempest in 2016, there's no need to
check it out anymore. Remove it from PROJECTS list.
See also
https://specs.openstack.org/openstack/qa-specs/specs/tempest/implemented/reintegrate-tempest-lib.html
Change-Id: I3ed33ad9cf4097bc48ab71a666c2ce95b26c3329
- Set up stable/queens
Change-Id: I505bb7f7d226845e96a815a34a548ceacee65517
- Merge "Remove run-tests and py3-run-tests"
- Merge "Fix setup_project checking out eol with branch name"
- Handle stestr execution for stackviz
This commit makes to handle a stestr execution for stackviz process.
Tempest is now in the process of switching the tempest run command to
use stestr internally instead of testrepository. This means that results
will be stored in .stestr instead of .testrepository. So, this commit
makes to handle a stestr or testrepository execution with checking which
directory exists before attempting to process the subunit results.
Change-Id: Ib19d3779deb89142e95762794dd1ce3fe3236b55
- Handle a stestr results directory
Tempest is in the process of switching the tempest run command to use
stestr internally instead of testrepository. This means that results
will be stored in .stestr instead of .testrepository now. This commit
updates the post-processing function to check which directory exists
before attempting to copy the subunit results.
Change-Id: I3855aad5ce129ec8ccb87c05f7aa709b74070efe
- Remove run-tests and py3-run-tests
We have standard jobs for doing unittests under python2 and python3 -
namely, the builtin tox environments py27 and py35. Just use those and
remove the locally defined jobs.
Depends-On: I6d7a96adf5cfb075f5a2ffbd089ccbb883a1c1b4
Change-Id: I0cc0c07daafba331a64861c134029e443ba2aa8d
- Move commands to the base testenv
This should allow py27 and py35 to both work in parallel while we remove
the run-tests versions.
Add the new jobs here, even though the next patch will remove them,
since we can't verify the new jobs work with depends-on to
project-config.
Change-Id: I78cfadf5a3b9822ce32f5a1d9b76321d573618ab
- Import tox jobs
Import the tox jobs and convert them to Zuul v3.
Change-Id: Idcdc8d4508fa8d7746b3ba094d0bd96410007ef1
Needed-By: I6d7a96adf5cfb075f5a2ffbd089ccbb883a1c1b4
- Create a test matrix role
Modify test-matrix.py so that is can be used as an ansible module.
Add a role in d-g that runs test matrix for the given branch,
role and features file.
Change-Id: Ie36ba0cd7cfcd450b75000a76a64d856f2a83eba
- Fix setup_project checking out eol with branch name
A recent change to devstack-gate to enable falling back to EOL tags for
zuulv2 has a bug in it where it will try to checkout the stable/branch
instead of the converted eol tag. This patch addresses that issue.
Change-Id: I23330884da09befc3bca10973cbfd2ea9b666430
- Merge "Use = for string comparisons"
- Add fallback to -eol tag if stable branch doesn't exists
In order to support continued testing against EOL version of projects,
the setup_project function needs to be able to understand checking out
to an eol tag.
Change-Id: I1b2d030df8cb2a850bf9248595171d96a813d381
- Use stackviz tarball from cache directly
The stackviz tarball used to be copied along with other devstack
files in devstack space, but it's not anymore since
1a49f65dd9509d27fcddfa7f9526d12c4889e68c.
There's actually no point in moving that tarball around, so just
use it from its original cache location directly.
Change-Id: I602507648e17a7d8d06d8f541ba0918b3b972723
- Checkout from -eol tag if stable branch does not exist
Since several projects stable/newton branches have been end of life'd,
we can't install base devstack on stable/newton.
This modifies the setup_workspace function to check, as a last resort,
if the base_branch is a stable branch and if there is a corresponding
-eol tag, to use that for the checkout rather than the stable branch.
This is needed in the cases that projects are end of life'd out of order,
as is the case with keystone, cinder and neutron being end of life before
nova for stable/newton.
Co-Authored-By: Eric Fried <efried@us.ibm.com>
Change-Id: I344d8fdded9b7d5385fcb41b699f1352acb4cda7
- Revert "Work around cffi install error"
This reverts commit e473fdec13445191d1acf1c77d19c87bbda512c8.
Change-Id: Iff8d3c4b8f514bd66649cc7c4f788302af32cbc4
- Don't set CEILOMETER_BACKEND in localrc
mysql backend is not supported anymore. default is
gnocchi.
Change-Id: I2d1e31e386a2576b3a44ec5b8e15dc49d2a474d3
- Remove v3 devstack job
In preparation for moving to the devstack repo.
Change-Id: Ie2119f24360d56690ffd772b95a9ea6b98dd4a39
- Stop it with the moving then copying of cache files
Originally, for snapshot images and in early dib days, files were
cached into ~/cache/files (~ being jenkins). Thus the original
copying of files from ~/cache/files to $DEST/cache/files, introduced
with 25ba5c9bce825106b25cf4d8a64f76a1e604a92c, was to move these files
from here into the devstack checkouts.
However, when we were converting away from puppet for image builds, we
found that we do this caching very early; before the jenkins user is
created even -- so having the homedir populated was causing issues
creating the user. Thus we moved the devstack cache to
/opt/cache/files (Ibca6867f29b257a5110cb5522a5cca3a97fa9377)
This copy probably should have been removed at this point. However,
since we also added back the ~/cache/files symlink this continued to
work.
Thus this removes the unnecessary copy out of ~/cache/files and links
the files into the devstack checkouts directly from /opt/cache/files
Change-Id: I35f76c59d894b00d9544b82a2d8cdcd7f526f243
- Use = for string comparisons
Change I384e4c376076051e7a4a8b2d704107cbe3ac08ad introduced
comparisons of $DEVSTACK_PROJECT_FROM_GIT against a couple of
hardcoded string values in a bash [[ ]] expression, but incorrectly
used the -eq integer comparison operator. This seems to work under
normal circumstances, but actually breaks if the string value of the
variable contains a "." since the equivalence test tries to fail
early if it detects what it thinks is a float value (because it's
intended only for integers). Instead of -eq use = for string
comparisons here, because that's what the POSIX test(1) utility
mandates.
Change-Id: If33d7aea9142e650b57c0f58c14e2a4434e30bf0
- Work around cffi install error
cffi-1.11.1 was released without wheels so we cannot install it because
of missing libraries. Install 1.11.0 as a workaround.
Change-Id: I6e0eab8e6ea126eec4c2c0767229cb915338e486
- Check for branches in zuulv3 git repos properly
Zuulv3 git repos do not have remotes. git_has_branch checks if the
branch exists in the origin remote which does not exist so all branch
specific checkouts were falling back to master which caused job
failures.
Instead just check if the base branch name exists in the repo as that
existing in a zuulv3 repo is sufficient to know we are up to date.
Depends-On: I110879bac5d8a671d73fab906ffbcf8156b1135d
Change-Id: Ifcae3ff217259926a8950f6da83212ee311002b2
- Remove manually added legacy-tempest-dsvm-neutron-full
Change-Id: I72687a56285a3d733a9adeaf3dc037a1ac95efd3
- Merge "Don't double-quote the rsync options"
- Merge "Remove devstack-legacy base job"
- Merge "Zuul v3: export devstack journal"
- Merge "Zuul v3: Save devstack log"
- Don't double-quote the rsync options
We need to quote for yaml. If we do, it works.
Change-Id: I7d208d3799205402254c0e023104a3a69adb2b46
- Remove devstack-legacy base job
We added it to openstack-zuul-jobs so we can use it as a base job in
the migration.
Use the results of the migrated
gate-tempest-dsvm-neutron-full-ubuntu-xenial to test that the base job
will work for migration purposes.
Depends-On: I3ff2b486702fed9342097cdcd30ffa0c043bdecc
Change-Id: I34514c2c38d2121c6b6fbca7e83bd273f2ec49f0
- Zuul v3: export devstack journal
Change-Id: I2d9b25f12de09a99f140cdb7cb7ec3f23fef0a34
- Zuul v3: Save devstack log
Change-Id: I2ec4d620e34303e26a231ed000b1e5e7b8141ff8
- Create stack home folder
The create stack user role creates the home for the stack user,
which works as long as the containing folder already exists.
Since this may not always be the case, create the folder first.
Change-Id: Ibe3539a738340d6e4d95e3661bca5e2067e3e959
- Grant tempest user access to virt-filesystems
Access to /usr/bin/virt-filesystems is required by ironic tests
to check that partitioning table was removed from VM after cleaning.
Related-Bug: #1523640
Change-Id: I7335638e513f066069672772ba0d9171b66ec710
Project: openstack-infra/devstack-gate 96978baec5feb07ed115cf8d5ea69f15d1109ce6
Zuulv3: Ansiblise ephemeral/swap setup
Move the "fix_disk_layout" role from a big shell script to ansible
steps for the native v3 devstack job.
This change is based on Icd4e6d8ab84471ad06e69c3e0f9bac92776efc78.
(Requires Ansible 2.3 for the parted module)
Change-Id: Ia6dcb13803a549390cad736849a26c92494a914c
Depends-On: I2a59e22a38918ae45e0518b0af85ad6e8bc9423c
Project: openstack-infra/devstack-gate d8b44c78aba070616aaf7412881ec52c445b291c
Zuul v3: run devstack
Add a role to run devstack, and add it to the main devstack playbook
for the next-gen devstack job.
Change-Id: If84d764e9b2f8dbb6beb1990abc11cbb9f1156b0
Project: openstack-infra/devstack-gate bd612be0b6c5f4709bba493603c59d6707f07b09
Zuul v3: Add devstack_local_conf ansible module
This writes the contents of a variable dictionary as a devstack
localrc file. It sorts the output so that references to other
variables may be resolved.
Change-Id: Ib9716317333aecffca627f5a38a95d86fc4b320b
Project: openstack-infra/devstack-gate 2ffabdbbffdfc13e0e57639cf40f15c8c06e8514
Zuul v3: create stack and tempest users
Note, the stack user home directory is different than current, however,
these roles are now diverging from the legacy roles. This matches
the current default devstack behavior.
Change-Id: I9a19579dd159dff38750afa3a0f9c642f2056408
Project: openstack-infra/devstack-gate aaf4774b581263f714b5386158271493de3df63f
Zuul v3: add a devstack-legacy job
This job attempts to run devstack as close as possible to the manner
in Zuul v2.
Also, don't write the devstack-local conf file if no variables were
supplied.
Change-Id: I308504bf5a48652c62d4d05572c5c077a7dfe368
Project: openstack-infra/devstack-gate b91005fc521d4881998c8147b8dd89ad42e04e65
Allow for arguments to DEVSTACK_GATE_SETTINGS.
The following patch added some arguments to be passed to the
DEVSTACK_GATE_SETTINGS file:
https://review.openstack.org/394684
This is not currently supported by devstack-gate, as the argument is
included as part of the filename when checking to see if the settings
file exists. This patch makes it ignore arguments when checking for
the existence of the settings file.
Closes-bug: 1665856
Change-Id: Ie787baeeafd38670e4085d734329b64eff3d3741
Signed-off-by: Russell Bryant <rbryant@redhat.com>
Project: openstack-infra/devstack-gate 0ea4c4ef607300d8d179f6023c3fa7c57b654628
Update Ansible from 2.2.0.0 to 2.3.2.0
Let's update Ansible to the latest version, 2.2 is bound to be
end of life shortly after 2.4 releases sometime next month if all
things go according to plan.
Change-Id: I2a59e22a38918ae45e0518b0af85ad6e8bc9423c
Project: openstack-infra/devstack-gate 101e0fbbc5e8851c53b4d09672bd26cee0099201
Combine parted script into one command
It looks like we may be encountering issues running the second or
third of these commands; combine them into one to reduce system
raciness.
Change-Id: Iacb93868c678161d84bb5c06a8180b8eb12b5fe7
Project: openstack-infra/devstack-gate 47b2b4d31cabf54633afe97d069cb1e30e50580d
Re-introduce sync/partprobe in fix_disk_layout
We've seen at least one occurence of a
"Device or resource busy while setting up superblock" error while
setting up xvde2 which, as far as we know, is a new error.
This problem was not happening before we took out sync/partprobe so
let's put that back in for safe measures.
Related-bug: #1706103
Change-Id: Iad1a75aa5fb4ae5a2f4a9cad6373091124917c24
Project: openstack-infra/devstack-gate e69d8b835db3783301fd33e04acadf1d06d307e4
Revert "Revert "Move fix_disk_layout to an Ansible role in setup_host""
This re-introduces the Ansible role to set up the disk layout.
The initial introduction increased dramatically the occurrence of the
race condition involving the failure when configuring swap on /dev/xvde1 [1].
This (re)revert substitutes the sync and partprobe commands by a
udevadm settle command in order to wait until the device and it's partitions
are ready for use.
[1]: https://bugs.launchpad.net/openstack-gate/+bug/1706103
This reverts commit 71aa1bd6cfe7e7a98179008638e27f2f4c675441.
Change-Id: Iac0efdb6077ab18c2e1991820da4fcea7642f708
Project: openstack-infra/devstack-gate 66e06c55ff7baea76183fc260fb897dfe19377b9
Revert "Move fix_disk_layout to an Ansible role in setup_host"
This seems to have increased the rate at which the missing partition issue is occurring, let's revert for now while we figure this issue out.
This reverts commit 279ba7c1d5e0411733761e144061c56917c92f17.
Change-Id: Idbfa6ec321fe8dd96b68b9d7213aab530e0f5381