flocker acceptance tests DatasetAPITests.test_extra_volume fails

30 views
Skip to first unread message

sheeta...@gmail.com

unread,
Apr 18, 2016, 12:44:48 PM4/18/16
to flocker-users
Hi,

The following test fails for our plugin - 
flocker.acceptance.endtoend.test_dataset.DatasetAPITests.test_extra_volume


 @skip_backend(
        unsupported={backends.GCE},
        reason="The GCE backend does not let you create two volumes with the "
               "same dataset id. When this test is run with GCE the test "
               "fails to create the extra volume, and we do not test the "
               "functionality this test was designed to test.")
 @require_cluster(2)
    def test_extra_volume(self, cluster):


In the flocker storage driver plugin documentation they talk about dataset id as unique and can be used to create volumes. We have used the dataset Id along with a friendly name as our id for the volume.
Our backend does not support creation of volumes with the same dataset id. Are the backends supposed to return the existing dataset if asked to create a volume with the dataset id again ?
Also, the test_extra_volume is skipped for GCE. Can the test be skipped for our backend ?

Thanks,
Sheetal

Shay Berman

unread,
Dec 14, 2016, 3:17:21 PM12/14/16
to flocker-users
I have the same problem in my IBM storage flocker driver.
This test fails in the acceptance test because we cannot create 2 volumes with the same name. 
Can we skip that test for the acceptance?

if so, how can we skip it? is there a way to run the acceptance and provide skip list? or to update the test code directly? what is recommended here?

here is how i execute the acceptance test : 
#> admin/run-acceptance-tests --keep --distribution=centos-7.2 --provider=managed  --config-file=/root/acceptance_config.yml --flocker-version=1.15.0 --dataset-backend=ibm_storage_flocker_driver

Thanks
Shay Berman
Reply all
Reply to author
Forward
0 new messages