[10:35] <DanyC> hi, anyone able to help me out understand why cloud-final.service on a new started EC2 instance is in inactive (dead) state? same state is for cloud-init.target. However if i ssh and manually start cloud-final.service everything is okay. If i run "cloud-init modules --mode=final" everything gets applied, no errors
[10:36] <DanyC> i came across https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1623868 which shows similar behaviour however that bug is present on my cloud-init version .. hence i'm v confused
[10:37] <DanyC> *that bug is fixed
[10:39] <meena> DanyC: which now? fixed or present?
[10:41] <DanyC> meena: what i meant to say is that the above bug it should be fixed in my latest cloud-init version hence i suspect i get only the same symptom but different root cause
[11:12] <meena> DanyC: aye
[11:38] <meena> DanyC: which version of cloud-init do you have?
[19:55] <blackboxsw> https://github.com/canonical/cloud-init/pull/225 up to add ubuntu focal cloud-integration tests to cloud-init
[20:46] <blackboxsw> thx powersj on the review there. I'm plugging that into CI and saw the expected failure with ssh_import_id in our tests too
[20:48] <powersj> yea tests \o/
[20:54] <blackboxsw> powersj: do you know again where that re-sync cloud-init code url is on launchpad. I can't find it
[20:57] <powersj> blackboxsw, I think last time we said it was a jenkins job
[20:57] <powersj> which surprised me
[20:57] <blackboxsw> ahh right,https://jenkins.ubuntu.com/server/job/cloud-init-github-mirror/
[20:57] <blackboxsw> right I forgot about that
[20:58] <blackboxsw> so that we could better control when we have the urge to "do it now"
[21:06] <blackboxsw> anyhow, didn't matter because the integration tests work off of daily ppas. which has uploaded, but still waiting on package publish
[21:34] <Odd_Bloke> smoser: blackboxsw: I've updated https://github.com/canonical/cloud-init/pull/211/ with an approach that gives us two xenial tox envs: one for CI (with the "right" version of pytest) and one for local dev (with the working version of pytest, still in the default list executed).  Could you re-review, please?
[21:45] <smoser> Odd_Bloke: i dont mean to cause problems.
[21:47] <Odd_Bloke> smoser: How would you expect that failure to manifest?
[21:47] <Odd_Bloke> `./tools/tox-venv -h` does work, and lists both environments in its output.
[21:48] <smoser> ./tools/tox-venv xenial-dev
[21:48] <smoser> probaly wont work.
[21:48] <smoser> i ugess it doesnt parse that section at al
[21:48] <smoser> all
[21:49] <Odd_Bloke> smoser: I've just commented (https://github.com/canonical/cloud-init/pull/211/files#r384146914) and it looks OK to me?
[21:49] <Odd_Bloke> Yeah, I think it just ignores that section because it doesn't start with [testenv: