Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present
Bug #2024900 reported by
Gauthier Jolly
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Committed
|
Medium
|
Tim Gardner | ||
Focal |
Fix Released
|
Medium
|
Tim Gardner | ||
Jammy |
Fix Released
|
Medium
|
Tim Gardner | ||
Kinetic |
Won't Fix
|
Medium
|
Tim Gardner | ||
Lunar |
Fix Released
|
Medium
|
Tim Gardner | ||
Mantic |
Won't Fix
|
Medium
|
Tim Gardner |
Bug Description
SRU Justification
[Impact]
If the daemon is started and the vmbus is not present it will just exit with an error: https:/
Thus, it would make sense to add "ConditionPathE
[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.
Changed in linux (Ubuntu Focal): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux (Ubuntu Jammy): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux (Ubuntu Kinetic): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux (Ubuntu Lunar): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linux (Ubuntu Mantic): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
importance: | Undecided → Medium |
status: | Incomplete → In Progress |
status: | In Progress → Fix Committed |
tags: | added: patch |
Changed in linux (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Kinetic): | |
status: | In Progress → Won't Fix |
Changed in linux (Ubuntu Lunar): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-focal verification-done-jammy verification-done-lunar removed: verification-needed-focal verification-needed-jammy verification-needed-lunar |
tags: |
added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-azure verification-done-focal-linux-bluefield verification-done-focal-linux-ibm verification-done-jammy-linux-aws verification-done-jammy-linux-aws-6.2 verification-done-jammy-linux-azure verification-done-lunar-linux-azure verification-done-lunar-linux-riscv verification-done-lunar-linux-starfive removed: verification-needed-focal-linux-aws-5.15 verification-needed-focal-linux-azure verification-needed-focal-linux-bluefield verification-needed-focal-linux-ibm verification-needed-jammy-linux-aws verification-needed-jammy-linux-aws-6.2 verification-needed-jammy-linux-azure verification-needed-lunar-linux-azure verification-needed-lunar-linux-riscv verification-needed-lunar-linux-starfive |
tags: |
added: verification-done-focal verification-done-jammy removed: verification-needed-focal verification-needed-jammy |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 2024900
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.