← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1830427] Re: Instance may lose network connectivity after resuming the 2nd time

 

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 <rbalint@xxxxxxxxxx>  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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1830427

Title:
  Instance may lose network connectivity after resuming the 2nd time

Status in ec2-hibinit-agent package in Ubuntu:
  Fix Released
Status in ec2-hibinit-agent source package in Xenial:
  Fix Released
Status in ec2-hibinit-agent source package in Bionic:
  Fix Released
Status in ec2-hibinit-agent source package in Cosmic:
  Fix Committed
Status in ec2-hibinit-agent source package in Disco:
  Fix Released

Bug description:
  [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 an m5.large instance from an encrypted EBS-backed AMI, with
  hibernation enabled.

   1. Install ec2-hibinit-agent

   2. Start a long running process on the instance, like top in screen.

   3. Hibernate, then after it finished start the instance on EC2
  console

   4. Log in to the instance and observe top still running in screen (to
  prove that the instance resumed and had not been restarted).

   5. Hibernate, then after it finished start the instance on EC2
  console

   6. Log in to the instance and observe top still running in screen.
     (This second cycle ensures that hibernation works more than once.)

  [Regression Potential]

   * Restarting systemd-networkd may cause disturbances in complex networking setups, but since the system was hibernated networking was down anyway.
   * The hook in /lib/systemd/system-sleep/ is ran in parallel to other hooks in the same directory and restarting networking may break them. In Bionic the following packages use similar hooks:

   $ apt-file search /lib/systemd/system-sleep/
  atop: /lib/systemd/system-sleep/atop-pm
  battery-stats: /lib/systemd/system-sleep/battery-stats
  ec2-hibinit-agent: /lib/systemd/system-sleep/hibinit-agent
  hdparm: /lib/systemd/system-sleep/hdparm
  lizardfs-chunkserver: /lib/systemd/system-sleep/lizardfs-chunkserver
  tuxonice-userui: /lib/systemd/system-sleep/tuxonice
  unattended-upgrades: /lib/systemd/system-sleep/unattended-upgrades

  Only lizardfs-chunkserver may be affected because it starts lizardfs-
  chunkserver.service on resume but by the description it claims to be
  reliable thus a networking restart is probably tolerated, too. Also it
  has ~50 popcon count in Debian which may not warrant an extensive
  investigation nor adding Breaks: without being sure that it breaks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1830427/+subscriptions