| 2016-12-06 12:55:38 |
Dan Watkins |
bug |
|
|
added bug |
| 2016-12-06 12:55:46 |
Dan Watkins |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-12-06 12:55:46 |
Dan Watkins |
bug task added |
|
cloud-init (Ubuntu Xenial) |
|
| 2016-12-07 00:08:49 |
Andrew Spiers |
bug |
|
|
added subscriber Andrew Spiers |
| 2016-12-07 00:08:54 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
New |
Confirmed |
|
| 2016-12-07 00:08:54 |
Launchpad Janitor |
cloud-init (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2016-12-08 16:31:03 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/312841 |
|
| 2016-12-12 03:34:44 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2016-12-13 21:12:01 |
Scott Moser |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-12-13 21:12:01 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Yakkety) |
|
| 2016-12-13 21:12:11 |
Scott Moser |
cloud-init (Ubuntu Yakkety): status |
New |
Confirmed |
|
| 2016-12-13 21:12:14 |
Scott Moser |
cloud-init (Ubuntu Yakkety): importance |
Undecided |
Medium |
|
| 2016-12-13 21:12:20 |
Scott Moser |
cloud-init (Ubuntu Xenial): importance |
Undecided |
Critical |
|
| 2016-12-13 21:12:23 |
Scott Moser |
cloud-init (Ubuntu Yakkety): importance |
Medium |
High |
|
| 2016-12-13 21:14:20 |
Scott Moser |
description |
When I boot the latest xenial Azure image (containing cloud-init 0.7.8-49-g9e904bb-0ubuntu1~16.04.1), the ephemeral disk does not end up mounted (though it is formatted appropriately). Restarting the mnt.mount service does mount it, which suggests there is an issue in the ordering of the services at boot.
$ mount | grep mnt
$ sudo systemctl status mnt.mount
● mnt.mount - /mnt
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: inactive (dead)
Where: /mnt
What: /dev/disk/cloud/azure_resource-part1
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
$ sudo journalctl -u mnt.mount
-- No entries --
$ cat /etc/fstab
# CLOUD_IMG: This file was created/modified by the Cloud Image build process
UUID=6a8554fa-8e1d-4916-ba03-4ca3837feb34 / ext4 defaults,discard 0 0
/dev/disk/cloud/azure_resource-part1 /mnt auto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2
$ sudo systemctl restart mnt.mount
$ mount | grep mnt
/dev/sdb1 on /mnt type ext4 (rw,relatime,data=ordered)
$ ls /mnt/
lost+found
$ sudo systemctl status mnt.mount
● mnt.mount - /mnt
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: active (mounted) since Tue 2016-12-06 12:49:06 UTC; 6s ago
Where: /mnt
What: /dev/sdb1
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 1916 ExecMount=/bin/mount /dev/disk/cloud/azure_resource-part1 /mnt -o defaults,x-systemd.requires=cloud-init.service,comment=cloudconfig (code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 88.0K
CPU: 15ms
Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounting /mnt...
Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounted /mnt. |
When I boot the latest xenial Azure image (containing cloud-init 0.7.8-49-g9e904bb-0ubuntu1~16.04.1), the ephemeral disk does not end up mounted (though it is formatted appropriately). Restarting the mnt.mount service does mount it, which suggests there is an issue in the ordering of the services at boot.
$ mount | grep mnt
$ sudo systemctl status mnt.mount
● mnt.mount - /mnt
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: inactive (dead)
Where: /mnt
What: /dev/disk/cloud/azure_resource-part1
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
$ sudo journalctl -u mnt.mount
-- No entries --
$ cat /etc/fstab
# CLOUD_IMG: This file was created/modified by the Cloud Image build process
UUID=6a8554fa-8e1d-4916-ba03-4ca3837feb34 / ext4 defaults,discard 0 0
/dev/disk/cloud/azure_resource-part1 /mnt auto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2
$ sudo systemctl restart mnt.mount
$ mount | grep mnt
/dev/sdb1 on /mnt type ext4 (rw,relatime,data=ordered)
$ ls /mnt/
lost+found
$ sudo systemctl status mnt.mount
● mnt.mount - /mnt
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: active (mounted) since Tue 2016-12-06 12:49:06 UTC; 6s ago
Where: /mnt
What: /dev/sdb1
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 1916 ExecMount=/bin/mount /dev/disk/cloud/azure_resource-part1 /mnt -o defaults,x-systemd.requires=cloud-init.service,comment=cloudconfig (code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 88.0K
CPU: 15ms
Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounting /mnt...
Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounted /mnt.
Related bugs:
* bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM
* bug 1642383: Unable to configure swap space on ephemeral disk in Azure |
|
| 2016-12-13 22:15:26 |
Scott Moser |
description |
When I boot the latest xenial Azure image (containing cloud-init 0.7.8-49-g9e904bb-0ubuntu1~16.04.1), the ephemeral disk does not end up mounted (though it is formatted appropriately). Restarting the mnt.mount service does mount it, which suggests there is an issue in the ordering of the services at boot.
$ mount | grep mnt
$ sudo systemctl status mnt.mount
● mnt.mount - /mnt
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: inactive (dead)
Where: /mnt
What: /dev/disk/cloud/azure_resource-part1
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
$ sudo journalctl -u mnt.mount
-- No entries --
$ cat /etc/fstab
# CLOUD_IMG: This file was created/modified by the Cloud Image build process
UUID=6a8554fa-8e1d-4916-ba03-4ca3837feb34 / ext4 defaults,discard 0 0
/dev/disk/cloud/azure_resource-part1 /mnt auto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2
$ sudo systemctl restart mnt.mount
$ mount | grep mnt
/dev/sdb1 on /mnt type ext4 (rw,relatime,data=ordered)
$ ls /mnt/
lost+found
$ sudo systemctl status mnt.mount
● mnt.mount - /mnt
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: active (mounted) since Tue 2016-12-06 12:49:06 UTC; 6s ago
Where: /mnt
What: /dev/sdb1
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 1916 ExecMount=/bin/mount /dev/disk/cloud/azure_resource-part1 /mnt -o defaults,x-systemd.requires=cloud-init.service,comment=cloudconfig (code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 88.0K
CPU: 15ms
Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounting /mnt...
Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounted /mnt.
Related bugs:
* bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM
* bug 1642383: Unable to configure swap space on ephemeral disk in Azure |
=== Begin SRU Template ===
[Impact]
An ephemeral disk will not correctly be mounted on /mnt.
This affects Azure and other instances where an ephemeral device is
mounted by default on /mnt. It is recreated in Azure and on OpenStack.
This can be mitigated by either:
1.) mount -a
2.) reboot
[Test Case]
In a correctly functioning image on OpenStack or Azure, you should be
able to:
1.) Launch an instance
2.) ssh into instance and look around
$ awk '$2 == "/mnt" { print $0 }' /etc/fstab
/dev/vdb /mnt auto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2
$ awk '$2 == "/mnt" { print $0 }' /proc/mounts
/dev/vdb /mnt vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
$ df -h /mnt
Filesystem Size Used Avail Use% Mounted on
/dev/vdb 40G 32K 40G 1% /mnt
To check that this is functional with -proposed, after you've seen it failed
3.) enable -proposed and apt-get install cloud-init
4.) clean up and reboot as if fresh:
sudo rm -Rf /var/lib/cloud /var/log/cloud-init
sudo sed -i '/cloudconfig/d' /etc/fstab
sudo reboot
[Regression Potential]
This is a regression caused by bug 1611074, so in addition to the above
test case, we should go through the test cases shown there to see that
those also work.
=== End SRU Template ===
When I boot the latest xenial Azure image (containing cloud-init 0.7.8-49-g9e904bb-0ubuntu1~16.04.1), the ephemeral disk does not end up mounted (though it is formatted appropriately). Restarting the mnt.mount service does mount it, which suggests there is an issue in the ordering of the services at boot.
$ mount | grep mnt
$ sudo systemctl status mnt.mount
● mnt.mount - /mnt
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: inactive (dead)
Where: /mnt
What: /dev/disk/cloud/azure_resource-part1
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
$ sudo journalctl -u mnt.mount
-- No entries --
$ cat /etc/fstab
# CLOUD_IMG: This file was created/modified by the Cloud Image build process
UUID=6a8554fa-8e1d-4916-ba03-4ca3837feb34 / ext4 defaults,discard 0 0
/dev/disk/cloud/azure_resource-part1 /mnt auto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2
$ sudo systemctl restart mnt.mount
$ mount | grep mnt
/dev/sdb1 on /mnt type ext4 (rw,relatime,data=ordered)
$ ls /mnt/
lost+found
$ sudo systemctl status mnt.mount
● mnt.mount - /mnt
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: active (mounted) since Tue 2016-12-06 12:49:06 UTC; 6s ago
Where: /mnt
What: /dev/sdb1
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 1916 ExecMount=/bin/mount /dev/disk/cloud/azure_resource-part1 /mnt -o defaults,x-systemd.requires=cloud-init.service,comment=cloudconfig (code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 88.0K
CPU: 15ms
Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounting /mnt...
Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounted /mnt.
Related bugs:
* bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM
* bug 1642383: Unable to configure swap space on ephemeral disk in Azure |
|
| 2016-12-15 18:18:13 |
Jon Grimm |
bug |
|
|
added subscriber Jon Grimm |
| 2016-12-15 21:50:48 |
Jon Grimm |
cloud-init (Ubuntu Xenial): status |
Confirmed |
In Progress |
|
| 2016-12-20 16:35:54 |
Robie Basak |
cloud-init (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-12-20 16:35:58 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-12-20 16:36:02 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2016-12-20 16:36:10 |
Robie Basak |
tags |
|
verification-needed |
|
| 2016-12-20 18:38:24 |
Scott Moser |
tags |
verification-needed |
verification-done-xenial |
|
| 2016-12-21 01:44:23 |
Patricia Gaughen |
tags |
verification-done-xenial |
verification-done |
|
| 2016-12-21 02:02:23 |
Launchpad Janitor |
cloud-init (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-12-21 02:02:46 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-12-21 14:23:48 |
Christopher Horrell |
bug |
|
|
added subscriber Christopher Horrell |
| 2016-12-23 17:34:37 |
Scott Moser |
bug task added |
|
cloud-init |
|
| 2016-12-23 17:34:55 |
Scott Moser |
cloud-init: importance |
Undecided |
High |
|
| 2016-12-23 17:34:55 |
Scott Moser |
cloud-init: status |
New |
Fix Released |
|
| 2017-01-12 19:48:26 |
Brian Murray |
cloud-init (Ubuntu Yakkety): status |
Confirmed |
Fix Committed |
|
| 2017-01-12 19:48:29 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-01-12 19:48:38 |
Brian Murray |
tags |
verification-done |
|
|
| 2017-01-12 19:48:41 |
Brian Murray |
tags |
|
verification-needed |
|
| 2017-01-20 17:27:50 |
Scott Moser |
tags |
verification-needed |
verification-done |
|
| 2017-01-30 18:18:12 |
Launchpad Janitor |
cloud-init (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2023-05-10 19:08:29 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2781 |
|
