bionic/linux-gke-5.0: 5.0.0-1024.24~18.04.1 -proposed tracker
Bug #1848994 reported by
Khaled El Mously
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kernel SRU Workflow |
Invalid
|
Medium
|
Unassigned | ||
Automated-testing |
Invalid
|
Medium
|
Canonical Kernel Team | ||
Certification-testing |
Invalid
|
Medium
|
Canonical Hardware Certification | ||
Prepare-package |
Invalid
|
Medium
|
Khaled El Mously | ||
Prepare-package-meta |
Invalid
|
Medium
|
Khaled El Mously | ||
Prepare-package-signed |
Invalid
|
Medium
|
Khaled El Mously | ||
Promote-to-proposed |
Invalid
|
Medium
|
Andy Whitcroft | ||
Promote-to-security |
Invalid
|
Medium
|
Ubuntu Stable Release Updates Team | ||
Promote-to-updates |
Invalid
|
Medium
|
Ubuntu Stable Release Updates Team | ||
Regression-testing |
Invalid
|
Medium
|
Canonical Kernel Team | ||
Security-signoff |
Invalid
|
Medium
|
Steve Beattie | ||
Verification-testing |
Invalid
|
Medium
|
Canonical Kernel Team | ||
linux-gke-5.0 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
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 --
boot-testing-
packages:
main: linux-gke-5.0
meta: linux-meta-gke-5.0
signed: linux-signed-
phase: Holding before Promote to Updates
phase-changed: Monday, 11. November 2019 16:55 UTC
proposed-
proposed-
trackers:
bionic/
variant: debs
tags: | added: bionic kernel-release-tracking-bug |
Changed in linux-gke-5.0 (Ubuntu Bionic): | |
status: | New → Confirmed |
Changed in linux-gke-5.0 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-gke-5.0 (Ubuntu Bionic): | |
importance: | Undecided → Medium |
tags: | added: kernel-release-tracking-bug-live |
description: | updated |
tags: | added: kernel-sru-cycle-2019.10.21-1 |
description: | updated |
tags: | added: kernel-sru-backport-of-1848995 |
Changed in kernel-sru-workflow: | |
status: | New → In Progress |
importance: | Undecided → Medium |
tags: | removed: kernel-sru-backport-of-1848995 |
tags: | added: kernel-sru-backport-of-1848995 |
summary: |
- linux-gke-5.0: <version to be filled> -proposed tracker + bionic/linux-gke-5.0: <version to be filled> -proposed tracker |
description: | updated |
description: | updated |
summary: |
- bionic/linux-gke-5.0: <version to be filled> -proposed tracker + bionic/linux-gke-5.0: 5.0.0-1024.24~18.04.1 -proposed tracker |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | added: block-proposed-bionic |
tags: | added: block-proposed |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | added: regression-testing-passed |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | removed: kernel-sru-backport-of-1848995 |
description: | updated |
tags: | removed: kernel-release-tracking-bug-live |
Changed in kernel-sru-workflow: | |
status: | In Progress → Invalid |
Changed in linux-gke-5.0 (Ubuntu Bionic): | |
status: | Fix Released → Invalid |
To post a comment you must log in.
The diff for this seems to show the following emergency commit being lost:
-linux-gke-5.0 (5.0.0- 1022.22~ 18.04.3) bionic; urgency=medium linux-gke- 5.0: 5.0.0-1022. 22~18.04. 3 -proposed tracker (LP: #1847644)
-
- * bionic/
-
- * fdatasync performance regression on 5.0 kernels (LP: #1847641)
- - blk-wbt: fix performance regression in wbt scale_up/scale_down
-
- -- Khalid Elmously <email address hidden> Thu, 10 Oct 2019 14:25:06 -0400
I suspect this has occured because this rebase was not done from the correct tag.
Now I am not 100% convinced we have lost the actual change, bit it would be good confirm that please. If this is present just that the changelog is missformed then we can move this back to Confirmed and accept it, assuming we get the changelog fragment restored for the next upload.