2016-07-14 22:07:26 |
Stephen A. Zarkos |
bug |
|
|
added bug |
2016-07-14 22:36:59 |
Patricia Gaughen |
cloud-init (Ubuntu): importance |
Undecided |
High |
|
2016-07-20 17:16:45 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
New |
Confirmed |
|
2016-07-22 20:25:35 |
Scott Moser |
nominated for series |
|
Ubuntu Precise |
|
2016-07-22 20:25:35 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Precise) |
|
2016-07-22 20:25:35 |
Scott Moser |
nominated for series |
|
Ubuntu Xenial |
|
2016-07-22 20:25:35 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Xenial) |
|
2016-07-22 20:25:35 |
Scott Moser |
nominated for series |
|
Ubuntu Trusty |
|
2016-07-22 20:25:35 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Trusty) |
|
2016-07-22 20:25:35 |
Scott Moser |
nominated for series |
|
Ubuntu Yakkety |
|
2016-07-22 20:25:35 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Yakkety) |
|
2016-07-22 20:25:35 |
Scott Moser |
nominated for series |
|
Ubuntu Wily |
|
2016-07-22 20:25:35 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Wily) |
|
2016-07-22 20:25:43 |
Scott Moser |
cloud-init (Ubuntu Yakkety): status |
Confirmed |
Fix Released |
|
2016-07-22 20:25:54 |
Scott Moser |
bug task deleted |
cloud-init (Ubuntu Yakkety) |
|
|
2016-07-22 20:26:08 |
Scott Moser |
bug task deleted |
cloud-init (Ubuntu Xenial) |
|
|
2016-07-22 20:26:29 |
Scott Moser |
cloud-init (Ubuntu Trusty): importance |
Undecided |
High |
|
2016-07-22 20:26:29 |
Scott Moser |
cloud-init (Ubuntu Trusty): status |
New |
Confirmed |
|
2016-08-15 13:23:20 |
Patricia Gaughen |
cloud-init (Ubuntu Wily): status |
New |
Won't Fix |
|
2016-11-09 10:02:19 |
Dan Watkins |
cloud-init (Ubuntu): status |
Fix Released |
Confirmed |
|
2016-11-09 10:03:50 |
Dan Watkins |
bug task added |
|
cloud-init |
|
2016-11-09 10:03:56 |
Dan Watkins |
cloud-init: status |
New |
In Progress |
|
2016-11-09 10:03:59 |
Dan Watkins |
cloud-init: assignee |
|
Dan Watkins (daniel-thewatkins) |
|
2016-11-09 10:04:02 |
Dan Watkins |
cloud-init (Ubuntu): assignee |
|
Dan Watkins (daniel-thewatkins) |
|
2016-11-09 10:04:05 |
Dan Watkins |
cloud-init (Ubuntu Trusty): assignee |
|
Dan Watkins (daniel-thewatkins) |
|
2016-11-09 10:04:10 |
Dan Watkins |
bug task deleted |
cloud-init (Ubuntu Wily) |
|
|
2016-11-09 10:05:37 |
Dan Watkins |
nominated for series |
|
Ubuntu Xenial |
|
2016-11-09 10:05:37 |
Dan Watkins |
bug task added |
|
cloud-init (Ubuntu Xenial) |
|
2016-11-09 10:05:37 |
Dan Watkins |
nominated for series |
|
Ubuntu Yakkety |
|
2016-11-09 10:05:37 |
Dan Watkins |
bug task added |
|
cloud-init (Ubuntu Yakkety) |
|
2016-11-09 10:16:25 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/310411 |
|
2016-11-22 17:54:49 |
Scott Moser |
cloud-init (Ubuntu): status |
Confirmed |
Fix Released |
|
2016-11-22 17:54:57 |
Scott Moser |
cloud-init (Ubuntu Xenial): status |
New |
Fix Committed |
|
2016-11-22 17:55:00 |
Scott Moser |
cloud-init (Ubuntu Xenial): importance |
Undecided |
Medium |
|
2016-11-22 17:55:08 |
Scott Moser |
cloud-init: status |
In Progress |
Fix Committed |
|
2016-11-22 17:56:28 |
Scott Moser |
cloud-init (Ubuntu Yakkety): status |
New |
Confirmed |
|
2016-11-22 17:56:31 |
Scott Moser |
cloud-init (Ubuntu Yakkety): importance |
Undecided |
Medium |
|
2016-11-22 17:57:27 |
Scott Moser |
description |
During provisioning cloud-init adds an entry for the ephemeral disk in /etc/fstab. After provisioning this entry is correct and points to "/dev/disk/azure/resource-part1". This symlink is created dynamically by 66-azure-storage.rules.
For some reason after the first reboot cloud-init overwrites the fstab entry and changes the "/dev/disk/azure/resource-part1" to the device name that it points to, i.e. /dev/sdb1. However, this is incorrect since /dev/sd* device names are not persistent.
Repro:
1) Provision an Ubuntu VM on Azure (I tested with 14.04.4)
2) The fstab entry for the ephemeral disk (/mnt) correctly points to "/dev/disk/azure/resource-part1".
3) Reboot the VM (sudo reboot)
4) The fstab entry now incorrectly points to /dev/sdb1 instead of the symlink.
Impact:
There is a chance that the customer's ephemeral disk will not be mounted properly if the device names change after a reboot. |
During provisioning cloud-init adds an entry for the ephemeral disk in /etc/fstab. After provisioning this entry is correct and points to "/dev/disk/azure/resource-part1". This symlink is created dynamically by 66-azure-storage.rules.
For some reason after the first reboot cloud-init overwrites the fstab entry and changes the "/dev/disk/azure/resource-part1" to the device name that it points to, i.e. /dev/sdb1. However, this is incorrect since /dev/sd* device names are not persistent.
Repro:
1) Provision an Ubuntu VM on Azure (I tested with 14.04.4)
2) The fstab entry for the ephemeral disk (/mnt) correctly points to "/dev/disk/azure/resource-part1".
3) Reboot the VM (sudo reboot)
4) The fstab entry now incorrectly points to /dev/sdb1 instead of the symlink.
Impact:
There is a chance that the customer's ephemeral disk will not be mounted properly if the device names change after a reboot.
Related bugs:
* bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM |
|
2016-11-25 10:03:34 |
Dan Watkins |
cloud-init (Ubuntu Yakkety): status |
Confirmed |
Invalid |
|
2016-11-25 10:04:31 |
Dan Watkins |
cloud-init (Ubuntu Xenial): status |
Fix Committed |
Invalid |
|
2016-11-25 10:26:45 |
Dan Watkins |
cloud-init (Ubuntu Precise): status |
New |
Confirmed |
|
2016-11-25 10:48:32 |
Dan Watkins |
description |
During provisioning cloud-init adds an entry for the ephemeral disk in /etc/fstab. After provisioning this entry is correct and points to "/dev/disk/azure/resource-part1". This symlink is created dynamically by 66-azure-storage.rules.
For some reason after the first reboot cloud-init overwrites the fstab entry and changes the "/dev/disk/azure/resource-part1" to the device name that it points to, i.e. /dev/sdb1. However, this is incorrect since /dev/sd* device names are not persistent.
Repro:
1) Provision an Ubuntu VM on Azure (I tested with 14.04.4)
2) The fstab entry for the ephemeral disk (/mnt) correctly points to "/dev/disk/azure/resource-part1".
3) Reboot the VM (sudo reboot)
4) The fstab entry now incorrectly points to /dev/sdb1 instead of the symlink.
Impact:
There is a chance that the customer's ephemeral disk will not be mounted properly if the device names change after a reboot.
Related bugs:
* bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM |
[Impact]
There is a chance that Azure users' ephemeral disks will not be mounted properly if the device names change after a reboot.
[Test Case]
1) Provision an Ubuntu VM on Azure (I tested with 14.04.4)
2) The fstab entry for the ephemeral disk (/mnt) correctly points to /dev/disk/cloud/azure_resource
3) Reboot the VM (sudo reboot)
4) The fstab entry still points to /dev/disk/cloud/azure_resource (and not /dev/sdb)
[Regression Potential]
This introduces new udev rules to the cloud-init package. These will only cause entries to appear on Azure. It also makes a minor change to how cloud-init will write to /etc/fstab on Azure.
Both of these changes will have no impact outside of Azure, and are the intended behaviour on Azure.
[Original Bug Report]
During provisioning cloud-init adds an entry for the ephemeral disk in /etc/fstab. After provisioning this entry is correct and points to "/dev/disk/azure/resource-part1". This symlink is created dynamically by 66-azure-storage.rules.
For some reason after the first reboot cloud-init overwrites the fstab entry and changes the "/dev/disk/azure/resource-part1" to the device name that it points to, i.e. /dev/sdb1. However, this is incorrect since /dev/sd* device names are not persistent.
Repro:
1) Provision an Ubuntu VM on Azure (I tested with 14.04.4)
2) The fstab entry for the ephemeral disk (/mnt) correctly points to "/dev/disk/azure/resource-part1".
3) Reboot the VM (sudo reboot)
4) The fstab entry now incorrectly points to /dev/sdb1 instead of the symlink.
Impact:
There is a chance that the customer's ephemeral disk will not be mounted properly if the device names change after a reboot.
Related bugs:
* bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM |
|
2016-11-25 12:19:55 |
Timo Aaltonen |
cloud-init (Ubuntu Trusty): status |
Confirmed |
Fix Committed |
|
2016-11-25 12:19:57 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2016-11-25 12:20:02 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
2016-11-25 12:20:09 |
Timo Aaltonen |
tags |
|
verification-needed |
|
2016-11-25 16:48:34 |
Dan Watkins |
tags |
verification-needed |
verification-done-trusty |
|
2016-11-30 00:24:45 |
Mathew Hodson |
bug |
|
|
added subscriber Mathew Hodson |
2016-12-07 13:40:19 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
2016-12-07 13:50:24 |
Launchpad Janitor |
cloud-init (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
2016-12-08 02:39:30 |
Mathew Hodson |
bug task deleted |
cloud-init (Ubuntu Xenial) |
|
|
2016-12-08 02:39:37 |
Mathew Hodson |
bug task deleted |
cloud-init (Ubuntu Yakkety) |
|
|
2016-12-08 02:39:43 |
Mathew Hodson |
cloud-init (Ubuntu Precise): importance |
Undecided |
Medium |
|
2016-12-08 02:39:49 |
Mathew Hodson |
removed subscriber Mathew Hodson |
|
|
|
2016-12-14 08:46:10 |
Amit |
bug |
|
|
added subscriber Amit |
2017-06-22 16:22:00 |
Patricia Gaughen |
cloud-init (Ubuntu Precise): status |
Confirmed |
Won't Fix |
|
2017-06-22 16:22:08 |
Patricia Gaughen |
cloud-init: status |
Fix Committed |
Fix Released |
|
2023-05-10 15:18:59 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2693 |
|