/srv/irclogs.ubuntu.com/2017/05/02/#cloud-init.txt

blackboxsw_bblsmoser: 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:44
smoserblackboxsw_bbl, no easy way to do that. you'd have to mount bind over /sys to do it i think01:45
smoseri'd just launch on digital ocean is the easiest thing. (i still need to get the ds-identify unit tests in)01:45
blackboxsw_bbltrying to think how better to test (other than spinning up a DO droplet).01:45
blackboxsw_bblyeah01:45
blackboxsw_bblok01:45
smoserthat is non-trivial for sure.01:48
smoserwe could/should bother utlemming to help01:48
smoserand ask for him to give template and such01:48
blackboxsw_bblthx again. yeah /me ❤️'s nontrivial and trying to generate the failure case currently to prove it works once we see the fix01:49
* blackboxsw_bbl needs to head out for the night. see you all tomorrow 01:51
=== blackboxsw_bbl is now known as blackboxsw_away
=== blackboxsw_away is now known as blackboxsw
blackboxswhi 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]13:36
=== rangerpbzzzz is now known as rangerpb
ragechin_From the "It's probably staring me in the face" department - is there a public changelog available?14:21
powersjragechin_: 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:25
ragechin_If not, that's fine. I'll just dig directly into the code.14:26
powersjso 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=master14:28
powersjIf 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:29
powersjah you are right, getting my numbers mixed up14:31
powersjhere was the announcement for 0.7.9 https://lists.launchpad.net/cloud-init/msg00057.html14:31
ragechin_No worries.14:31
ragechin_Thanks. I found the section of code that I'm concerned with.14:31
ragechinAnyone around that's intimately familiar with the config options?14:48
ragechinThere'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:53
rharperragechin: yes, working on getting the docs landed14:55
rharperlemme get the PR link14:55
ragechinThanks.14:55
rharperhttps://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/32139714:56
rharperthat's not the easiest to read, but the network_config.rst in there is pretty comprehensive14:56
rharperfeel free to leave any feedback or ask questions on what's not clear in here or in the PR14:57
ragechinI'm skimming, so I may have missed it..14:58
ragechinI don't see an option to disable cloud-init's network config stuff.14:58
ragechinFound it14:59
ragechinTo be clear, tha'15:00
ragechinThat's still under system_info? So system_info/network/whatever, correct?15:00
rharperragechin: network: disabled15:27
rharpersorry, network: {config: disabled}15:28
rharperthere's a section, Dsiabling Network Configuration15:28
rharpercan be done via kernel command line or config,  echo "network: {config: disabled}" > /etc/cloud/cloud.cfg.d/10-disable-networking.cfg15:29
ragechinrharper: Yeah, found it, thanks15:59
smoserblackboxsw, readin17:19
smoserblackboxsw, reading17:19
smoserblackboxsw, so i should probably open another bug17:21
smoseras i think what is happening is it is fixed, but the warnings do not stop showing on upgrade.17:22
blackboxswahasenack: 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:20
ahasenackblackboxsw: no, I used another one from a tools or sru branch, let me find it19:21
blackboxswI was trying to glean the intent behind https://launchpadlibrarian.net/314573877/make-configdrive-dir but that attached file doesn't seem to be rendered properly19:21
blackboxswahh19:21
blackboxswgotit ahasenack19:21
ahasenackblackboxsw: you found it?19:21
blackboxsw/chad.smith@git.launchpad.net/~smoser/cloud-init/+git/sru-info19:22
blackboxswyeah in the tool directory.19:22
ahasenackI found the script, but I lost the branch19:22
ahasenackyeah19:22
blackboxswok thanks19:22
smoserblackboxsw, did you get what you needed before ?19:22
ahasenackblackboxsw: right, that one19:22
smoserbasically i think that bug is fixed.19:22
smoserbut we never clear up the .warning files19:22
blackboxswsmoser 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 comment19:23
blackboxswsmoser: https://bugs.launchpad.net/cloud-init/+bug/1673637/comments/719:24
ubot5`Ubuntu bug 1673637 in cloud-init "cloud-init - Hosts in softlayer receiving warning" [High,Confirmed]19:24
blackboxswso what about that comment tells you it's an upgrade which hadn't cleaned up a previous warning?19:24
smoserthe version he lists does not have this fix19:24
smoseright ?19:24
* blackboxsw needs to check my reading comprehension19:24
blackboxswahh19:24
blackboxswok me goes back to the git logs to match fixed version versus bug report19:25
smosernew version is 0.7.9-113-g513e99e0-0ubuntu1~16.04.119:25
smoserold version is 0.7.9-90-g61eb03fe-0ubuntu1~16.04.119:26
blackboxsw+1 thanks smoser19:29
blackboxswsmoser: trivial for get-proposed-image for zesty? http://paste.ubuntu.com/24500525/19:47
blackboxswstrike that19:47
blackboxswjust a sec19:47
blackboxswsmoser this rather: http://paste.ubuntu.com/24500540/    zesty no longer publishes img files named *-disk1.img19:48
blackboxswhttp://cloud-images.ubuntu.com/daily/server/zesty/current/19:48
smoseryeah. blackboxsw it already knew that... just didn't have an entry for zesty19:52
smosersee line 619:52
smoserso it already *should* work with zesty, youjust gave a better error message and broke arful19:52
smoser(i htink)19:52
blackboxswoops true19:53
blackboxswhmm why did that break me. I must've typo'd20:01
blackboxswhmm smoser  powersj rharper what's the best way for me to create a nova-lxd image containing proposed cloud-init content for testing?21:29
blackboxswI was going down the route of something like http://pastebin.ubuntu.com/24501031/21:30
blackboxswbut I'm not sure that's correct21:30
smoserblackboxsw, you could use the lxd proposed script there21:30
smoserand then export it21:30
rharperlxc init ubuntu-daily:<release> test;  mount-image-callback --system-mounts lxd:test chroot _MOUNTPOINT_ /bin/bash -c 'script to upgrade to proposed'21:30
smoserand that should be importable/uploadable to nova-lxd21:30
smoserhttps://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot21:31
smoserrharper, ^ fyi, that is what you do.21:31
smoserwhat you said... that just does it.21:31
rharpersmoser: thanks21:31
rharperI 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 instance21:32
blackboxswok will try loading that lxc-proposed-snapshot up as an lxd image on serverstack.21:32
blackboxswrharper: ahh good thoughts as well, so I really wouldn't have to actually use an openstack cloud for this , just lxcs locally?21:33
rharperwell21:33
rharperno, you want nova-lxd I think since we need to see that it exports something into the ENV21:33
blackboxswI'd prefer the former (loading them up in openstack and checking there)21:33
blackboxswyeah in /proc/1/environ21:33
rharperblackboxsw: I was manually telling you what smoser already has a script for21:33
* rharper relocates back hom21:33
blackboxswgotit thx21:34
=== rangerpb is now known as rangerpbzzzz
blackboxswhmm 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.21:55
blackboxswhttp://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 raw22:01
smoserraw is wrong file type for nova-lxd22:01
blackboxswthe main difference I see vs a working lxd image is that disk-format is reported by the working image as root-tar22:01
blackboxswhttp://pastebin.ubuntu.com/24501149/22:01
smoserbut i dont know what the right format is.22:01
smosernova-lxd also does support squashfs22:02
smoseroh shoot.22:02
smosershoot shoot.22:02
* blackboxsw is trying to figure out how to get that root-tar type22:02
smoserso lxd export is going to give you a tarball of a root.tar and then also the metadata22:02
smoserand you only want the root.tar to go into nova-lxd22:02
smoser(as it adds the metadata bits)22:02
smoseri think22:02
smoserso take the export output of lxd22:02
blackboxswahh so I might need to extract/prune then load22:02
smoserand extract it. i think you'll see 2 files22:02
smoseror what ever.22:02
smoserand one is root.tar.xz22:02
smoseri think.22:03
smoseryeah.22:03
* smoser has to run22:03
blackboxswhave a good one22:03
blackboxswthat worked, thanks smoser. The following snippet worked http://pastebin.ubuntu.com/24501524/22:46
blackboxswok three bugs left to template #1682871 #1673637 #167690822:53

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!