| 2015-11-09 15:28:30 |
Ben Howard |
bug |
|
|
added bug |
| 2015-11-09 15:29:30 |
Ben Howard |
affects |
ubuntu |
cloud-init (Ubuntu) |
|
| 2015-11-09 15:29:37 |
Ben Howard |
nominated for series |
|
Ubuntu Xenial |
|
| 2015-11-09 15:29:37 |
Ben Howard |
bug task added |
|
cloud-init (Ubuntu Xenial) |
|
| 2015-11-09 15:29:37 |
Ben Howard |
nominated for series |
|
Ubuntu Wily |
|
| 2015-11-09 15:29:37 |
Ben Howard |
bug task added |
|
cloud-init (Ubuntu Wily) |
|
| 2015-11-09 16:40:31 |
Scott Moser |
description |
Snapshotted instances may fail to boot due to a change in udev in 15.10. Starting with Ubuntu 15.10, "nobootwait" != "nofail". |
Snapshotted instances may fail to boot due to a change in udev in 15.10. Starting with Ubuntu 15.10, "nobootwait" != "nofail".
For reference, Ubuntu's systemd had a patch that accepted nobootwait [1], but that was dropped in 15.10. discussed some in ubuntu-devel at [2]
--
[1] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu&id=8fbf6c7e671c663190eae8a63b158e686c3d41fa
[2] http://irclogs.ubuntu.com/2015/11/09/%23ubuntu-devel.html#t13:34 |
|
| 2015-11-09 16:43:06 |
Scott Moser |
cloud-init (Ubuntu Wily): importance |
Undecided |
High |
|
| 2015-11-09 16:43:08 |
Scott Moser |
cloud-init (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2015-11-09 23:40:06 |
Ben Howard |
cloud-init (Ubuntu Xenial): assignee |
|
Ben Howard (utlemming) |
|
| 2015-11-09 23:40:10 |
Ben Howard |
cloud-init (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2015-11-09 23:40:13 |
Ben Howard |
cloud-init (Ubuntu Wily): status |
New |
In Progress |
|
| 2015-11-09 23:40:17 |
Ben Howard |
cloud-init (Ubuntu Xenial): status |
Confirmed |
In Progress |
|
| 2015-11-09 23:43:20 |
Ben Howard |
branch linked |
|
lp:~utlemming/cloud-init/lp1514485 |
|
| 2015-11-09 23:56:32 |
Ben Howard |
cloud-init (Ubuntu Wily): importance |
High |
Critical |
|
| 2015-11-10 00:02:21 |
Ben Howard |
summary |
cloud-init should use "nofail" instead of "bootwait" |
[SRU] cloud-init should use "nofail" instead of "bootwait" |
|
| 2015-11-10 00:06:53 |
Ben Howard |
description |
Snapshotted instances may fail to boot due to a change in udev in 15.10. Starting with Ubuntu 15.10, "nobootwait" != "nofail".
For reference, Ubuntu's systemd had a patch that accepted nobootwait [1], but that was dropped in 15.10. discussed some in ubuntu-devel at [2]
--
[1] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu&id=8fbf6c7e671c663190eae8a63b158e686c3d41fa
[2] http://irclogs.ubuntu.com/2015/11/09/%23ubuntu-devel.html#t13:34 |
SRU JUSTIFICATION
[IMPACT] Prior to Ubuntu 15.10, the mount option of "nobootwait" == "nofail." However, with Ubuntu 15.10, this is no longer the case. As a result, snapshotted, stopped and restarted, or migrated Cloud instances may fail to boot if the ephemeral device does not match /etc/fstab.
[FIX] Changed the default mount option to "nofail"
[TEST]
1. Boot Ubuntu 15.10 on Azure
2. Upgrade cloud-init to proposed version
3. Confirm that "nobootwait" for the ephemeral device has been changed to "nofail"
4. Shutdown instance
5. Restart instance, confirm it comes up
6. Capture restarted instance
7. Boot captured image
8. Confirm that capture instance came back up
[ORIGINAL REPORT]
Snapshotted instances may fail to boot due to a change in udev in 15.10. Starting with Ubuntu 15.10, "nobootwait" != "nofail".
For reference, Ubuntu's systemd had a patch that accepted nobootwait [1], but that was dropped in 15.10. discussed some in ubuntu-devel at [2]
--
[1] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu&id=8fbf6c7e671c663190eae8a63b158e686c3d41fa
[2] http://irclogs.ubuntu.com/2015/11/09/%23ubuntu-devel.html#t13:34 |
|
| 2015-11-10 00:07:11 |
Ben Howard |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2015-11-10 00:27:47 |
Ben Howard |
cloud-init (Ubuntu Wily): assignee |
|
Ben Howard (utlemming) |
|
| 2015-11-10 01:05:58 |
Ben Howard |
attachment added |
|
Patch candidate for 15.10 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1514485/+attachment/4515824/+files/lp-1514485-wily-deb.diff |
|
| 2015-11-10 17:40:59 |
Ben Howard |
description |
SRU JUSTIFICATION
[IMPACT] Prior to Ubuntu 15.10, the mount option of "nobootwait" == "nofail." However, with Ubuntu 15.10, this is no longer the case. As a result, snapshotted, stopped and restarted, or migrated Cloud instances may fail to boot if the ephemeral device does not match /etc/fstab.
[FIX] Changed the default mount option to "nofail"
[TEST]
1. Boot Ubuntu 15.10 on Azure
2. Upgrade cloud-init to proposed version
3. Confirm that "nobootwait" for the ephemeral device has been changed to "nofail"
4. Shutdown instance
5. Restart instance, confirm it comes up
6. Capture restarted instance
7. Boot captured image
8. Confirm that capture instance came back up
[ORIGINAL REPORT]
Snapshotted instances may fail to boot due to a change in udev in 15.10. Starting with Ubuntu 15.10, "nobootwait" != "nofail".
For reference, Ubuntu's systemd had a patch that accepted nobootwait [1], but that was dropped in 15.10. discussed some in ubuntu-devel at [2]
--
[1] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu&id=8fbf6c7e671c663190eae8a63b158e686c3d41fa
[2] http://irclogs.ubuntu.com/2015/11/09/%23ubuntu-devel.html#t13:34 |
SRU JUSTIFICATION
[IMPACT] Prior to Ubuntu 15.10, the mount option of "nobootwait" == "nofail." However, with Ubuntu 15.10, this is no longer the case. As a result, snapshotted, stopped and restarted, or migrated Cloud instances may fail to boot if the ephemeral device does not match /etc/fstab.
[FIX] Changed the default mount option to "nofail"
[TEST]
1. Boot Ubuntu 15.10 on Azure
2. Upgrade cloud-init to proposed version
3. Run "sed -i 's/nobootwait/nofail/g' /etc/fstab"
4. Shutdown instance
5. Restart instance, confirm it comes up
6. Capture restarted instance
7. Boot captured image
8. Confirm that capture instance came back up
[ORIGINAL REPORT]
Snapshotted instances may fail to boot due to a change in udev in 15.10. Starting with Ubuntu 15.10, "nobootwait" != "nofail".
For reference, Ubuntu's systemd had a patch that accepted nobootwait [1], but that was dropped in 15.10. discussed some in ubuntu-devel at [2]
--
[1] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu&id=8fbf6c7e671c663190eae8a63b158e686c3d41fa
[2] http://irclogs.ubuntu.com/2015/11/09/%23ubuntu-devel.html#t13:34 |
|
| 2015-11-10 18:09:19 |
Stéphane Graber |
cloud-init (Ubuntu Wily): status |
In Progress |
Fix Committed |
|
| 2015-11-10 18:09:21 |
Stéphane Graber |
bug |
|
|
added subscriber SRU Verification |
| 2015-11-10 18:09:24 |
Stéphane Graber |
tags |
|
verification-needed |
|
| 2015-11-10 18:56:54 |
Launchpad Janitor |
cloud-init (Ubuntu Xenial): status |
In Progress |
Fix Released |
|
| 2015-11-10 19:54:55 |
Ben Howard |
tags |
verification-needed |
verification-done |
|
| 2015-11-10 23:27:03 |
Launchpad Janitor |
cloud-init (Ubuntu Wily): status |
Fix Committed |
Fix Released |
|
| 2015-11-10 23:27:07 |
Adam Conrad |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2015-11-18 18:25:21 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/wily/cloud-init |
|
| 2016-03-04 07:40:53 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/xenial/cloud-init/pkg |
|
