rharper | ok, systemd_timesyncd and chrony done; | 00:39 |
---|---|---|
rharper | now I'm done, tomorrow fixing up py26 unittests | 00:39 |
rharper | *sigh* | 00:39 |
smoser | blackboxsw: i would probably not add the new depends into x, a | 01:38 |
smoser | it probably *is* strictly required. | 01:39 |
smoser | but because isc-dhcp-client is part of ubuntu-minimal | 01:39 |
smoser | and you're really expected to create a ubuntu without 'ubuntu-minimal' | 01:40 |
smoser | it is not likely that cloud-init is to be installed in such a place. | 01:40 |
smoser | so.. i'd just leave it be. additionally, adding depends or recommends like that to a stable can be problematic | 01:43 |
smoser | see someone complaining about a similar add | 01:43 |
smoser | https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1633643 | 01:43 |
ubot5 | Ubuntu bug 1633643 in initramfs-tools (Ubuntu) "unnecessary dependency upon isc-dhcp-client" [Undecided,Invalid] | 01:43 |
smoser | and then also the squashfuse bug (bug 1628289) | 01:44 |
ubot5 | bug 1628289 in Snappy "snapd should depend on squashfuse (for use in containers)" [Undecided,In progress] https://launchpad.net/bugs/1628289 | 01:44 |
blackboxsw | +1 on dropping isc-dhcp-client depends | 01:53 |
blackboxsw | will repost the MPs without that | 01:53 |
blackboxsw | smoser: thanks for the reference to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1756173 | 02:01 |
ubot5 | Ubuntu bug 1756173 in snapd (Ubuntu Artful) "[SRU] 2.32" [Undecided,New] | 02:01 |
blackboxsw | I've added a card https://trello.com/c/OTYKbFEu/720-drop-squashfuse-install-logic-from-ccsnap-when-https-bugslaunchpadnet-ubuntu-source-snapd-bug-1756173-lands | 02:03 |
blackboxsw | pushed ubuntu/xenial and ubuntu/artful without isc-dhcp-client explicit dependency | 02:29 |
=== shardy is now known as shardy_lunch | ||
rharper | smoser: ./tools/run-centos is super handy =) | 13:53 |
smoser | yeah. we need to make it work for suse too | 13:55 |
smoser | and actually.. i've even wnated it to work for ubuntu | 13:56 |
smoser | when there was some bug trhat didnt reproduce on my desktoip, but c-i saw. | 13:56 |
rharper | interesting | 14:05 |
=== shardy_lunch is now known as shardy | ||
=== r-daneel_ is now known as r-daneel | ||
smoser | blackboxsw: ok... can you give qa-scripts/new-upstream-snapshot a try ? | 17:01 |
smoser | you can see the last commit message there. | 17:01 |
smoser | i think i have addressed most of the pain in it. | 17:02 |
blackboxsw | checking/updating now | 17:02 |
blackboxsw | and thanks! | 17:02 |
blackboxsw | smoser: we'll drop new-upstream-snapshot script after the SRU or as part of the SRU? | 17:03 |
blackboxsw | in the ubuntu/xenial|artful branches | 17:03 |
smoser | i think no hurry to drop it. | 17:03 |
smoser | so i'd say after. | 17:03 |
smoser | but if you want to drop it we can. | 17:03 |
* blackboxsw checks out the refresh patches logic. that was a surprise | 17:06 | |
smoser | thats why your xenial didnt work | 17:07 |
smoser | because the patch would only apply with fuzz | 17:07 |
smoser | as we'd changed ds-identify aroudn the xenial patches | 17:07 |
blackboxsw | gotcha, yeah I just didn't expect to see a separate commit message for it, and changelog entry. Both make sense as separate items, I just wanted to understand the quilt magic | 17:09 |
blackboxsw | smoser: pushed just ubuntu/xenial branch again | 17:13 |
blackboxsw | shall I push artful again? | 17:13 |
blackboxsw | new-upstream-snapshot works like a charm | 17:14 |
smoser | blackboxsw: i uploaded artful all ready. | 17:15 |
blackboxsw | ahh hadn't checked, thx | 17:15 |
smoser | i don tthink any reason to re-do it. | 17:15 |
blackboxsw | changelog didn't end up changing anything, so good there on artful anyway | 17:16 |
ihre | I'd like to test some changes in user-data after applying some changes to user-data. So far, I've mostly used cloud-init w/ qemu and genisoimage for testing, but I think there should be an easier way. I've tested w/ manual changes to cloud-config.txt/user-data.txt/user-data.txt.1 in /var/lib/cloud/instances/$instance-id/, and by reattaching the cdrom through the qemu monitor, yet changes aren't picked up. | 17:26 |
ihre | Which file on disk should I modify to be able to rerun cloud-init without having to go through the qemu/genisoimage steps? | 17:26 |
blackboxsw | ihre: there are several semaphores that block re-running specific cloud-init modules across reboots | 17:26 |
blackboxsw | you can clear out those semaphores by running "sudo cloud-init clean --logs --reboot" | 17:27 |
blackboxsw | it'll remove all cloud-init former run logs and reboot the machine so cloud-init can re-run "fresh" with any user data you've provided | 17:27 |
blackboxsw | I generally iterate using lxc on ubuntu | 17:28 |
blackboxsw | via lxc launch ubuntu-daily:bionic myb1 | 17:28 |
blackboxsw | lxc exec myb1 bash # then manipulate user-data in /var/lib/cloud/seed/nocloud-net/user-data | 17:29 |
blackboxsw | in lxcs, the no-cloud/seed directory is kept across reboots. I'll check how the qemu image detected re-run to better answer your question | 17:30 |
blackboxsw | hrm, I actually have to run on an errand, will get back to that in ~45 mins | 17:31 |
ihre | blackboxsw: Thanks, didnt think of using a container to test it, that seems a nice alternative as well. | 17:32 |
ihre | Previously, I just removed a/the semaphore(s) by hand and reran cloud-init modules --mode final. | 17:32 |
blackboxsw | it's at least the fastest iterative method I've found for dev-test cycles. | 17:33 |
* blackboxsw heads out | 17:33 | |
ihre | No rush on my end, the current way works fine though, it just feels a little cumbersome at times, anyways, thanks for taking the time to look into it :) | 17:33 |
smoser | blackboxsw: your quilt refrsh differs in behavior from mine. | 17:39 |
nacc | blackboxsw: smoser: it's sensitive to ~/.quiltrc | 17:40 |
nacc | use --quiltrc - | 17:40 |
nacc | (just a guess) | 17:40 |
smoser | yeah. | 17:42 |
nacc | we have to do that in git-ubuntu | 17:44 |
nacc | smoser: i'm guessing this is about reproducibility? | 17:44 |
smoser | blackboxsw: grab tip of qa-scripts and try again, would you ? | 17:49 |
smoser | nacc: well, yeah. | 17:50 |
smoser | 17:50 | |
smoser | http://paste.ubuntu.com/p/3BwC5n3v4P/ | 17:50 |
nacc | smoser: yeah | 17:50 |
smoser | we run 'new-upstream-snapshot' to create a new upstream snapshot of cloud-init. | 17:50 |
smoser | and that is a run here versus on chad's system. | 17:50 |
nacc | yeah, you want your snapshot to be the same as chad | 17:50 |
nacc | similar idea for us, we want our same-argument builds to be contentfully the same | 17:51 |
=== r-daneel_ is now known as r-daneel | ||
blackboxsw | smoser: just pushed https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/ubuntu/xenial | 18:33 |
smoser | blackboxsw: woot. | 18:36 |
smoser | mine to yours : http://paste.ubuntu.com/p/spBd2CCrKg/ | 18:36 |
smoser | new feature there to strip bug numbers on sru | 18:36 |
smoser | and make you give an SRU bug | 18:36 |
blackboxsw | ahh right I totally forgot to strip bug#'s on artful | 18:53 |
blackboxsw | smoser: what should I do w.r.t. devel/arful | 18:56 |
blackboxsw | smoser: what should I do w.r.t. devel/artful. should we strip bug#'s | 18:56 |
smoser | blackboxsw: oh. shoot. yeah i guess we should. right ? | 18:58 |
smoser | we are supposed to. | 18:58 |
smoser | we can just re-upload | 18:58 |
blackboxsw | yeah, I think so, yeah I'll repropose and do that right. | 18:58 |
blackboxsw | forgot that part of the process obviously | 18:58 |
smoser | well now the script does the right thing | 18:59 |
smoser | you forgot, i forgot too. | 18:59 |
blackboxsw | https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/342329 just --forced a new-upstream-release for artful | 19:11 |
blackboxsw | merge conflicts against existing ubuntu/artful. | 19:12 |
blackboxsw | for all the bug comment drops | 19:13 |
smoser | blackboxsw: how bout this.. | 19:13 |
smoser | git checkout ubuntu/artful | 19:16 |
smoser | git reset --hard ubuntu/17.2-35-gf576b2a2-0ubuntu1_17.10.2 | 19:16 |
smoser | new-upstream-snapshot | 19:16 |
smoser | dch --release --distribution=artful | 19:16 |
smoser | git push chad.smith HEAD --force | 19:16 |
smoser | basically, lets just re-do it. | 19:16 |
blackboxsw | yeah I did basically that. | 19:16 |
blackboxsw | git checkout -b ubuntu/artful a2ce41af52c619c13da66f84ee2a789b9df8f3a2 | 19:16 |
blackboxsw | and re-ran everything | 19:16 |
blackboxsw | I'll use your git-fu here and try again | 19:16 |
smoser | yours is probably ok now. | 19:17 |
smoser | let me see. i thought you were saying it wasnt | 19:17 |
blackboxsw | In the UI I see merge conflicts | 19:17 |
blackboxsw | in debian/changelog | 19:17 |
blackboxsw | but all the other content is good | 19:17 |
smoser | yours is good. | 19:19 |
smoser | k. i'll just build and push and push over upstream | 19:19 |
blackboxsw | excellent. and the moral if this story is: Chad don't push branches late in the evening | 19:21 |
smoser | i'm quite happy with those changes to that script. | 19:22 |
smoser | i think we have covered most of the pain poitns of it. | 19:22 |
blackboxsw | smoser: I love it. though I throw eggs at any shell script. | 19:23 |
* blackboxsw will become better versed in shell someday. | 19:23 | |
smoser | blackboxsw: fair enough. it is lots of variables and such in there. definitely "shell script" | 19:26 |
blackboxsw | smoser: right so although you pushed the upload, nothing showed in artful-proposed yet so we're safe to re-push right? | 19:26 |
blackboxsw | I'm looking for the proposed build queue in launchpad again | 19:27 |
blackboxsw | https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=cloud-init | 19:27 |
blackboxsw | or https://launchpad.net/ubuntu/artful/+queue?queue_state=1&queue_text=cloud-init rather | 19:27 |
smoser | i just uploaded artful | 19:28 |
blackboxsw | ok great so that list tells me you just re-submitted same unapproved upload 30 seconds ago | 19:29 |
smoser | yep | 19:29 |
blackboxsw | now do we ping in ubuntu-release for attention on artful/xenial? | 19:29 |
smoser | we can, yeah. | 19:30 |
blackboxsw | will do. | 19:30 |
blackboxsw | ok smoser I'm going to get to work on updating out manual cloud test scripts for this SRU https://hackmd.io/jlq3C4qbSgurZ_DZ5GTiuw?both | 19:43 |
blackboxsw | smoser: I hadn't tested review-mps yet on non-master branches. I didn't want to automatically botch the merges | 20:25 |
blackboxsw | all 3 branches are approved | 20:26 |
blackboxsw | I can use review-mps to land them later if you don't land them now | 20:26 |
=== r-daneel_ is now known as r-daneel | ||
ihre | thanks for the tip re: lxc/lxd blackboxsw, that is definitely an easier workflow than using qemu :) | 20:58 |
blackboxsw | good to hear ihre, I'll probably write up a blog post about it (and use of other cloud-init CLI commands=) | 20:59 |
=== r-daneel_ is now known as r-daneel | ||
ihre | i'll keep an eye out for it! | 21:03 |
blackboxsw | ok smoser landed your ubuntu/(artful|xenial) mps and fixed up qa-scripts:review-mps tool to properly handle --upstream-branch origin/ubuntu/* | 21:51 |
blackboxsw | thanks for the cloud-init release email BTW https://lists.launchpad.net/cloud-init/msg00145.html | 22:09 |
=== blackboxsw changed the topic of #cloud-init to: Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting: Monday 4/2 16:00 UTC | cloud-init 18.2 released (03/28/2018) |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!