This was fixed in commit 9e904bbc3336b96475bfd00fb3bf1262ae4de49f
as part of the re-work for getting reliable mounts in Azure.
https://git.launchpad.net/cloud-init/commit/?id=9e904bbc3336b96475bfd00fb3bf1262ae4de49f
--
https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merg
The proposal to merge ~daniel-thewatkins/cloud-init/+git/cloud-init:lp1603222
into cloud-init:master has been updated.
Status: Needs review => Merged
For more details, see:
https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/310411
--
Your team cloud init develop
Yeah, this doesn't change the behaviour if there is no disk, but it does make
it correct if there is one.
(AIUI, there's always an ephemeral disk on Azure, so handling the no-disk
situation is less important.)
--
https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/31
Generally this looks ok, but I dont think we have a path for "I didnt find
anything".
If we just change this and there is ever not a disk, we'll still provide the
alias, i'm not sure if thats a good thing or not (right now in that scenario we
provide one alias, i think this just changes the beh
Dan Watkins has proposed merging
~daniel-thewatkins/cloud-init/+git/cloud-init:lp1603222 into cloud-init:master.
Requested reviews:
cloud init development team (cloud-init-dev)
Related bugs:
Bug #1603222 in cloud-init: "Azure: incorrect entry in fstab for ephemeral
disk"
https://bugs.launc
5 matches
Mail list logo
