[Hyper-V] VSS and File Copy daemons intermittently fails to start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Groovy |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
We have most reliably reproduced this on a Standard_B1s in Azure in the North Europe region (>80% of the time). Tests in other regions/VM types do not show this failure as often (<1%). We have reproduced this in Xenial, Bionic, Focal, and Groovy. We saw an increase of test failures around a month ago.
From the journal :
Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-
Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-
Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V VSS Protocol Daemon.
Aug 11 09:55:28 ubuntu systemd[1]: hv-vss-
Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-
Aug 11 09:55:28 ubuntu systemd[1]: sys-devices-
Aug 11 09:55:28 ubuntu systemd[1]: Timed out waiting for device sys-devices-
Aug 11 09:55:28 ubuntu systemd[1]: Dependency failed for Hyper-V File Copy Protocol Daemon.
We've seen problems in the past with KVP daemons that looked very similar : https:/
[Test Case]
There two main scenarios that need to be tested:
1. Azure instances:
- Just start an azure instance using our Ubuntu images and check the the status of the hv-vss-daemon and hv-fcopy-daemon services using systemctl.
- If the issue is solved they shouldn't be listed as failed.
2. Local Hyper-V VM:
- Create a local Hyper-V instance and enable the two systemd services if necessary (hv-vss-daemon and hv-fcopy-daemon) and reboot.
- You can change the integration services that are enable to the guest.
1. With desktop integration and the backup feature disabled, the hv-fcopy-daemon and the hv-vss-daemon service, respectively should not be listed as failed.
2. With the same features enabled the services should start without errors.
[Regression Potential]
The major risk with a potential regression is that those systemd service units are shipped by a package produced by our generic kernels and not the linux-azure kernel. So in case of a regression we might need to re-spin the generic kernels.
CVE References
description: | updated |
Changed in systemd (Ubuntu): | |
status: | New → Invalid |
Changed in systemd (Ubuntu Xenial): | |
status: | New → Invalid |
Changed in systemd (Ubuntu Bionic): | |
status: | New → Invalid |
Changed in systemd (Ubuntu Focal): | |
status: | New → Invalid |
Changed in linux (Ubuntu Groovy): | |
status: | Incomplete → In Progress |
Changed in linux (Ubuntu Focal): | |
status: | New → In Progress |
Changed in linux (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in linux (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
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 1891224
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.