Public bug reported: SRU Justification
[Impact] Re-opening for Noble, Oracular, and current development cycle (Plucky) as this appears to have accidentally been dropped. * Previous LP bug: https://bugs.launchpad.net/bugs/2024900 * Commit from Jammy release: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/debian/linux-cloud-tools- common.hv-kvp-daemon.service?h=master- next&id=7da99ea3a1a745f6fd0c8632ef89573437888af6 * Previous mailing list discussion: https://lists.ubuntu.com/archives/kernel-team/2023-June/140646.html Following description copied from original LP bug: If the daemon is started and the vmbus is not present it will just exit with an error: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424 Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools-common.hv-kvp-daemon.service to prevent systemd from starting the daemon if the device is not there. [Test Plan] Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that hv-kvp-daemon is running. Start a non-Azure cloud instance and check that hv-kvp-daemon is not running. [Regression potential] Its possible that kv-hvp-daemon is not started when it should be. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** Affects: linux (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** Description changed: SRU Justification [Impact] Re-opening for Noble, Oracular, and current development cycle (Plucky) as this appears to have accidentally been dropped. - * Previous LP bug: #2024900 + * Previous LP bug: https://bugs.launchpad.net/bugs/2024900 * Patch from latest release (Lunar): https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/lunar/commit/debian/linux-cloud-tools- common.hv-kvp-daemon.service?h=master- next&id=9bc14a92cd7d4355024bebc0984b6bb6d8f721a8 * Previous mailing list discussion: https://lists.ubuntu.com/archives/kernel-team/2023-June/140646.html Following description copied from original LP bug: If the daemon is started and the vmbus is not present it will just exit with an error: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424 Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools-common.hv-kvp-daemon.service to prevent systemd from starting the daemon if the device is not there. [Test Plan] Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that hv-kvp-daemon is running. Start a non-Azure cloud instance and check that hv-kvp-daemon is not running. [Regression potential] Its possible that kv-hvp-daemon is not started when it should be. ** Description changed: SRU Justification [Impact] Re-opening for Noble, Oracular, and current development cycle (Plucky) as this appears to have accidentally been dropped. * Previous LP bug: https://bugs.launchpad.net/bugs/2024900 - * Patch from latest release (Lunar): https://git.launchpad.net/~ubuntu- - kernel/ubuntu/+source/linux/+git/lunar/commit/debian/linux-cloud-tools- + * Commit from Jammy release: https://git.launchpad.net/~ubuntu- + kernel/ubuntu/+source/linux/+git/jammy/commit/debian/linux-cloud-tools- common.hv-kvp-daemon.service?h=master- - next&id=9bc14a92cd7d4355024bebc0984b6bb6d8f721a8 + next&id=7da99ea3a1a745f6fd0c8632ef89573437888af6 * Previous mailing list discussion: https://lists.ubuntu.com/archives/kernel-team/2023-June/140646.html Following description copied from original LP bug: If the daemon is started and the vmbus is not present it will just exit with an error: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424 Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools-common.hv-kvp-daemon.service to prevent systemd from starting the daemon if the device is not there. [Test Plan] Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that hv-kvp-daemon is running. Start a non-Azure cloud instance and check that hv-kvp-daemon is not running. [Regression potential] Its possible that kv-hvp-daemon is not started when it should be. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2091744 Title: When /dev/vmbus/hv_kvp is not present, disable hv-kvp-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
