[01:44] <blackboxsw_bbl> smoser: I was trying to think of the best way to test/validate a DigitalOcean fix for https://bugs.launchpad.net/cloud-init/+bug/1676908 . WDYT about testing an lxc w/ overwritten /sys/class/dmi/id/system_vendor == "DigitalOcean"?
[01:44] <ubot5`> Ubuntu bug 1676908 in cloud-init (Ubuntu) "DigitalOcean network improvements" [Undecided,Fix committed]
[01:45] <smoser> blackboxsw_bbl, no easy way to do that. you'd have to mount bind over /sys to do it i think
[01:45] <smoser> i'd just launch on digital ocean is the easiest thing. (i still need to get the ds-identify unit tests in)
[01:45] <blackboxsw_bbl> trying to think how better to test (other than spinning up a DO droplet).
[01:45] <blackboxsw_bbl> yeah
[01:45] <blackboxsw_bbl> ok
[01:48] <smoser> that is non-trivial for sure.
[01:48] <smoser> we could/should bother utlemming to help
[01:48] <smoser> and ask for him to give template and such
[01:49] <blackboxsw_bbl> thx again. yeah /me ❤️'s nontrivial and trying to generate the failure case currently to prove it works once we see the fix
[01:51]  * blackboxsw_bbl needs to head out for the night. see you all tomorrow 
=== blackboxsw_bbl is now known as blackboxsw_away
=== blackboxsw_away is now known as blackboxsw
[13:36] <blackboxsw> hi smoser: https://bugs.launchpad.net/cloud-init/+bug/1673637 has some updated customer comments that point to this sru bug not quite resolving things for them. How should we proceed for this SRU-related bug?
[13:36] <ubot5`> Ubuntu bug 1673637 in cloud-init "cloud-init - Hosts in softlayer receiving warning" [High,Confirmed]
=== rangerpbzzzz is now known as rangerpb
[14:21] <ragechin_> From the "It's probably staring me in the face" department - is there a public changelog available?
[14:25] <powersj> ragechin_: is there a particular version of cloud_init in Ubuntu you are looking for or are you after the git log?
[14:25] <ragechin_> 0.7.9.
[14:25] <ragechin_> It's been injested into RHEL and, consequently, overrides ifcfg-eth0;
[14:25] <ragechin_> I'm trying to debug that.
[14:26] <ragechin_> If not, that's fine. I'll just dig directly into the code.
[14:28] <powersj> so 0.7.9 is the version that is under development, so you can look at the master git log here https://git.launchpad.net/cloud-init/log/?h=master
[14:29] <powersj> If I recall there is the yum-changelog command you can use as on RHEL, but it has been a while...
[14:29] <ragechin_> the topic suggests otherwise.
[14:31] <powersj> ah you are right, getting my numbers mixed up
[14:31] <powersj> here was the announcement for 0.7.9 https://lists.launchpad.net/cloud-init/msg00057.html
[14:31] <ragechin_> No worries.
[14:31] <ragechin_> Thanks. I found the section of code that I'm concerned with.
[14:48] <ragechin> Anyone around that's intimately familiar with the config options?
[14:53] <ragechin> There's an undocumented key under 'system_info', and I'm trying to determine what options are available for it.
[14:53] <ragechin> ('network', specifically)
[14:55] <rharper> ragechin: yes, working on getting the docs landed
[14:55] <rharper> lemme get the PR link
[14:55] <ragechin> Thanks.
[14:56] <rharper> https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/321397
[14:56] <rharper> that's not the easiest to read, but the network_config.rst in there is pretty comprehensive
[14:57] <rharper> feel free to leave any feedback or ask questions on what's not clear in here or in the PR
[14:58] <ragechin> I'm skimming, so I may have missed it..
[14:58] <ragechin> I don't see an option to disable cloud-init's network config stuff.
[14:59] <ragechin> Found it
[15:00] <ragechin> To be clear, tha'
[15:00] <ragechin> That's still under system_info? So system_info/network/whatever, correct?
[15:27] <rharper> ragechin: network: disabled
[15:28] <rharper> sorry, network: {config: disabled}
[15:28] <rharper> there's a section, Dsiabling Network Configuration
[15:29] <rharper> can be done via kernel command line or config,  echo "network: {config: disabled}" > /etc/cloud/cloud.cfg.d/10-disable-networking.cfg
[15:59] <ragechin> rharper: Yeah, found it, thanks
[17:19] <smoser> blackboxsw, readin
[17:19] <smoser> blackboxsw, reading
[17:21] <smoser> blackboxsw, so i should probably open another bug
[17:22] <smoser> as i think what is happening is it is fixed, but the warnings do not stop showing on upgrade.
[19:20] <blackboxsw> ahasenack: when you validated https://bugs.launchpad.net/nova-lxd/+bug/1673411 for previous sru did you end up using make-configdrive-dir script that was attached?
[19:20] <ubot5`> Ubuntu bug 1673411 in nova-lxd (Ubuntu Yakkety) "config-drive support is broken" [Medium,Triaged]
[19:21] <ahasenack> blackboxsw: no, I used another one from a tools or sru branch, let me find it
[19:21] <blackboxsw> I was trying to glean the intent behind https://launchpadlibrarian.net/314573877/make-configdrive-dir but that attached file doesn't seem to be rendered properly
[19:21] <blackboxsw> ahh
[19:21] <blackboxsw> gotit ahasenack
[19:21] <ahasenack> blackboxsw: you found it?
[19:22] <blackboxsw> /chad.smith@git.launchpad.net/~smoser/cloud-init/+git/sru-info
[19:22] <blackboxsw> yeah in the tool directory.
[19:22] <ahasenack> I found the script, but I lost the branch
[19:22] <ahasenack> yeah
[19:22] <blackboxsw> ok thanks
[19:22] <smoser> blackboxsw, did you get what you needed before ?
[19:22] <ahasenack> blackboxsw: right, that one
[19:22] <smoser> basically i think that bug is fixed.
[19:22] <smoser> but we never clear up the .warning files
[19:23] <blackboxsw> smoser thanks for the message before on the earlier bug. Yeah, I'm not quite certain how we know what was broken on the followup comment as it sounded like it was a fresh install at a later date. let me dig up that comment
[19:24] <blackboxsw> smoser: https://bugs.launchpad.net/cloud-init/+bug/1673637/comments/7
[19:24] <ubot5`> Ubuntu bug 1673637 in cloud-init "cloud-init - Hosts in softlayer receiving warning" [High,Confirmed]
[19:24] <blackboxsw> so what about that comment tells you it's an upgrade which hadn't cleaned up a previous warning?
[19:24] <smoser> the version he lists does not have this fix
[19:24] <smoser> ight ?
[19:24]  * blackboxsw needs to check my reading comprehension
[19:24] <blackboxsw> ahh
[19:25] <blackboxsw> ok me goes back to the git logs to match fixed version versus bug report
[19:25] <smoser> new version is 0.7.9-113-g513e99e0-0ubuntu1~16.04.1
[19:26] <smoser> old version is 0.7.9-90-g61eb03fe-0ubuntu1~16.04.1
[19:29] <blackboxsw> +1 thanks smoser
[19:47] <blackboxsw> smoser: trivial for get-proposed-image for zesty? http://paste.ubuntu.com/24500525/
[19:47] <blackboxsw> strike that
[19:47] <blackboxsw> just a sec
[19:48] <blackboxsw> smoser this rather: http://paste.ubuntu.com/24500540/    zesty no longer publishes img files named *-disk1.img
[19:48] <blackboxsw> http://cloud-images.ubuntu.com/daily/server/zesty/current/
[19:52] <smoser> yeah. blackboxsw it already knew that... just didn't have an entry for zesty
[19:52] <smoser> see line 6
[19:52] <smoser> so it already *should* work with zesty, youjust gave a better error message and broke arful
[19:52] <smoser> (i htink)
[19:53] <blackboxsw> oops true
[20:01] <blackboxsw> hmm why did that break me. I must've typo'd
[21:29] <blackboxsw> hmm smoser  powersj rharper what's the best way for me to create a nova-lxd image containing proposed cloud-init content for testing?
[21:30] <blackboxsw> I was going down the route of something like http://pastebin.ubuntu.com/24501031/
[21:30] <blackboxsw> but I'm not sure that's correct
[21:30] <smoser> blackboxsw, you could use the lxd proposed script there
[21:30] <smoser> and then export it
[21:30] <rharper> lxc init ubuntu-daily:<release> test;  mount-image-callback --system-mounts lxd:test chroot _MOUNTPOINT_ /bin/bash -c 'script to upgrade to proposed'
[21:30] <smoser> and that should be importable/uploadable to nova-lxd
[21:31] <smoser> https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot
[21:31] <smoser> rharper, ^ fyi, that is what you do.
[21:31] <smoser> what you said... that just does it.
[21:31] <rharper> smoser: thanks
[21:32] <rharper> I think you could also add -proposed, update cloud-init; rm -rf /var/log/cloud-init* /var/lib/cloud/{data,instance*,scripts,sem}; and reboot the instance
[21:32] <blackboxsw> ok will try loading that lxc-proposed-snapshot up as an lxd image on serverstack.
[21:33] <blackboxsw> rharper: ahh good thoughts as well, so I really wouldn't have to actually use an openstack cloud for this , just lxcs locally?
[21:33] <rharper> well
[21:33] <rharper> no, you want nova-lxd I think since we need to see that it exports something into the ENV
[21:33] <blackboxsw> I'd prefer the former (loading them up in openstack and checking there)
[21:33] <blackboxsw> yeah in /proc/1/environ
[21:33] <rharper> blackboxsw: I was manually telling you what smoser already has a script for
[21:33]  * rharper relocates back hom
[21:34] <blackboxsw> gotit thx
=== rangerpb is now known as rangerpbzzzz
[21:55] <blackboxsw> hmm didn't work the instance hasn't come up on serverstack. let me get a trace of what I did so you can tell me what went wrong.
[22:01] <blackboxsw> http://pastebin.ubuntu.com/24501137/  rharper smoser I was able to export the zesty proposed image I created  via 'lxc image export' and i attempted to upload it into our openstack cloud as --disk-format raw
[22:01] <smoser> raw is wrong file type for nova-lxd
[22:01] <blackboxsw> the main difference I see vs a working lxd image is that disk-format is reported by the working image as root-tar
[22:01] <blackboxsw> http://pastebin.ubuntu.com/24501149/
[22:01] <smoser> but i dont know what the right format is.
[22:02] <smoser> nova-lxd also does support squashfs
[22:02] <smoser> oh shoot.
[22:02] <smoser> shoot shoot.
[22:02]  * blackboxsw is trying to figure out how to get that root-tar type
[22:02] <smoser> so lxd export is going to give you a tarball of a root.tar and then also the metadata
[22:02] <smoser> and you only want the root.tar to go into nova-lxd
[22:02] <smoser> (as it adds the metadata bits)
[22:02] <smoser> i think
[22:02] <smoser> so take the export output of lxd
[22:02] <blackboxsw> ahh so I might need to extract/prune then load
[22:02] <smoser> and extract it. i think you'll see 2 files
[22:02] <smoser> or what ever.
[22:02] <smoser> and one is root.tar.xz
[22:03] <smoser> i think.
[22:03] <smoser> yeah.
[22:03]  * smoser has to run
[22:03] <blackboxsw> have a good one
[22:46] <blackboxsw> that worked, thanks smoser. The following snippet worked http://pastebin.ubuntu.com/24501524/
[22:53] <blackboxsw> ok three bugs left to template #1682871 #1673637 #1676908