| blackboxsw | paride: falcojr: As we are going through CI scrub. Looks like Azure hit some networking timeouts. I also think something may be up with kintetic-only storage_profile params provided during launch https://jenkins.canonical.com/server-team/view/cloud-init/job/cloud-init-integration-kinetic-azure/10/ | 15:40 |
|---|---|---|
| blackboxsw | I'm peeking at that storage_profile error we have right now on kinetic azure | 15:40 |
| blackboxsw | possibly just CI problem and pycloudlib, but verifying | 15:40 |
| blackboxsw | ok pycloudlib can launch kinetic fine using storage_profiles on azure. I'm thinking CI run #10 was an intermittent error. I'm not going to re-kick that as we have other CI runs going for SRU verification | 16:39 |
| blackboxsw | Ran the individual Azure tests that were failing our CI dailies for jammy and that was a success, so intermittent timeout for Jammy. Kinetic CI failures is due to older pycloudlib commitish in cloud-init. I'll have a PR up in a min | 17:17 |
| blackboxsw | so all kinetic cloud-init daily jenkins failures are expected at the moment on Azure | 17:18 |
| blackboxsw | https://github.com/canonical/cloud-init/pull/1476 | 17:25 |
| ubottu | Pull 1476 in canonical/cloud-init "tests: bump pycloudlib pinned commit for kinetic Azure" [Open] | 17:25 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!