bionic/linux-azure: 5.0.0-1024.25~18.04.1 snap-debs snap:azure-kernel
Bug #1848985 reported by
Khaled El Mously
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Kernel SRU Workflow |
Fix Released
|
Medium
|
Unassigned | ||
| Snap-release-to-beta |
Fix Released
|
Medium
|
Canonical Kernel Team | ||
| Snap-release-to-candidate |
Fix Released
|
Medium
|
Canonical Kernel Team | ||
| Snap-release-to-edge |
Fix Released
|
Medium
|
Canonical Kernel Team | ||
| Snap-release-to-stable |
Invalid
|
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 --
kernel-
phase: Complete
phase-changed: Friday, 25. October 2019 01:40 UTC
snap-name: azure-kernel
variant: snap-debs
| tags: | added: bionic kernel-release-tracking-bug |
| tags: | added: kernel-release-tracking-bug-live |
| description: | updated |
| tags: | added: kernel-sru-cycle-2019.10.21-1 |
| description: | updated |
| tags: | added: kernel-sru-derivative-of-1848987 |
| Changed in kernel-sru-workflow: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| summary: |
- linux-azure: <version to be filled> snap-debs + bionic/linux-azure: <version to be filled> snap-debs snap:azure-kernel |
| description: | updated |
| tags: | removed: kernel-sru-derivative-of-1848987 |
| tags: | added: kernel-sru-derivative-of-1848987 |
| summary: |
- bionic/linux-azure: <version to be filled> snap-debs snap:azure-kernel + bionic/linux-azure: 5.0.0-1024.25~18.04.1 snap-debs snap:azure-kernel |
| description: | updated |
| description: | updated |
| description: | updated |
Revision history for this message
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote Workflow done! | #1 |
| Changed in kernel-sru-workflow: | |
| status: | In Progress → Fix Released |
| tags: | removed: kernel-release-tracking-bug-live |
To post a comment you must log in.
All tasks have been completed and the bug is being set to Fix Released