[Group.of.nepali.translators] [Bug 1613184] Re: method mirror broken at 1.3

[Julian Andres Klode]

@Bojan The fix would have been in 1.4.8, but zesty is not supported
anymore - please upgrade to artful.

** Changed in: apt (Ubuntu Zesty)
   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/1613184

Title:
  method mirror broken at 1.3

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Zesty:
  Won't Fix

Bug description:
  [Impact]
  The mirror method always dies with a SEGV. It does not initialize _system but 
calls a function that sometimes uses it.

  [Test case]
  Use a mirror sources.list entry like

  deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted
  universe multiverse

  [Regression potential]
  The fix is small, and simply avoids using _system if _system is NULL in the 
called method. There should not be any regressions due to this.

  
https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1613184/+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 1664602] Re: Using an NVMe drive causes huge power drain

[Anthony Wong]

** Tags added: originate-from-1659177 somerville

** Changed in: hwe-next
   Status: New => 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/1664602

Title:
  Using an NVMe drive causes huge power drain

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  PCIe NVMe drives are very common in new laptops. The Zesty's kernels 
(including latest 4.10 rc8 from CKT PPA) does not support APST (autonomous 
power state transitions). A patch does exist :
  http://lists.infradead.org/pipermail/linux-nvme/2017-February/008051.html
  https://github.com/damige/linux-nvme

  It seems that we cannot expect this before kernel 4.11.

  Additionally my laptop CPU does never go under PC3 power saving state, 
powertop says. I don't know if it's related.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ft 1900 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=a04b55bf-b1b6-464c-88ce-44b6adbbbc10
  InstallationDate: Installed on 2016-12-12 (63 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=0d1f213e-73a9-4097-ae64-9cd963cfba23 ro quiet
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-8-generic N/A
   linux-backports-modules-4.10.0-8-generic  N/A
   linux-firmware1.163
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.5
  dmi.board.name: 0YH43H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.5:bd12/22/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0YH43H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1664602/+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 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

[Joseph Salisbury]

Commit 2a8a98673c13 has been in Xenial and Artful for some time now.
Can you confirm this bug is now resolved with the latest updates.

** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Fix Released

** Changed in: linux (Ubuntu Xenial)
   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/1717224

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Released
Status in procps source package in Xenial:
  New
Status in linux source package in Artful:
  Fix Released
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  

[Group.of.nepali.translators] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

[Joseph Salisbury]

** No longer affects: linux (Ubuntu Zesty)

** No longer affects: procps (Ubuntu Zesty)

-- 
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/1717224

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat /proc/sys/fs/aio-max-nr
  65536


  # Attempt to start more than 17 qcow2 virtual guests on the Ubuntu
  host.  Fails on the 18th XML.

  Script used to start 

[Group.of.nepali.translators] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

[Seth Forshee]

** Changed in: linux (Ubuntu)
   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/1717224

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in linux source package in Zesty:
  Won't Fix
Status in procps source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat /proc/sys/fs/aio-max-nr
  65536


  # Attempt to start more than 17 

[Group.of.nepali.translators] [Bug 1747090] Re: KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)

[Seth Forshee]

** Changed in: linux (Ubuntu Bionic)
   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/1747090

Title:
  KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  Mainline commit 35b3fde6203b9 is a KVM patch for s390x to provide facility
  bits 81 (ppa15) and 82 (bpb).  This is required for branch prediction 
behaviour
  changes.

  This is the public bug for SRU.  There is also a priave bug report:
  http://bugs.launchpad.net/bugs/1743560

  There is a qemu portion to this fix:
  http://patchwork.ozlabs.org/cover/862801/

  == Fixes ==
  Artful/Bionic:
  35b3fde6203b ("KVM: s390: wire up bpb feature")

  Xenial:
  ed8dda0bf74b ("Enable all facility bits that are known good for passthrough")
  35b3fde6203b ("KVM: s390: wire up bpb feature")

  
  == Regression Potential ==
  Low, this fix is limited to s390.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747090/+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 1729417] Re: [SRU] New stable micro release 2.35

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.39.2+18.04.2

---
snapcraft (2.39.2+18.04.2) bionic; urgency=medium

  [ Sergio Schvezov ]
  * tests: improvements to demos (#1938)
  * tests: remove the webcam-webui demo (#1940)
  * elf: contemplate more patching scenarios (#1935)
  * New upstream release (LP: #1745488)

  [ Kyle Fazzari ]
  * tests: remove duplicate tests (#1928)
  * schema: remove underscore from version pattern (#1933)
  * store: support pushing snap with no architectures (#1937)
  * storeapi: handle errors even for >400 responses (#1936)

  [ Christian Dywan ]
  * sources: proper errors for invalid handlers (#1929)

  [ Sylvain Pineau ]
  * tests: update the plainbox-provider tests (#1931)

 -- Sergio Schvezov   Tue, 20 Feb 2018
00:40:00 +

** Changed in: snapcraft (Ubuntu Bionic)
   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/1729417

Title:
   [SRU] New stable micro release 2.35

Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  Fix Released
Status in snapcraft source package in Zesty:
  Fix Released
Status in snapcraft source package in Artful:
  Fix Committed
Status in snapcraft source package in Bionic:
  Fix Released

Bug description:
  This is an SRU bug to release 2.35 of snapcraft which follows the
  guidelines defined in the wiki over at
  https://wiki.ubuntu.com/SnapcraftUpdates

  The list of bugs and features in this release are defined at
  https://launchpad.net/snapcraft/+milestone/2.35 and
  https://github.com/snapcore/snapcraft/milestone/10?closed=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1729417/+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 1745488] Re: [SRU] New stable micro release 2.39.2

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.39.2+18.04.2

---
snapcraft (2.39.2+18.04.2) bionic; urgency=medium

  [ Sergio Schvezov ]
  * tests: improvements to demos (#1938)
  * tests: remove the webcam-webui demo (#1940)
  * elf: contemplate more patching scenarios (#1935)
  * New upstream release (LP: #1745488)

  [ Kyle Fazzari ]
  * tests: remove duplicate tests (#1928)
  * schema: remove underscore from version pattern (#1933)
  * store: support pushing snap with no architectures (#1937)
  * storeapi: handle errors even for >400 responses (#1936)

  [ Christian Dywan ]
  * sources: proper errors for invalid handlers (#1929)

  [ Sylvain Pineau ]
  * tests: update the plainbox-provider tests (#1931)

 -- Sergio Schvezov   Tue, 20 Feb 2018
00:40:00 +

** Changed in: snapcraft (Ubuntu Bionic)
   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/1745488

Title:
  [SRU] New stable micro release 2.39.2

Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  Fix Committed
Status in snapcraft source package in Artful:
  Confirmed
Status in snapcraft source package in Bionic:
  Fix Released

Bug description:
  This is an SRU bug to release 2.39.2 of snapcraft which follows the
  guidelines defined in the wiki over at
  https://wiki.ubuntu.com/SnapcraftUpdates

  The list of bugs and features in this release are defined at
  https://github.com/snapcore/snapcraft/milestone/14?closed=1

  Releases since 2.35 and this one are defined at:
  https://github.com/snapcore/snapcraft/milestone/13?closed=1
  https://github.com/snapcore/snapcraft/milestone/12?closed=1
  https://github.com/snapcore/snapcraft/milestone/11?closed=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1745488/+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 1676328] Re: sssd_be is leaking memory

[Andreas Hasenack]

** Changed in: sssd (Ubuntu Yakkety)
   Status: Confirmed => 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/1676328

Title:
  sssd_be is leaking memory

Status in sssd package in Ubuntu:
  Fix Released
Status in sssd source package in Xenial:
  Confirmed
Status in sssd source package in Yakkety:
  Won't Fix

Bug description:
  The bug is described here:

  https://pagure.io/SSSD/sssd/issue/3176

  Please consider to upgrade from 1.13.4 to 1.13.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1676328/+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 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler

[dino99]

Looks like everything is ok now in 2018; closing that report.

** Changed in: virtualbox (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: gcc-defaults (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1574982

Title:
  Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
  not supported by compiler

Status in dkms package in Ubuntu:
  Invalid
Status in gcc-defaults package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in virtualbox package in Ubuntu:
  Invalid
Status in dkms source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Installing the latest 4.4.0-22 kernel ends with that error logged into 
dkmsbuildlog
  (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine)

  https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt

  make "CC=cc"  KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build 
M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 
NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build 
NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia 
nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules
  make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic'
  arch/x86/Makefile:133: stack-protector enabled but compiler support broken
  Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler

  the latest error logged is:

  /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error:
  code model kernel does not support PIC mode

  Looks like it is related to the latest changes updates: gcc-6/gcc-5 
5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the 
packages built with gcc-6)
  Maybe some alternatives has not been updated to take care of these changes, 
as asked some time ago:
  http://askubuntu.com/questions/26498/choose-gcc-and-g-version

  This has been firstly reported against a nvidia crash:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gcc 4:5.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 08:41:32 2016
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2014 F pulseaudio
   /dev/snd/pcmC0D0p:   oem2014 F...m pulseaudio
   /dev/snd/controlC0:  oem2014 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: ubuntu
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  yakkety
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Group.of.nepali.translators] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

[Kamal Mostafa]

The fix for this issue has been released in the linux-aws and standard
Ubuntu kernels.  Fixed versions are:

linux-aws (4.4.0-1052.61) xenial
linux-aws (4.4.0-1014.14) trusty
linux (4.4.0-116.140) xenial


** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

** Changed in: linux-aws (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: linux-aws (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/1746806

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-aws source package in Xenial:
  Fix Released

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+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 1750780] Re: Race with local file systems can make open-vm-tools fail to start

[ChristianEhrhardt]

Installed another Xenial and Bionic in vmware to take a deper look.
- Xenial (with backported open-vm-tools): affected
- Bionic (with the interim fix reverted): no hit in several retries, 
explanation below

Systemd fixed it (via our assumed implicit dependency).
In Bionic the PrivateTmp gives it a dependency on systemd-tmpfile-setup.service 
(seen in systemd analyze, there might be more but not on crit path).
This is configured by default to include /var/tmp in 
/usr/lib/tmpfiles.d/tmp.conf.

In regard to your thoughts about later on changing cloud-init ordering
that won't help you, as the dependency is there (implicit or explicit
doesn't matter).

For the xenial case where I reliably hit the issue instead of stracing I cut 
things short.
A service with the following exposes exactly the same error:
[Unit]
Description=foo
DefaultDependencies=no

[Service]
PrivateTmp=yes
ExecStart=/bin/true

[Install]
WantedBy=multi-user.target

So back on Xenial it is privateTmp + too early that breaks it.

Xenial vs Bionic critical-chain according to "systemd-analyze critical-
chain open.vm-tools.service"

Xenial with fix:
open-vm-tools.service @3.482s
└─local-fs.target @3.460s
  └─local-fs-pre.target @3.460s
└─systemd-remount-fs.service @3.442s +9ms
  └─system.slice @220ms
└─-.slice @204m

Xenial without fix:
└─run-vmblock\x2dfuse.mount @6.076s +390ms
  └─sys-fs-fuse-connections.mount @5.510s +375ms
└─systemd-modules-load.service @1.996s +75ms
  └─system.slice @1.984s
└─-.slice @1.966s

Bionic
open-vm-tools.service @3.566s
└─systemd-tmpfiles-setup.service @3.421s +100ms
  └─systemd-journal-flush.service @3.054s +342ms
└─systemd-journald.service @825ms +2.219s
  └─syslog.socket @808ms
└─system.slice @621ms
  └─-.slice @613ms

To Summarize, we can:
- revert the fix for Bionic (or later) - just make it a sync when convenient 
down the road, it doesn't hurt for now as it is (almost) the same as the 
implicit dependency)
- add a xenials systemd bug task (probably too complex to fix as -upstream)
- until said systemd bug is fixed a backport of open-vm-tools needs this fix


** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: open-vm-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: open-vm-tools (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: systemd (Ubuntu)
   Status: New => 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/1750780

Title:
  Race with local file systems can make open-vm-tools fail to start

Status in cloud-init:
  Invalid
Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in open-vm-tools package in Debian:
  Incomplete

Bug description:
  Since the change in [1] open-vm-tools-service starts very (very) early.
  Not so much due to the 
  Before=cloud-init-local.service
  But much more by
  DefaultDependencies=no

  That can trigger an issue that looks like
  root@ubuntuguest:~# systemctl status -l open-vm-tools.service
  ● open-vm-tools.service - Service for virtual machines hosted on VMware
 Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: resources)

  
  As it is right now open-vm-tools can race with the other early start and then 
fail.
  In detail one can find a message like:
open-vm-tools.service: Failed to run 'start' task: Read-only file system"

  This is due to privtaeTmp=yes which is also set needing a writable
  /var/tmp [2]

  To ensure this works PrivateTmp would have to be removed (not good) or some 
after dependencies added that make this work reliably.
  I added
  After=local-fs.target
  which made it work for me in 3/3 tests.

  I' like to have an ack by the cloud-init Team that this does not totally kill 
the originally intended Before=cloud-init-local.service
  I think it does not as local-fs can complete before cloud-init-local, then 
open-vm-tools can initialize and finally cloud-init-local can pick up the data.

  To summarize:
  # cloud-init-local #
  DefaultDependencies=no
  Wants=network-pre.target
  After=systemd-remount-fs.service
  Before=NetworkManager.service
  Before=network-pre.target
  Before=shutdown.target
  Before=sysinit.target
  Conflicts=shutdown.target
  RequiresMountsFor=/var/lib/cloud

  # open-vm-tools #
  DefaultDependencies=no
  Before=cloud-init-local.service

  Proposed is to add to the latter:
  After=local-fs.target

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859677
  [2]: 

[Group.of.nepali.translators] [Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Thadeu Lima de Souza Cascardo]

Should already be fixed in bionic. If we backport the bionic package to
xenial, we will get this working as well.

Cascardo.

** Changed in: makedumpfile (Ubuntu Bionic)
   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/1714485

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714485/+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 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Manoj Iyer]

Cascardo, did you get chance to make those changes you mentioned in
comment #8 ? Please update this bug if this fix was already applied to
x/a/z releases.

** Changed in: makedumpfile (Ubuntu Zesty)
   Status: New => 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/1714485

Title:
  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Artful:
  New
Status in makedumpfile source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714485/+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 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter

[Frank Heimes]

** Changed in: makedumpfile (Ubuntu Zesty)
   Status: New => Invalid

** Changed in: kexec-tools (Ubuntu Zesty)
   Status: New => Invalid

-- 
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/1658733

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Zesty:
  Invalid
Status in makedumpfile source package in Zesty:
  Invalid
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to 

[Group.of.nepali.translators] [Bug 1735821] Re: netplan needs bridge port-priority support

[Mathieu Trudel-Lapierre]

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

** Also affects: nplan (Ubuntu Artful)
   Importance: Undecided
   Status: New

-- 
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/1735821

Title:
  netplan needs bridge port-priority support

Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  New
Status in nplan source package in Artful:
  New

Bug description:
  Now that systemd supports port-priority for bridges (LP: #1668347)
  netplan should handle port-priority like it does path-cost.

  1) % lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  1) # lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) # apt-cache policy nplan
  nplan:
Installed: 0.30
Candidate: 0.32
Version table:
   0.32 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
   *** 0.30 100
  100 /var/lib/dpkg/status

  3) netplan generate renders a networkd .network file which has
  [Bridge] section including  Priority  value set on each of the bridge
  ports specified

  4) netplan fails to parse the input yaml with

  Sample config that should parse:

  % cat br-pp.yaml
  network:
  version: 2
  ethernets:
  eth0:
  match:
  macaddress: '52:54:00:12:34:04'
  bridges:
  br0:
  addresses:
  - 192.168.14.2/24
  interfaces:
  - eth0
  parameters:
  path-cost:
  eth0: 50
  priority: 22
  port-priority:
  eth0: 14

  % netplan generate
  Error in network definition br-pp.yaml line 13 column 16: unknown key 
port-priority

  
  If fixed, then I would expect a /run/systemd/network/10-netplan-eth0.network 
that looks like
  [Match]
  MACAddress=52:54:00:12:34:00
  Name=eth0

  [Network]
  Bridge=br0
  LinkLocalAddressing=no
  IPv6AcceptRA=no

  [Bridge]
  Cost=50
  Priority=14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1735821/+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 1582585] Re: the speed of query user from ldap server is very slow

[Corey Bryant]

This bug was fixed in the package keystone - 2:10.0.3-0ubuntu1~cloud1
---

 keystone (2:10.0.3-0ubuntu1~cloud1) xenial-newton; urgency=medium
 .
   * LDAP backend performance improvements (LP: #1582585)
 - d/p/faster-id-mapping-lookup.patch: Allow querying for all
   public ids in a domain at once instead of N queries (one per
   entity).
 - d/p/fallback-for-custom-id-map-drivers.patch: Add fallback
   path for faster-id-mapping lookup for any customer id mapping
   drivers that may be in use or existing deployments.


** Changed in: cloud-archive/newton
   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/1582585

Title:
  the speed of query user from ldap server is very slow

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystone package in Ubuntu:
  Invalid
Status in keystone source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * When using an LDAP backend for Keystone, the performance can be slow if 
there are
 a large number of users using the cloud. This is due in large part to 
querying the
 SQL database for the identity mapping information of each user in a 
separate transaction.
 For example, an environment with 12,000 users will result in 12,000 sql 
queries to the
 backend database in order to fulfill a user list request. This causes some 
admin
 functions in Horizon UI to take several minutes, which often exceeds the 
WSGI and any
 haproxy timeouts configured.

   * This is fixed by backporting a series of patches which caches previously 
fetched identity
 mapping information in a memcached instance and changes the logic to query 
all of the
 user id mapping by the domain the id mapping is in. Additionally, the 
keystone-manage
 command to sync the id mapping information with a backend database in an 
offline manner
 is included to allow offline syncing of the data.

  [Test Case]

   * Install keystone using an ldap backend w/ large number of users.
   * List user information: openstack user list --domain 
   * observe slow down

  [Regression Potential]

   * For Mitaka, the caching backends such as memcached or mongodb will likely 
see more
 usage and an increased footprint due to additional data being cached. 
Caching the
 identity mapping information is now standard since Newton and no major 
issues have
 been seen coming from this.

   * This code affects the identity mapping between keystone user and the ldap 
user
 (essentially the bridge between the two). While it does not functionally 
alter the
 information that is mapped (e.g. no difference in how the identity mapping 
is calculated),
 it does alter a key code path for information regarding user identity 
mappings.

  [Other Info]

   * These patches have been run and tested in a staging environment to 
production and
 have had exposure in the Mitaka path for approximately one month to show 
their stability.

  [Original Description]

  In our project, the speed of query user from ldap server is very
  slow,our ldap user number is 12,000,the query costs almost 45 seconds

  The reason is that keystone will generate the uuid for the ldap users one by 
one and insert db.And second query time later,it also goes to db,not use the 
cache.
  So adding the cache to improve the query speed

  After adding @MEMOIZE to the following function
  
https://github.com/openstack/keystone/blob/master/keystone/identity/core.py#L580.
  First query time almost costs 50 seconds,but second query time later it only 
costs 7 seconds.

  So it is very necessary to improve this feature

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1582585/+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 1582585] Re: the speed of query user from ldap server is very slow

[Corey Bryant]

This bug was fixed in the package keystone - 2:9.3.0-0ubuntu3.2~cloud0
---

 keystone (2:9.3.0-0ubuntu3.2~cloud0) trusty-mitaka; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 keystone (2:9.3.0-0ubuntu3.2) xenial; urgency=medium
 .
   * LDAP backend performance improvements (LP: #1582585)
 - d/p/prevent-error-when-duplicate-mapping-is-created.patch:
   Handle races for creating id mappings.
 - d/p/added-cache-for-id-mapping-manager.patch: Add a cache to
   the id mapping manager to improve performance.
 - d/p/add-mapping_populate-command.patch: Add a keystone-manage
   command to populate id mappings between backend identity
   provider and keystone database.
 - d/p/faster-id-mapping-lookup.patch: Allow querying for all
   public ids in a domain at once instead of N queries (one per
   entity).
 - d/p/fallback-for-custom-id-map-drivers.patch: Add fallback
   path for faster-id-mapping lookup for any customer id mapping
   drivers that may be in use or existing deployments.


** Changed in: cloud-archive/mitaka
   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/1582585

Title:
  the speed of query user from ldap server is very slow

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystone package in Ubuntu:
  Invalid
Status in keystone source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * When using an LDAP backend for Keystone, the performance can be slow if 
there are
 a large number of users using the cloud. This is due in large part to 
querying the
 SQL database for the identity mapping information of each user in a 
separate transaction.
 For example, an environment with 12,000 users will result in 12,000 sql 
queries to the
 backend database in order to fulfill a user list request. This causes some 
admin
 functions in Horizon UI to take several minutes, which often exceeds the 
WSGI and any
 haproxy timeouts configured.

   * This is fixed by backporting a series of patches which caches previously 
fetched identity
 mapping information in a memcached instance and changes the logic to query 
all of the
 user id mapping by the domain the id mapping is in. Additionally, the 
keystone-manage
 command to sync the id mapping information with a backend database in an 
offline manner
 is included to allow offline syncing of the data.

  [Test Case]

   * Install keystone using an ldap backend w/ large number of users.
   * List user information: openstack user list --domain 
   * observe slow down

  [Regression Potential]

   * For Mitaka, the caching backends such as memcached or mongodb will likely 
see more
 usage and an increased footprint due to additional data being cached. 
Caching the
 identity mapping information is now standard since Newton and no major 
issues have
 been seen coming from this.

   * This code affects the identity mapping between keystone user and the ldap 
user
 (essentially the bridge between the two). While it does not functionally 
alter the
 information that is mapped (e.g. no difference in how the identity mapping 
is calculated),
 it does alter a key code path for information regarding user identity 
mappings.

  [Other Info]

   * These patches have been run and tested in a staging environment to 
production and
 have had exposure in the Mitaka path for approximately one month to show 
their stability.

  [Original Description]

  In our project, the speed of query user from ldap server is very
  slow,our ldap user number is 12,000,the query costs almost 45 seconds

  The reason is that keystone will generate the uuid for the ldap users one by 
one and insert db.And second query time later,it also goes to db,not use the 
cache.
  So adding the cache to improve the query speed

  After adding @MEMOIZE to the following function
  
https://github.com/openstack/keystone/blob/master/keystone/identity/core.py#L580.
  First query time almost costs 50 seconds,but second query time later it only 
costs 7 seconds.

  So it is very necessary to improve this feature

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1582585/+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 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1692538

Title:
  Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  
  == SRU Justification ==
  Commit 66aa0678ef is request to fix four issues with the ibmveth driver.
  The issues are as follows:
  - Issue 1: ibmveth doesn't support largesend and checksum offload features 
when configured as "Trunk".
  - Issue 2: SYN packet drops seen at destination VM. When the packet
  originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO
  server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth
  receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag.
  - Issue 3: First packet of a TCP connection will be dropped, if there is
  no OVS flow cached in datapath.
  - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.

  The details for the fixes to these issues are described in the commits
  git log.



  == Comment: #0 - BRYANT G. LY  - 2017-05-22 08:40:16 ==
  ---Problem Description---

   - Issue 1: ibmveth doesn't support largesend and checksum offload features
     when configured as "Trunk". Driver has explicit checks to prevent
     enabling these offloads.

   - Issue 2: SYN packet drops seen at destination VM. When the packet
     originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to
     IO server's inbound Trunk ibmveth, on validating "checksum good" bits
     in ibmveth receive routine, SKB's ip_summed field is set with
     CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux
     Bridge) and delivered to outbound Trunk ibmveth. At this point the
     outbound ibmveth transmit routine will not set "no checksum" and
     "checksum good" bits in transmit buffer descriptor, as it does so only
     when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets
     delivered to destination VM, TCP layer receives the packet with checksum
     value of 0 and with no checksum related flags in ip_summed field. This
     leads to packet drops. So, TCP connections never goes through fine.

   - Issue 3: First packet of a TCP connection will be dropped, if there is
     no OVS flow cached in datapath. OVS while trying to identify the flow,
     computes the checksum. The computed checksum will be invalid at the
     receiving end, as ibmveth transmit routine zeroes out the pseudo
     checksum value in the packet. This leads to packet drop.

   - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list.
     When Physical NIC has GRO enabled and when OVS bridges these packets,
     OVS vport send code will end up calling dev_queue_xmit, which in turn
     calls validate_xmit_skb.
     In validate_xmit_skb routine, the larger packets will get segmented into
     MSS sized segments, if SKB has a frag_list and if the driver to which
     they are delivered to doesn't support NETIF_F_FRAGLIST feature.

  Contact Information = Bryant G. Ly/b...@us.ibm.com

  ---uname output---
  4.8.0-51.54

  Machine Type = p8

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   Increases performance greatly

  The patch has been accepted upstream:
  https://patchwork.ozlabs.org/patch/764533/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1692538/+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 1751799] [NEW] linux-azure: -proposed tracker

[Kleber Sacilotto de Souza]

Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1751798

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-lbm
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-ports-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-azure (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1751798 kernel-sru-cycle-2018.02.01-4 xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux-azure (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Tags added: xenial

** Changed in: linux-azure (Ubuntu Xenial)
   Status: New => Confirmed

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lbm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-ports-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** 

[Group.of.nepali.translators] [Bug 1751803] [NEW] linux-hwe: -proposed tracker

[Kleber Sacilotto de Souza]

Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1751798

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-lbm
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-ports-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-hwe (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-hwe (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1751798 kernel-sru-cycle-2018.02.01-4 xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux-hwe (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Tags added: xenial

** Changed in: linux-hwe (Ubuntu Xenial)
   Status: New => Confirmed

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lbm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-ports-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team 

[Group.of.nepali.translators] [Bug 1751802] [NEW] linux-gcp: -proposed tracker

[Kleber Sacilotto de Souza]

Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1751798

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-lbm
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-ports-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/snap-publish
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-qa-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-gcp (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-gcp (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1751798 kernel-sru-cycle-2018.02.01-4 xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux-gcp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Tags added: xenial

** Changed in: linux-gcp (Ubuntu Xenial)
   Status: New => Confirmed

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lbm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-ports-meta
   Importance: Undecided
   Status: New

** Also affects: 

[Group.of.nepali.translators] [Bug 1751805] [NEW] linux-oem: -proposed tracker

[Kleber Sacilotto de Souza]

Public bug reported:

This bug is for tracking the  upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1751798

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-lbm
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-ports-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1751798 kernel-sru-cycle-2018.02.01-4 xenial

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Tags added: xenial

** Changed in: linux-oem (Ubuntu Xenial)
   Status: New => Confirmed

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-lbm
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-ports-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team 

[Group.of.nepali.translators] [Bug 1688508] Re: libvirt-guests.sh fails to shutdown guests in parallel

[Dariusz Gadomski]

** Changed in: libvirt (Ubuntu Zesty)
   Status: In Progress => 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/1688508

Title:
  libvirt-guests.sh fails to shutdown guests in parallel

Status in libvirt:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  In Progress
Status in libvirt source package in Zesty:
  Won't Fix
Status in libvirt source package in Artful:
  In Progress

Bug description:
  [Environment]

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  [Impact]

  There is a bug/race condition on libvirt-guests.service, that prevents
  the shutdown of guests to happen in parallel.

  The critical chain for this service is:

  libvirt-guests.service +20ms
  └─libvirt-bin.service @2.784s +140ms
    └─remote-fs.target @2.777s
  └─remote-fs-pre.target @2.775s
    └─open-iscsi.service @2.554s +116ms
  └─iscsid.service @2.525s +18ms
    └─network-online.target @2.502s
  └─network.target @1.955s
    └─networking.service @1.625s +299ms
  └─network-pre.target @1.601s
    └─cloud-init-local.service @405ms +1.072s
  └─systemd-remount-fs.service @232ms +64ms
    └─systemd-journald.socket @178ms
  └─-.slice @117ms

  As an example, I have the following kvm host with 42 virtual
  machines.

  ubuntu@xenial-base:~$ virsh list --all
   IdName   State
  
   12locked-trusty-2running
   13locked-trusty-3running
  [...]
   41locked-trusty-42   running

  After rebooting the machine:

  [  250.999516] libvirt-guests.sh[4215]: Running guests on default URI: 
locked-trusty-2, locked-trusty-4, locked-trusty-12, locked-trusty-3, 
locked-trusty-5, locked-trusty-11, locked-trusty-10, locked-trusty-8, 
locked-trusty-9, locked-trusty-7, locked-trusty-6, locked-trusty-13, 
locked-trusty-14, locked-trusty-15, locked-trusty-16, locked-trusty-17, 
locked-trusty-18, locked-trusty-19, locked-trusty-20, locked-trusty-21, 
locked-trusty-22, locked-trusty-23, locked-trusty-24, locked-trusty-25, 
locked-trusty-26, locked-trusty-27, locked-trusty-28, locked-trusty-29, 
locked-trusty-30, locked-trusty-31, locked-trusty-32, locked-trusty-33, 
locked-trusty-34, locked-trusty-35, locked-trusty-36, locked-trusty-37, 
locked-trusty-38, locked-trusty-39, locked-trusty-40, locked-trusty-41, 
locked-trusty-42
  [  251.011367] libvirt-guests.sh[4215]: Shutting down guests on default URI...
  [  251.027072] libvirt-guests.sh[4215]: Starting shutdown on guest: 
locked-trusty-2
  [...]
  [  391.949941] libvirt-guests.sh[4215]: Waiting for 28 guests to shut down, 
10 seconds left
  [  398.074405] libvirt-guests.sh[4215]: Waiting for 28 guests to shut down, 5 
seconds left
  [  403.020479] libvirt-guests.sh[4215]: Timeout expired while shutting down 
domains
  [  OK  ] Stopped Suspend Active Libvirt Guests.
  [  OK  ] Stopped target System Time Synchronized.

  [Test Case]

   * Make sure the following variables are set in /etc/default/libvirt-
  guests (which are all default options):

  ON_SHUTDOWN=shutdown
  PARALLEL_SHUTDOWN=10
  SHUTDOWN_TIMEOUT=120

   * Create over 20 virtual machines (in my case, using uvt-kvm).

  $  for f in $(seq 0 40); do uvt-kvm create --memory 2000 --cpu 1
  locked-trusty-$f release=xenial arch=amd64 ; done

   * Reboot the machine and monitor the systemd service stop sequence
  or console output.

  (With systemd: systemctl start debug-shell and jumpt to ctrl+alt+f9)

  * Error message "Timeout expired while shutting down domains" should
  be displayed.

  [Regression Potential]

  * None identified.

  [Other Info]

  * There is a proposed patch in upstream already that has been already
  linked to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1450141

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1688508/+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 1466926] Re: reload apache2 with mpm_event cause scoreboard is full

[ChristianEhrhardt]

Thanks Tobias for all the tests.

With all that prep done I'll try to push it to SRU review now.

** Changed in: apache2 (Ubuntu Trusty)
   Status: Incomplete => 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/1466926

Title:
  reload apache2  with mpm_event cause  scoreboard is full

Status in apache2 package in Ubuntu:
  Fix Released
Status in apache2 source package in Trusty:
  Won't Fix
Status in apache2 source package in Xenial:
  Incomplete
Status in apache2 source package in Zesty:
  Fix Released

Bug description:
  On the clean install Ubuntu 14.04 with Apache without almost any
  client load the Apache server with the command "service apache2
  reload" itself allocates slots marked with "Gracefully finishing" for
  which rejects new connections.

  For full rejection of new requests is sufficient to perform 4x command
  "service apache2 reload".

  Ubuntu 14.04.2 LTS
  Apache 2.4.7-ubuntu4.4 (mpm_event)
  Kernel 2.16.0-30-generic

  
  Reproduce problem:
  #
  1/ service apache2 start
  __W_
  ___.
  ..

  2/ service apache2 reload

  .GGG
  GGG__W__
  __

  3/ service apache2 reload

  ___W_GGG
  GGG__...
  ..

  4/ service apache2 reload

  
  G___
  W_

  5/ service apache2 reload -> Server Apache not responding 
  With logs in apache error log file:
  ... [mpm_event:error] [pid 9381:tid 1234563234] AH00485: scoreboard is full, 
not at MaxRequestWorkers
  ...
  #

  
  My workaround was change to  MPM module  from "mpm_event" to "mpm_worker".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1466926/+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