[00:10] <dojordan> would someone be able to help me retrigger a build again? https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341
[00:27] <powersj> dojordan: added you to the CI team users group
[00:27] <dojordan> thank you
[00:28] <powersj> next trigger job will auto launch for you
[00:28] <powersj> so in ~15mins
[00:28] <powersj> or like right now since I pushed the big red button
[00:29] <dojordan> even better!
[05:12] <blackboxsw> thx smoser for the SRU bug merge
[12:50] <catmando> hey all
[12:51] <catmando> does anyone have experience with cloud-init on powervc/powervm hosts?
[12:51] <catmando> specifically, with config drive datasources
[15:55] <smoser> blackboxsw: in your mp for cloud-init... i think they'll want you to put a new changelog entry in
[15:55] <smoser> i could just e reading the email-diff wrong but it looks like youjust updated teh original?
[16:55] <blackboxsw> smoser: just pushed this, is this what you mean? https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334593
[16:55]  * smoser opens
[16:56] <smoser> yeah.
[16:56] <blackboxsw> I didn't pull the process bug up into the latest changelog. is that ok?
[16:56] <blackboxsw> because that would be changing 'history'
[16:57] <blackboxsw> smoser: resubmitting artful one sec
[16:57] <blackboxsw> forgot the ~17.04.1
[16:58] <blackboxsw> I mean ~17.10.1
[17:05] <blackboxsw> https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334594 https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334595 https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/334597
[17:06] <blackboxsw> ok all pushed, awaiting CI
[17:06] <blackboxsw> getting a coffee while magic happen
[17:06] <blackboxsw> s
[17:40] <smoser> blackboxsw: given 'build-and-push' as http://paste.ubuntu.com/26090392/
[17:40] <smoser> currently running
[17:40] <smoser>  for r in artful zesty xenial; do git checkout $r && ../build-and-push || break; done
[17:40] <smoser> with your merges into my local branches.
[17:41] <blackboxsw> nice little script there.
[17:41] <blackboxsw> trying to walk through it now
[17:42] <blackboxsw> to make sure I understand.
[17:42] <blackboxsw> what's sbuild-it alias?
[17:42] <smoser> oh. sbuild-it is http://smoser.brickies.net/git/?p=tildabin.git;a=blob;f=sbuild-it;h=ab48dc16cfbb3c2153c91ba4a14243b627ff2568;hb=HEAD
[17:42] <blackboxsw> dpkg-buildpackage -us -uc or something?
[17:43] <smoser> it will build a dsc or a changes as intput. and reads the file to figure out what the release is. and then calls sbuild with correct --dist=
[17:45] <blackboxsw> good deal. nice to streamline some of those steps
[17:45] <blackboxsw> bookmarking
[17:46] <smoser> looks like sbuild-it will also try to download the original source if it does not have a corresponding .orig.tar.gz
[17:47] <blackboxsw> think I can ping   tjaalton now in #ubuntu-release?
[17:52] <smoser> yes, blackboxsw
[18:05] <blackboxsw> ok pinged there, updated the SRU process bug #1733653 and put up the placeholder updated SRU log sheet https://github.com/cloud-init/ubuntu-sru/tree/master/20171121
[18:05] <ubot5> bug 1733653 in cloud-init (Ubuntu Artful) "sru cloud-init (17.1-27-geb292c18) update to 17.1-41-g76243487-0ubuntu1" [Medium,Fix committed] https://launchpad.net/bugs/1733653
[18:57] <smoser> blackboxsw: updated https://hackmd.io/s/rJdKR9q3b
[19:17] <blackboxsw> excellent smoser thanks
[19:22] <dojordan_> hey guys, I believe I was added to the CI group yet when i log into jenkins I don't see an option to kick off a new CI build. Would someone be able to kick one off for me again?
[19:26] <dojordan_> ignore me, one just got launched. I assume its time based or something?
[19:28] <rharper> dojordan: one you push an update, a new job is queue
[19:28] <rharper> queued, the backend does lots of ci, so it may take a bit before it runs your job
[19:29] <rharper> on jenkins, you can see the queued jobs
[19:31] <dojordan> awesome, thanks !rharper!
[19:31] <dojordan> @rharper *
[20:05] <blackboxsw> hrm trying to fire up kvm with  OVF per doc/sources/ovf/README by downloading cloudimages... Failed to initialize module: /usr/lib/x86_64-linux-gnu/qemu/block-iscsi.so
[20:06] <blackboxsw> I've tried both i386 and amd64 images
[20:29] <rharper> blackboxsw: can you paste your cmdline ?
[20:30] <rharper> and dpkg --list | grep qemu
[20:30] <rharper> you might need the block-extras package
[20:30] <rharper> yeah, sudo apt install qemu-block-extra
[20:30] <rharper> blackboxsw: ^^
[20:30] <rharper> % dpkg -S /usr/lib/x86_64-linux-gnu/qemu/block-iscsi.so
[20:30] <rharper> qemu-block-extra:amd64: /usr/lib/x86_64-linux-gnu/qemu/block-iscsi.so
[20:31] <smoser> hm..
[20:32] <smoser> blackboxsw: what are you doing ?
[20:32] <smoser> how did you try to use block-iscsi ?
[20:33] <blackboxsw> http://pastebin.ubuntu.com
[20:33] <blackboxsw> following the readme in doc/sources/ovf
[20:33] <blackboxsw> trying to validate against master before trying msaika's branch
[20:33] <smoser> blackboxsw: yes, thats a nice pastebin :)
[20:33] <rharper> blackboxsw: need longer url
[20:33] <blackboxsw> hahaha
[20:33] <blackboxsw> http://pastebin.ubuntu.com/26091298/
[20:33] <blackboxsw> can't you guess the #?
[20:34] <rharper> lol
[20:36] <rharper> smoser: it's possible the newer qemu is linked against it; i think it's only a suggests though; cpaelzer might know more about that
[20:36] <rharper> I thought on 2.5+ newer systems it was automatically installed though
[20:36] <smoser> its wierd.
[20:36] <smoser> i am missing something
[20:36] <smoser> qemu-system-x86 'Suggests' qemu-block-extra
[20:37] <smoser> qemu-system-common
[20:37] <rharper> I am to; it should work without those
[20:37] <smoser> Depends on it
[20:37] <rharper> unless you specify a drive that uses that backend
[20:37] <rharper> like rbd
[20:38] <smoser> well, that makes sense in theory.
[20:38] <smoser> but at least in bionic, you can't install qemu-system-x86 without getting it
[20:39] <rharper> yeah, I don't recall why it's required  now
[20:39] <rharper> it was originally broken out to keep the deps out unless you needed it (like librbd etc)
[20:39] <smoser> qemu-system-x86 -> Depends qemu-system-common -> Depends qemu-block-extra
[20:39] <smoser> right
[20:41] <rharper> I have those, I move them out of the way
[20:41] <rharper> and kvm still runs
[20:41] <rharper> blackboxsw: I think we need to see more
[20:41] <smoser> http://paste.ubuntu.com/26091332/
[20:41] <smoser> it blames to some guy named Ryan Harper
[20:41] <smoser> :)
[20:42] <rharper> https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1495895
[20:42] <ubot5> Launchpad bug 1495895 in qemu (Ubuntu) "Unable to attach rados block device to instances" [High,Fix released]
[20:43] <smoser> hm..
[20:43] <smoser> so that went into 2.3 something
[20:43] <smoser> and blackboxsw  had 2.5
[20:43] <smoser> so...
[20:43] <smoser> confused.
[20:44] <rharper> it's been around for some time
[20:44] <blackboxsw> yeah I'll go through the steps again (I'm on xenial but will switch to artful to re-test)
[20:44] <rharper> I'm confused as to why the message is present witout a disk asking for iscsi
[20:44] <rharper> for example, in the original bug, they used a disk with the rbd driver
[20:44] <rharper> qemu when launched will dynamically load those .so files if present and then add support for that block driver
[20:44] <smoser> what is the error you saw ?
[20:45] <smoser> blackboxsw:  ?
[20:45] <smoser> you didnt show an error
[20:45] <rharper> so, your command like of a -qcow2 virtio disk and cdrom shouldn't trip iscsi
[20:45] <smoser> unless i just missed it.
[20:45] <rharper> <-- ckonstanski has quit (Ping timeout: 248 seconds)
[20:45] <rharper> <blackboxsw> hrm trying to fire up kvm with  OVF per doc/sources/ovf/README by downloading cloudimages... Failed to initialize module: /usr/lib/x86_64-linux-gnu/qemu/block-iscsi.so
[20:45] <rharper> <blackboxsw> I've tried both i386 and amd64 images
[20:45] <rharper> but the kvm command like pasted doesn't show any iscsi block devices ...
[20:46] <ckonstanski> Someone needed me? Got new cable installed today -- underwent an outage.
[20:46] <smoser> yeah i dont know. that is wierd.
[20:46] <blackboxsw> ohh sorry will grab again. yes, I'm getting Failed to initlializew module etc http://pastebin.ubuntu.com/26091348/
[20:46] <rharper> ckonstanski: sorry, pasted too much
[20:46] <ckonstanski> oh
[20:47] <smoser> blackboxsw: i'm not sure how it happened
[20:47] <smoser> but the error message is pretty clear
[20:47] <smoser> Note: only modules from the same build can be loaded.
[20:47] <rharper> blackboxsw: can you qemu-img info on that qcow2
[20:47] <smoser> qemu-block-extra:amd64                      1:2.5+dfsg-5ubuntu10.11
[20:48] <smoser> qemu-kvm                                    1:2.5+dfsg-5ubuntu10.14
[20:48] <smoser> its just dlopening stuff in the directory
[20:48] <blackboxsw> not sure what build# I'm at or what the mismatch was but checking
[20:48] <smoser> and it failed to open those things
[20:48] <smoser> because tehy're wrong.
[20:48] <blackboxsw> checking qemu-img
[20:48] <smoser> see above.
[20:48] <smoser> 10.11 and 10.14
[20:48] <rharper> smoser is right, you have mixed packages
[20:48] <blackboxsw> ahh right
[20:48] <blackboxsw> bah
[20:49] <smoser> you must have had a failed apt-upgrad e?
[20:49] <rharper> you really want 2.5+dfsg-5ubuntu10.16 ;
[20:49] <rharper> on xenial that is
[20:49] <rharper> that's the latest
[20:49] <rharper> apt-get -f install should clean that up after an update I'd think
[20:49] <blackboxsw> strange yeah I  must've had a partial upgrade or something
[20:49] <rharper> indeed
[20:58] <blackboxsw> smoser: do you understand what slangasek is saying in ubuntu-release about building -v?
[20:58] <smoser> oh. yes. sorry.
[21:03] <smoser> blackboxsw: that is just annoying.
[21:03] <smoser> it goes t hrough to dpkg-genchanges
[21:04] <smoser> and by default it is the previous entry in debian/changelog
[21:04] <smoser> there is kind of no way to do the right thing.
[21:17] <blackboxsw> hrm, so what's the action here?
[21:18] <smoser> i uploaded
[21:18] <smoser> i was just giving background
[21:19] <smoser> basically i did
[21:19] <smoser>  git checkout ubuntu/xenial
[21:19] <smoser>   build-package -- -v17.1-27-geb292c18-0ubuntu1~16.04.1 -S -d
[21:19] <smoser> then did the same for artful and zesty
[21:19] <smoser> with different ~XX.YY values
[21:28] <blackboxsw> ahh I see, ok. right specify how far back you want changes documented for this release
[21:42] <blackboxsw> ok kvm testing of ovf is fine. configuration error on my side thx smoser rharper
[21:43] <rharper> np
[21:45] <blackboxsw> installing updated kvm packages (and discovered via kvm-ok that I had also disabled kvm in testing that new virt snap)
[21:59] <rharper> eww
[22:03] <smoser> my http://paste.ubuntu.com/26091620/
[22:03] <smoser> just sticking that here in case my system were to die.
[22:03] <smoser> thats current 'launch-softlayer' as I make changes to launch-ec2 copy.
[22:03] <smoser> and /me is out
[22:03] <smoser> later
[22:05] <blackboxsw> sweet !
[22:42] <dojordan> hey guys, can someone take a look at this PR for azure when you get a chance? Many thanks https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+merge/334341