Hi trialotto,
cloud-init has default settings for Azure instances that ensure that the
first partition of the ephemeral disk is formatted as ext4. It does this
by providing default values for disk_setup and fs_setup; you can see
these at http://bazaar.launchpad.net/~cloud-init-dev/cloud-
Steve,
I have just filed https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1411582 regarding the inconstancy of device naming; could you
confirm that I've captured the issue accurately?
Thanks,
Dan
--
You received this bug notification because you are a member of Ubuntu
Server Team,
trialotto, I've just been doing some testing, and I've realised my above
answer is incorrect; this is definitely a problem in how cloud-init's
Azure data source works.
I'm looking in to it now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Actually, I've realised that I was passing in invalid cloud
configuration data. If I have the following in azure-disk.cfg:
#cloud-config
disk_setup:
ephemeral0:
table_type: mbr
layout: [66, 33]
overwrite: True
fs_setup:
- device: ephemeral0.1
filesystem: ext4
Daniel,
I was aware of DataSourceAzure.py and cc_mounts.py and the fact that
built-in config for Azure requires declaration of sdb (and not
ephemeral0). The before mentioned fact is only an inconvenience for
users that would like to declare custom mount points and make the
mistake to use an in
@Daniel,
I just read your latest (two) posts, I was not able to read them while
commenting, my apologies.
The makeswap bug (when using partitions) is very different from the
swap bug and the alias bug.
In short:
- the swap bug can be resolved by sanitizing declarations of form [ swap, x,
x,
@Stephen,
The non-persistence of device names is indeed a bug, even though device
names can be declared by cloud-config settings.
With respect to the Azure Linux Agent, it should be noted that one has
the option to use a standard declaration of device names (and
partitions, if desired), instead
+1 :)
The [ sdb, mount point ] syntax is a bug as well. Device names are
not persistent in Linux and could change, so it is not guaranteed that
the ephemeral disk will be called /dev/sdb. Ideally this should be
auto-detected in cloud-init at runtime (for example, see
DeviceForIdePort() in the
