Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

[Test]VerifyAttachedStatus() assumes only one volume with a given name can exist in the system fails verification #1566

Closed
govint opened this issue Jul 9, 2017 · 1 comment

Comments

@govint
Copy link
Contributor

govint commented Jul 9, 2017

VerifyAttachedStatus() is making the assumption that only one volume can exist across datastores with a particular name. The result is verification fails and the CI errors out for a test thats using volumes with the same name on multiple datastores. VerifyAttachedStatus() should take the datastore as a parameter and verify the specific volume alone.

@govint govint self-assigned this Jul 12, 2017
@tusharnt tusharnt added P1 and removed P0 labels Jul 17, 2017
@tusharnt tusharnt added this to the Future milestone Jul 17, 2017
@tusharnt tusharnt removed the kind/bug label Jul 17, 2017
@govint govint changed the title VerifyAttachedStatus() assumes only one volume with a given name can exist in the system fails verification [Test]VerifyAttachedStatus() assumes only one volume with a given name can exist in the system fails verification Jul 26, 2017
@govint
Copy link
Contributor Author

govint commented Sep 13, 2017

Closing, this is only for e2e test code thats not failing presently and the datastore configurations we use for the test doesn't require fixing this in anyway.

@govint govint closed this as completed Sep 13, 2017
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

No branches or pull requests

2 participants