bionic/linux-azure-5.4: 5.4.0-1092.97~18.04.1 snap-debs snap:azure-kernel
Bug #1992615 reported by
Andy Whitcroft
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kernel SRU Workflow |
Fix Released
|
Medium
|
Unassigned | ||
Snap-prepare |
New
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-beta |
New
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-candidate |
New
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-edge |
New
|
Medium
|
Canonical Kernel Team | ||
Snap-release-to-stable |
New
|
Medium
|
Canonical Kernel Team |
Bug Description
This bug will contain status and test results related to a kernel source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https:/
-- swm properties --
issue: KSRU-5243
kernel-
phase: Complete
phase-changed: Wednesday, 12. October 2022 23:04 UTC
reason: {}
snap-name: azure-kernel
variant: snap-debs
~~:
clamps:
parent: 5.4.0-1095.
self: 5.4.0-1092.
tags: | added: kernel-release-tracking-bug-live |
description: | updated |
tags: | added: kernel-sru-cycle-2022.09.19-5 |
description: | updated |
tags: | added: kernel-sru-derivative-of-1992616 |
Changed in kernel-sru-workflow: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in kernel-sru-workflow: | |
status: | Confirmed → Triaged |
description: | updated |
summary: |
- bionic/linux-azure-5.4: <version to be filled> snap-debs + bionic/linux-azure-5.4: <version to be filled> snap-debs snap:azure- + kernel |
Changed in kernel-sru-workflow: | |
status: | Triaged → In Progress |
tags: | added: kernel-jira-issue-ksru-5243 |
description: | updated |
description: | updated |
summary: |
- bionic/linux-azure-5.4: <version to be filled> snap-debs snap:azure- + bionic/linux-azure-5.4: 5.4.0-1092.97~18.04.1 snap-debs snap:azure- kernel |
description: | updated |
description: | updated |
Changed in kernel-sru-workflow: | |
status: | Fix Committed → Fix Released |
description: | updated |
To post a comment you must log in.
All tasks have been completed and the bug is being closed