[Group.of.nepali.translators] [Bug 1889555] Re: cc_grub_dpkg was fixed to support nvme drives, but didn't clear the state of cc_grub_dpkg and didn't rerun it on upgrades

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 20.3-15-g6d332e5c-
0ubuntu1

---
cloud-init (20.3-15-g6d332e5c-0ubuntu1) groovy; urgency=medium

  * d/cloud-init.postinst: fix the grub install device for NVMe-rooted
instances on upgrade.  (LP: #1889555)
  * d/cloud-init.templates: add RbxCloud to Choices-C.
  * Add d/clean to fully clean the build artifacts.
  * d/control:
- Bump Standards-Version to 4.5.0, no changes needed.
- B-D on debhelper-compat; drop d/compat.
  * Bump the debhelper compat level to 13. Required changes:
- Stop including the dh systemd plugin.
- Switch from dh_systemd_start to dh_installsystemd
  * New upstream snapshot.
- create a shutdown_command method in distro classes (#567)
  [Emmanuel Thomé]
- user_data: remove unused constant (#566)
- network: Fix type and respect name when rendering vlan in
  sysconfig. (#541) [Eduardo Otubo] (LP: #1788915, #1826608)
- Retrieve SSH keys from IMDS first with OVF as a fallback (#509)
  [Thomas Stringer]
- Add jqueuniet as contributor (#569) [Johann Queuniet]
- distros: minor typo fix (#562)
- Bump the integration-requirements versioned dependencies (#565)
  [Paride Legovini]
- network-config-format-v1: fix typo in nameserver example (#564)
  [Stanislas]
- Run cloud-init-local.service after the hv_kvp_daemon (#505)
  [Robert Schweikert]
- Add method type hints for Azure helper (#540) [Johnson Shi]
- systemd: add Before=shutdown.target when Conflicts=shutdown.target is
  used (#546) [Paride Legovini]
- LXD: detach network from profile before deleting it (#542)
  [Paride Legovini] (LP: #1776958)
- redhat spec: add missing BuildRequires (#552) [Paride Legovini]

 -- Chad Smith   Tue, 15 Sep 2020 20:19:10
-0600

** Changed in: cloud-init (Ubuntu Groovy)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1889555

Title:
  cc_grub_dpkg was fixed to support nvme drives, but didn't clear the
  state of cc_grub_dpkg and didn't rerun it on upgrades

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in cloud-init source package in Bionic:
  Fix Committed
Status in cloud-init source package in Focal:
  Fix Committed
Status in cloud-init source package in Groovy:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Older versions of cloud-init could misconfigure grub on nvme devices,
  which could prevent instances from booting after a grub upgrade.

  [Test Case]
  For focal, bionic, and xenial verify the following:
  1. on an affected instance, test that installing the new version of 
cloud-init appropriately updates debconf
  2. on an affected instance, modify of the debconf settings and test that 
installing the new version of cloud-init does not touch those values
  3. in a container, confirm that cloud-init does not touch the values
  4. in an unaffected instance (i.e. one without an NVMe root), confirm that 
cloud-init does not touch the values

  Steps for test 1:
  # Find an old affected image with
  aws ec2 describe-images --filters "Name=name,Values=Ubuntu *"

  # Launch an AWS with affected image-id, ssh in

  # After startup, connect via SSH, then
  # Verify we're on an nvme device
  lsblk | grep nvme

  # Verify install_devices set incorrectly
  debconf-show grub-pc | grep "install_devices:"

  # update cloud-init to proposed
  mirror=http://archive.ubuntu.com/ubuntu
  echo deb $mirror $(lsb_release -sc)-proposed main | tee 
/etc/apt/sources.list.d/proposed.list
  apt-get update -q
  apt-get install -qy cloud-init

  # Verify "Reconfiguring grub" message in upgrade output

  # Verify install_devices set correctly
  debconf-show grub-pc | grep "install_devices:"

  # Verify that after reboot we can still connect

  Steps for test 2:
  # Find an old affected image with
  aws ec2 describe-images --filters "Name=name,Values=Ubuntu *"

  # Launch an AWS with affected image-id

  # After startup, connect via SSH, then
  # Verify we're on an nvme device
  lsblk | grep nvme

  # Verify install_devices set incorrectly
  debconf-show grub-pc | grep "install_devices:"

  # Update install device to something (anything) else
  echo 'set grub-pc/install_devices /dev/sdb' | debconf-communicate

  # update cloud-init to proposed
  mirror=http://archive.ubuntu.com/ubuntu
  echo deb $mirror $(lsb_release -sc)-proposed main | tee 
/etc/apt/sources.list.d/proposed.list
  apt-get update -q
  apt-get install -qy cloud-init

  # Verify no "Reconfiguring grub" message in upgrade output
  # Verify install_devices not changed
  debconf-show grub-pc | grep "install_devices:"

  Steps for test 3:
  # lxd launch affected image
  lxc launch 

  # Obtain bash shell
  lxc 

[Group.of.nepali.translators] [Bug 1892526] Re: dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.04-1ubuntu26.4

---
grub2 (2.04-1ubuntu26.4) focal; urgency=medium

  * grub-install: cherry-pick patch from grub-devel to make grub-install
fault tolerant. Create backup of files in /boot/grub, and restore them
on failure to complete grub-install. LP: #1891680
  * postinst.in: do not exit successfully when failing to show critical
grub-pc/install_devices_failed and grub-pc/install_devices_empty
prompts in non-interactive mode. This enables surfacing upgrade errors
to the users and/or automation. LP: #1891680
  * postinst.in: do not attempt to call grub-install upon fresh install of
grub-pc because it it a job of installers to do that after fresh
install. Fixup for the issue unmasked by above. LP: #1891680
  * grub-multi-install: fix non-interactive failures for grub-efi like it
was fixed in postinst for grub-pc. LP: #1891680
  * postinst.in: Fixup postinst.in, to attempt grub-install upon explicit
dpkg-reconfigure grub-pc. LP: #1892526

 -- Dimitri John Ledkov   Tue, 08 Sep 2020 11:24:35
+0100

** Changed in: grub2 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1892526

Title:
  dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Trusty:
  Confirmed
Status in grub2 source package in Xenial:
  Confirmed
Status in grub2 source package in Bionic:
  Confirmed
Status in grub2 source package in Focal:
  Fix Released
Status in grub2 source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * dpkg-reconfigure grub-pc no longer reinstalls grub, as it should.

  [Test Case]

   * Set grub-pc/install_devices to some invalid device that does not
  exist (i.e. /dev/hda)

   * Execute $ sudo dpkg-reconfigure grub-pc

  One should expect attempts to grub-instal onto /dev/hda, fail that,
  and see dialogues asking which devices to install grub-pc onto, and
  successfully install them.

  [Regression Potential]

   * We are patching, the recently/newly added postinst condition to
  skip trying to install grub-install during typical/regular upgrades.
  Further tighten the conditions there, to still force install grub-
  install when executing grub-reconfigure to be inline with existing
  documentation that this is the command to use when one wishes to
  reinstall grub-pc interactively.

  [Other Info]
   
   * Original bug report

  I recently had a RAID-5 disk failure and was greeted by an inoperable
  grub due to not having installed grub on all the disks.  I temporarily
  fixed this problem by manually running "grub-install" on the other
  disks in the array and got my system working.

  Previously it was advised to run "dpkg-reconfigure grub-pc" and select
  the relevant disks to ensure that future grub updates installed on all
  the disks in the array.  This command no longer prompts for the
  install disks due to the changed introduced by
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556.  In
  /var/lib/dpkg/info/grub-pc.postinst, the following elif block
  immediately precedes the elif block that prompts for grub-
  pc/install_devices and short circuits on all recent grub versions:

    elif dpkg --compare-versions "$2" ge 2.04-1ubuntu26; then
  # Avoid the possibility of breaking grub on SRU update
  # due to ABI change
  :

  I can confirm this issue is present on 20.04.1 and it appears to be
  present on 18.04.4 per https://askubuntu.com/questions/1212569/dpkg-
  reconfigure-grub-pc-no-option-to-select-boot-device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892526/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1891680] Re: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.04-1ubuntu26.4

---
grub2 (2.04-1ubuntu26.4) focal; urgency=medium

  * grub-install: cherry-pick patch from grub-devel to make grub-install
fault tolerant. Create backup of files in /boot/grub, and restore them
on failure to complete grub-install. LP: #1891680
  * postinst.in: do not exit successfully when failing to show critical
grub-pc/install_devices_failed and grub-pc/install_devices_empty
prompts in non-interactive mode. This enables surfacing upgrade errors
to the users and/or automation. LP: #1891680
  * postinst.in: do not attempt to call grub-install upon fresh install of
grub-pc because it it a job of installers to do that after fresh
install. Fixup for the issue unmasked by above. LP: #1891680
  * grub-multi-install: fix non-interactive failures for grub-efi like it
was fixed in postinst for grub-pc. LP: #1891680
  * postinst.in: Fixup postinst.in, to attempt grub-install upon explicit
dpkg-reconfigure grub-pc. LP: #1892526

 -- Dimitri John Ledkov   Tue, 08 Sep 2020 11:24:35
+0100

** Changed in: grub2 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1891680

Title:
  grub-pc needs to detect when debconf points to invalid drive and stop
  in preinst, before unpacking files, and also treat this as a failure
  in postinst

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Confirmed
Status in grub2 source package in Bionic:
  Confirmed
Status in grub2 source package in Focal:
  Fix Released
Status in grub2 source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * grub-pc currently installs new core to MBR and installs new modules
  to /boot in an unsafe manner, which may lead to incompatible
  combination of MBR and modules resulting in failure to boot.

  [Test Case]

   * Install using old point media, of an old release. I.e. 16.04.(p-1)
  for testing upgrades to 18.04 sru, in bios mode.

   * backup the contents of /boot

   * First we will test a case where target boot device exists, yet
  writes to it are denied, thus one can update modules, but cannot
  update the MBR.

   * install /etc/apparmor.d/usr.sbin.grub-install profile

  "/usr/sbin/grub-install" {
    capability,
    mount,
    ptrace,
    signal,
    unix,
    file,
    deny /dev/* w,
  }

     and load it with

    sudo apparmor_parser -r usr.sbin.grub-install

   * Upgrade to the package from next series-proposed, non-interactively

   * Observe the package installation has failed, the grub-pc package is
  in a broken state.

   * Compare the backup of /boot with current /boot, it should have
  remained the same, and is different to modules in
  /usr/lib/grub/i386-pc

   * Remove the apparmor profile /etc/apparmor.d/usr.sbin.grub-install

   * Reboot, reboot should be successful. If possible observe the
  version number in the grub menu, it should still be old.

   * Now we will test a case where a non-existing device ended up being
  configured in debconf. For example, due to old buggy cloud-init having
  been used during first boot, or because the VM got migrated from one
  hardware configuration to another (i.e. offline switch from SCSI sda,
  to VIRTIO vda).

   * Configure invalid grub-pc/install_devices to a non existing device
  (e.g. /dev/sdk)

   * Attempt non-interactive configuration of the grub-pc package

   * Observe the package fails, and the grub-pc package remains in a
  broken state.

   * Compare the backup of /boot with current /boot, it should have
  remained the same, and is different to modules in
  /usr/lib/grub/i386-pc

   * Reboot, reboot should be successful. If possible observe the
  version number in the grub menu, it should still be old.

   * Try to configure all the packages, interactively (i.e. using $ sudo
  dpkg --configure -a or by using $ sudo apt install -f) and ensure to
  select the right drive for grub installation offer

   * Observe that now /boot matches /usr/lib/grub/i386-pc contents, and
  is different from the backup taken at the start.

   * Reboot should be successful, and grub menu should have the new
  version number finally

  [Regression Potential]

   * Existing call to grub-install, is now split into two. And when any
     devices fail to configure, non-interactively error is reported just
     like it was already done with the interactive case.

     It means, it will fail configuration of the package, where
     previously it would report success. However, it is now safer and
     keeps the system bootable, whilst having unconfigured
     packages. This mostly affects non-interactive upgrades, as the
     interactive ones have always shown critical errors trying to
     correct grub-pc installation problems.

[Group.of.nepali.translators] [Bug 1821662] Re: [SRU] xfce4-weather-plugin 0.8.11

[Steve Langasek]

The version of xfce4-weather-plugin in the proposed pocket of Xenial
that was purported to fix this bug report has been removed because the
bugs that were to be fixed by the upload were not verified in a timely
(105 days) fashion.

** Tags removed: verification-needed-xenial

** Changed in: xfce4-weather-plugin (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1821662

Title:
  [SRU] xfce4-weather-plugin 0.8.11

Status in xfce4-weather-plugin package in Ubuntu:
  Fix Released
Status in xfce4-weather-plugin source package in Xenial:
  Won't Fix
Status in xfce4-weather-plugin source package in Bionic:
  Fix Released
Status in xfce4-weather-plugin source package in Cosmic:
  Fix Released
Status in xfce4-weather-plugin source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * Downstream bug: https://bugzilla.xfce.org/show_bug.cgi?id=14972

   * The met.no sunrise API version 1.1, used by xfce4-weather-plugin
  versions prior to 0.8.11, expired on 2019-02-15. As with previous
  expirations, this is expected to make the plugin stop working entirely
  at some point.

   * Ubuntu 19.04 is unaffected, as xfce4-weather-plugin 0.9.1 includes
  the newer API

   * Affected supported releases include: 16.04, 18.04, 18.10

  [Test Case]

   * Add the weather plugin to the Xfce panel.

   * Right-click on the plugin and select Preferences to configure it.

   * After configuring the plugin, click on it to show the Weather
  Report dialog.

   * Click on the details tab.
     * With version 0.8.10 and older, the following message is displayed on the 
weather details:
   Met.no sunrise API states that this version of the webservice
   is deprecated, and the plugin needs to be adapted to use
   a newer version, or it will stop working within a few months.
   Please file a bug on https://bugzilla.xfce.org if no one
   else has done so yet.
   * Alternatively, ~/.xsession-errors will be littered with this message: 
(wrapper-1.0:1828): weather-WARNING **: 20:09:40.088: Download of astronomical 
data failed with HTTP Status Code 404, Reason phrase: Not Found
     * With version 0.8.11 and 0.9.1, the notice and error messages are no 
longer displayed. Additionally, "Moon phase" should be populated under 
"Astronomical Data".

   * Verify that the weather forecast works with the newer version by
  right-clicking on the plugin and selecting "Refresh".

  [Regression Potential]

   * Along with the updated API, this release now uses alternate https 
connections. If SSL certificates expire (unlikely and rare), these connections 
will fail:
     http://geoip.xfce.org/ -> https://geoip.xfce.org/
     http://api.geonames.org -> https://secure.geonames.org

   * Other regression potential is minimal.

  [0.8.11 Release Notes]

  - Use the latest sunrise API (2.0) (bug #14972)
  - Use https for all connections
  - Fix link to the met.no logo
  - Translation updates: Albanian, Belarusian, Catalan, Chinese (China),
    Danish, Dutch, French, Hungarian, Korean, Lithuanian, Russian, Swedish

  https://git.xfce.org/panel-plugins/xfce4-weather-
  plugin/log/?h=master-0.8

  [ Other Notes ]

  For those reviewing the code/commits, the API replacement consists of
  3 commits:

  1. API replacement (not including moonphase): https://git.xfce.org
  /panel-plugins/xfce4-weather-
  plugin/commit/?h=master-0.8=3653203bd4ac03ee3c6bee7d0e35144a94cc27bb

  2. Code improvements: https://git.xfce.org/panel-plugins/xfce4
  -weather-
  plugin/commit/?h=master-0.8=f2e44941a70dd92c6e0858b1358b9e3eb148da85

  3. Fixing the moonphase integration with the 2.0 API:
  https://git.xfce.org/panel-plugins/xfce4-weather-
  plugin/commit/?h=master-0.8=1cc55b7fc509a1ccb98b686b1b102b38fe68348d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1821662/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1894686] Re: xenial/linux-gcp: 4.15.0-1084.95~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  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
  kernel-stable-master-bug: 1894687
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 10. September 2020 14:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1894684
xenial/linux-gcp/gke-kernel: bug 1894685
  variant: debs
  versions:
main: 4.15.0-1084.95~16.04.1
meta: 4.15.0.1084.85
signed: 4.15.0-1084.95~16.04.1

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1894686

Title:
  xenial/linux-gcp: 4.15.0-1084.95~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp source package in Xenial:
  New

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
  kernel-stable-master-bug: 1894687
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 10. September 2020 14:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1894684
xenial/linux-gcp/gke-kernel: bug 1894685
  variant: debs
  versions:
main: 4.15.0-1084.95~16.04.1
meta: 4.15.0.1084.85
signed: 4.15.0-1084.95~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1894686/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1894677] Re: xenial/linux-aws-hwe: 4.15.0-1083.87~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  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
  kernel-stable-master-bug: 1894678
  packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
  phase: Testing
  phase-changed: Thursday, 10. September 2020 09:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs
  versions:
main: 4.15.0-1083.87~16.04.1
meta: 4.15.0.1083.79

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1894677

Title:
  xenial/linux-aws-hwe: 4.15.0-1083.87~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws-hwe source package in Xenial:
  New

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
  kernel-stable-master-bug: 1894678
  packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
  phase: Testing
  phase-changed: Thursday, 10. September 2020 09:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs
  versions:
main: 4.15.0-1083.87~16.04.1
meta: 4.15.0.1083.79

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1894677/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1891680] Re: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst

[Brian Murray]

** Changed in: grub2 (Ubuntu Focal)
   Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1891680

Title:
  grub-pc needs to detect when debconf points to invalid drive and stop
  in preinst, before unpacking files, and also treat this as a failure
  in postinst

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Confirmed
Status in grub2 source package in Bionic:
  Confirmed
Status in grub2 source package in Focal:
  Fix Committed
Status in grub2 source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * grub-pc currently installs new core to MBR and installs new modules
  to /boot in an unsafe manner, which may lead to incompatible
  combination of MBR and modules resulting in failure to boot.

  [Test Case]

   * Install using old point media, of an old release. I.e. 16.04.(p-1)
  for testing upgrades to 18.04 sru, in bios mode.

   * backup the contents of /boot

   * First we will test a case where target boot device exists, yet
  writes to it are denied, thus one can update modules, but cannot
  update the MBR.

   * install /etc/apparmor.d/usr.sbin.grub-install profile

  "/usr/sbin/grub-install" {
    capability,
    mount,
    ptrace,
    signal,
    unix,
    file,
    deny /dev/* w,
  }

     and load it with

    sudo apparmor_parser -r usr.sbin.grub-install

   * Upgrade to the package from next series-proposed, non-interactively

   * Observe the package installation has failed, the grub-pc package is
  in a broken state.

   * Compare the backup of /boot with current /boot, it should have
  remained the same, and is different to modules in
  /usr/lib/grub/i386-pc

   * Remove the apparmor profile /etc/apparmor.d/usr.sbin.grub-install

   * Reboot, reboot should be successful. If possible observe the
  version number in the grub menu, it should still be old.

   * Now we will test a case where a non-existing device ended up being
  configured in debconf. For example, due to old buggy cloud-init having
  been used during first boot, or because the VM got migrated from one
  hardware configuration to another (i.e. offline switch from SCSI sda,
  to VIRTIO vda).

   * Configure invalid grub-pc/install_devices to a non existing device
  (e.g. /dev/sdk)

   * Attempt non-interactive configuration of the grub-pc package

   * Observe the package fails, and the grub-pc package remains in a
  broken state.

   * Compare the backup of /boot with current /boot, it should have
  remained the same, and is different to modules in
  /usr/lib/grub/i386-pc

   * Reboot, reboot should be successful. If possible observe the
  version number in the grub menu, it should still be old.

   * Try to configure all the packages, interactively (i.e. using $ sudo
  dpkg --configure -a or by using $ sudo apt install -f) and ensure to
  select the right drive for grub installation offer

   * Observe that now /boot matches /usr/lib/grub/i386-pc contents, and
  is different from the backup taken at the start.

   * Reboot should be successful, and grub menu should have the new
  version number finally

  [Regression Potential]

   * Existing call to grub-install, is now split into two. And when any
     devices fail to configure, non-interactively error is reported just
     like it was already done with the interactive case.

     It means, it will fail configuration of the package, where
     previously it would report success. However, it is now safer and
     keeps the system bootable, whilst having unconfigured
     packages. This mostly affects non-interactive upgrades, as the
     interactive ones have always shown critical errors trying to
     correct grub-pc installation problems.

     The first stage of grub-install only tries to update the MBR,
     whilst utilizing tmpdirectory to create the core image. This is a
     slight increase in disk space usage, as previously core was created
     in-pace in /boot. Then whilst tmpdir is still populated, /boot
     modules and core are upgraded.

     These changes do not address multi-mbr systems, or cases where
     updating modules fails. For example, it is possible that MBR update
     is successful, yet writting updated modules fails (out of disk space),
     in such scenario MBR is not rolled back to previous one. Or a case
     where MBR updates have succeeded, but only on some devices.
     A choice has been made to update modules in /boot, if at least one
     device has a successful MBR update. No backup, or rollback of MBR is
     performed if module updates fail. This is tricky to do, as it is
     uncertain if current MBR matches the core.img & boot.img from /boot, or
     if some other bootsectors code was in use before. Ideally in the
     future, grub-install itself will be able to stage module 

[Group.of.nepali.translators] [Bug 1891680] Re: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst

[Louis Fal]

** Changed in: grub2 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1891680

Title:
  grub-pc needs to detect when debconf points to invalid drive and stop
  in preinst, before unpacking files, and also treat this as a failure
  in postinst

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2 source package in Xenial:
  Confirmed
Status in grub2 source package in Bionic:
  Confirmed
Status in grub2 source package in Focal:
  Fix Released
Status in grub2 source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * grub-pc currently installs new core to MBR and installs new modules
  to /boot in an unsafe manner, which may lead to incompatible
  combination of MBR and modules resulting in failure to boot.

  [Test Case]

   * Install using old point media, of an old release. I.e. 16.04.(p-1)
  for testing upgrades to 18.04 sru, in bios mode.

   * backup the contents of /boot

   * First we will test a case where target boot device exists, yet
  writes to it are denied, thus one can update modules, but cannot
  update the MBR.

   * install /etc/apparmor.d/usr.sbin.grub-install profile

  "/usr/sbin/grub-install" {
    capability,
    mount,
    ptrace,
    signal,
    unix,
    file,
    deny /dev/* w,
  }

     and load it with

    sudo apparmor_parser -r usr.sbin.grub-install

   * Upgrade to the package from next series-proposed, non-interactively

   * Observe the package installation has failed, the grub-pc package is
  in a broken state.

   * Compare the backup of /boot with current /boot, it should have
  remained the same, and is different to modules in
  /usr/lib/grub/i386-pc

   * Remove the apparmor profile /etc/apparmor.d/usr.sbin.grub-install

   * Reboot, reboot should be successful. If possible observe the
  version number in the grub menu, it should still be old.

   * Now we will test a case where a non-existing device ended up being
  configured in debconf. For example, due to old buggy cloud-init having
  been used during first boot, or because the VM got migrated from one
  hardware configuration to another (i.e. offline switch from SCSI sda,
  to VIRTIO vda).

   * Configure invalid grub-pc/install_devices to a non existing device
  (e.g. /dev/sdk)

   * Attempt non-interactive configuration of the grub-pc package

   * Observe the package fails, and the grub-pc package remains in a
  broken state.

   * Compare the backup of /boot with current /boot, it should have
  remained the same, and is different to modules in
  /usr/lib/grub/i386-pc

   * Reboot, reboot should be successful. If possible observe the
  version number in the grub menu, it should still be old.

   * Try to configure all the packages, interactively (i.e. using $ sudo
  dpkg --configure -a or by using $ sudo apt install -f) and ensure to
  select the right drive for grub installation offer

   * Observe that now /boot matches /usr/lib/grub/i386-pc contents, and
  is different from the backup taken at the start.

   * Reboot should be successful, and grub menu should have the new
  version number finally

  [Regression Potential]

   * Existing call to grub-install, is now split into two. And when any
     devices fail to configure, non-interactively error is reported just
     like it was already done with the interactive case.

     It means, it will fail configuration of the package, where
     previously it would report success. However, it is now safer and
     keeps the system bootable, whilst having unconfigured
     packages. This mostly affects non-interactive upgrades, as the
     interactive ones have always shown critical errors trying to
     correct grub-pc installation problems.

     The first stage of grub-install only tries to update the MBR,
     whilst utilizing tmpdirectory to create the core image. This is a
     slight increase in disk space usage, as previously core was created
     in-pace in /boot. Then whilst tmpdir is still populated, /boot
     modules and core are upgraded.

     These changes do not address multi-mbr systems, or cases where
     updating modules fails. For example, it is possible that MBR update
     is successful, yet writting updated modules fails (out of disk space),
     in such scenario MBR is not rolled back to previous one. Or a case
     where MBR updates have succeeded, but only on some devices.
     A choice has been made to update modules in /boot, if at least one
     device has a successful MBR update. No backup, or rollback of MBR is
     performed if module updates fail. This is tricky to do, as it is
     uncertain if current MBR matches the core.img & boot.img from /boot, or
     if some other bootsectors code was in use before. Ideally in the
     future, grub-install itself will be able to stage module 

[Group.of.nepali.translators] [Bug 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu21.29

---
systemd (229-4ubuntu21.29) xenial; urgency=medium

  [ Dan Streetman ]
  * 
d/p/lp1881312/0001-core-don-t-dispatch-load-queue-when-setting-Slice-fo.patch,
d/p/lp1881312/0002-run-make-slice-work-in-conjunction-with-scope.patch:
- run new scope unit in specified slice (LP: #1881312)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5a778c3cd93e3d684602146f281f315f30778a8
  * d/p/lp1877176-sd-dhcp-client-validate-hostnames-stricter-7308.patch:
- strictly validate hostname sent to dhcp server (LP: #1877176)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a1f1c41dcd860fcba6be42a2153cfe4315ebf17
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=43357bd260a1c3e7b4951d33cbacaebda1d086b3
  * d/p/lp1698388-journal-remote-Ensure-reallocation-of-source-buf-doe.patch:
- Fix assertion failure when journald source->filled < source->size
  (LP: #1698388)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1cc15b88113510227e5a76654e103ef54a8b8f3

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8dc9ef188944349169044d8974a4ffa55c66be9d

 -- Heitor Alves de Siqueira   Tue, 07 Jul 2020
17:28:11 -0400

** Changed in: systemd (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1876018

Title:
  40-vm-hotadd.rules attempts to set non-existent sysfs parameters

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  40-vm-hotadd.rules unconditionally tries onlining memory, which
  results in logged error messages if the memory is already online

  [test case]

  since this rules file restricts operation to only hyper-v or xen
  guests, boot a hyper-v or xen vm guest, and check for logged error
  msgs like:

  Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
  /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
  ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
  argument

  alternately, to test on a vm guest other than hyper-v or xen,
  comment/remove the 'GOTO="vm_hotadd_end"' line from the rules file and
  reboot.

  [regression potential]

  as this adds a check before attempting to online memory for hyper-v
  and xen vm guests, any regression would likely involve failure to
  correctly online all memory on those guest platforms.

  [scope]

  this rule has been around for a long time, so is needed for x/b/f/g.

  [original description]

  In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
  tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
  resulting in warnings such as:

  Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
  /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
  ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
  argument

  Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
  removed, or something else. This behavior is present on systems
  upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
  first reboot of the VM.

  udev: 245.4-4ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1876600] Re: cookie overruns can cause org.freedesktop.systemd1 dbus to hang

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu21.29

---
systemd (229-4ubuntu21.29) xenial; urgency=medium

  [ Dan Streetman ]
  * 
d/p/lp1881312/0001-core-don-t-dispatch-load-queue-when-setting-Slice-fo.patch,
d/p/lp1881312/0002-run-make-slice-work-in-conjunction-with-scope.patch:
- run new scope unit in specified slice (LP: #1881312)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5a778c3cd93e3d684602146f281f315f30778a8
  * d/p/lp1877176-sd-dhcp-client-validate-hostnames-stricter-7308.patch:
- strictly validate hostname sent to dhcp server (LP: #1877176)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a1f1c41dcd860fcba6be42a2153cfe4315ebf17
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=43357bd260a1c3e7b4951d33cbacaebda1d086b3
  * d/p/lp1698388-journal-remote-Ensure-reallocation-of-source-buf-doe.patch:
- Fix assertion failure when journald source->filled < source->size
  (LP: #1698388)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1cc15b88113510227e5a76654e103ef54a8b8f3

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8dc9ef188944349169044d8974a4ffa55c66be9d

 -- Heitor Alves de Siqueira   Tue, 07 Jul 2020
17:28:11 -0400

** Changed in: systemd (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1876600

Title:
  cookie overruns can cause org.freedesktop.systemd1 dbus to hang

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Long-running services overflow the sd_bus->cookie counter, causing further 
communication with org.freedesktop.systemd1 to stall.

  [Description]
  Systemd dbus messages include a "cookie" value to uniquely identify them in 
their bus context. This value is obtained from the bus header, and incremented 
for each exchanged message in the same bus object. For services that run for 
longer periods of time and keep communicating through dbus, it's possible to 
overflow the cookie value, causing further messages to the 
org.freedesktop.systemd1 dbus to fail. This can lead to these services becoming 
unresponsive, as they get stuck trying to communicate with invalid bus cookie 
values.

  This issue has been fixed upstream by the commit below:
  -  sd-bus: deal with cookie overruns (1f82f5bb4237)

  $ git describe --contains 1f82f5bb4237
  v242-rc1~228

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.27 | xenial-security | source, ...
   systemd | 229-4ubuntu21.27 | xenial-updates  | source, ...
   systemd | 229-4ubuntu21.28 | xenial-proposed | source, ...
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.38 | bionic-security | source, ...
   systemd | 237-3ubuntu10.39 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.40 | bionic-proposed | source, ... <
   systemd | 242-7ubuntu3 | eoan| source, ...

  Releases starting with Eoan already have this fix.

  [Test Case]
  There doesn't seem to be an easy test case for this, as the cookie values 
start at zero and won't overflow until (1<<32). There have been reports from 
users hitting this on Kubernetes clusters continuously running for longer 
periods (~5 months).
  Using GDB, we can construct an artificial test case to test the cookie 
overflow. The test case below performs the following steps:

  1. Create a new system bus object through sd_bus_default_system()
  2. Allocate and append a new method_call message to the bus
  3. Send the message through sd_bus_call()
  4. Handle the response message and free up the message objects

  It's essentially the example code from the
  sd_bus_message_new_method_call() manpage, with minor modifications:
  this is done continuously, to keep incrementing the bus cookie value.
  We step in with GDB when it reaches 0x1, and set its value to
  0xff00 which then causes the test program to fail shortly
  afterwards. An example test run of an impacted system:

  ubuntu@bionic:~$ gcc -Wall test.c -o cookie -lsystemd -g
  ubuntu@bionic:~$ gdb --batch --command=test.gdb --args ./cookie
  Breakpoint 1 at 0xe61: file test.c, line 38.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  

[Group.of.nepali.translators] [Bug 1698388] Re: Assertion failure in journal-remote-parse.c

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu21.29

---
systemd (229-4ubuntu21.29) xenial; urgency=medium

  [ Dan Streetman ]
  * 
d/p/lp1881312/0001-core-don-t-dispatch-load-queue-when-setting-Slice-fo.patch,
d/p/lp1881312/0002-run-make-slice-work-in-conjunction-with-scope.patch:
- run new scope unit in specified slice (LP: #1881312)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5a778c3cd93e3d684602146f281f315f30778a8
  * d/p/lp1877176-sd-dhcp-client-validate-hostnames-stricter-7308.patch:
- strictly validate hostname sent to dhcp server (LP: #1877176)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a1f1c41dcd860fcba6be42a2153cfe4315ebf17
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=43357bd260a1c3e7b4951d33cbacaebda1d086b3
  * d/p/lp1698388-journal-remote-Ensure-reallocation-of-source-buf-doe.patch:
- Fix assertion failure when journald source->filled < source->size
  (LP: #1698388)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1cc15b88113510227e5a76654e103ef54a8b8f3

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8dc9ef188944349169044d8974a4ffa55c66be9d

 -- Heitor Alves de Siqueira   Tue, 07 Jul 2020
17:28:11 -0400

** Changed in: systemd (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1698388

Title:
  Assertion failure in journal-remote-parse.c

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [impact]

  assertion failure in systemd-journal-remote

  [test case]

  only happens under specific circumstances, which is unclear exactly
  how to reproduce it

  [regression potential]

  any regression would likely result in the failure/crash of systemd-
  journal-remote program while processing data from a remote source.

  [scope]

  this is needed only for x.

  this is fixed by commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1 which
  is included upstream starting in v230, so this is already included in
  b and later.

  [original description]

  I am observing the following assertion failure in systemd-journal-
  remote:

  Assertion 'source->filled <= source->size' failed at ../src/journal-
  remote/journal-remote-parse.c:95, function get_line(). Aborting.

  Systemd version:

  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Ubuntu release:

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Package version:

  systemd:
    Installed: 229-4ubuntu13
    Candidate: 229-4ubuntu17

  It looks like this issue has been fixed upstream in v230, specifically
  in commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1. Could this
  particular commit be backported?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698388/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1881312] Re: systemd-run does not make the new scope unit part of the slice specified via the --slice arg

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu21.29

---
systemd (229-4ubuntu21.29) xenial; urgency=medium

  [ Dan Streetman ]
  * 
d/p/lp1881312/0001-core-don-t-dispatch-load-queue-when-setting-Slice-fo.patch,
d/p/lp1881312/0002-run-make-slice-work-in-conjunction-with-scope.patch:
- run new scope unit in specified slice (LP: #1881312)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5a778c3cd93e3d684602146f281f315f30778a8
  * d/p/lp1877176-sd-dhcp-client-validate-hostnames-stricter-7308.patch:
- strictly validate hostname sent to dhcp server (LP: #1877176)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a1f1c41dcd860fcba6be42a2153cfe4315ebf17
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=43357bd260a1c3e7b4951d33cbacaebda1d086b3
  * d/p/lp1698388-journal-remote-Ensure-reallocation-of-source-buf-doe.patch:
- Fix assertion failure when journald source->filled < source->size
  (LP: #1698388)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1cc15b88113510227e5a76654e103ef54a8b8f3

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8dc9ef188944349169044d8974a4ffa55c66be9d

 -- Heitor Alves de Siqueira   Tue, 07 Jul 2020
17:28:11 -0400

** Changed in: systemd (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1881312

Title:
  systemd-run does not make the new scope unit part of the slice
  specified via the --slice arg

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [impact]

  running 'systemd-run --scope --slice=$SLICE $PROGRAM' does not start
  the program under $SLICE, instead it starts it under system.slice

  [test case]

  root:~# systemd-run --scope --slice=user-1000.slice sleep 1000
  Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope.
  ^Z
  [3]+  Stopped systemd-run --scope --slice=user-1000.slice 
sleep 1000
  root:~# bg
  [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 &
  root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope
  Slice=system.slice

  [regression potential]

  This defers running the manager unit load queue when setting the slice
  for a transient unit, as well as actually passing the slice parameter
  over the bus when using --scope, so any regression would very likely
  involve incorrectly setting the slice for a scope and/or problems when
  processing transient units that specify a slice.

  [scope]

  this is needed only for Xenial.

  this is fixed upstream by
  https://github.com/systemd/systemd/pull/3094
  which is included starting in v230, so is included in Bionic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1881312/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1877176] Re: 64-char hostname causes dhcp server to reject lease

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu21.29

---
systemd (229-4ubuntu21.29) xenial; urgency=medium

  [ Dan Streetman ]
  * 
d/p/lp1881312/0001-core-don-t-dispatch-load-queue-when-setting-Slice-fo.patch,
d/p/lp1881312/0002-run-make-slice-work-in-conjunction-with-scope.patch:
- run new scope unit in specified slice (LP: #1881312)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b5a778c3cd93e3d684602146f281f315f30778a8
  * d/p/lp1877176-sd-dhcp-client-validate-hostnames-stricter-7308.patch:
- strictly validate hostname sent to dhcp server (LP: #1877176)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a1f1c41dcd860fcba6be42a2153cfe4315ebf17
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=43357bd260a1c3e7b4951d33cbacaebda1d086b3
  * d/p/lp1698388-journal-remote-Ensure-reallocation-of-source-buf-doe.patch:
- Fix assertion failure when journald source->filled < source->size
  (LP: #1698388)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d1cc15b88113510227e5a76654e103ef54a8b8f3

  [ Heitor Alves de Siqueira ]
  * d/p/lp1876600-sd-bus-deal-with-cookie-overruns.patch:
- deal with dbus cookie overruns (LP: #1876600)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8dc9ef188944349169044d8974a4ffa55c66be9d

 -- Heitor Alves de Siqueira   Tue, 07 Jul 2020
17:28:11 -0400

** Changed in: systemd (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1877176

Title:
  64-char hostname causes dhcp server to reject lease

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [impact]

  a systemd with a 64-character hostname (the maximum hostname length
  for Linux) will cause a dhcp server to reject its dhcp lease due to
  passing the invalid hostname in the dhcp lease request.

  [test case]

  $ cat /etc/systemd/network/10-ens3.network
  [Match]
  Name=ens3

  [Network]
  DHCP=yes

  set hostname to 64-char name, e.g.:

  $ sudo hostnamectl set-hostname
  a123456789b123456789c123456789d123456789e123456789f123456789g123

  restart networkd:

  $ sudo systemctl restart systemd-networkd

  check logs:

  root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# 
journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error'
  May 06 19:01:30 
a123456789b123456789c123456789d123456789e123456789f123456789g123 
systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument

  [regression potential]

  Any regression would likely result in failure configuring/processing
  dhcpv4 server response, or rejection from the dhcpv4 server.

  [scope]

  this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which
  is included in Bionic and later.  This is needed only for Xenial.

  [other info]

  this is a follow on to bug 1862232, which corrected sd-dhcp-client.c
  to continue networkd dhcp even if the hostname is invalid, however the
  older code in Xenial doesn't correctly detect the invalid hostname, so
  this additional patch is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877176/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.136ubuntu6.3

---
initramfs-tools (0.136ubuntu6.3) focal; urgency=medium

  * scripts/functions: Prevent printf error carry over if the wrong
console is set. (LP: #1879987)
  The function _log_msg() is "void" typed, returning whatever its
  last command returns. This function is the basic building block
  for all error/warning messages in initramfs-tools. If a bad console
  is provided to kernel on command-line, printf returns error, and so
  this error is carried over in _log_msg(). Happens that checkfs()
  function has a loop that runs forever in this scenario (*if* fsck
  is not present in initramfs and "quiet" is not passed in the
  command-line). If that happens, boot is stuck and cannot progress.
  The simple fix hereby merged is to return zero on _log_msg().

  * scripts/local: Re-execute cryptroot local-block script. (LP: #1879980)
  Currently, if an encrypted rootfs is configured on top of a MD RAID1
  array and such array gets degraded (like a member is removed/failed),
  initramfs-tools cannot mount the rootfs and the boot fails. We fix
  that issue here by allowing cryptroot script to re-run on local-block
  stage, given that mdadm is able to activate a degraded array in that
  point. There is a cryptsetup counter-part for this fix, but alone the
  initramfs-tools portion is innocuous.

  * d/tests: Add explicit call to partprobe on net test, specially in
prep-image and run-image. (LP: #1893675)

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Mon, 31 Aug 2020
13:43:29 -0300

** Changed in: initramfs-tools (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1879987

Title:
  machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  In Progress
Status in initramfs-tools source package in Bionic:
  In Progress
Status in initramfs-tools source package in Eoan:
  Won't Fix
Status in initramfs-tools source package in Focal:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  * Currently, if users provide the wrong console in kernel command-line
  (like console=ttyS1, when the right one is ttyS0) *and* "quiet"
  parameter is not provided, we may face an infinite loop on initramfs-
  tools, effectively blocking the boot.

  * Details are: the _log_msg() functions is "void" typed, which means it 
returns whatever its last command returns; this function is the basic building 
block for all error/warning messages in initramfs-tools. In case a bad console 
was provided to kernel on command-line, printf (and apparently all 
write()-related functions) returns error, and so this error is carried over in 
_log_msg().
   
  * Happens that checkfs() function has a loop that runs forever in this 
scenario (*if* fsck is not present in initramfs, and obviously if "quiet" is 
not provided in the command-line). The situation is easily reproducible.

  * This SRU proposes a pretty simple fix: return zero on _log_msg(). We
  should definitely not brake the boot due to error log functions.

  
  [Test Case]

  * To reproduce this, one must boot a system (virtual machine is good)
  with the wrong console set on kernel command-line through the
  "console=" parameter *and* not pass the "quiet" parameter.

  * Also, e2fsck tool shouldn't be present in the initrd - for that, the
  6th field of /etc/fstab (fs_passno) should be 0 and initrd must be
  recreated after that. This is the default in Ubuntu, though.

  
  [Regression Potential]

  * The regression potential is small, we're just returning 0 after a
  printf that is executed in error paths, so I don't expect any issues
  from that. But in case something bad happens after this change, I
  expect a more friendly" breakage, like an initramfs panic (drop to a
  shell), not a silent failure or boot-loop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.136ubuntu6.3

---
initramfs-tools (0.136ubuntu6.3) focal; urgency=medium

  * scripts/functions: Prevent printf error carry over if the wrong
console is set. (LP: #1879987)
  The function _log_msg() is "void" typed, returning whatever its
  last command returns. This function is the basic building block
  for all error/warning messages in initramfs-tools. If a bad console
  is provided to kernel on command-line, printf returns error, and so
  this error is carried over in _log_msg(). Happens that checkfs()
  function has a loop that runs forever in this scenario (*if* fsck
  is not present in initramfs and "quiet" is not passed in the
  command-line). If that happens, boot is stuck and cannot progress.
  The simple fix hereby merged is to return zero on _log_msg().

  * scripts/local: Re-execute cryptroot local-block script. (LP: #1879980)
  Currently, if an encrypted rootfs is configured on top of a MD RAID1
  array and such array gets degraded (like a member is removed/failed),
  initramfs-tools cannot mount the rootfs and the boot fails. We fix
  that issue here by allowing cryptroot script to re-run on local-block
  stage, given that mdadm is able to activate a degraded array in that
  point. There is a cryptsetup counter-part for this fix, but alone the
  initramfs-tools portion is innocuous.

  * d/tests: Add explicit call to partprobe on net test, specially in
prep-image and run-image. (LP: #1893675)

 -- gpicc...@canonical.com (Guilherme G. Piccoli)  Mon, 31 Aug 2020
13:43:29 -0300

** Changed in: initramfs-tools (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1879980

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  In Progress
Status in initramfs-tools source package in Bionic:
  In Progress
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  In Progress
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top 

[Group.of.nepali.translators] [Bug 1895294] Re: Fix Raccoon vulnerability (CVE-2020-1968)

[Dimitri John Ledkov]

It is true that said vulnerability is not patched in xenial; but also it
is low; and no public patches for it exist.

Please upgrade to bionic or focal? which are unaffected / fixes
released?

** Information type changed from Public to Public Security

** Also affects: openssl (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: openssl (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: openssl (Ubuntu)
   Status: New => Fix Released

** Changed in: openssl (Ubuntu Xenial)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1895294

Title:
  Fix Raccoon vulnerability (CVE-2020-1968)

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Xenial:
  Confirmed

Bug description:
  Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been
  patched yet against the Raccoon Attack (CVE-2020-1968):

  - https://www.openssl.org/news/secadv/20200909.txt
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968
  - https://raccoon-attack.com/

  Ubuntu's CVE tracker still lists this as NEEDED for Xenial:

  - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html
  - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html

  Other supported Ubuntu releases use versions of OpenSSL that are not
  affected.

  Indeed:

    $ apt-cache policy openssl
    openssl:
  Installed: 1.0.2g-1ubuntu4.16

    $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched"
    Not patched

  What is the status?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895294/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1893428] Re: xenial/linux-fips: 4.4.0-1046.51 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => In Progress

** Description changed:

  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
  kernel-stable-master-bug: 1893431
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Promote to Proposed
- phase-changed: Tuesday, 15. September 2020 12:21 UTC
+ phase: Testing
+ phase-changed: Tuesday, 15. September 2020 12:45 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-signing-to-proposed: Ongoing -- review in progress
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  variant: debs
  versions:
main: 4.4.0-1046.51
meta: 4.4.0.1046.48
signed: 4.4.0-1046.51

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1893428

Title:
  xenial/linux-fips: 4.4.0-1046.51 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux source package in Xenial:
  Confirmed

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
  kernel-stable-master-bug: 1893431
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Testing
  phase-changed: Tuesday, 15. September 2020 12:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs
  versions:
main: 4.4.0-1046.51
meta: 4.4.0.1046.48
signed: 4.4.0-1046.51

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1893428/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1893425] Re: xenial/linux-raspi2: 4.4.0-1139.148 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1893425

Title:
  xenial/linux-raspi2: 4.4.0-1139.148 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 source package in Xenial:
  Confirmed

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
  kernel-stable-master-bug: 1893431
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Thursday, 03. September 2020 11:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1893424
  variant: debs
  versions:
main: 4.4.0-1139.148
meta: 4.4.0.1139.139

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1893425/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1893427] Re: xenial/linux-snapdragon: 4.4.0-1143.152 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1893427

Title:
  xenial/linux-snapdragon: 4.4.0-1143.152 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon source package in Xenial:
  Confirmed

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
  kernel-stable-master-bug: 1893431
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Friday, 04. September 2020 19:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1893426
  variant: debs
  versions:
main: 4.4.0-1143.152
meta: 4.4.0.1143.135

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1893427/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1893427] Re: xenial/linux-snapdragon: 4.4.0-1143.152 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1893427

Title:
  xenial/linux-snapdragon: 4.4.0-1143.152 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon source package in Xenial:
  Confirmed

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
  kernel-stable-master-bug: 1893431
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Friday, 04. September 2020 19:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1893426
  variant: debs
  versions:
main: 4.4.0-1143.152
meta: 4.4.0.1143.135

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1893427/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1893425] Re: xenial/linux-raspi2: 4.4.0-1139.148 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1893425

Title:
  xenial/linux-raspi2: 4.4.0-1139.148 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 source package in Xenial:
  Confirmed

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
  kernel-stable-master-bug: 1893431
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Thursday, 03. September 2020 11:21 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1893424
  variant: debs
  versions:
main: 4.4.0-1139.148
meta: 4.4.0.1139.139

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1893425/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1893431] Re: xenial/linux: 4.4.0-190.220 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1893431

Title:
  xenial/linux: 4.4.0-190.220 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux source package in Xenial:
  Confirmed

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
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Monday, 31. August 2020 21:04 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1893429
trusty/linux-lts-xenial: bug 1893430
xenial/linux-aws: bug 1893420
xenial/linux-cascade: bug 1893422
xenial/linux-fips: bug 1893428
xenial/linux-kvm: bug 1893423
xenial/linux-raspi2: bug 1893425
xenial/linux-snapdragon: bug 1893427
xenial/linux/caracalla-kernel: bug 1893416
xenial/linux/pc-kernel: bug 1893417
xenial/linux/stlouis-kernel: bug 1893418
  variant: debs
  versions:
main: 4.4.0-190.220
meta: 4.4.0.190.196
signed: 4.4.0-190.220

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1893431/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1893428] Re: xenial/linux-fips: 4.4.0-1046.51 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Description changed:

  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
  kernel-stable-master-bug: 1893431
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Promote to Proposed
- phase-changed: Tuesday, 15. September 2020 08:16 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Tuesday, 15. September 2020 11:51 UTC
  reason:
-   promote-to-proposed: Stalled -- packages copying to Signing
- signed:depwait
+   promote-signing-to-proposed: Pending -- ready for review
  variant: debs
  versions:
main: 4.4.0-1046.51
meta: 4.4.0.1046.48
signed: 4.4.0-1046.51

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1893428

Title:
  xenial/linux-fips: 4.4.0-1046.51 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux source package in Xenial:
  Confirmed

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
  kernel-stable-master-bug: 1893431
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 15. September 2020 11:51 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review
  variant: debs
  versions:
main: 4.4.0-1046.51
meta: 4.4.0.1046.48
signed: 4.4.0-1046.51

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1893428/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1894677] Re: xenial/linux-aws-hwe: 4.15.0-1083.87~16.04.1 -proposed tracker

[Po-Hsu Lin]

4.15.0-1083.87~16.04.1 - aws
Regression test CMPL, RTB.

Issue to note in amd64 (aws):
  ubuntu_kernel_selftests - rtnetlink.sh in net returning 1 for a skipped test 
(bug 1895258)
  ubuntu_kvm_unti_tests - 2 failures in apic (bug 1853433) vmx (bug 1821394) 1 
failure in vmx_apic_passthrough_thread (bug 1822309) vmx_hlt_with_rvi_test (bug 
1822308) vmx_host_state_area (bug 1866585) vmx_intr_window_test (bug 1866586) 
vmx_nm_test (bug 1866587) vmx_nmi_window_test (bug 1866588) 
vmx_pending_event_test (bug 1866591) on bare-metal nodes
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) 
fanotify09 case 3 (bug 1876684) kill11 (bug 1865965) move_pages12 on some 
instances (bug 1831043) pkey01 on some instances (c5.metal) (bug 1849093) 
quotactl04 (bug 1854153) shmctl04 (bug 1895276) statx05 (bug 1798524) 
clock_nanosleep02 (bug 1872388) on some instances

Skipped / blacklisted:
 * ubuntu_bpf
 * ubuntu_ltp

Issue to note in arm64 (aws):
  ubuntu_kernel_selftests - memory-hotplug non-executable (bug 1892816) 
rtnetlink.sh in net returning 1 for a skipped test (bug 1895258)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) 
fanotify09 case 3 (bug 1876684) kill11 (bug 1865965) quotactl04 (bug 1854153) 
shmctl04 (bug 1895276) statx05 (bug 1798524) clock_nanosleep02 on some 
instances (bug 1872388)
  ubuntu_lxc - lxc-test-apparmor-mount failed with Unable to fetch GPG key from 
keyserver

Skipped / blacklisted:
 * iosched_bugs
 * monotonic_time
 * ubuntu_32_on_64
 * ubuntu_bpf
 * ubuntu_ltp
 * ubuntu_seccomp
 * ubuntu_sysdig_smoke_test


** Changed in: kernel-sru-workflow/regression-testing
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1894677

Title:
  xenial/linux-aws-hwe: 4.15.0-1083.87~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws-hwe source package in Xenial:
  New

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
  kernel-stable-master-bug: 1894678
  packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
  phase: Testing
  phase-changed: Thursday, 10. September 2020 09:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs
  versions:
main: 4.15.0-1083.87~16.04.1
meta: 4.15.0.1083.79

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1894677/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1894681] Re: xenial/linux-azure: 4.15.0-1096.106~16.04.1 -proposed tracker

[Po-Hsu Lin]

4.15.0-1096.106~16.04.1 - azure
Regression test CMPL, RTB.

Issue to note in x86_64 (azure):
  ubuntu_kernel_selftests - cpu-hotplug on some instances (bug 1831543) 
rtnetlink.sh in net returning 1 for a skipped test (bug 1895258)
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) memory (bug 1831449) vmx 
(bug 1821394) vmx_host_state_area (bug 1866585) vmx_intr_window_test (bug 
1866586) vmx_nm_test (bug 1866587) vmx_nmi_window_test (bug 1866588) 
vmx_pending_event_test (bug 1866591) failed on Standard_D16s_v3, 
Standard_D2_v3, Standard_D2s_v3, Standard_E2s_v3, Standard_F2s_v2, 
Standard_F32s_v2
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) 
fanotify09 case 3 (bug 1876684) kill11 (bug 1865965) quotactl04 (bug 1854153) 
shmctl04 (bug 1895276) statx05 (bug 1798524) move_pages12 on some instance (bug 
1831043) 
  ubuntu_lxc - lxc-test-apparmor-mount failed with Unable to fetch GPG key from 
keyserver

Skipped / blacklisted:
  * ubuntu_bpf
  * ubuntu_ltp


** Changed in: kernel-sru-workflow/regression-testing
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1894681

Title:
  xenial/linux-azure: 4.15.0-1096.106~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure source package in Xenial:
  New

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
  kernel-stable-master-bug: 1894683
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Friday, 11. September 2020 12:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-azure/azure-kernel: bug 1894680
  variant: debs
  versions:
main: 4.15.0-1096.106~16.04.1
meta: 4.15.0.1096.90
signed: 4.15.0-1096.106~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1894681/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1894686] Re: xenial/linux-gcp: 4.15.0-1084.95~16.04.1 -proposed tracker

[Po-Hsu Lin]

4.15.0-1084.95~16.04.1 - gcp
Regression test CMPL, RTB.

Issue to note in gcp:
  ubuntu_k8s_unit_tests - test failed with context package not found in go (bug 
1850105)
  ubuntu_kernel_selftests - rtnetlink.sh in net returning 1 for a skipped test 
(bug 1895258)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) 
fanotify09 case 3 (bug 1876684) kill11 (bug 1865965) quotactl04 (bug 1854153) 
shmctl04 (bug 1895276) statx05 (bug 1798524)
  ubuntu_lxc - Unable to fetch GPG key for lxc-test-autostart on n1-highcpu-32 
and n1-highmem-8, python3-api on n1-highmem-8

Skipped / blacklisted:
 * ubuntu_bpf
 * ubuntu_ltp


** Changed in: kernel-sru-workflow/regression-testing
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1894686

Title:
  xenial/linux-gcp: 4.15.0-1084.95~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp source package in Xenial:
  New

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
  kernel-stable-master-bug: 1894687
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Thursday, 10. September 2020 14:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1894684
xenial/linux-gcp/gke-kernel: bug 1894685
  variant: debs
  versions:
main: 4.15.0-1084.95~16.04.1
meta: 4.15.0.1084.85
signed: 4.15.0-1084.95~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1894686/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp