18:54 <blackboxsw> #startmeeting cloud-init status meeting && office hours 18:54 <meetingology> Meeting started Tue Dec 1 18:54:54 2020 UTC. The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 18:54 <meetingology> 18:54 <meetingology> Available commands: action commands idea info link nick 18:57 <blackboxsw> community-notice: cloud-init async status is scheduled for today. delayed a bit as it took a while to create the post for this meeting. Details status updates for cloud-init are available in discourse at https://discourse.ubuntu.com/t/cloud-init-status-12-01-20/19604 18:57 <blackboxsw> #link https://discourse.ubuntu.com/t/cloud-init-status-12-01-20/19604 19:00 <blackboxsw> This meeting has moved to an async format, where we basically will host "office hours" and cloud-init devs should be available for questions and discussions for those who are available at this time. For others in timezones that make this meeting time a challenge, we can hold conversations or questions about the status updates on the discourse post above. 19:01 <blackboxsw> The spotlight for this status meeting is that updates 20.4 was released Nov 24, and published to Ubuntu 21.04 (Hirsute). It should be in Ubuntu 21.04 cloud-images at the moment. 19:02 <blackboxsw> We also have just started the SRU process for cloud-init into Ubuntu Xenial, Bionic, Focal and Groovy per this bug https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1905599 19:02 <ubot5> Ubuntu bug 1905599 in cloud-init (Ubuntu Groovy) "sru cloud-init (20.3-2 to 20.4-0ubuntu1) Xenial, Bionic, Focal, and Groovy" [Undecided,New] 19:02 <blackboxsw> #link https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1905599 19:04 <blackboxsw> SRU verification is a lot of work and we will be working down our verification items by creating cloud-init new tests/integration_tests for a lot of this "manual" verification work. We have made our SRU trello board public which tracks our verification efforts at 19:04 <blackboxsw> #link https://trello.com/b/hP1KfPeU/sru-cloud-init-204 19:06 <blackboxsw> Our specific verification work items are listed in this trello card 19:06 <blackboxsw> #link https://trello.com/c/cw8YUo1o/35-preliminary-write-integration-tests-for-commits-in-sru 19:07 <blackboxsw> we welcome anyone interested in involvement in SRU verification, if there is work item, bug or feature that you are interested in from that card, let us know and we can assign that work item to you and help shepherd you through the integration test writing. 19:09 <blackboxsw> .... thus concludes today's broadcast :). The floor is open for any discussions about features/bugs/life etc. In the absence of discussion, we'll be sorting the SRU upload requests of 20.4 into and writing integration tests for the existing features to validate 19:23 <meena> how is the SRU going so far, blackboxsw? 19:29 <blackboxsw> meena: Odd_Bloke and falcojr are chugging away at writing integration tests at the moment for 4 of 19 manual work items here. https://trello.com/c/cw8YUo1o/35-preliminary-write-integration-tests-for-commits-in-sru 19:33 <blackboxsw> falcojr and, I need to queue an Ubuntu groovy upload into Ubuntu's groovy-proposed apt-suite to officially allow folks to run against cloud-init 24.0 on each Ubuntu series 19:34 <blackboxsw> so plan is finish that upload today, at which point we are going to work in parallel on cloud-init verification integration test tasks. 19:47 <Odd_Bloke> I've been diverted into writing some integration test framework support for the test I'm working on. 19:49 <blackboxsw> Odd_Bloke: or falcojr minor tweak to the bionic upload, I found a bug in log2dch https://github.com/canonical/cloud-init/pull/703 19:50 <blackboxsw> bdmurray has rejected bionic so we can get this changelog fix. 19:50 <blackboxsw> once approved I can re-queue the bionic upload 20:42 <blackboxsw> falcojr: I've updated https://github.com/canonical/uss-tableflip/pull/68. So new-upstream-snapshot/log2dch redacts LP: #\d+" -> LP:\d+ from entries added to debian/changelog. You and I can regenerate ubuntu/groovy PR with the following: git checkout ubuntu/groovy; git reset 7fe46f454cf9b081c30398626954d31103ace764; git checkout .; git clean -fd; new-upstream-snapshot --first-sru --sru-bug 1905599 20:42 <blackboxsw> 47f4229ebcef9f83df8b549bb869a2dbf6dff17c 20:42 <ubot5> bug 1905599 in cloud-init (Ubuntu Groovy) "sru cloud-init (20.3-2 to 20.4-0ubuntu1) Xenial, Bionic, Focal, and Groovy" [Undecided,New] https://launchpad.net/bugs/1905599 20:46 <blackboxsw> I've pushed up https://github.com/blackboxsw/cloud-init/tree/ubuntu/groovy as reference for my output 20:49 <blackboxsw> rharper: smoser: Odd_Bloke: falcojr, I'm looking for input on how best to resolve this issue. 20:50 <blackboxsw> I accepted a cloud-init new-upstream-snapshot accidentally for ubuntu/groovy that included two commits past 20.4 release. resulting in 20.4.3 pkg version. 20:50 <blackboxsw> and I pushed the upstream/ubuntu/groovy 20:50 <blackboxsw> daily build recipe built that and uploaded to cloud-init-daily for groovy 20:50 <blackboxsw> we ultimately only want to SRU 20.4.0 to groovy 20:51 <blackboxsw> which is what we are doing for X, B and F (20.4.0~XX.YY) 20:52 * blackboxsw wants to --force push to upstream/ubuntu/groovy with the downrev'd 20.4.0-0ubntu1~20.10. but daily builds for our cloud-init ppa will not actually be able to upload that to the daily PPA because package version will be lower than 20.4.3. 20:53 <blackboxsw> and it's naughty to force push to the ubuntu/groovy branch.... but the only consumer is the daily build recipe 20:56 <blackboxsw> well, our build recipe into daily PPA for groovy does encode the commit revno in the builds. https://code.launchpad.net/~cloud-init-dev/+recipe/cloud-init-daily-groovy so maybe this is a non-issue 20:57 <blackboxsw> because it doesn't actually rely on the debian/changelog 20.4.3 version name 21:00 <blackboxsw> #endmeeting