Comment 52 for bug 1890501
Revision history for this message
| Lee Yarwood (lyarwood) wrote Re: Soft reboot after live-migration reverts instance to original source domain XML (CVE-2020-17376) | #52 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Jeremy, yes I think we can remove the reference to `host-based connections for root and ephemeral disk devices` as Dan is correct, this could potentially impact anything we map through from the host that changes between the source and destination.
Dan, I think Nick is referring to our downstream approach between Queens and Train that will require operators to live migrate instances between el7 and el8 computes to keep workloads active and allow us to upgrade all computes to el8. I agree however that we should just reference live migration and not complicate things by introducing additional upgrade and fast forward upgrade workflows into the description.
Melanie had asked that I try to verify the libvirt < v1.3.4 behaviour as our MIN_LIBVIRT_VERSION in stable/queens and stable/rocky technically allow us to use older versions. However we missed that the only supported distro using these older versions, Ubuntu 16.04 [1], always has the Ubuntu Cloud Archive enabled by devstack that pulls in updated versions of libvirt, QEMU etc.
Melanie, I think this is a dead end tbh, I can't see any deployments using < v1.3.4 in production anymore given the above. Should we leave that for now and just highlight this is for >= v1.3.4 in the impact description?
I have verified that the attached stable/queens patch works against the UCA provided libvirt v3.6.0 FWIW. I'll try to verify the stable/rocky patch shortly as well.
[1] https:/