I tried verification on Cosmic and Disco, too, but they did not hibernate for
the second time.
Since the contents of _this_ package is the same I suspect a kernel issue but I
need to do more debugging.
Since getting the fix in for Bionic and Xenial is quite urgent I propose
accepting the SRUs
Verified 1.0.0-0ubuntu4~18.04.2 on Bionic:
[ 104.950957] PM: hibernation entry
[ 105.058661] PM: Syncing filesystems ...
[ 105.070422] PM: done.
[ 105.070423] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 105.071662] OOM killer disabled.
[ 105.071811] PM: Marking nosave
Verified ec2-hibinit-agent 1.0.0-0ubuntu4~16.04.2 on Xenial:
[ 195.098817] done.
[ 470.982689] Adding 4095996k swap on /swap-hibinit. Priority:-1 extents:5
across:4382716k SSFS
[ 471.001029] PM: Hibernation mode set to 'platform'
[ 471.089553] PM: Syncing filesystems ... done.
[
Hello Balint, or anyone else affected,
Accepted ec2-hibinit-agent into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ec2
-hibinit-agent/1.0.0-0ubuntu4~16.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing
** Description changed:
[Impact]
* Some hibernated, then started instances don't restore network connectivity
keeping the instance unreachable.
* The fix is restarting systemd-networkd on resume.
[Test Case]
- 0. Start a instance from an encrypted EBS-backed AMI, with
+
** Tags added: id-5c000da0aa62bc2994611bd2
--
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 loose network connectivity after resuming the 2nd time
To manage notifications
Hello Balint, or anyone else affected,
Accepted ec2-hibinit-agent into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ec2
-hibinit-agent/1.0.0-0ubuntu4~18.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello Balint, or anyone else affected,
Accepted ec2-hibinit-agent into disco-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/ec2
-hibinit-agent/1.0.0-0ubuntu4.19.04.0 in a few hours, and then in the
-proposed repository.
Please help us by testing
This bug was fixed in the package ec2-hibinit-agent - 1.0.0-0ubuntu5
---
ec2-hibinit-agent (1.0.0-0ubuntu5) eoan; urgency=medium
* debian/gbp.conf: Fix packaging branch name
* Restart systemd-networkd on resuming from hibernation.
On resume the system sometimes does not
** Description changed:
[Impact]
- * Some hibernated, then started instances don't restore network
- connectivity keeping the instance unreachable.
+ * Some hibernated, then started instances don't restore network connectivity
keeping the instance unreachable.
+ * The fix is restarting
** Summary changed:
- Instance may loosw network connectivity after resuming the 2nd time
+ Instance may loose network connectivity after resuming the 2nd time
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
11 matches
Mail list logo