This is fixed in cloud-init 0.7.9.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided => High
** Changed in: cloud-init
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1647708
Title:
Ephemeral disk on xenial is not mounted at boot
Status in cloud-init:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
Fix Released
Status in cloud-init source package in Yakkety:
Confirmed
Bug description:
=== 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1647708/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
