| 2019-05-24 19:11:10 |
Balint Reczey |
bug |
|
|
added bug |
| 2019-05-24 19:22:14 |
Balint Reczey |
summary |
Instance may loosw network connectivity after resuming the 2nd time |
Instance may loose network connectivity after resuming the 2nd time |
|
| 2019-05-24 20:06:40 |
Balint Reczey |
description |
[Impact]
* Some hibernated, then started instances don't restore network connectivity keeping the instance unreachable.
[Test Case]
0. Start a ???? 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.
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]
TODO |
[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 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.
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. |
|
| 2019-05-24 20:18:15 |
Launchpad Janitor |
ec2-hibinit-agent (Ubuntu): status |
New |
Fix Released |
|
| 2019-05-24 20:37:59 |
Steve Langasek |
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 a ???? 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.
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. |
[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 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. |
|
| 2019-05-24 20:38:09 |
Steve Langasek |
ec2-hibinit-agent (Ubuntu Disco): status |
New |
Fix Committed |
|
| 2019-05-24 20:38:11 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-05-24 20:38:14 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2019-05-24 20:38:17 |
Steve Langasek |
tags |
|
verification-needed verification-needed-disco |
|
| 2019-05-24 20:41:28 |
Steve Langasek |
ec2-hibinit-agent (Ubuntu Cosmic): status |
New |
Fix Committed |
|
| 2019-05-24 20:41:33 |
Steve Langasek |
tags |
verification-needed verification-needed-disco |
verification-needed verification-needed-cosmic verification-needed-disco |
|
| 2019-05-24 20:48:09 |
Steve Langasek |
ec2-hibinit-agent (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2019-05-24 20:48:14 |
Steve Langasek |
tags |
verification-needed verification-needed-cosmic verification-needed-disco |
verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco |
|
| 2019-05-25 12:37:24 |
Francis Ginther |
tags |
verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco |
id-5c000da0aa62bc2994611bd2 verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco |
|
| 2019-05-27 16:26:33 |
Balint Reczey |
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 a ???? 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. |
[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. |
|
| 2019-06-07 19:42:11 |
Steve Langasek |
ec2-hibinit-agent (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2019-06-07 19:42:16 |
Steve Langasek |
tags |
id-5c000da0aa62bc2994611bd2 verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco |
id-5c000da0aa62bc2994611bd2 verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco verification-needed-xenial |
|
| 2019-06-20 21:10:12 |
Balint Reczey |
tags |
id-5c000da0aa62bc2994611bd2 verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco verification-needed-xenial |
id-5c000da0aa62bc2994611bd2 verification-done-bionic verification-done-xenial verification-needed verification-needed-cosmic verification-needed-disco |
|
| 2019-06-20 21:30:44 |
Brian Murray |
summary |
Instance may loose network connectivity after resuming the 2nd time |
Instance may lose network connectivity after resuming the 2nd time |
|
| 2019-06-20 21:57:29 |
Launchpad Janitor |
ec2-hibinit-agent (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2019-06-20 21:57:33 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-06-20 22:09:13 |
Launchpad Janitor |
ec2-hibinit-agent (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-06-21 12:43:34 |
Balint Reczey |
tags |
id-5c000da0aa62bc2994611bd2 verification-done-bionic verification-done-xenial verification-needed verification-needed-cosmic verification-needed-disco |
id-5c000da0aa62bc2994611bd2 verification-done verification-done-bionic verification-done-cosmic verification-done-disco verification-done-xenial |
|
| 2019-06-24 04:51:50 |
Launchpad Janitor |
ec2-hibinit-agent (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-06-24 09:51:48 |
Launchpad Janitor |
ec2-hibinit-agent (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
