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
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)
Cinder and cinderclient assumes an attachment create request will always contain instance_uuid. This is not true when glance calls cinder for attachment in glance cinder configuration. This patch (along with the cinder patch) make the instance_uuid optional and allow glance to do attachments without passing instance_uuid. Change-Id: Ifbaca4aa87d890bc5130069638d42665b914b378 (cherry picked from commit d714249ca9e95297f5e53c9dcc0af9ba58d0ab6d)
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 Change-Id: I2e2aa24e1592b66b287c84eda97b5079c40a36ec (cherry picked from commit b891c9980f316bd603a9f1429eebad41adf43825)
Specifying specific nodes for these jobs was a holdover from ussuri. For wallaby and victoria, py36 and py38 should be available on all nodes, so we can just use the default. original commit message: Run functional job on Ubuntu Focal Devstack is planning to remove the Ubuntu Bionic support. - https://review.opendev.org/c/openstack/devstack/+/788754 Before that we need to switch Bionic job to focal. devstack-tox-functional define the latest nodeset which is single node focal currently so removing nodeset setting from python-cinderclient functional jobs. Change-Id: Ibbbfb20c86bb2ea0d3d74f6a6a1bc913874f67ad (cherry picked from commit f54b873ca3f9900e17b42f3600a20a36abe2b1a7)
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: I2872eee0bd43dcef75a1508d7f707823fb6eccfa
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/wallaby branch, tests will continue to use the upper-constraints list on master. Change-Id: I589decfa42329da00789cb2021e0a62c911a80ee
Change-Id: Iaffb8d63a7ea933faf92fed87247bd9cf96fdad1