-
Notifications
You must be signed in to change notification settings - Fork 898
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
V2V - Collect virt-v2v PID from conversion host in kill_virtv2v #18372
Conversation
f58f079
to
8e5e70f
Compare
@miq-bot add-label transformation, bug, hammer/yes, blocker |
@fdupont-redhat why don't we store that anymore, since |
Because we get the whole state in VMCheckTransformed method. So, that's just an extra retrieval when we need to cleanup the conversion stuff. |
Checked commits fabiendupont/manageiq@8e5e70f~...38a7994 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@fdupont-redhat does the PID change over the course of a |
Since this is a blocker I'll merge but @fdupont-redhat lets look at this refactoring in a follow-up, I'd rather not have to do an extra ssh call before the cancel |
@agree I do agree that it could be cached, as the PID doesn't change once virt-v2v is started. It's a broader discussion about what should be stored in |
V2V - Collect virt-v2v PID from conversion host in kill_virtv2v (cherry picked from commit 526045d) https://bugzilla.redhat.com/show_bug.cgi?id=1672699
Hammer backport details:
|
In the current implementation, we still use the old format of
task.options[:virtv2v_wrapper]
to identify the PID of virt-v2v. The value is alwaysnil
as we don't store it there anymore, which in turns makes the cancellation ineffective. This PR fixes it by callingget_conversion_state
, that gets the state from the conversion host, and thus the PID.Associated RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1666799