Add specs for storage_hosts that are inaccessible #506
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@miq-bot assign @gmcculloug |
Pull Request Test Coverage Report for Build 2690
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Specs for ManageIQ/manageiq-automation_engine#292.
Since we now have a "... property to the host storage mount information about if a
particular datastore is accessible to the given host or not..." (ManageIQ/manageiq-schema#329) and since we're exposing
writable_storagesto runwritable_accessible_storagesper https://bugzilla.redhat.com/show_bug.cgi?id=1668020#c26 we should test vmware with storages set to inaccessible.