Restore VM ownership and retirement when migrating #397
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
ghost
force-pushed
the
v2v_preserve_ownership_and_retirement_date
branch
from
69a1d6a
to
c9e1771
Compare
|
Checked commits fabiendupont/manageiq-content@c9e1771~...831fb82 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
|
@miq-bot add-labels transformation, enhancement, gaprindashvili/yes, blocker |
mkanoor
approved these changes
Aug 13, 2018
|
@fdupont-redhat Looks like this PR is built on top of #385, but currently there is no plan to backport PR 385 to Gaprindashvili branch. (I could have backported PR 385 if it was just spec only changes as the PR says, but the PR actually modifies the production code as well as adding specs. In which case, I have to have a blocker BZ targeted for the next G-release to backport). Can you create a separate PR for Gaprindashvili branch? |
simaishi
pushed a commit
that referenced
this pull request
Sep 19, 2018
…d_retirement_date Restore VM ownership and retirement when migrating (cherry picked from commit 836d63c) https://bugzilla.redhat.com/show_bug.cgi?id=1618807
|
Gaprindashvili backport details: |
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.
When a virtual machine is migrated (v2v), the ownership and retirement data are not propagated to the destination VM. This PR implements this feature.
Associated RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1615141