[00:08] no idea, anyone ? what can cause that changing timeout and max_wait for datasource doesn't work [00:09] can you guide me how to debug it ? [08:12] mastier, ? [08:12] what was the question ? [10:41] Hello, I was going through the examples on https://cloudinit.readthedocs.io/en/latest/topics/examples.html [10:42] It seems like https://cloudinit.readthedocs.io/en/latest/topics/examples.html#adjust-mount-points-mounted uses an option called "nobootwait" and mentions that this should be used for volumes that may not be attached at instance boot [10:43] It seems like that's not a valid option for fstab in general and was only supported by certain versions of ubuntu [10:44] The correct option to use is likely "nofail", can the example be changed to reflect that? [10:50] ffledgling: i assume that could be done with a merge request somewhere [10:52] nacc: I think I need to modify the docs folder in https://git.launchpad.net/cloud-init [10:53] But I wanted to confirm that that's not an intentional mention [10:55] ffledgling: fyi, http://unix.stackexchange.com/questions/53456/what-is-the-difference-between-nobootwait-and-nofail-in-fstab [10:56] ffledgling: so you could verify they are semantically the same (and if not, file a diffeent bug :) [10:57] nacc: I saw that question, I can confirm that nobootwait does not work on fedora (which is how I started digging in the first place), and from the comments - "nobootwait is no longer a valid option in Ubuntu 16.04 (as of 2016-07-10 ...)" :) [10:57] I don't think they're semantically the same either [11:02] ffledgling: yeah, makes sense. I would suggest sending a merge request with explanation there and see what the maintainers say [11:06] nacc: Will do === lunarlamp is now known as mariusv [14:39] Hi, I opened up a MR for change to docs - https://code.launchpad.net/~ffledgling/cloud-init/+git/cloud-init-1/+merge/312917 [14:39] I'm not entirely sure who to mark for review, if someone could take a look and give me feedback, that'd be great.