=== vrubiolo1 is now known as vrubiolo [16:58] community notice: hi cloud-init. Now that 20.4 upstream is "released" and in Hirsute (21.04), we are looking to follow the StableUpdateRelease (SRU) process for Ubuntu to release to Xenial (16.06), Bionic (18.04), Focal (20.04) and Groovy (20.10) . [16:58] community notice: The SRU validation will be starting today. Given the US holidays and the amount of work associated with the SRU validation of new features and bug-fixes, this effort will take us > 1 week. Updates will be reported in channel and an SRU process bug will be created for this [17:00] community notice: We will be tracking our SRU validation efforts on this trello board, clicking check boxes on cards to show completion. as we go. https://trello.com/b/hP1KfPeU/sru-cloud-init-204. [17:06] falcojr: when we perform new-upstream-snapshot into Groovy/focal/bionic/xenial branches let's provide commitish 47f4229ebcef9f83df8b549bb869a2dbf6dff17c to make sure we are syncing just your release 20.4 commit [17:06] I'm creating the SRU bug now [17:12] falcojr: also looks like we'll have to sort the quilt patch regeneration for the ds-identify changes too [17:13] you'll notice the failure when you new-upstream-snapshot on ubuntu/xenial [17:13] oh, blackboxsw: I already created the bug [17:13] https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1905599 [17:13] Ubuntu bug 1905599 in cloud-init (Ubuntu Groovy) "sru cloud-init (20.3-2 to 20.4-2) Xenial, Bionic, Focal, and Groovy" [Undecided,New] [17:13] excellent thanks. I was grabbing the changelogs now. will forget that then thank you [17:13] sorry, didn't see your message till now [17:14] no worries [17:14] groovy branch here https://github.com/canonical/cloud-init/pull/695 [17:15] falcojr: we probably only want to new-upstream-snapshot the specific commit though 47f4229ebcef9f83df8b549bb869a2dbf6dff17c giving you a 20.4-0 version [17:16] falcojr: otherwise you and I have to re-release into hirsute again with those two extra commits before SRUing that content back to keep Ubuntu policy that you can only SRU changesets that are published to later Ubuntu series [17:16] gotcha, makes sense [17:16] falcor we *could* re-release to hirsute current tip of master if you'd like. I'd sponsor that upload if you want [17:16] nah, I think they're just test changes anyway [17:16] your choice. but I know we may run out of time on the imminent turkey-day approaching [17:17] +1 let's gen based on the commitish then [17:17] no extra upload to hirsute [17:21] falcojr: I re-added the missing TODOs from the general SRU template for https://wiki.ubuntu.com/CloudinitUpdates as its used for paperwork/checking [17:21] it got lost in the bug creation I think [17:22] ah, right thanks [17:22] new groovy pushed [17:37] blackboxsw: so the quilt patch... [17:38] do I just commit it to ubuntu/xenial on top of the previous head, then run new-upstream-snapshot on top of that? [17:43] falcojr: you and I need this I think https://github.com/canonical/uss-tableflip/pull/68 [17:43] to provide new-upstream-stanpshot --first-sru [17:43] otherwise the changelog includes bug numbers and doesn't prompt for SRU_BUG [17:45] falcojr: as the debian package version in groovy should not be cloud-init (20.4-0ubuntu1) groovy; urgency=medium [17:45] but cloud-init (20.4-0ubuntu1~20.10.1) groovy; urgency=medium [17:45] falcojr: this always happens only on our --first-sru to a recently stable Ubuntu release [17:46] falcojr: with that PR above I can regenerate the groovy branch with the following cmd: neww-upstream-snapshot --first-sru --sru-bug 1905599 47f4229ebcef9f83df8b549bb869a2dbf6dff17c [17:46] 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 [17:47] blackboxsw ok...trying to get the xenial quilt patch thing in before I do that [17:48] +1 falcojr that groovy reference can wait. and note as well in groovy when you get to it. that someone we will need to manually redact LP: #1900837 from the debian/changelog [17:48] Launchpad bug 1900837 in cloud-init "cloud-init resets permissions on log file after reboot" [High,Fix released] https://launchpad.net/bugs/1900837 [17:48] checking your quilt comment [17:49] blackboxsw: also, I think I'm gonna have to get going in a minute here [17:50] falcojr: +1 you apply the quilt patches in the quilt shell you get dropped into, then exit 0 [17:50] like here https://github.com/canonical/uss-tableflip/blob/master/doc/ubuntu_release_process.md#when-the-daily-recipe-build-fails [17:51] and falcojr we can forget about xenial and we will sort that one since it's unique [17:51] if the quilt stuff is a PITA. [17:51] if you get groovy/focal/bionic then we are good. I'm checking those now [17:52] ok, I think this is what the diff should be [17:52] https://paste.ubuntu.com/p/2FKbKPSyPs/ [17:53] that seems reasonable falcojr [17:53] whitespace and one line replacement [17:53] I'm checking bionic/focal right now [17:54] wait, there were 3 lines :D [17:54] it should be a simple diff though [17:56] blackboxsw pushed a new groovy [17:57] falcojr: thanks a ton! and have a good one [17:59] groovy is excellent. will upload that === ijohnson is now known as ijohnson|lunch [18:08] groovy upload complete. [18:23] any upstream committers, I'd like to upload latest bits into hirsute https://github.com/canonical/cloud-init/pull/698 for review [18:23] then we can reflect those commits into the SRU as well [18:41] bionic queued and uploaded === ijohnson|lunch is now known as ijohnson [20:11] Odd_Bloke: if there is a chance today/tomorrow: xenial upload (which required a quilt manual refresh/fix) https://github.com/canonical/cloud-init/pull/699 [20:11] I'd like to get that last upload queued as we didn't get a chance with falcojr [20:12] bionic focal and groovy are already queued uploads for cloud-init 20.4 [20:27] blackboxsw: Ack, looking now. [20:35] blackboxsw: https://github.com/canonical/cloud-init/pull/699/files#r530630179 [22:11] that would have been bad Odd_Bloke thanks for the catch. I've updated and pushed and my diff against upstream/ubuntu/xenial:debian/patches/ds-identify matches your suggestion. [22:18] blackboxsw: Thanks, LGTM now, +1. [22:20] thanks Odd_Bloke I'll push and publish [22:32] I pinged in SRU team #ubuntu-release to let those uploads into -proposed. if nobody is available this week, we can pick it up again next week [22:37] blackboxsw: Yep, sounds good. I'd be surprised if we're ready to release 7 days from now anyway (given the testing we need to do plus holidays) so not getting that clock ticking isn't a major issue. [22:37] I'll chase for the rest of the week regardless. [22:54] thank you sir [22:56] what, what [22:56] are you done with SRU validation?? [23:29] meena: sorry for confusion there. just uploading to a test queue called xenial-proposed/bionic-proposed/focal-proposed [23:30] these are the ubuntu packaging queues https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=cloud-init [23:30] it needs to get accepted into proposed, then we can *start* test validation