jammy/linux-lowlatency: 5.15.0-43.46 -proposed tracker
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-
bugs-spammed: true
built:
from: 3f82175099dbe434
route-entry: 1
delta:
promote-
promote-
promote-
flag:
boot-
bugs-spammed: true
proposed-
proposed-
issue: KSRU-4378
kernel-
packages:
lrg: linux-restricte
lrm: linux-restricte
lrs: linux-restricte
main: linux-lowlatency
meta: linux-meta-
signed: linux-signed-
phase: Complete
phase-changed: Monday, 01. August 2022 21:26 UTC
proposed-
proposed-
reason: {}
synthetic:
:promote-
trackers:
focal/
jammy/
variant: debs
versions:
lrm: 5.15.0-43.46
main: 5.15.0-43.46
meta: 5.15.0.43.41
signed: 5.15.0-43.46
~~:
clamps:
new-review: 3f82175099dbe434
promote-
self: 5.15.0-43.46
sru-review: 3f82175099dbe434
CVE References
tags: | added: kernel-release-tracking-bug-live |
description: | updated |
tags: | added: kernel-sru-cycle-2022.07.11-1 |
description: | updated |
tags: | added: kernel-sru-derivative-of-1981243 |
Changed in kernel-sru-workflow: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in linux-lowlatency (Ubuntu Jammy): | |
importance: | Undecided → Medium |
Changed in kernel-sru-workflow: | |
status: | Confirmed → Triaged |
description: | updated |
Changed in kernel-sru-workflow: | |
status: | Triaged → In Progress |
tags: | added: kernel-jira-issue-ksru-4378 |
description: | updated |
description: | updated |
summary: |
- jammy/linux-lowlatency: <version to be filled> -proposed tracker + jammy/linux-lowlatency: 5.15.0-43.46 -proposed tracker |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | added: kernel-signing-bot |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in kernel-sru-workflow: | |
status: | In Progress → Fix Committed |
description: | updated |
Changed in kernel-sru-workflow: | |
status: | Fix Committed → In Progress |
description: | updated |
tags: | added: kernel-manual-release |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | removed: kernel-sru-derivative-of-1981243 |
tags: | added: kernel-sru-derivative-of-1983061 |
description: | updated |
This looks like potentially azure cloud expects arm64 specific lowlatency-64k which has no results at all. It is unclear whether this is a cloud problem or even has never been there before.