Targeted refresh enhacements for VM import\rename\migration events #119
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
We need to make sure that we target vm when refreshing after import, rename or migration events. Bug: https://bugzilla.redhat.com/1404357
|
@miq-bot assign @gmcculloug |
|
Checked commit pkliczewski@613ad50 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
|
cc @lfu |
|
@pkliczewski When migrating the Vm we should refresh the cluster as well, don't we? |
|
@borod108 We refresh cluster [1] when we target a vm. The change you mentioned use vm as a target rather than ems. |
|
Migration verified on small env using one vm. |
borod108
approved these changes
May 29, 2017
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.
We need to make sure that we target vm when refreshing after import,
rename or migration events.
Bug:
https://bugzilla.redhat.com/1404357