jammy/linux-uc22-jollyville: 5.15.0-1003.5.5 snap-debs snap:ibmcloud-elba-kernel
Bug #2062403 reported by
Magali Lemes do Sacramento
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kernel SRU Workflow |
Fix Released
|
Medium
|
Unassigned | ||
Snap-prepare |
Fix Released
|
Medium
|
Unassigned | ||
Snap-prepare-signed |
Invalid
|
Medium
|
Unassigned | ||
Snap-release-to-beta |
Fix Released
|
Medium
|
Unassigned | ||
Snap-release-to-candidate |
Invalid
|
Medium
|
Unassigned | ||
Snap-release-to-edge |
Fix Released
|
Medium
|
Unassigned | ||
Snap-release-to-stable |
Invalid
|
Medium
|
Unassigned |
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 --
kernel-
phase: Complete
phase-changed: Tuesday, 23. April 2024 12:18 UTC
reason: {}
snap-name: ibmcloud-
variant: snap-debs
~~:
clamps:
parent: 5.15.0-1003.5.5
self: 5.15.0-1003.5.5
tracker:
last-message: '2024-04-23 13:21:05.
tags: | added: kernel-release-tracking-bug-live |
description: | updated |
tags: | added: kernel-sru-cycle-d2024.04.02-1 |
description: | updated |
tags: | added: kernel-sru-derivative-of-2062404 |
Changed in kernel-sru-workflow: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in kernel-sru-workflow: | |
status: | Confirmed → Triaged |
description: | updated |
summary: |
jammy/linux-uc22-jollyville: <version to be filled> snap-debs + snap:ibmcloud-elba-kernel |
Changed in kernel-sru-workflow: | |
status: | Triaged → In Progress |
description: | updated |
summary: |
- jammy/linux-uc22-jollyville: <version to be filled> snap-debs - snap:ibmcloud-elba-kernel + jammy/linux-uc22-jollyville: 5.15.0-1003.5.5 snap-debs snap:ibmcloud- + elba-kernel |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in kernel-sru-workflow: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
All tasks have been completed and the bug is being closed