[01:54] <blackboxsw> rharper: know why route -A inet6 has more ip6-localhost/multicast routes listed than 'ip 6 route show'? https://pastebin.ubuntu.com/p/vJD798wDJV/
[01:56] <blackboxsw> https://pastebin.ubuntu.com/p/FfzWrJ6nzB/
[07:55] <dj_drops> Hello all, I am newbie to clout-init but I started to experimenting. Basically everything working as I want - but I have problem with runcmd module. Script is correctly creater under /var/lib/cloud/instance/scripts/runcmd (I have in module simple: touch /tmp/it_works). Even when I run cloud-init single --frequency=always --name=cc_runcmd nothing happens. OS Debian9.4 and cloud-init from debian repo 0.7.9
[14:35] <rharper> blackboxsw: you want ip -6 route list table all
[16:49] <blkadder> Morning all. Is there a way to resize an AWS ec2 volume on launch with cloud-init? I know how to do it via aws cli but was hoping to avoid that.
[16:49] <blkadder> EBS...
[16:49] <blkadder> Sorry
[16:55] <rharper> yeah, it should automatically
[16:56] <rharper> sorry, it resizes root
[16:56] <rharper> lemme look at config, I think it may also find attached EBS as well
[16:58] <blkadder> My use case is that I have a AMI built with a 35GB root partition that I want to change to 250GB on launch for a specific role type if that helps.
[16:58] <rharper> yeah, in cc_growpart
[16:58] <rharper>  http://cloudinit.readthedocs.io/en/latest/topics/modules.html#growpart
[16:58] <blkadder> Cool thx.
[16:58] <rharper> it does root by default, but you can list other devices as well
[16:58] <blkadder> I just want to do root so that's fine.
[16:58] <rharper> cool
[16:59] <rharper> there are restrictions w.r.t how you have your device partition,  is it a single partition ?
[17:00] <rharper> that is the rootfs has to be on the "last" partition before the free space;
[17:00] <blkadder> Yes, but looking at this, it looks like it will only grow the partition to fill space.
[17:00] <blkadder> I need to change the size on launch.
[17:00] <blkadder> Perhaps I need to use the aws cli for that when launching?
[17:00] <rharper> oh, I see, you mean the actual device, not just the file system
[17:01] <blkadder> Yep
[17:01] <rharper> ah, yeah cloud-init doesn't call into to aws cli/api
[17:01] <rharper> I think you can specify that at launch though
[17:01] <blkadder> Ok, let me go figure that part out, thx.
[17:02] <blkadder> Then I can just use growpart for the last bit.
[17:02] <rharper> y
[17:02] <blkadder> ty
[17:58] <powersj> rharper: if I add an invalid key to cloud-config is there suppose to be an error of some sort or is it ignored?
[17:59]  * powersj can't recall the behavior 
[17:59] <rharper> powersj: in some cases we have schema
[17:59] <rharper> so in bionic in the modules where it's enabled, like ntp, it'll throw an exception
[17:59] <powersj> ah that's right!
[17:59] <powersj> ok thanks :)
[17:59] <rharper> in general, if you pass in an unknown key at the top level, you won't see any error
[18:00] <rharper> if you specify an unknown value in sub dicts, also not likely to trip anything up save schema enabled modules
[18:00] <rharper> https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438
[18:00] <rharper> powersj: that's ready for test
[18:00] <rharper> if you feel so inclined
[18:02] <powersj> rharper: thx will be early next week most likly
[18:02] <rharper> sure, no worries
[19:48] <rascal999> I've got a cloud-config script I'd like to use with a VPS but the provider no longer supports cloud-init. Is it possible to install cloud-init and put the user data somewhere and reboot? Distro is Ubuntu
[19:50] <rharper> rascal999: yes, you want to use the NoCloud datatsource
[19:50] <rharper> http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
[19:51] <powersj> rascal999: are you the one who sent mail to the mailing list?
[19:52] <powersj> if I recall he added the limitation of being unable to add a device
[19:52] <rharper> that was VMware stuff
[19:53] <powersj> oh look at that.. my bad
[19:53] <rharper> well, it's somewhat related, the difference was wanting to genernate network config outside of the cloud-init boot process, which we don't currently support
[19:53] <rharper> I've not yet replied to that on list
[19:53] <rharper> it's something that could be added to the cli; just not there today
[19:54] <rharper> somewhat complicated by *when* can you run scripts in your image;
[20:00] <rascal999> rharper: thanks for this I'll have a look
[20:00] <rascal999> powersj: I haven't raised this in mailing list