[00:22]  * smoser summons the all knowing python hero
[00:22] <smoser> pip install --pre bzr-fastimport==0.11.0.final.0
[00:22] <smoser> Collecting bzr-fastimport==0.11.0.final.0
[00:22] <smoser>   Could not find a version that satisfies the requirement bzr-fastimport==0.11.0.final.0 (from versions: )
[00:22] <smoser> No matching distribution found for bzr-fastimport==0.11.0.final.0
[00:22] <smoser> yet ...
[00:22] <smoser> https://pypi.python.org/pypi/bzr-fastimport
[00:22] <smoser> so what vifes ?
[00:25] <smoser> gives even
[00:28] <smoser> seems taht there is only a pip record, no data
[00:29] <nacc> smoser: yeah, usually the pypi page has more info
[00:29] <smoser> the url there is bad, 404
[00:30] <nacc> smoser: ah that could cause it to fail to fetch, maybe
[15:54] <smoser> blackboxsw: http://paste.ubuntu.com/25831034/
[17:23]  * powersj is running a full nocloud-kvm run on his branch after changing /tmp to /var/tmp and then will push
[17:55] <powersj> blackboxsw: https://paste.ubuntu.com/25831640/
[17:57] <powersj> blackboxsw: am I missing a commit? I rebased on master and ran into those?
[18:08] <blackboxsw> powersj: yeah that should be fixed to be a debug msg
[18:09] <powersj> blackboxsw: should be fixed as in, already in master?
[18:09] <blackboxsw> yeah
[18:09] <blackboxsw> checking rev
[18:10] <blackboxsw> 41152f10ddbd8681cdac44b408038a4f23ab02df powersj
[18:10] <blackboxsw> oct 17th
[18:10] <blackboxsw> stale pyc files in your tree?
[18:17] <powersj> smoser: "With regard to "not logged in as root by default", that is kind of wrong."
[18:17] <powersj> only lxd and digital-ocean use a root user as default, aws, gce, azure, kvm cloud-images else assumes some sort of generic user, whether that is ubuntu or otherwise
[18:18] <powersj> help me understand what you are looking for with that comment
[18:23] <powersj> blackboxsw: ... realized what I was doing wrong... not using in tree cloud-init, so cloud image has old version of cloud-init
[18:23] <powersj> sigh my bad
[19:28] <Sargun> Do I have to do anything to get cloud-init to nudge netplan to reload
[19:34] <smoser> Sargun: what have youd one that made you think netplan needed nudging ?
[19:35] <blackboxsw> I thought "it just worked"™    cloud-init calls "netplan generate" to put appropriate configs in the right place at the right time.
[19:37] <rharper> there is at least one bug where netplan bug related
[19:37] <rharper> https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564
[20:38] <Sargun> smoser: Using the following cloudinit: https://gist.github.com/sargun/7152cac024896cb73152fc35bef2fb17
[20:38] <Sargun> using ec2 user metadata
[20:39] <Sargun> On Ubuntu 17.04
[20:39] <smoser> Sargun: yu're hoping to get ipv6 dhcp ?
[20:40] <smoser> you'd have to put that network config inside the image
[20:40] <smoser> you can't feed it in from user-data
[20:40] <smoser> that it reads over the network
[20:40] <smoser> that said, 17.10 should get you wahat you want there.
[20:40] <Sargun> Well, I was hoping it'd read it, and realize that it needs to restart.
[20:40] <Sargun> 17.10 AMI?
[20:42] <Sargun> Does 17.10 automatically do dhcp6?
[20:47] <smoser> Sargun: at this point that doesnt work.
[20:47] <smoser> but on 17.10 it should correclty notice that you have ipv6 enabled
[20:47] <smoser> and will then do the right thing
[20:48] <smoser> and that is actually in process of sru to 17.04 also
[20:49] <Sargun> Tried 17.10
[20:49] <Sargun> It only configured V6 and didn't do v4
[20:49] <Sargun> I need dual-stack
[20:50] <smoser> Sargun: hm.
[20:50] <smoser> it should definitely do v4
[20:50] <smoser> can you give more details on taht ?
[20:50] <smoser> in 17.10
[20:50] <smoser> blackboxsw: ^
[20:51] <Sargun> smoser: Just used the some cloud-init.
[20:51] <Sargun> https://gist.github.com/sargun/3bda5690c7bf573a47e5ab8e16d14425
[20:52] <rharper> urg
[20:53] <rharper> needs a dhcp4: true in there too
[20:53] <blackboxsw> so Sargun you are trying to get dual stack up ipv4/6 on an ec2 instance. The provided network-config makes sense as it should be passed through in cloud-init direct to netplan config
[20:53] <blackboxsw> the first paste was it right
[20:53] <Sargun> rharper: That's what I'm putting into user-data.
[20:53] <Sargun> my expectation is that the cloud-init file in /etc will be written out with dhcp4 and dhcp6.
[20:54] <rharper> we can't pass network config as user-data; it's too late as smoser said
[20:54] <rharper> Sargun: it should; but need to check the cloud-init code
[20:54] <smoser> you cna't do it in user-ata.
[20:54] <Sargun> Hrm.
[20:54] <rharper> it's going to read EC2 metadata to see what network config looks like
[20:54] <Sargun> Is there any other mechanism?
[20:54] <smoser> but it should do the right thing.
[20:54] <rharper> it should see that you enabled dhcp6 , but it should also enable dhcp4
[20:54] <Sargun> Yeah
[20:55] <blackboxsw> dpkg -l cloud-init on that image to see what rev you have on that instance
[20:55] <Sargun> ii  cloud-init                                            17.1-18-gd4f70470-0ubuntu1      all                             Init scripts for cloud instances
[20:55] <blackboxsw> thx
[20:55] <rharper> if nic_metadata.get('public-ipv4s'):
[20:55] <rharper>             nic_cfg['subnets'].append({'type': 'dhcp4'})
[20:55] <blackboxsw> right it shoulce to that for both ipv4 and ipv6
[20:55] <Sargun> I don't have any public-ipv4s
[20:56] <Sargun> it should check for both private & public ipv4.
[20:56] <Sargun> if nic_metadata.get('public-ipv4s') or nic_metadata.get('private-ipv4s'):...
[20:57] <rharper> network/interfaces/macs/mac/local-ipv4s
[20:57] <rharper> blackboxsw: ^
[20:57] <rharper> that's the metadata path to private v4
[20:58] <blackboxsw> could be, was just checking http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
[20:58] <Sargun> yeah
[20:58] <Sargun> you have both public and private IPv4s on the metadata service
[20:58] <rharper> but you explicitly don't have a public-v4 enabled ?
[20:59] <Sargun> yeah
[20:59] <rharper> gotcha
[20:59] <blackboxsw> right agreed, I think we probably need to add the internal/local ipv4 check too.
[20:59] <rharper> it's normally enabled by default IIUC
[20:59] <Sargun> that'sthe default for a private subnet on VPC wizzard.
[20:59] <rharper> interesting
[20:59] <Sargun> EC2 is weird.
[20:59] <blackboxsw> I thought all aws instances had to have public ipv4 addrs.
[20:59] <blackboxsw> wow
[21:00] <Sargun> blackboxsw: not VPC
[21:01] <rharper> looks like ubuntu-bug time
[21:02] <blackboxsw> yeah sargun for giggles can you ubuntu-bug cloud-init   and follow the prompts to submit a bug on the terminal CLI?
[21:02] <blackboxsw> Sargun: rather ^
[21:02] <blackboxsw> I'll add the check there on local-ipv4 too today and put something up for review/landing so Ec2 can be 'fixed' for dual stack internal ipv4 as well
[21:03] <blackboxsw> so I meant to say: "Can your run 'ubuntu-bug cloud-init'   and follow the prompts from your instance"
[21:03] <Sargun> Trying
[21:03] <blackboxsw> thx
[21:04] <Sargun> I can't from that instance, because it turns out to need IPv4.
[21:04] <Sargun> oh
[21:04] <Sargun> wait.
[21:05] <Sargun> Can I just file it from launchpad.net?
[21:06] <smoser> Sargun: you can.
[21:06] <blackboxsw> for sure
[21:07] <smoser> please do run 'cloud-init collect'
[21:07] <smoser> and attach that.
[21:07] <smoser> but yeah, you're already provided a good amount of information.
[21:07] <smoser> thanks.
[21:07] <blackboxsw> https://bugs.launchpad.net/cloud-init/+filebug :)
[21:08] <Sargun> /usr/bin/cloud-init: error: argument subcommand: invalid choice: 'collect' (choose from 'init', 'modules', 'single', 'dhclient-hook', 'features', 'analyze', 'devel', 'collect-logs')
[21:08] <Sargun> Are you sure?
[21:10] <blackboxsw> collect-logs
[21:10] <blackboxsw> instead of collect
[21:11] <blackboxsw> it should dump a tarfile in your local directory
[21:11] <blackboxsw> that can be attached to the bug
[21:11] <Sargun> https://bugs.launchpad.net/cloud-init/+bug/1728152
[21:12] <blackboxsw> superb thanks Sargun
[21:12] <Sargun> you can't actually single-stack (IPv6 only) on ec2
[21:12] <Sargun> you always get an IPv4 IP
[21:12] <blackboxsw> yeah I was under mistaken impression that the ipv4 IP also had to be public
[21:12] <blackboxsw> because of the defaults in vpc
[21:13] <blackboxsw> will reproduce a faliure on my vpc account and confirm I can see it too and we'll have something. (it's a quick fix to cloud-init)
[21:13] <Sargun> yeah
[21:14] <Sargun> I wonder if I can give this instance a public-ipv4 IP.
[21:15] <blackboxsw> if you can re-associate ipv4 public, you could sudo rm -rf /var/lib/cloud /var/log/cloud-init.*; sudo reboot and cloud-init could come back up w/ the newly rendered network config
[21:18] <blackboxsw> but minimally Sargun I'm expecting this should work for you...
[21:18] <blackboxsw> http://paste.ubuntu.com/25832582/
[21:19] <blackboxsw> save it on the instance to /tmp/patch1  then cd /usr/lib/python3/dist-packages/cloudinit/sources/; sudo patch -p3 < /tmp/patch1; sudo rm -rf /var/lib/cloud  /var/log/cloud-init*; sudo reboot
[21:20] <blackboxsw> I believe that should render dhcp4 properly
[21:20] <blackboxsw> as it'll see your local-ipv4s in metadata
[21:25] <Sargun> Any idea why my apt source isn't working
[21:29] <blackboxsw> Sargun: you need apt:\n  sources:\n <yoursourcename>:
[21:31] <blackboxsw> hrm....
[21:31] <Sargun> ah
[21:34] <blackboxsw> Sargun: yeah it's admitedly a really long example described at https://cloudinit.readthedocs.io/en/latest/topics/modules.html#apt-configure
[21:34] <blackboxsw> it has quite a few options for cloud-config
[21:35] <smoser> rharper: suck.
[21:35] <smoser> so if i take a stock artful image
[21:36] <smoser> then
[21:36] <smoser> qemu-img create -f qcow2 -b artful-cloud-image.img my.img && sudo mount-image-callback my.img -- mchroot touch /etc/cloud/cloud-init.disabled
[21:36] <smoser> it hangs on boot.
[21:36] <smoser> not sure what is hanging.
[21:37] <smoser> ends with a very unhelipful systemd
[21:37] <smoser> [  OK  ] Started Snappy daemon.
[21:37] <smoser> [  OK  ] Started LXD - container startup/shutdown.
[21:37] <smoser> [  *** ] A start job is running for Wait for…e Configured (1min 19s / no limit)
[21:37] <blackboxsw> smoser: is that what cyphermox hit?
[21:37] <Sargun> Maybe I'll patch in JSON support into cloud-init.
[21:37] <Sargun> and write json-schema for this
[21:37] <rharper> you can turn on systemd debugging via cmdline
[21:37] <smoser> blackboxsw: i dont think so. but in debugging his and trying different things i found it.
[21:38] <rharper> systemd.log_level=debug systemd.log_target=console
[21:38] <rharper> passed as params
[21:40] <rharper> smoser: I wonder if there's no default network config in the iamge ?
[21:40] <rharper> so if you don't run cloud-init you don't get a network config ? but you booted with an interface ?
[21:40] <rharper> can do drop your -net user ?
[21:40] <rharper> no nic, no wait ?
[21:42] <smoser> rharper: http://paste.ubuntu.com/25832717/
[21:43] <smoser> it doesnt help much
[21:43] <smoser> i had used debug on systemd before.
[21:43] <smoser> theres all the noise
[21:43] <smoser> [***] A start job is running blahblahblah ...<removed important part in ...> more blahblahblah
[21:44] <smoser> ohw ell.
[21:44] <smoser> suck
[21:44] <smoser> later.
[21:44] <smoser> i have to run.
[21:45] <rharper> I think the .mounts for cloud migth cause issue
[21:49] <blackboxsw> ok smoser rharper Sargun just put up a trivial branch on this https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/332954
[21:49] <blackboxsw> I'm going to try testing it now
[21:50]  * blackboxsw needs to find that default checkbox for internal only ipv4
[21:56] <blackboxsw> well smoser now I get to write an SRU-verification test for this bug too using the script that I'm halfway done w/ launch-ec2 :)
[21:56] <blackboxsw> anyway you guys should be leaving, it's EOW time
[22:01] <smoser> rharper: http://paste.ubuntu.com/25832788/
[22:02] <smoser> "no limit" finally gave up
[22:02] <smoser> systemd-networkd-wait-online.service
[22:02] <smoser> fun
[22:02] <rharper> lol
[22:02] <rharper> I knew it
[22:03] <rharper> it's configured to wait until at least *one* interface is up
[22:03] <rharper> we gave it none
[22:03] <rharper> or we'll have one, but no config
[22:03] <smoser> ireally have to be gone
[22:03] <smoser> well, cloud-init iddnt run
[22:03] <rharper> there may need to be a "baked" in netplan yaml for dhcp on en*
[22:03] <smoser> so it didnt give it anyting
[22:03] <rharper> right
[22:03] <smoser> and there wasnt any nick there.
[22:03] <rharper> but the old networking service asked if there were network devices to be configured
[22:03] <smoser> either way, it should have decided "nothing to do"
[22:03] <rharper> networkd-wait-online says, wait until I have networking
[22:03] <rharper> which will never happen
[22:03] <smoser> could you file a bug against cloud-images ?
[22:04] <rharper> I think there is one, but if not I will
[22:04] <smoser> yeah. which is wrong.
[22:04] <rharper> I know
[22:04] <rharper> I argued with slangasek about it before
[22:12] <rharper> smoser: https://bugs.launchpad.net/cloud-images/+bug/1728164
[22:32] <blackboxsw> here's where I got that ipv4 required "You cannot disable IPv4 support for your VPC and subnets; this is the default IP addressing system for Amazon VPC and Amazon EC2."   per http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-migrate-ipv6.html
[22:32] <blackboxsw> I interpreted that a public-ipv4 required... bummer
[22:34] <blackboxsw> meh our chef example is also bogus as far as apt configuration is concerned https://cloudinit.readthedocs.io/en/latest/topics/examples.html#install-and-run-chef-recipes
[22:35] <blackboxsw> I'll fix that when  I touch bug: #1727876