This is fixed in 0.7.9.
** 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/1611074
Title:
Reformatting of ephemeral drive fails on
This is fixed in cloud-init 0.7.9.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611074
Title:
Reformatting of ephemeral drive fails on resize of Azure VM
To manage notifications about this bug
This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.10.1
---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/cloud-init.templates: enable DigitalOcean by default [Ben Howard]
* debian/cloud-init.postinst: update
I've verified this on yakkety as shown in description, using:
smoser@smoser1219y:~$ dpkg-query --show cloud-init
cloud-init 0.7.8-49-g9e904bb-0ubuntu1~16.10.1
smoser@smoser1219y:~$ cat /etc/cloud/build.info
build_name: server
serial: 20161214
** Tags removed: verification-needed
** Tags
** Changed in: cloud-init (Ubuntu Yakkety)
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/1611074
Title:
Reformatting of ephemeral drive fails on resize of Azure
Hello Paul, or anyone else affected,
Accepted cloud-init into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.8-49-g9e904bb-0ubuntu1~16.10.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.1
---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
* debian/cloud-init.postinst: update /etc/fstab on Azure to fix
future resize operations. (LP: #1611074)
*
** Description changed:
=== Begin SRU Template ===
[Impact]
In some cases, cloud-init writes entries to /etc/fstab, and on azure it will
even format a disk for mounting and then write the entry for that 'ephemeral'
disk there.
A supported operation on Azure is to "resize" the
Thanks Scott, Steve, and Paul for driving a fix that will help everyone!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611074
Title:
Reformatting of ephemeral drive fails on resize of Azure VM
To
Thanks for the fix, Scott! Thanks for testing and confirming, Matt!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611074
Title:
Reformatting of ephemeral drive fails on resize of Azure VM
To
I've marked verification done based on Matt's comment above.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611074
Title:
I tested this latest fix and it looks good to me. The post-install fix
seems to work and after multiple resizes I still see /mnt coming back as
ext4
-> Pre-install
$ dpkg -l | grep 'cloudinit '
ii cloud-init 0.7.8-1-g3705bb5-0ubuntu1~16.04.3 all
Init scripts for
Hello Paul, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-init/0.7.8-49
-g9e904bb-0ubuntu1~16.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this
This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1
---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1) zesty; urgency=medium
* debian/cloud-init.postinst: update /etc/fstab on Azure to fix
future resize operations. (LP: #1611074)
* New upstream snapshot.
-
I've just uploaded this to zesty and to xenial-proposed.
The changes can be seen
https://git.launchpad.net/cloud-init/commit/?id=9e904bbc3336b96475bfd00fb3bf1262ae4de49f
There was also a change made to packaging so that on upgrade we will update
/etc/fstab
on the ephemeral disk to include
I've uploaded again to my ppa, 0.7.8-53-g902745d-1~bddeb should build there
sometime soon.
I've been testing that with my quick hack of formatting /dev/sdb1 to ntfs and
rebooting,
(go-format.sh: http://paste.ubuntu.com/23492436/) and so far it is looking
reasonable.
I expect to test tomorrow
I have put up a merge proposal at
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/311205
The plan there seems sane, we will now wait in the Azure datasource for
the azure disk resource to appear. Paul told me that all azure instances
will have an ephemeral disk, so waiting
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/311205
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611074
Title:
Reformatting of ephemeral drive
Thanks Scott for the thorough explanation.
To answer your question: I don't know that there is any such property.
I'm asking around to see if there is, but let's assume 'no' for now.
Aside from resize, we run into the same situation after a VM needs to be
moved to another node. In that case, the
Paul,
A long winded comment, please stick with me. Please try to answer these
first:
Question 1.) Is there a way to definitive/declaritive way to determine
that an instance has been resized? I'd hope for something kind of
like an insnance id, like a "size-id". Basically, we need a way to
Turns out it's cloud-config.service (not cloud-init.service) that does
the mkfs:
paulmey@testvm3:~$ journalctl -b -ojson|jq
'select(.MESSAGE|contains("mkfs"))|._SYSTEMD_UNIT'
"cloud-config.service"
"cloud-config.service"
"cloud-config.service"
"cloud-config.service"
"cloud-config.service"
I
Agree with Paul, in my testing x-system.after makes no difference.
Removing ntfs-3g and blocking the ntfs kernel module are the only things
that are working for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That can't be it... systemd.mount man page says:
x-systemd.requires=
Configures a Requires= and an After= dependency between the created
mount unit and another systemd unit, such as a device or mount unit.
--
You received this bug notification because you are a member of Ubuntu
So I tried another time, this time paying attention to fstab in between
steps. I created a machine and updated cloud-init to
0.7.8-47-gb6561a1-0u.
$ mount|grep sdb ; grep mnt /etc/fstab
/dev/sdb1 on /mnt type ext4 (rw,relatime,data=ordered)
/dev/disk/cloud/azure_resource-part1/mntauto
Attaching logs from my repro as well. I did (patch -> reboot -> resize).
The included fstab is after resize, I'll check the state of fstab at
intermediary steps as well.
** Attachment added: "logs.tar.gz"
At the moment, I'm hoping the issue really stems from this being an upgrade,
and that a new instance that already had the newer version would be OK. What I
believe is happening is:
a.) old cloud-init on first boot writes /etc/fstab for the resource disk with
something like:
** Attachment added: "log repro with 0.7.8-47-gb6561a1-0u"
https://bugs.launchpad.net/cloud-init/+bug/1611074/+attachment/4778323/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Paul, can you attach your full cloud-init.log from that boot above?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611074
Title:
Reformatting of ephemeral drive fails on resize of Azure VM
To
I tested 0.7.8-47-gb6561a1-0ubuntu1~16.04.1 and it did not fix this bug
yet:
Nov 16 20:09:18 testvm [CLOUDINIT] cc_disk_setup.py[DEBUG]: Device /dev/sdb1
has Temporary Storage ntfs
Nov 16 20:09:18 testvm [CLOUDINIT] cc_disk_setup.py[DEBUG]: Device /dev/sdb1 is
cleared for formating
Nov 16
Hello Paul, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.8-47-gb6561a1-0ubuntu1~16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
** Description changed:
=== Begin SRU Template ===
[Impact]
In some cases, cloud-init writes entries to /etc/fstab, and on azure it will
even format a disk for mounting and then write the entry for that 'ephemeral'
disk there.
A supported operation on Azure is to "resize" the
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a
Hey Scott - I see that the version you were waiting for to clear has
landed. Do you have an ETA on when the this change will hit -proposed?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
now that bug 1629868 is understood (duped to bug 1629797) we can reasonably
safely move this back to xenial. The issue is also not relevant for ubuntu on
xenial, because resolved is not used there.
There is a release of cloud-init currently in -proposed
(0.7.8-1-g3705bb5-0ubuntu1~16.04.3)
This can / will go back to xenial the next time we sync cloud-init back to
xenial.
bug 1629868 seems like it is related, so I would hold off on an SRU to xenial
until that is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-init
Status: Confirmed => Fix Committed
** Description changed:
=== Begin SRU Template ===
- [Impact]
+ [Impact]
In some cases, cloud-init writes entries to /etc/fstab, and on azure it will
even format a disk for mounting and then write the entry for that
I tested http://archive.ubuntu.com/ubuntu/pool/main/c/cloud-init/cloud-
init_0.7.8-3-g80f5ec4-0ubuntu1_all.deb on 16.04 on Azure and it seems to
work well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Scott - wanted to confirm that this will be SRU'd back to Xenial. Also,
this is seen on Trusty, can it be backported to Trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611074
Title:
This bug was fixed in the package cloud-init - 0.7.8-3-g80f5ec4-0ubuntu1
---
cloud-init (0.7.8-3-g80f5ec4-0ubuntu1) yakkety; urgency=medium
* New upstream snapshot.
- Adjust mounts and disk configuration for systemd. (LP: #1611074)
- dmidecode: run dmidecode only on i?86 or
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ In some cases, cloud-init writes entries to /etc/fstab, and on azure it will
+ even format a disk for mounting and then write the entry for that 'ephemeral'
+ disk there.
+
+ A supported operation on Azure is to "resize" the
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/306145
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611074
Title:
Reformatting of ephemeral drive
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification
Summary from IRC:
- Add "x-systemd.requires=cloud-init.service" mount flag to fstab if [ -d
/run/systemd/system ] (mountall chokes on unknown options, argh)
- Make sure cloud-init calls "mount" on a newly written mount point, so that
it is mounted when later services start
- Mark them as
Dan, thanks for the recreate description.
I'd never been aware of 'quick-create'. I'd built another wrapper around the
azure cli to do something similar. https://gist.github.com/smoser/5806147
I think that the crux of the issue here is in the change to systemd we
do not block mounts from
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611074
Title:
Reformatting of ephemeral drive fails on resize
Hi Dan,
Thanks for checking this out. Basically just create a 16.04 VM and
resize it (e.g. from D1 to D2). Look at mount/blkid ouput in between and
after to see the difference:
azure config mode arm
azure vm quick-create bug1611074 reprovm centralus linux
Hi Paul,
Could you give me steps that I can follow to reproduce this issue
(ideally using the Azure CLI)? That'll make it easier for us to test
fixes.
Thanks,
Dan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: cloud-init
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/1611074
Title:
Reformatting of ephemeral drive fails on resize of Azure VM
To
49 matches
Mail list logo
