delta/openstack/python-cinderclient.git, branch stable/victoria

Migrate job from CentOS8 to Bionic

2022-02-10T20:13:43+00:00

CentOS 8 is being removed from CI because of its EOL[1].
CentOS 8 stream is not currently supported by victoria devstack.
Our functional-py36 job is a child of devstack-tox-functional.
So we need to run devstack with py36 on a supported platform.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026621.html

Change-Id: I6d8864905cbfdffa32b02d9ffbc463f30d3ff720

Merge "[stable-only] Add missing classes to cinderclient.v3" into stable/victoria

2021-09-17T16:15:07+00:00

Merge "Unset tempest.lib timeout in functional tests" into stable/victoria

2021-09-17T16:02:04+00:00

[stable-only] Add missing classes to cinderclient.v3

2021-08-31T12:19:26+00:00

The QuotaSet class was never added to cinderclient.v3.quotas, and
the VolumeTransfer class was never added to cinderclient.v3.
volume_transfers.

Note: this fix is proposed directly to the stable branches, as the
issue was fixed differently in master (Xena development) when the
cinderclient.v2 classes were removed by change I335db5c1799e.

Change-Id: Ie00f068d7818e20683a0c242b51027d657382dd4
Closes-bug: #1938451
(cherry picked from commit 579846c7a4446be98763540b1669f39464c2cab8)

Unset tempest.lib timeout in functional tests

2021-08-31T12:18:38+00:00

The test_cli.CinderBackupTests.test_backup_create_and_delete test
is hitting timeout errors in the python-cinderclient-functional-py36
zuul job.  This is happening because it's inheriting the
OS_TEST_TIMEOUT value of 60 from the base testenv, and that value is
being used by the tempest.lib class we inherit from as a timeout for
each test.  This is a problem for test_backup_create_and_delete
because it creates a volume, waits for available, creates a backup,
waits for available, deletes the volume, waits for deletion, deletes
the backup, waits for deletion.

Our functional tests have their own timeout handling, so turn off
the tempest.lib timeout and use ours.  An alternative to turning it
off is to set it at a value that respects our timeout for our longest
test, which would be:
- time-to-available: 120 sec (x2)
- time-to-deleted: 60 sec (x2)
that is, 360 sec.

Change-Id: I33399b4c094af2cc059da6e332f4c0a91e6ab57e
(cherry picked from commit d04ded6a6ff4cc9ba8377a1b025493e939047b2c)
(cherry picked from commit fa00aff41b266f46362b581ac48b4cec1692de71)

Remove skip_missing_interpreters

2021-07-30T18:43:15+00:00

This prevents a job reporting 'success' when the appropriate python
interpreter cannot be found, when actually it didn't run at all.
Also change the default envlist to use generic 'py3' instead of a
specific version which might not be present.

Also change zuul config so the python-cinderclient-functional-py36
job runs on centos-8-stream nodes, where py36 should be available.
And change bindep.txt to specify the correct package name for
centos-8.

Jeremy Stanley has given a more thorough explanation of why this
is a good change:
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014810.html

This isn't a theoretical issue.  If you look at recent
python-cinderclient-functional-py36 job results (for example,
[0]), you'll see that Zuul reported 'success', but on a closer look,
you'll see that no tests were run.

[0] https://zuul.opendev.org/t/openstack/build/1bfc80638086405f8b29905cdd6f71be/log/job-output.txt#25470

Depends-on: https://review.opendev.org/c/openstack/devstack/+/803072

Change-Id: I2e2aa24e1592b66b287c84eda97b5079c40a36ec
(cherry picked from commit b891c9980f316bd603a9f1429eebad41adf43825)
(cherry picked from commit 4c6c3b49b5334518be1b776d32fada394743142f)
changed:
  .zuul.yaml - using centos-8 node

Drop lower-constraints job

2021-04-09T18:38:15+00:00

Running a lower-constraints job is optional in master, and seems
pointless in the stable branches, so drop it.

Additional information here:
http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021204.html

Change-Id: I0311f7076f4640a42f82217f9ddfc13a3907f8a4

Adjust requirements and lower-constraints

2020-12-23T16:59:32+00:00

Conservative changes to get the l-c job passing with the new
pip resolver.

Big changes:
- pytz 2013.6 -> 2015.7 (u-c allows 2020.1)
  * needed for babel
- tempest 17.1.0 -> 24.0.0 (u-c allows 25.0.1)
  * for dulwich (long story)
- urllib3 1.21.1 -> 1.24.1 (u-c allows 1.25.10)
  * for tempest
- oslo.concurrency 3.25.0 -> 3.26.0 (u-c allows 4.3.1)
  * for tempest
- mccabe 0.2.1 -> 0.6.0
  * for flake8

Also added dulwich to test-requirements to narrow down versions
considered by the resolver.

Change-Id: I8bb622c947cada2905e8d756d5a64f08abaeee8d

Update TOX_CONSTRAINTS_FILE for stable/victoria

2020-09-16T18:35:14+00:00

Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.

Until the requirements repository has as stable/victoria branch, tests will
continue to use the upper-constraints list on master.

Change-Id: I1ae3f5147bceb006b014809edd0470eaf3a1783b

Update .gitreview for stable/victoria

2020-09-16T18:35:09+00:00

Change-Id: I9b58b47580b06549cd674fc15f4b88dace13443b