Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transformation - Fix virt-v2v success check #393

Merged

Conversation

ghost
Copy link

@ghost ghost commented Aug 3, 2018

The current approach checks the return_code attribute of the virt-v2v-wrapper state file. However, if the wrapper failed to launch virt-v2v, there no return code. Nonetheless, the failed attribute is a boolean that we can use to properly raise the exception. This PR implements this new method.

Associated RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1564251

@ghost
Copy link
Author

ghost commented Aug 3, 2018

@miq-bot add-labels transformation, gaprindashvili/yes, bug, blocker

@miq-bot
Copy link
Member

miq-bot commented Aug 3, 2018

Checked commit fabiendupont@8412315 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
1 file checked, 0 offenses detected
Everything looks fine. 🍪

@mkanoor mkanoor self-assigned this Aug 3, 2018
@mkanoor mkanoor merged commit 6d3d0a3 into ManageIQ:master Aug 3, 2018
@mkanoor mkanoor added this to the Sprint 92 Ending Aug 13, 2018 milestone Aug 3, 2018
simaishi pushed a commit that referenced this pull request Aug 6, 2018
@simaishi
Copy link
Contributor

simaishi commented Aug 6, 2018

Gaprindashvili backport details:

$ git log -1
commit deab31446d813bfafa3ab62083b5b943f2983b93
Author: Madhu Kanoor <mkanoor@redhat.com>
Date:   Fri Aug 3 11:56:38 2018 -0400

    Merge pull request #393 from fdupont-redhat/v2v_fix_virtv2v_success_check
    
    Transformation - Fix virt-v2v success check
    (cherry picked from commit 6d3d0a31d1938e631637038935394b83ce078a6c)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1610055

@ghost ghost deleted the v2v_fix_virtv2v_success_check branch August 14, 2018 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants