delta/openstack/python-openstackclient.git/openstackclient/tests/functional/volume/v3/test_volume.py, branch 6.1.0 opendev.org: openstack/python-openstackclient tests: Convert volume tests to use 'parse_output' 2022-11-29T16:21:29+00:00 Stephen Finucane sfinucan@redhat.com 2022-11-08T10:49:24+00:00 686fabef31ee36ec25574ddb086d6e9e3f170045 Change-Id: Iec8ca873f6bc3993e0ba557f68895d9aefb6f9c6 Signed-off-by: Stephen Finucane <sfinucan@redhat.com> 
Change-Id: Iec8ca873f6bc3993e0ba557f68895d9aefb6f9c6
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Fix volume set functional test 2022-01-11T06:24:48+00:00 Dr. Jens Harbott harbott@osism.tech 2022-01-10T18:43:04+00:00 f533dca520127446f2769b88f239799336954833 Sometimes it can happen that when extending a volume it is shown as status "extending" with the original size for a while. Wait for the volume to enter state "available" again before checking the result. Signed-off-by: Dr. Jens Harbott <harbott@osism.tech> Change-Id: Ib70cfa1c241ce94426214c7a05c550213f427caa 
Sometimes it can happen that when extending a volume it is shown as
status "extending" with the original size for a while. Wait for the
volume to enter state "available" again before checking the result.

Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: Ib70cfa1c241ce94426214c7a05c550213f427caa
Create Volume v3 functional tests 2019-11-18T20:47:56+00:00 Dean Troyer dtroyer@gmail.com 2019-11-18T20:44:49+00:00 1c0160c8aa8482958df54e0814023c5eeed0611e Until now-ish Volume v3 has been a pass-through to v2. In order to prepare to make the Volume v3 commands stand-alone copy the v2 functional tests to v3. This is the first of a series of reviews to completely separate Volume v2 and v3 commands. Once these are split we can begin to implement v3 microversion support and/or start using the OpenStack SDK as the REST library. Change-Id: Iefd78d8ef6bb851d7360596337a88ee8f8476767 Signed-off-by: Dean Troyer <dtroyer@gmail.com> 
Until now-ish Volume v3 has been a pass-through to v2.  In order
to prepare to make the Volume v3 commands stand-alone copy the
v2 functional tests to v3.

This is the first of a series of reviews to completely separate
Volume v2 and v3 commands.  Once these are split we can begin to
implement v3 microversion support and/or start using the
OpenStack SDK as the REST library.

Change-Id: Iefd78d8ef6bb851d7360596337a88ee8f8476767
Signed-off-by: Dean Troyer <dtroyer@gmail.com>
Clean up the changes of os.environ in functional tests 2017-07-20T16:39:32+00:00 Rui Chen chenrui.momo@gmail.com 2017-06-06T13:03:33+00:00 f1d32dbe9b6f5f2e47853b9969483fa841e451f4 Use fixtures to restore the API version changes of os.environ in each functional tests, aims to avoid the following test cases failing in unexpected context. And make sure setUpClass/tearDownClass call super class's corresponding methods first. Change-Id: Ie248fe9d3a9e25f1b076c9f2c363200f29a83817 Closes-Bug: #1696080 
Use fixtures to restore the API version changes of os.environ
in each functional tests, aims to avoid the following test cases
failing in unexpected context.

And make sure setUpClass/tearDownClass call super class's
corresponding methods first.

Change-Id: Ie248fe9d3a9e25f1b076c9f2c363200f29a83817
Closes-Bug: #1696080
Add Cinder v3 client support for volumes 2017-02-20T20:37:36+00:00 Justin A Wilson justin.wilson@intel.com 2016-09-30T20:44:26+00:00 4d5f2c3925068fe49748e05a47c5c9c7e7999b3c Initial Cinder v3 support Change-Id: Idd5074832e80697ed0671f06d3291dfd92dbfb08 
Initial Cinder v3 support

Change-Id: Idd5074832e80697ed0671f06d3291dfd92dbfb08