focal/linux-azure-5.13: 5.13.0-1009.10~20.04.1 -proposed tracker

Bug #1953680 reported by Marcelo Cerri
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Unassigned
Automated-testing
Incomplete
Medium
Canonical Kernel Team
Boot-testing
Fix Released
Medium
Unassigned
Certification-testing
Invalid
Medium
Unassigned
Prepare-package
Fix Released
Medium
Marcelo Cerri
Prepare-package-lrg
Fix Released
Medium
Marcelo Cerri
Prepare-package-lrm
Fix Released
Medium
Marcelo Cerri
Prepare-package-lrs
Fix Released
Medium
Marcelo Cerri
Prepare-package-meta
Fix Released
Medium
Marcelo Cerri
Prepare-package-signed
Fix Released
Medium
Marcelo Cerri
Promote-signing-to-proposed
Invalid
Medium
Unassigned
Promote-to-proposed
Incomplete
Medium
Andy Whitcroft
Promote-to-security
New
Medium
Ubuntu Stable Release Updates Team
Promote-to-updates
New
Medium
Ubuntu Stable Release Updates Team
Regression-testing
Triaged
Medium
Canonical Kernel Team
Security-signoff
In Progress
Medium
Canonical Security Team
Sru-review
Fix Released
Medium
Andy Whitcroft
Stakeholder-signoff
Confirmed
Medium
linux-azure stakeholder signoff
Verification-testing
Fix Released
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://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
boot-testing-requested: true
bugs-spammed: true
built:
  route-entry: 1
delta:
  promote-to-proposed:
  - lrm
  - lrs
  - signed
  - meta
  - lrg
  - main
  sru-review:
  - lrs
  - lrm
  - signed
  - lrg
  - main
  - meta
issue: KSRU-664
kernel-stable-master-bug: 1952257
packages:
  lrg: linux-restricted-generate-azure-5.13
  lrm: linux-restricted-modules-azure-5.13
  lrs: linux-restricted-signatures-azure-5.13
  main: linux-azure-5.13
  meta: linux-meta-azure-5.13
  signed: linux-signed-azure-5.13
phase: Promote to Proposed
phase-changed: Monday, 13. December 2021 21:24 UTC
reason:
  automated-testing: Stalled -- testing FAILED
  promote-to-proposed: Stalled -- copy FAILED
  regression-testing: Ongoing -- testing in progress
  security-signoff: Pending -- waiting for signoff
  stakeholder-signoff: Stalled -- waiting for signoff
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  lrm: 5.13.0-1009.10~20.04.1
  main: 5.13.0-1009.10~20.04.1
  meta: 5.13.0.1009.10~20.04.1
  signed: 5.13.0-1009.10~20.04.1
  source: 5.13.0-1009.10~20.04.1

Marcelo Cerri (mhcerri)
tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2021.11.29-1
description: updated
tags: added: kernel-sru-backport-of-1952257
Changed in kernel-sru-workflow:
status: New → Confirmed
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-664
description: updated
Marcelo Cerri (mhcerri)
summary: - focal/linux-azure-5.13: <version to be filled> -proposed tracker
+ focal/linux-azure-5.13: 5.13.0-1009.10~20.04.1 -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
Andy Whitcroft (apw)
tags: added: kernel-signing-bot
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Packages outside of proper component
Download full text (3.8 KiB)

The following packages ended up in the wrong component in the Proposed pocket:

linux-restricted-modules-azure-5.13 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-modules-nvidia-390-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-modules-nvidia-390-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-418-server-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-modules-nvidia-418-server-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-435-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-440-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-440-server-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-450-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-450-server-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-modules-nvidia-450-server-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-455-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-460-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-460-server-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-modules-nvidia-460-server-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-465-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-470-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-modules-nvidia-470-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-470-server-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-modules-nvidia-470-server-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-495-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-modules-nvidia-495-azure-edge 5.13.0-1009.10~20.04.1 - is in restricted instead of multiverse
linux-objects-nvidia-390-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-objects-nvidia-418-server-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-objects-nvidia-450-server-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-objects-nvidia-460-server-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-objects-nvidia-470-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-objects-nvidia-470-server-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-objects-nvidia-495-5.13.0-1009-azure 5.13.0-1009.10~20.04.1 - is in universe instead of multiverse
linux-restricted-signatures-azure-5.13 5.13.0-1009.10~20.04.1...

Read more...

description: updated
description: updated
description: updated
Andy Whitcroft (apw)
tags: removed: kernel-release-tracking-bug-live
Changed in kernel-sru-workflow:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.