[Backport] #4698 Fix npe when migrating vm with volume#4775
[Backport] #4698 Fix npe when migrating vm with volume#4775yadvr merged 1 commit intoapache:4.14from
Conversation
Cherry-pick commit 59fba49 and fix conflict.
weizhouapache
left a comment
There was a problem hiding this comment.
lgtm.
why did not create pr for 4.14 instead of 4.16?
|
@weizhouapache thanks for the review! It was the contributor option sending the changes to the master. I have nothing against their decision. I understand and respect their point of view. Personally, I see the benefit of porting it into 4.14.2 and 4.15.1 and thus proposed this PR. Here is the discussion about it with the contributor point of view. |
@GabrielBrascher thanks for your explanation. |
|
@blueorangutan package |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S] |
|
Packaging result: ✔️ centos7 ✖️ centos8 ✔️ debian. SL-JID 97 |
|
@blueorangutan test |
|
@shwstppr a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests [S] |
|
@blueorangutan package |
|
@GabrielBrascher a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ centos7 ✔️ debian. SL-JID 300 |
|
@blueorangutan test |
|
@shwstppr a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-319)
|
|
@blueorangutan package |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ centos7 ✔️ debian. SL-JID 324 |
|
@blueorangutan test |
|
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-351)
|
Cherry-pick commit 59fba49 and fix conflict. Co-authored-by: Daniel Augusto Veronezi Salvador <38945620+GutoVeronezi@users.noreply.github.com>
Description
PR #4698 was merged at the master (4.16) but it fixes an issue that is also relevant for current LTS versions.
Considering that the port is relatively straight-forward and it can benefit releases 4.14.2.0 and 4.15.1.0, this PR proposes back-porting PR #4698 into 4.14 and later forward it to 4.15.
More details at #4698.