[08:35] <tribaal> mruffell: as far as I can see it's currently undergoing testing, so it should be relatively soon (you can help by enabling -proposed and checking that it works for your use-case, too!)
[12:25] <Odd_Bloke> mruffell: Yep, tribaal is correct, we're currently performing validation; I would expect that would be complete this week, but blackboxsw would have a better perspective.
[15:12] <blackboxsw> correct, mruffell tribaal Odd_Bloke this SRU was a big one to verify as we hadn't SRU'd for 4 months, so lots to verify. We are tracking and adding logs to this process bug  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1881018  and need to knock out the rest of the TODOs. expectation is this week if we don't hit a significant regression in testing.
[15:15] <AnhVoMSFT> @blackboxsw it would be useful to keep a list of what can be automated during your manual verification and have a list of tasks to automate them. If there is anything we can help from the Azure side of things please let us know.
[16:15] <blackboxsw> AnhVoMSFT: agreed, this sru has been painful. In our retro I believe we will be trying to instrument a new approach to spread the wealth of some of this verification cost by potentially looking at requesting that new features have some integration test coverage under tests/cloud_tests.
[16:16] <blackboxsw> AnhVoMSFT: I was aware at one point you may have an internal CI running cloud-init's azure cloud_tests, is that still true?
[16:19] <blackboxsw> and if so, I think it would be excellent if there is an ability to kick off a CI run on Azure's side which added the (xenial|bionic|focal)-proposed pocket and run that test suite https://cloudinit.readthedocs.io/en/latest/topics/debugging.html#manual-sru-verification-procedure.
[16:25] <blackboxsw> it would be effective to have a successful CI run from any cloud vendor running tox -e citest -- --ppa ppa:cloud-init-dev/proposed
[16:26] <blackboxsw> that would exercise the cloud-init version under current SRU verification and ensure no feature regression.
[17:54] <blackboxsw> rharper: do you think this week you'll have a chance for SRU verification tests for either https://git.launchpad.net/cloud-init/commit/?id=46cf23c2  or https://git.launchpad.net/cloud-init/commit/?id=723e2bc1
[17:54] <blackboxsw> otherwise I think we'll probably grab them in a day or two
[17:55] <blackboxsw> I think we/I volunteered you for them last week when you thought there might be time, no pressure either way, we are just closing in on release verification
[18:17] <AnhVoMSFT> @blackboxsw I will look into it. If not I can look into integrating it
[18:28] <rharper> blackboxsw: yeah, I can get those done
[18:29] <blackboxsw> excellent rharper thank you sir
[18:29] <blackboxsw> AnhVoMSFT: also good to hear. I'll get a rtd update together on manual SRU testing too to suggest the tox -e citest -- --ppa ppa:cloud-init-dev/proposed  run. for additional SRU verification tasks for a given c;loud
[19:34] <meena> oh nooo… github is dead, or at least it doesn't resolve anymore….
[21:59] <blackboxsw> lucasmoura: responded on the azure sru verification results PR. thanks. https://github.com/cloud-init/ubuntu-sru/pull/126
[22:00] <blackboxsw> I think we need to improve this process before our next SRU (which I suppose is in about 2 weeks ;/)
[22:00] <blackboxsw> so we should be able to trim this verification process a bit so it doesn't sink our ship for 2.5 weeks
[22:51] <blackboxsw> and addressed comments on consolidated SRU verification scripts https://github.com/cloud-init/ubuntu-sru/pull/128