You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
The text was updated successfully, but these errors were encountered: