This bug was fixed in the package ec2-hibinit-agent -
1.0.0-0ubuntu4.19.04.1
---------------
ec2-hibinit-agent (1.0.0-0ubuntu4.19.04.1) disco; urgency=medium
* Drop 0007-Match-ACPI-sleep-action-in-a-very-liberal-way.patch.
It turned out LP: #1831103 was responsible for the missing SBTN event
and where it was fixed two events were handled causing two hibernations.
* Call swapoff via systemd-run to avoid the command getting killed on timeout.
Also stop swap after restarting systemd-networkd to recover network
connectivity earlier.
* debian/hibinit-agent.system-sleep: Restart systemd-networkd with --no-block
to finish running the hook faster.
* Drop 0007-Match-ACPI-sleep-action-in-a-very-liberal-way.patch.
It turned out LP: #1831103 was responsible for the missing SBTN event
and where it was fixed two events were handled causing two hibernations.
* Call swapoff via systemd-run to avoid the command getting killed on timeout.
Also stop swap after restarting systemd-networkd to recover network
connectivity earlier.
* debian/hibinit-agent.system-sleep: Restart systemd-networkd with --no-block
to finish running the hook faster.
ec2-hibinit-agent (1.0.0-0ubuntu4.19.04.0) disco; urgency=medium
* Restart systemd-networkd on resuming from hibernation.
On resume the system sometimes does not restore network connections
and this is a way of reliably triggering the restoration. (LP: #1830427)
-- Balint Reczey <rbal...@ubuntu.com> Fri, 07 Jun 2019 16:35:45 +0200
** Changed in: ec2-hibinit-agent (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830427
Title:
Instance may lose network connectivity after resuming the 2nd time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1830427/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
