mbox series

[{bionic,xenial}:linux,0/1] LP:#1820063 - Hyper-V: Fix failed KVP daemon start on first boot of disco VM

Message ID 20191211143509.9729-1-marcelo.cerri@canonical.com
Headers show
Series LP:#1820063 - Hyper-V: Fix failed KVP daemon start on first boot of disco VM | expand

Message

Marcelo Henrique Cerri Dec. 11, 2019, 2:35 p.m. UTC 
BugLink: https://bugs.launchpad.net/bugs/1820063

That's the same fixed submitted by Seth some time ago for Disco. We
need the same fix in Xenial and Bionic as well.

SRU Justification

Impact: The KVP daemon fails to start on first boot due to being started
before the hv_kvp device appears.

Fix: Update the hv-kvp-daemon service file to start the daemon after
device node appears.

Regression Potential: The changes are updates to the hv-kvp-daemon
service file and addition of a udev rule, so the worst case regression
would be that the service does not start. In testing the service did
start as expected.

Test Case: Tested on the bug, see comment #15 for test procedure and
results.

---

Seth Forshee (1):
  UBUNTU: [Packaging] bind hv_kvp_daemon startup to hv_kvp device

 debian/linux-cloud-tools-common.hv-kvp-daemon.service | 3 ++-
 debian/linux-cloud-tools-common.hv-kvp-daemon.udev    | 1 +
 debian/rules.d/3-binary-indep.mk                      | 1 +
 3 files changed, 4 insertions(+), 1 deletion(-)
 create mode 100644 debian/linux-cloud-tools-common.hv-kvp-daemon.udev

Comments

Khalid Elmously Dec. 18, 2019, 4:29 a.m. UTC | #1 
On 2019-12-11 11:35:08 , Marcelo Henrique Cerri wrote:
> BugLink: https://bugs.launchpad.net/bugs/1820063
> 
> That's the same fixed submitted by Seth some time ago for Disco. We
> need the same fix in Xenial and Bionic as well.
> 
> SRU Justification
> 
> Impact: The KVP daemon fails to start on first boot due to being started
> before the hv_kvp device appears.
> 
> Fix: Update the hv-kvp-daemon service file to start the daemon after
> device node appears.
> 
> Regression Potential: The changes are updates to the hv-kvp-daemon
> service file and addition of a udev rule, so the worst case regression
> would be that the service does not start. In testing the service did
> start as expected.
> 
> Test Case: Tested on the bug, see comment #15 for test procedure and
> results.
> 
> ---
> 
> Seth Forshee (1):
>   UBUNTU: [Packaging] bind hv_kvp_daemon startup to hv_kvp device
> 
>  debian/linux-cloud-tools-common.hv-kvp-daemon.service | 3 ++-
>  debian/linux-cloud-tools-common.hv-kvp-daemon.udev    | 1 +
>  debian/rules.d/3-binary-indep.mk                      | 1 +
>  3 files changed, 4 insertions(+), 1 deletion(-)
>  create mode 100644 debian/linux-cloud-tools-common.hv-kvp-daemon.udev
> 
> -- 
> 2.20.1
> 
> 
> -- 
> kernel-team mailing list
> kernel-team@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team