If there is kernel in proposed, upgrade to repeat smoke test
Bug #2038574 reported by
Dimitri John Ledkov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-images |
New
|
Undecided
|
Unassigned | ||
Bug Description
If there is kernel in proposed, upgrade to repeat smoke test
When doing cloud image testing, once the test is successful and communicate as such, please enable proposed, pin proposed up, and upgrade kernels from there.
Then reboot, and repeat smoke test (for example the "launch lxd container test").
(alternatively kernel team also has ppas, which _only_ contain kernels from proposed).
If that fails, please escalate immediately, as like your image tomorrow will fail as well.
Revision history for this message
| John Chittum (jchittum) wrote | #1 |
To post a comment you must log in.
some counter points -- what are we testing here? Is it the Kernel or LXD? Is it something in the _image_ or is it a stand in for a missing dependency type test?
if LXD has requirements on the kernel, if it were a debian, they could use a `depends` statement, and get caught in a `rdeps` type test. Since LXD in Ubuntu is currently delivered as a snap, I'm unsure what they're doing. I think the same statement can be made for snapd as a snap.
I'm not sure cloud-images, and the CPC team, is the right fit to handle this testing. We should engage with the LXD team as well to see what tests they're doing related to kernel updates. And probably a separate session with the snap team.
I understand that cloud-images are big continuous integrators, so we can likely help enable further testing for other teams. But we're downstream consumers of, not owners of, the packages under test. Yes, it will affect our distribution, but it feels like it's a package level QA issue.