I would reopen and add Affects: Bionic but I don't see a way to do so.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1701222
Title:
[Hyper-V] LIS daemons fail to start
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1701222
Title:
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu)
Status: In Progress =>
Since it requires control of the host, this cannot be done in Azure.
Control of the host is rather restricted there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1701222
The unit entered a failed state, and thus would not automatically started until
failed state clears.
Why does bouncing of the services result in the daemon exiting with an error
condition? Should that particular exit code result in a graceful shutdown of
the service, such that the unit can be
It is possible. I've added a systemd bug task.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
6 matches
Mail list logo
