** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Yakkety)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Medium => High
** Description changed:
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
+ $ 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
+ 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
+ $ 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
+ $ 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
+ 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
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1647708
Title:
Ephemeral disk on xenial is not mounted at boot
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
Confirmed
Status in cloud-init source package in Yakkety:
Confirmed
Bug 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1647708/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
