Fix spec assuming default zone #297
Merged
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
This container scan test was assuming the EMS was put in the default zone when checking the zone name.
|
cc @Ladas |
|
Checked commit agrare@905845b with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
cben
approved these changes
Oct 24, 2018
cben
added a commit
to cben/manageiq-providers-kubernetes
that referenced
this pull request
Nov 1, 2018
…_zone Fix spec assuming default zone
cben
added a commit
to cben/manageiq-providers-kubernetes
that referenced
this pull request
Nov 1, 2018
…_zone Fix spec assuming default zone
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.
This container scan test was assuming the EMS was put in the default
zone when checking the zone name.
The behavior of the default ext_management_system factory was changed here ManageIQ/manageiq#18118