Le Thu, Jun 25, 2015 at 03:34:05PM +1000, Andrew Lau a écrit : > > I've just come across the following bug where if an EC2 instance is > launched with an instance store, cloud-init formats /dev/xvdb as an ext3 > filesystem and injects the following line into /etc/fstab > > /dev/xvdb /mnt auto defaults,nobootwait,comment=cloudconfig 0 2 > > However, since the nobootwait option is still unsupported in Debian > (unlike for Ubuntu 14.04), cloud-init will fail when it tries to mount > the newly formatted filesystem
Thanks Andrew for the report. Am I right that the solution would be to add « mount_default_fields: [ None, None, "auto", "defaults,nofail", "0", "2" ] » in one of the configuration files in /etc, as suggested in Launchpad and as done in Fedora ? - https://bugs.launchpad.net/cloud-init/+bug/785542 - http://pkgs.fedoraproject.org/cgit/cloud-init.git/tree/cloud-init-fedora.cfg Have a nice week-end, Charles -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org