* Update grenade from branch 'master'
to 62584f06e881265ec6a4a773b93b75bef038a378
- Merge "Upgrade skiplevel jobs to check the right from_branches"
- Upgrade skiplevel jobs to check the right from_branches
Now that we're on 2024.2, we need skip-level-always to gate against
2023.2.
Change-Id: I155cefe0365d88b312344f5154ad45513ecdc2f1
* Update grenade from branch 'master'
to 35dd0e47ad5e76f974f65125221da5ef84e7b5f7
- Merge "Update the master grenade setting for 2024.1 to master upgrade"
- Update the master grenade setting for 2024.1 to master upgrade
Change-Id: I91701133f6b1b9f9d66cb8429ed82824d6e80b1f
* Update grenade from branch 'master'
to f9ab3afa695817261ef1e13c4c044ff4360815ef
- Remove grenade-skip-level job from non SLURP master
Current master branch (2024.2) is non SLURP release and
grenade-skip-level job is not supposed to run on non SLURP
gate.If any project want to test upgrade from stable/2023.2
to 2024.2 then they can use grenade-skip-level-always job.
Keeping its job definition create more issue and confusion when
zuul looks for the job selection.
Change-Id: I705996a9eefd40b975080cdc51b68c4467b94437
* Update grenade from branch 'master'
to 2523aa0b41578ba57e7dfd176a947ee3ced8de84
- update grenade-base to use 8G of swap
we have notice failures in the grenade jobs
corralated with OOM events. grenade-base
previously used the default value of 1G
for configure_swap_size: but now its updated
to configure_swap_size: 8192
most devstack jobs have already been changed
to either 4096 or 8192. all jobs that inherit
form devstack-tempest use 4096 where as more
complex jobs such as those that have ceph use
8192. as grenade is a non trivial job this patch
uses 8192 MB
Change-Id: Ibf6dfe84f15019d0360e2c2042856aeecb22209d
* Update grenade from branch 'master'
to f1980a682ba072d694efa59a62cf68cef7ecb5ce
- Set NOVA_VNC_ENABLED: true for subnode in the grenade job
Currently, because we don't run the n-novnc (console proxy) service on
the subnode, devstack won't enable VNC for guests hosted on the
subnode.
We see occasional failures in the gate when VNC tempest tests attempt
to obtain a VNC console for a guest that happened to get scheduled to
the subnode with the following error:
Details: {'code': 400, 'message': 'Unavailable console type novnc.'}
This sets NOVA_VNC_ENABLED = true for the subnode only, with the
thinking that the enabled n-novnc service is sufficient for the
controller node.
Jobs that derive from the "devstack" job [1] are already setting
NOVA_VNC_ENABLED: true for both the controller node and subnode.
[1] 3ffcc89d5d/.zuul.yaml (L535)
Change-Id: I1acbdb605e0e0d9e5b4604fcd21af850b06823b9
* Update grenade from branch 'master'
to 36c8d242f8a702c0e6673530e02990d6ab269588
- Increase cinder verify sync timeout
This is occasionally failing with a timeout. It has been for months,
but it seems like the frequency has increased lately.
Change-Id: Ib1270e4f5bada8680a5d19133a888a8ade8f73c3
Closes-Bug: #2039707
* Update grenade from branch 'master'
to 0f0d9dcb9e9d972cb319482c7192d8853b912e21
- Make octavia-grenade job voting
octavia-grenade job is fixed and passing now,
so making it back to voting.
Change-Id: I33f878dd0da28fd3985347f2ed7ef6b70cd5acc9
* Update grenade from branch 'master'
to 159054a9274f984d8e53e5e5bd9e7ab0fb29708b
- Update grenade setting on current master
grenade is branched for stable/2023.2, so updating
the current master default setting for:
- Update grenade testing from stable/2023.2 to master.
- Update grenade-skip-level and grenade-skip-level-always
jobs to upgrade from stable/2023.1 -> master
Depends-On: https://review.opendev.org/c/openstack/grenade/+/897381
Change-Id: I1dbea0caad676d6be7a4a58495a76a351e3c41e5
* Update grenade from branch 'master'
to 5d8b7569ee9f3fa825878dfcf44ff0f92853e427
- Use re2 compatible regexes in branch matchers
Python regexes are deprecated in Zuul, so update the use of regexes
in branch matchers with re2-compatible syntax.
The commit also removes matches for branches that are EOL - all
branches until stable/rocky (including).
Change-Id: I43c696ef2029cbf351f902b293df05f296dbb2a2
* Update grenade from branch 'master'
to 67858b98bd6ad568017c53ee4c396f0632f86da1
- Merge "Disable using GLOBAL_VENV for now"
- Disable using GLOBAL_VENV for now
We don't want to go through the hassle of changing existing deployments
from global pip installs to using a virtual environment, so disable this
feature in grenade jobs for now until we can use it on the old side,
too.
Needed-for: https://review.opendev.org/558930
Change-Id: I5e5a67cceade05a4a32ddd1b86802f9496d1bb79
* Update grenade from branch 'master'
to d8294440e7dede370b5ee80facf49a511dc7eb09
- [ironic] Add an instance wait setting for nova resources
In troubleshooting grenade failures in ironic,
we've observed a sporatic failure causing the
ironic-grenade job to fail upwards of 20-40%
of the time where it seems cirros, due to the
boot sequencing and interfaces, is not
online for networking until after sixty seconds
have passed. In one case 83 seconds before the
networking was fully online.
In consulting with neutron contributors, a random
job check seems to reveal that even with pure VM
workloads, it takes on average 35 seconds into the
ping check. As such, it seems reasonable to make
the setting configurable so ironic-grenade can
execute with an increased timeout more appropriate
to the job settings and test environment.
Adds a INSTANCE_WAIT variable, which defaults to
the prior setting which was static, 60 seconds.
Change-Id: Ie5acf1ad7f8dca39db07f7e61035a8916439004d
* Update grenade from branch 'master'
to 4c9c059883158fd6bf3cb79ca89d52003a63b7fe
- Fix tempest venv constraints for target branch tempest run
We fixed the tempest venv constraints setting for tempest test run
on base branch but forgot to do the same for target branch test run.
It cause issue when base and target branch have different Tempest
and constraints to use (for example stable/wallaby use old tmepest
and stable/wallaby constraints but stable/xena use tempest master
and master constraints), in such cases we need to set proper constraints
defined in devstack and then run tempest.
We do not see this issue as none of the job run tempest on target except
heat (https://review.opendev.org/c/openstack/heat/+/872055/5).
I reproduced the issue in grenade stable/xena by enaling the tempest run
on target:
- https://review.opendev.org/c/openstack/grenade/+/878247/1
- https://zuul.opendev.org/t/openstack/build/1b503d359717459c9c77010608068e27/log/controller/logs/grenade.sh_log.txt#17184
Closes-Bug: 2003993
Change-Id: I05fcdb5045a33997bd1a4c340a16458d88399f5f
* Update grenade from branch 'master'
to 1ce132fdafd0853d80e116f2a720a14c4f08b06a
- Update grenade setting on current master
grenade is branched for stable/2023.1, so updating
the current master default setting for:
- Update grenade testing from stable/2023.1 to master.
- Update grenade-skip-level job not to run for current non SLURP master
release
octavia-grenade job is broken due to diskimage-builder so to unblock
grenade gate, stop running it and we can run it once DIB fix is merged
and released
- https://review.opendev.org/c/openstack/diskimage-builder/+/878089
Change-Id: I400c7f386e5b900774039223c9199508229494a2
* Update grenade from branch 'master'
to a8cbe6d1a9c2aafd8294d8bcf342410d6451e97f
- Merge "Fix setting the tempest virtual env constraints env var"
- Fix setting the tempest virtual env constraints env var
Grenade set the env var TOX_CONSTRAINTS_FILE/UPPER_CONSTRAINTS_FILE
which are used to use the constraints during Tempest virtual env
installation. Those env var are set to non-master constraint when
we need to use non-master constraints but when we need to use the
master constraints we do not set/reset them point to master constraints.
This create the issue when grenade script install the tempest second time
on new devstack where we need to use master constraints but env var
TOX_CONSTRAINTS_FILE/UPPER_CONSTRAINTS_FILE set previously in tempest
installation in old devstack point to the stable constraints.
One case where it started failing when we tried to pin the stable/wallaby with
Tempest 29.0.0
- https://review.opendev.org/c/openstack/devstack/+/871782
and stable/xena grenade job failed (stable/xena use master tempest and supposed
to use master constraints)
- https://zuul.opendev.org/t/openstack/build/fb7b2a8b562c42bab4c741819f5e9732/log/controller/logs/grenade.sh_log.txt#16641
We should set/reset those constraint env var to master constraints if configuration
tell to use the master constraints.
Closes-Bug: #2003993
Change-Id: I8c623008292f3b2dd2cd6d596feea552194acd89
* Update grenade from branch 'master'
to 3877df6af1f5556d9960b6412e6e2011b19f5d49
- Factor out a grenade-skip-level-always job
For projects that want to opt-in to testing N-2 upgrades on all
releases (for early warning of issues, best practices, etc), this
pulls out a grenade-skip-level-always job that can track N-2 regardless
of whether master or N-2 is a SLURP release. The regular
grenade-skip-level job can inherit from that, with the branch
restriction and most recent SLURP as the from_branch.
Note that this makes the specific job a subset of the generic for
easier application of config to both. Right now they use different
nodeset rules, but in the next release they will be the same, so it
seems clearer to make it a hierarchy.
Change-Id: I39d1cbc4a2633c9908ba0e25205fb2f6a4aa729e
* Update grenade from branch 'master'
to 8fdda79453c47886bed947dc7109bf0fbf0868e2
- Generate SSH key locally for cinder resources
Nova has deprecated the server-side keypair generation process, which
is used by cinder's resource create phase in grenade. Even though it
still works for old microversions, it generates RSA keys which will
not be accepted (by default) in newer distros. This makes us generate
the keypair locally and upgrade the public key instead of generating
it server-side.
Change-Id: I0275a44f2ec4977b085b8129fd06e80a0ed6e68d
* Update grenade from branch 'master'
to 3f9fe2e8fc1fccf0324538274e3b07b3e90b96b9
- Bump ping timeout to 60 seconds
The jobs fails intermittently on ping check
with current timeout of 30 seconds.
The testvm can take time to boot and have network
ready on slow systems and using qemu hypervisor
and lead to ping timeout.
With [1] included noticed it taking more than 40 seconds
to boot testvm, so bumping timeout to 60 seconds will
help in such cases.
[1] https://review.opendev.org/c/openstack/grenade/+/874417
Related-Bug: #1463631
Related-Bug: #2007357
Change-Id: Ibdd030e126d508e6ff24cde180c611ada7f24cb3
* Update grenade from branch 'master'
to adcb563b185416451da419186a8d7773ffb6b913
- Dump Console log if ping fails
Console log will be useful in debugging
ping check fails.
Related-Bug: #2007357
Change-Id: I0f1603154eac85353aeb3a0c42da83c268174b05
* Update grenade from branch 'master'
to 79a138f8666ca0025a9997ed73a9b6cfb267f83e
- Don't enable the dstat service in CI jobs
It's already disabled for devstack jobs with
[1]. Let's do for grenade too as those too
seeing this issue.
[1] https://review.opendev.org/q/I32ef8038e21c818623db9389588b3c6d3f98dcad
Related-Bug: #1943184
Change-Id: I72db099726ec6f737bc8eccd94a44fd715552728
* Update grenade from branch 'master'
to c7a6dff51d8e047564b380de1a81cfa3d7798fcd
- Merge "Remove lib/neutron-legacy leftovers"
- Remove lib/neutron-legacy leftovers
In [1] we finally got rid of the unfinished lib/neutron module and kept
only lib/neutron-legacy. It's renamed to lib/neutron now and it's the
only neutron related module in Devstack.
So this patch removes leftovers related to the old lib/neutron-legacy.
[1] https://review.opendev.org/c/openstack/devstack/+/865014
Change-Id: I2a856b15eda992f0e78ee8eff65f39646e24c936
* Update grenade from branch 'master'
to 3d9486a1ab879f72b4716fb8c34ad3c5409b91a1
- Merge "Update the rootwrap config when upgrading Neutron"
- Update the rootwrap config when upgrading Neutron
As reported in the related bug, the rootwrap filters are not updated
between versions. This patch calls the devstack method that setups
the Neutron rootwrap configuration and filters.
Closes-Bug: #1999235
Change-Id: Iaebf1b33ccf3bfd64191f9a898408bcfe11dd557
* Update grenade from branch 'master'
to 0dd1e186b5e27f589c10272ff163dea4fe154faa
- Use default neutron backend in the base grenade job
When devstack was switching to ML2/OVN as default backend,
in the base grenade job it was explicitly configured to use old default
ML2/OVS backend. It was done like that to avoid problems with upgrade
and change backend in the same job.
Now, as ML2/OVN is default backend in Devstack since at least
couple of cycles it's fine to switch grenade jobs to use default
backend.
Depends-On: https://review.opendev.org/c/openstack/ironic/+/866993
Depends-On: https://review.opendev.org/c/openstack/devstack/+/867065
Change-Id: Iede9fe71d81fc86a92122800d5a16f45442dd79e
* Update grenade from branch 'master'
to b1cd7a1866ee7d17392bd9896db6060d40463726
- Update the master grenade setting for zed to master upgrade
Change-Id: Ic7b6a33e674fc9e292a85de6d818b8adad784baf
* Update grenade from branch 'master'
to 793f553bddfb74394f9d98eb5f1618b0caf2f9c3
- Define NEUTRON_ENDPOINT_SERVICE_NAME variable as empty string
This new Devstack's variable is introduced by patch [1] but as it's not
in the stable branches of Devstack yet, it can't be used in Grenade jobs
with default setting.
So lets set it to the emtpy string to make it working as it was before
[1].
[1] https://review.opendev.org/c/openstack/devstack/+/849145
Change-Id: I2de65d4764f23ae85a086d4d09ed80c81777434b
* Update grenade from branch 'master'
to b4c6851ceba78dc5f0ba46d28c355cc3c16037e0
- Skip stop of ovn services
Grenade jobs stop services, check fip connectivity
for a nova server and then upgrade to next release.
But since ovn data plane and db services are stopped along
with other services, fip connectivity fails as a result.
We shouldn't stop these services along with other
neutron services. This patch sets "SKIP_STOP_OVN" to True
to skip stop of ovn services.
This fixes ovn grenade jobs.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/839362
Change-Id: I2bd3f7e5f0af9a6532db7a1cdb4bc45a963042ca
* Update grenade from branch 'master'
to fc8b623145424babd5a273a5a2d2c209e65b8503
- Do not run grenade-skip-level job on older stable branches
grenade-skip-level is added and supposed to be run from Yoga
release. We have added this job in integrated template which
is in branchless tempest side and applicable for stable branches
also.
We can control to run this job on Yoga and SLURP release onwards but
that leave if anyone running it directly without template So controlling
the branches in the job definition will work for everyone.
Change-Id: Ie560b25f83c3f102f408077f5023f07facf6095d
* Update grenade from branch 'master'
to bdc4d7388eab499618cd7573275a7070669a0763
- Merge "Disable auto discovery"
- Disable auto discovery
Tripleo-ci jobs are broken after latest release of setuptools 61.0
because of breaking changes which are not backwork compatible,
details in related bug and [1].
Users that don't set ``packages``, ``py_modules``, or `configuration`
are still likely to observe the auto-discovery behavior, which may
halt the build if the project contains multiple directories and/or
multiple Python files directly under the project root.
To disable auto discovery, one can do below in setup.py
~~~
setuptools.setup(..,packages=[],..)
~~~
or
~~~
setuptools.setup(..,py_modules=[],..)
~~~
[1] https://github.com/pypa/setuptools/issues/3197
Releated-Bug: #1966382
Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: I8ba2f6eccb9f279406321915793709e50e8279d4
* Update grenade from branch 'master'
to b960348631840205786c58dc3e0445bcdd282d5a
- Update the master grenade setting for yoga to master upgrade
Change-Id: I076ee646ca0e017748a0eeba715e5604ec6b68eb
* Update grenade from branch 'master'
to e10ac41b71f41799cd6aefec122a0771b83fa535
- Remove sourcing of userrc_early
Devstack has stopped creating the userrc_early in yoga
and also fixed the start_swift function to stopm relying
on userrc_early.
- https://review.opendev.org/c/openstack/devstack/+/780417
It start failing when grenade started upgrade testing from
stable/yoga to master.
- https://review.opendev.org/c/openstack/grenade/+/835232
Change-Id: I6caaac9d84e4f3925378f496acd06fc38bb0d2d8
* Update grenade from branch 'master'
to 68aa50b183077e79808684597e9c4ada6fb20ba1
- Do not run integration test job for gitreview file change
Change-Id: I3bb398a5853cfd732ad150314cc0eac4440f0efe
* Update grenade from branch 'master'
to 9b223d3e22f2078cce7972ce65fe19e5c3323f6b
- Add grenade-skip-level job
This adds a grenade job that specifically skips the last release,
to prove that we can do it. Such a job would facilitate a new
goal of a tick/tock release arrangement where slower-moving operators
could stick on the "tick" release and know that they can upgrade to
the next "tick" release directly.
Currently this tests from wallaby to yoga (master) and is added as
non-voting until the TC resolution passes (if it does).
Change-Id: I5a8fcc1097956ebbbe7b5ea0bed0889eeeca1d80
* Update grenade from branch 'master'
to bf235cd904101fed34a1f04fed981a662e37fff0
- Enable nova workaround for upgrade bug
Nova recently introduced an issue that breaks FFU due to requiring
new compute service records to be recorded before control services are
allowed to start. However the former depends on the latter, which
creates an unsatisfiable circular dependency. Since this has been
both released and backported, Nova introduced a workaround config flag
specifically to get out of that loop, which we set here if needed.
Related-Bug: #1958883
Change-Id: If4820dd4ec7e05ade6eb4a82a328797102704570
Depends-On: https://review.opendev.org/c/openstack/nova/+/826097
* Update grenade from branch 'master'
to 6aae2a9cfa5ebd0762f74eda0a61ba3da6d43b36
- zuul: Add the neutron devstack plugin and enable neutron-trunk service
Depends-On: https://review.opendev.org/c/openstack/devstack/+/811303
Closes-Bug: #1945346
Change-Id: I3326ef7ea5f7340c8dc1e8c21fa977bc1b0ddba6
* Update grenade from branch 'master'
to e830e1d7084630e98bfe46c8e8944c635902f971
- Update the master grenade setting for xena to master upgrade
Change-Id: I614031450d7ac179826d3876d39323a1dd8a35f1
* Update grenade from branch 'master'
to d61a95325b3d052216aa13931c7a6d4a132a5843
- Unblock Gate: create encryption type with right params
Recently we added a check in cinder for cipher algorithm[1]
Currently grenade is not passing cipher when creating an
encrypted type, hence grenade job is failing in glance and cinder gate.
This patch addresses the same by passing the cipher and other
properties.
[1] https://review.opendev.org/c/openstack/cinder/+/800268
Closes-Bug: #1938763
Change-Id: I1eb352deca11916f4db1010a50d15a83e33a61bb
* Update grenade from branch 'master'
to e3cf221066f5a9aa9f760e396353cd6686075730
- Use Block Storage API v3
The openstackclient has defaulted to using the v3 API since 4.0.0 [0],
so there is no reason for grenade to insist on using v2, especially since
v2 is being removed in Xena [1].
[0] a96089ff6d
[1] https://review.opendev.org/c/openstack/cinder/+/792299
Change-Id: Ie558d45374f92f79942b80a9c27fd393ad4f4761
* Update grenade from branch 'master'
to e816fafffc9f7aca466e38d9c218d668f415065e
- setup.cfg: Replace dashes with underscores
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: Id782291f7892b93d8452c836bfdd7f47f8e940ef
* Update grenade from branch 'master'
to c7f6f5d1fa65de982d733ead59b08dbac4339744
- Changed minversion in tox to 3.18.0
The patch bumps min version of tox to 3.18.0 python in order to
replace tox's whitelist_externals by allowlist_externals option:
https://github.com/tox-dev/tox/blob/master/docs/changelog.rst#v3180-2020-07-23
Change-Id: Icea0fbbd3e389800d7fcfdd6ecd11f3b05b2a892
* Update grenade from branch 'master'
to 703926636dcd760f05a44bbb22b3027e95330ccd
- Merge "Remove the old release upgrade extra scripts"
- Remove the old release upgrade extra scripts
Grenade does not support the fast forward upgrade so old release
wise script are not in use in current grenade support.
from-* script in current grenade will only be run via from-$BASE_DEVSTACK_BRANCH
- 1a1f58a69e/inc/upgrade (L92)
and BASE_DEVSTACK_BRANCH will be wallaby for current master grenade or
immediate previous release which means we do not need to keep the older
releases upgrade extra scripts.
Ditto for within-* script.
Change-Id: I66b021f03faa38f976243b7f194454360def215f
* Update grenade from branch 'master'
to af1b4bf7d6a0bc7f8c89ca33bff534d6c776aa2a
- Remove neutron workaround for mitaka and newton
Remove condition for checking if BASE_DEVSTACK_DIR/lib/neutron
exists which was introduced ~5 years ago.
Based on the comment it looks like it can be deleted.
Change-Id: Ice9a709ad75bb5794aebed379fb35f78f0b3422f
* Update grenade from branch 'master'
to 1a1f58a69ee2f5cd01aba347c01b569424861ec0
- Do not suggest Gerrit as source of clones
Make infra-root happy.
Change-Id: Id2b87753236dcc055c8cd9e42e23cf5d3faee4c0
* Update grenade from branch 'master'
to 41364698b275498610506b06960510ea86b2a783
- References to review.openstack.org are replaced with review.opendev.org
Closes-Bug: #1832367
Change-Id: If38096aedac5c528a4feb5f70992afa4e13d6f67
* Update grenade from branch 'master'
to a1b98d6d7a40af3412df0d4c80280cb4240cc3da
- Merge "Make heat and octavia grenade jobs as voting"
- Make heat and octavia grenade jobs as voting
Most of the time, we miss to notice the n-v jobs failure and
end up introducing the regression. grenade-heat (new name grenade-heat-multinode)
and octavia-grenade are voting jobs on their project side so making those to voting
in grenade gate too.
Change-Id: Ic747ac9ddbb21a01e9dc18d8e8ad324d4d7d050d
* Update grenade from branch 'master'
to 47689aa917be7ceb2e864650733a4f9876ca1a0f
- Fix Grenade DSVM Tempest upper constraints
The initial source is too early when GRENADE_USE_EXTERNAL_DEVSTACK
is False (as, e.g., in DSVM [aka devstack-gate, aka legacy] jobs).
The issue was introduced in
I66b5d128c3dbe51289410760ea1cbf7f61c55c2f
fixing the Tempest upper constraints to be properly pinned.
It did not affect Zuul v3 (aka new) jobs.
Also, let's only source the one variable that we need rather than
the whole file.
See https://review.opendev.org/c/openstack/devstack/+/785547
for an example failure.
Closes-Bug: #1923343
Change-Id: If5f14654ab9aee2a140bbfb869b50d63cb289fdf
* Update grenade from branch 'master'
to 1e9fc91401bb753fa88467c837782b1d3abbc52d
- Merge "Configure the Tempest venv upper constraints properly"
- Configure the Tempest venv upper constraints properly
We use Tempest master for testing the supported stable
branches, so using master upper constraints works fine for
such master or stable branch testing, but when we need to
use old Tempest in the below cases then master upper constraints
do not work for Tempest venv:
- Testing Extended Maintenance branch
- Testing py2.7 jobs until stable/train with in-tree tempest plugins
grenade run smoke test on old devstack and if old devstack does not
use the master constraints for Tempest then we need to take care of
the same while running the tests too otherwise, it will end up recreating
the Tempest venv and flush the already installed tempest plugins
and their deps.
This commit set the compatible upper constraint
according to TEMPEST_VENV_UPPER_CONSTRAINTS variable, which is
what used in devstack while creating the Tempest venv and install
tempest plugins in that venv.
Closes-Bug: 1922597
Change-Id: I66b5d128c3dbe51289410760ea1cbf7f61c55c2f
* Update grenade from branch 'master'
to 106a5a2af24154fe6e05a0e241891c3b1dce5403
- Update the master grenade setting for wallaby to master upgrade
Change-Id: I31b218ec4b50b0419aede4cfffdbd7e669d1ac52
* Update grenade from branch 'master'
to 08199218df99ead17d7c34256ed0969b8ae3b3af
- Update min tox version to 2.0
To avoid "unkown environment variable 'TOX_CONSTRAINTS_FILE'"
error, tox needs to be >=2.0.
Closes-Bug: #1801484
Change-Id: Ia22d544297578c1fe3d2efa5dcc944ac1db026a9
* Update grenade from branch 'master'
to 9c729d15fc2933cdf1f81863fb22d855ae6c8d8a
- Switch the grenade job to focal
Victoria only supports focal, so the upgrade from victoria
(starting from victoria+1) should use focal.
This patch should not be backported to victoria, because the
upgrades from ussuri still need to use bionic.
In order to make it work on focal:
- do not fail if ebtables does not contain the broute table
(which happens when it is based on nft);
- when the swift loopback image is remounted on upgrade,
do not use the nobarrier option, which was removed
with the 4.19 kernel. See also the corresponding change
in devstack: I6871a7765e3e04122d8d546f43d36bb8415383fc
Change-Id: If57c54828baf4e250ad08fdd95351490010e1b41
Zuul
yatinkarel