In preparation for changes to the cinder API in https://review.openstack.org/#/c/90353/ , we need to make sure volumes
are in the expected state before we can call begin_detaching on it.
Adding this kind of check to the existing two tests would make them
scenario tests really, and also begin and roll detaching are already
tested as part of standard attach and detach scenario tests, plus are
kind of an implementation detail (even though, sadly, exposed as a
public API) and need not be tested by tempest tests.
Reviewed: https:/ /review. openstack. org/90410 /git.openstack. org/cgit/ openstack/ tempest/ commit/ ?id=1ad0f2b8b3f 3959a6a5d031c1a c0b5a82d714e61
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1ad0f2b8b3f3959 a6a5d031c1ac0b5 a82d714e61
Author: Nikola Dipanov <email address hidden>
Date: Mon Apr 28 12:33:12 2014 +0200
Remove {begin, roll}_detaching volume API tests
In preparation for changes to the cinder API in /review. openstack. org/#/c/ 90353/ , we need to make sure volumes
https:/
are in the expected state before we can call begin_detaching on it.
Adding this kind of check to the existing two tests would make them
scenario tests really, and also begin and roll detaching are already
tested as part of standard attach and detach scenario tests, plus are
kind of an implementation detail (even though, sadly, exposed as a
public API) and need not be tested by tempest tests.
Partial-bug: #1302774 0665a04c8ef5512 6a8f27bbf57
Change-Id: I59e88344e83b8c