bionic/linux-gcp-5.4: 5.4.0-1021.21~18.04.1 -proposed tracker

[Stefan Bader]

This is a manually created tracking bug to track the variant update (roll to 5.4) of linux-gcp.

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
packages:
  lrm: linux-restricted-modules-gcp-5.4
  main: linux-gcp-5.4
  meta: linux-meta-gcp-5.4
  signed: linux-signed-gcp-5.4
phase: Complete
phase-changed: Wednesday, 19. August 2020 15:16 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
versions:
  lrm: 5.4.0-1021.21~18.04.1+1
  main: 5.4.0-1021.21~18.04.1
  meta: 5.4.0.1021.8
  signed: 5.4.0-1021.21~18.04.1

[Andy Whitcroft (apw)]

Kernel signoff added as sign off on upgrade testing for this kernel.

[Po-Hsu Lin (cypressyew)]

5.4.0-1021.21~18.04.1 - gcp
Regression test CMPL, RTB.

Issue to note in gcp:
  ubuntu_fan_smoke_test - enable disable fan test failed (bug 1840904)
  ubuntu_k8s_unit_tests - scheduler and spdy (bug 1824136)
  ubuntu_kernel_selftests - test_bpf in net (bug 1812189) test_blackhole_dev in net (bug 1851619) msg_zerocopy in net (bug 1812620) pmtu.sh marked as failed (bug 1887661) memory-hotplug on some instances (bug 1866846)
  ubuntu_ltp - test timeouted with 4 hours threshold on jenkins (bug 1837206)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) fanotify10 test case 16 (bug 1882717) msgstress03 (bug 1797341) kill11 (bug 1865965)
  ubuntu_lxc - lxc-test-device-add-remove from ubuntu_lxc (bug 1884024)
  ubuntu_sysdig_smoke_test - failed to trace read / write (bug 1844493)

Skipped / blacklisted:
 * libhugetlbfs

[Khaled El Mously (kmously)]

No VT needed for this kernel

[Stefan Bader (smb)]

Verified that right now, only the additional lrm,meta update is pending in -proposed. This only assigns the main variant (linux-gcp) to a 5.4 base.

 linux-gcp-5.4 | 5.4.0-1021.21~18.04.1 | bionic-security | source
 linux-gcp-5.4 | 5.4.0-1021.21~18.04.1 | bionic-updates | source
 linux-meta-gcp-5.4 | 5.4.0.1021.7 | bionic-security | source
 linux-meta-gcp-5.4 | 5.4.0.1021.7 | bionic-updates | source
 linux-meta-gcp-5.4 | 5.4.0.1021.8 | bionic-proposed | source
 linux-signed-gcp-5.4 | 5.4.0-1021.21~18.04.1 | bionic-security | source
 linux-signed-gcp-5.4 | 5.4.0-1021.21~18.04.1 | bionic-updates | source
 linux-restricted-modules-gcp-5.4 | 5.4.0-1021.21~18.04.1 | bionic-security/restricted | source
 linux-restricted-modules-gcp-5.4 | 5.4.0-1021.21~18.04.1 | bionic-updates/restricted | source
 linux-restricted-modules-gcp-5.4 | 5.4.0-1021.21~18.04.1+1 | bionic-proposed/restricted | source

 linux-gcp | 5.3.0.1032.26 | bionic-security | amd64
 linux-gcp | 5.3.0.1032.26 | bionic-updates | amd64
 linux-gcp | 5.4.0.1021.8 | bionic-proposed | amd64

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

All tasks have been completed and the bug is being set to Fix Released