[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Patricia Gaughen]

** Changed in: cloud-init (Ubuntu Precise)
   Status: Confirmed => Won't Fix

** Changed in: cloud-init
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Amit]

After revisiting the problem, 0.7.8-49 seems to work fine. The problem
was that I didn't de-provision and started the machine again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Amit]

We also experience failure to mount ephemeral disk to /mnt in Yakkety
(both with 0.7.8-15 and 0.7.8-49 prerelease).

Seems like a race condition, can't reproduce 100% of the time.

the /etc/fstab is generated before the symlink /dev/disk/cloud
/azure_resource-part1 and contains:

cat /etc/fstab
/dev/disk/cloud/azure_resource  /mntauto...

cloud-init logs - 
cloud-init[1177]: [CLOUDINIT] cc_mounts.py[DEBUG]: Attempting to determine the 
real name of ephemeral0
cloud-init[1177]: [CLOUDINIT] cc_mounts.py[DEBUG]: Mapped metadata name 
ephemeral0 to /dev/disk/cloud/azure_resource
cloud-init[1177]: [CLOUDINIT] cc_mounts.py[DEBUG]: changed default device 
ephemeral0 => /dev/disk/cloud/azure_resource

change time of relevant files - 
2016-12-12 17:35:43.031397400 + /etc/fstab
2016-12-12 17:35:43.067397400 + /run/systemd/generator/mnt.mount
2016-12-12 17:35:43.175397400 + /dev/disk/cloud/azure_resource -> ../../sdb
2016-12-12 17:35:43.223397400 + /dev/disk/cloud/azure_resource-part1 -> 
../../sdb1


systemctl cat mnt.mount
...
[Mount]
What=/dev/disk/cloud/azure_resource
Where=/mnt
...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Mathew Hodson]

** No longer affects: cloud-init (Ubuntu Xenial)

** No longer affects: cloud-init (Ubuntu Yakkety)

** Changed in: cloud-init (Ubuntu Precise)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.5-0ubuntu1.21

---
cloud-init (0.7.5-0ubuntu1.21) trusty; urgency=medium

  * Microsoft Azure:
- Install udev rules to create /dev/disk/cloud entries for Azure ephemeral
  disk.
- debian/patches/lp-1603222-fix-ephemeral-disk-fstab.patch:
  - Use /dev/disk/cloud entries for ephemeral disk (LP: #1603222)

 -- Daniel Watkins   Fri, 25 Nov 2016
10:12:20 +

** Changed in: cloud-init (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Dan Watkins]

I have built a trusty Azure image using -proposed, and confirmed that
this now behaves as expected.

** Tags removed: verification-needed
** Tags added: verification-done-trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Timo Aaltonen]

Hello Stephen, or anyone else affected,

Accepted cloud-init into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.5-0ubuntu1.21 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: cloud-init (Ubuntu Trusty)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Dan Watkins]

** Description changed:

+ [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
+  * bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Dan Watkins]

** Changed in: cloud-init (Ubuntu Precise)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Dan Watkins]

As suggested to me by smoser in #cloud-init, this doesn't actually
reproduce on xenial and yakkety; I'll focus on fixing it in trusty.

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: Confirmed => Invalid

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Committed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Scott Moser]

This is fixed in commit
 9e904bbc3336b96475bfd00fb3bf1262ae4de49f
https://git.launchpad.net/cloud-init/commit/?id=9e904bbc3336b96475bfd00fb3bf1262ae4de49f

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-init
   Status: In Progress => Fix Committed

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Description changed:

  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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/310411

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Dan Watkins]

** Changed in: cloud-init (Ubuntu)
   Status: Fix Released => Confirmed

** Also affects: cloud-init
   Importance: Undecided
   Status: New

** Changed in: cloud-init
   Status: New => In Progress

** Changed in: cloud-init
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** Changed in: cloud-init (Ubuntu Trusty)
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** No longer affects: cloud-init (Ubuntu Wily)

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Patricia Gaughen]

** Changed in: cloud-init (Ubuntu Wily)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Dan Watkins]

OK, I've given this some thought.  I think we can probably just modify
the default, as udev rules will ensure that it exists.

As we'll be matching udev rules, we'll need to modify it to
/dev/disk/azure/resource in places where we don't ship udev rules with
cloud-init (i.e. trusty), and to /dev/disk/cloud/azure_resource in
places that we do (e.g. xenial and later).

We _could_ backport the cloud-init udev rules to trusty, but I don't
think we need to.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Dan Watkins]

Adding the following snippet to /etc/cloud/cloud.cfg before rebooting
for the first time seems to fix the issue, which supports my analysis.

datasource:
  Azure:
disk_aliases:
  ephemeral0: /dev/disk/azure/resource

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Dan Watkins]

On trusty systems (at least), walinuxagent ships the udev rules to
produce the devices that cloud-init expects to find.  So that isn't the
source of this bug.

Instead, the problem is that the Azure data source defaults to using
/dev/sdb for ephemeral0 ('disk_aliases': {'ephemeral0': '/dev/sdb'} at
[0]).  Iff we detect a _fabric-formatted_ (i.e. NTFS) ephemeral disk,
then the data source updates this default to instead point at that
ephemeral disk (which will, correctly, be /dev/disk/azure/...).  This
happens fine on every first boot, but on subsequent boots, we don't find
a fabric-formatted ephemeral disk (because we reformatted it on first
boot), so we don't update the default, so we end up rewriting the mounts
to point at /dev/sdb.

(I'll give fixing this some thought, and then comment again with
suggestions.)


[0] 
https://git.launchpad.net/cloud-init/tree/cloudinit/sources/DataSourceAzure.py#n57

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Scott Moser]

I think this is a matter of bug 1411582 actually not having been SRU'd 
correctly.
$ lsb_release -sc
trusty
$ dpkg-query --show cloud-init
cloud-init  0.7.5-0ubuntu1.19
$ dpkg -L cloud-init | grep udev
$ dpkg -L cloud-init | grep udev || echo no files named udev
no files named udev


I also checked that the version that was marked as SRU'd in (0.7.5-0ubuntu1.8) 
does not have any udev files.  So it seems that it just never got in, versus 
having regressed since 0.7.5-0ubuntu1.8.

$ wget 
https://launchpad.net/ubuntu/+archive/primary/+files/cloud-init_0.7.5-0ubuntu1.8_all.deb
$ dpkg -c cloud-init_0.7.5-0ubuntu1.8_all.deb | grep udev || echo no files 
named udev
no files named udev

** Also affects: cloud-init (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: High
   Status: Confirmed

** Also affects: cloud-init (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: Confirmed => Fix Released

** No longer affects: cloud-init (Ubuntu Yakkety)

** No longer affects: cloud-init (Ubuntu Xenial)

** Changed in: cloud-init (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: cloud-init (Ubuntu Trusty)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cloud-init (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Patricia Gaughen]

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Stephen A. Zarkos]

I also see these messages in cloud-init.log.  The first set is for the
first provision, and the second is after the first reboot:

[CLOUDINIT] cc_mounts.py[DEBUG]: Attempting to determine the real name of 
ephemeral0
[CLOUDINIT] cc_mounts.py[DEBUG]: Mapped metadata name ephemeral0 to 
/dev/disk/azure/resource
[CLOUDINIT] cc_mounts.py[DEBUG]: changed default device ephemeral0 => 
/dev/disk/azure/resource-part1

[CLOUDINIT] cc_mounts.py[DEBUG]: Mapped metadata name ephemeral0 to /dev/sdb
[CLOUDINIT] cc_mounts.py[DEBUG]: changed default device ephemeral0 => /dev/sdb1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1603222] Re: Azure: incorrect entry in fstab for ephemeral disk

[Stephen A. Zarkos]

Related bug: https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1411582

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603222

Title:
  Azure: incorrect entry in fstab for ephemeral disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1603222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs