[Group.of.nepali.translators] [Bug 1652466] Re: Totem can't play videos on Gallium graphics without mesa-va-drivers

[Brian Murray]

Hello Amr, or anyone else affected,

Accepted libva into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/libva/1.7.0-1ubuntu0.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libva (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

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

Title:
  Totem can't play videos on Gallium graphics without mesa-va-drivers

Status in One Hundred Papercuts:
  Confirmed
Status in libva package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid
Status in libva source package in Xenial:
  Fix Committed
Status in totem source package in Xenial:
  Invalid

Bug description:
  Impact
  ---
  Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium 
graphics in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.

  Here is the dependency chain in Xenial:
  gstreamer1.0-vaapi Depends on libva1
  libva1 Recommends va-driver-all
  va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers)

  This is fixed in version 1.7.0-2 in Debian and Yakkety.
  libva (1.7.0-2) unstable; urgency=medium

* debian/control:
  - Add mesa-va-drivers as alternative to Depends of va-driver-all.
  - Bump Standards-Versions.

   -- Sebastian Ramacher   Wed, 11 May 2016
  17:32:06 +0200

  
  Test case
  --
  - Purge va-driver-all and mesa-va-drivers if already installed
  - Install va-driver-all from xenial-proposed
  - Make sure that mesa-va-drivers is pulled in
  - Play videos in Totem with gstreamer1.0-vaapi installed and make sure that 
videos play nicely.

  Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and 
no mesa-va-drivers):
  :~$ totem
  Stream with high frequencies VQ coding
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0

  When mesa-va-drivers is installed, Totem plays videos just fine.

  
  Regression potential
  -
  Since there are no code changes at all, I cannot think of any regressions.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: va-driver-all 1.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 24 21:54:20 2016
  InstallationDate: Installed on 2016-04-26 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libva
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1652466/+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 1702529] Re: ACCESS_DENIED with symlinks within a root ("/") share

[Launchpad Bug Tracker]

This bug was fixed in the package samba - 2:4.3.11+dfsg-
0ubuntu0.16.04.10

---
samba (2:4.3.11+dfsg-0ubuntu0.16.04.10) xenial; urgency=medium

  * d/p/bug_1702529_EACCESS_with_rootshare.patch:
Handle corner case for / shares. (LP: #1702529)

 -- Dariusz Gadomski   Wed, 23 Aug 2017
11:43:46 +0200

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

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

Title:
   ACCESS_DENIED with symlinks within a root ("/") share

Status in samba:
  Unknown
Status in samba package in Ubuntu:
  Fix Released
Status in samba source package in Trusty:
  Fix Released
Status in samba source package in Xenial:
  Fix Released
Status in samba source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * In case of accessing directories chdir to it directly instead of
  its parent directory. This changes how dir symlinks are handled in
  root shares and leads to avoiding the ACCESS_DENIED ISSUE.

  [Test Case]

   1. Prepare smb server with a share:
  [rootshare]
     guest ok = yes
     path = /
     wide links = no
     follow symlinks = yes
   2. On the server:
  mkdir -p /srv/dir
  ln -s /srv/dir /srv/symdir.
   3. Connect from a client:
  smbclient -m smb3 //server/rootshare -c "cd srv\symdir; dir"

  [Regression Potential]

   * When accessing broken symlinks share's base directory is accessed.
  This however seems to be consistent with a pre-fix behavior.

   * One autopkgtest failure has been found, nothing related to samba so
  another bug has been reported (LP: #1713098) against gvfs DEP8 test.

  For more details: 
 - https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1702529/comments/18

  [Other Info]

  This fix is included in Samba 4.6.7 release so Artful and Debian both
  have it already.

  Original bug description:

  See Samba bug: https://bugzilla.samba.org/show_bug.cgi?id=12873 for
  more information and test case. Also view LP bug:
  https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1701073 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1702529/+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 1702529] Re: ACCESS_DENIED with symlinks within a root ("/") share

[Launchpad Bug Tracker]

This bug was fixed in the package samba - 2:4.3.11+dfsg-
0ubuntu0.14.04.11

---
samba (2:4.3.11+dfsg-0ubuntu0.14.04.11) trusty; urgency=medium

  * d/p/bug_1702529_EACCESS_with_rootshare.patch:
Handle corner case for / shares. (LP: #1702529)

 -- Dariusz Gadomski   Wed, 23 Aug 2017
11:36:59 +0200

** Changed in: samba (Ubuntu Trusty)
   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/1702529

Title:
   ACCESS_DENIED with symlinks within a root ("/") share

Status in samba:
  Unknown
Status in samba package in Ubuntu:
  Fix Released
Status in samba source package in Trusty:
  Fix Released
Status in samba source package in Xenial:
  Fix Released
Status in samba source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * In case of accessing directories chdir to it directly instead of
  its parent directory. This changes how dir symlinks are handled in
  root shares and leads to avoiding the ACCESS_DENIED ISSUE.

  [Test Case]

   1. Prepare smb server with a share:
  [rootshare]
     guest ok = yes
     path = /
     wide links = no
     follow symlinks = yes
   2. On the server:
  mkdir -p /srv/dir
  ln -s /srv/dir /srv/symdir.
   3. Connect from a client:
  smbclient -m smb3 //server/rootshare -c "cd srv\symdir; dir"

  [Regression Potential]

   * When accessing broken symlinks share's base directory is accessed.
  This however seems to be consistent with a pre-fix behavior.

   * One autopkgtest failure has been found, nothing related to samba so
  another bug has been reported (LP: #1713098) against gvfs DEP8 test.

  For more details: 
 - https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1702529/comments/18

  [Other Info]

  This fix is included in Samba 4.6.7 release so Artful and Debian both
  have it already.

  Original bug description:

  See Samba bug: https://bugzilla.samba.org/show_bug.cgi?id=12873 for
  more information and test case. Also view LP bug:
  https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1701073 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1702529/+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 1649616] Re: Keystone Token Flush job does not complete in HA deployed environment

[Corey Bryant]

** Changed in: keystone (Ubuntu)
   Status: In Progress => Invalid

** Changed in: cloud-archive
   Status: In Progress => 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/1649616

Title:
  Keystone Token Flush job does not complete in HA deployed environment

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 Ubuntu Cloud Archive ocata series:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in OpenStack Identity (keystone) newton series:
  In Progress
Status in OpenStack Identity (keystone) ocata series:
  In Progress
Status in puppet-keystone:
  Triaged
Status in tripleo:
  Fix Released
Status in keystone package in Ubuntu:
  Invalid
Status in keystone source package in Xenial:
  Fix Released
Status in keystone source package in Yakkety:
  Fix Released
Status in keystone source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * The Keystone token flush job can get into a state where it will
  never complete because the transaction size exceeds the mysql galara
  transaction size - wsrep_max_ws_size (1073741824).

  [Test Case]

  1. Authenticate many times
  2. Observe that keystone token flush job runs (should be a very long time 
depending on disk) >20 hours in my environment
  3. Observe errors in mysql.log indicating a transaction that is too large

  Actual results:
  Expired tokens are not actually flushed from the database without any errors 
in keystone.log.  Only errors appear in mysql.log.

  Expected results:
  Expired tokens to be removed from the database

  [Additional info:]

  It is likely that you can demonstrate this with less than 1 million
  tokens as the >1 million token table is larger than 13GiB and the max
  transaction size is 1GiB, my token bench-marking Browbeat job creates
  more than needed.

  Once the token flush job can not complete the token table will never
  decrease in size and eventually the cloud will run out of disk space.

  Furthermore the flush job will consume disk utilization resources.
  This was demonstrated on slow disks (Single 7.2K SATA disk).  On
  faster disks you will have more capacity to generate tokens, you can
  then generate the number of tokens to exceed the transaction size even
  faster.

  Log evidence:
  [root@overcloud-controller-0 log]# grep " Total expired" 
/var/log/keystone/keystone.log
  2016-12-08 01:33:40.530 21614 INFO keystone.token.persistence.backends.sql 
[-] Total expired tokens removed: 1082434
  2016-12-09 09:31:25.301 14120 INFO keystone.token.persistence.backends.sql 
[-] Total expired tokens removed: 1084241
  2016-12-11 01:35:39.082 4223 INFO keystone.token.persistence.backends.sql [-] 
Total expired tokens removed: 1086504
  2016-12-12 01:08:16.170 32575 INFO keystone.token.persistence.backends.sql 
[-] Total expired tokens removed: 1087823
  2016-12-13 01:22:18.121 28669 INFO keystone.token.persistence.backends.sql 
[-] Total expired tokens removed: 1089202
  [root@overcloud-controller-0 log]# tail mysqld.log
  161208  1:33:41 [Warning] WSREP: transaction size limit (1073741824) 
exceeded: 1073774592
  161208  1:33:41 [ERROR] WSREP: rbr write fail, data_len: 0, 2
  161209  9:31:26 [Warning] WSREP: transaction size limit (1073741824) 
exceeded: 1073774592
  161209  9:31:26 [ERROR] WSREP: rbr write fail, data_len: 0, 2
  161211  1:35:39 [Warning] WSREP: transaction size limit (1073741824) 
exceeded: 1073774592
  161211  1:35:40 [ERROR] WSREP: rbr write fail, data_len: 0, 2
  161212  1:08:16 [Warning] WSREP: transaction size limit (1073741824) 
exceeded: 1073774592
  161212  1:08:17 [ERROR] WSREP: rbr write fail, data_len: 0, 2
  161213  1:22:18 [Warning] WSREP: transaction size limit (1073741824) 
exceeded: 1073774592
  161213  1:22:19 [ERROR] WSREP: rbr write fail, data_len: 0, 2

  Disk utilization issue graph is attached.  The entire job in that
  graph takes from the first spike is disk util(~5:18UTC) and culminates
  in about ~90 minutes of pegging the disk (between 1:09utc to 2:43utc).

  [Regression Potential] 
  * Not identified

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1649616/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

[Mathieu Trudel-Lapierre]

** Changed in: network-manager (Ubuntu Xenial)
   Status: Confirmed => Invalid

** Description changed:

+ [Impact]
+ Users booting from OEM setup may find that their wireless device is "not 
ready" as per NetworkManager, because wpasupplicant is not running. This is 
because the steps taken to start in OEM prepare, before moving to the real 
system runs systemctl isolate, and wpasupplicant gets caught in the crossfire.
+ 
+ 
+ [Test case]
  * Steps to reproduce:
- 1. Install image
+ 1. Install in OEM mode
  2. Boot into OS
  3. Check the wifi status in network-manager applet
  
  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established
  
  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.
  
+ 
+ [Regression potential]
+ The following are examples of possible regression scenarios from this stable 
update:
+ - Failure to get the wireless device ready at session start
+ - Driver loading issues for the wireless devices
+ - Failure to complete OEM preparation steps, due to the oem user remaining 
connected while it's being removed by the last steps of the OEM preparation 
process.
+ 
+ 
+ [Background information]
  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Incomplete
Status in wpa package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in ubiquity source package in Xenial:
  Confirmed
Status in wpa source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Users booting from OEM setup may find that their wireless device is "not 
ready" as per NetworkManager, because wpasupplicant is not running. This is 
because the steps taken to start in OEM prepare, before moving to the real 
system runs systemctl isolate, and wpasupplicant gets caught in the crossfire.

  
  [Test case]
  * Steps to reproduce:
  1. Install in OEM mode
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  
  [Regression potential]
  The following are examples of possible regression scenarios from this stable 
update:
  - Failure to get the wireless device ready at session start
  - Driver loading issues for the wireless devices
  - Failure to complete OEM preparation steps, due to the oem user remaining 
connected while it's being removed by the last steps of the OEM preparation 
process.

  
  [Background information]
  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1668410] Re: [SRU] Infinite loop trying to delete deleted HA router

[Corey Bryant]

** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

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

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

** Changed in: neutron (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: cloud-archive/mitaka
   Importance: Undecided => High

** Changed in: neutron (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: neutron (Ubuntu)
   Status: Triaged => Invalid

** Changed in: cloud-archive
   Status: New => Invalid

** Description changed:

- [Impact]
+ [Descriptoin]
  
  When deleting a router the logfile is filled up. See full log -
  http://paste.ubuntu.com/25429257/
  
  I can see the error 'Error while deleting router
  c0dab368-5ac8-4996-88c9-f5d345a774a6' occured 3343386 times from
  _safe_router_removed() [1]:
  
  $ grep -r 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' 
|wc -l
  3343386
  
  This _safe_router_removed() is invoked by L488 [2], if
  _safe_router_removed() goes wrong it will return False, then
  self._resync_router(update) [3] will make the code _safe_router_removed
  be run again and again. So we saw so many errors 'Error while deleting
  router X'.
  
  [1] 
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L361
  [2] 
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488
  [3] 
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L457
  
  [Test Case]
  
  That's because race condition between neutron server and L3 agent, after
  neutron server deletes HA interfaces the L3 agent may sync a HA router
  without HA interface info (just need to trigger L708[1] after deleting
  HA interfaces and before deleting HA router). If we delete HA router at
  this time, this problem will happen. So test case we design is as below:
  
  1, First update fixed package, and restart neutron-server by 'sudo
  service neutron-server restart'
  
  2, Create ha_router
  
  neutron router-create harouter --ha=True
  
  3, Delete ports associated with ha_router before deleting ha_router
  
  neutron router-port-list harouter |grep 'HA port' |awk '{print $2}' |xargs -l 
neutron port-delete
  neutron router-port-list harouter
  
  4, Update ha_router to trigger l3-agent to update ha_router info without
  ha_port into self.router_info
  
  neutron router-update harouter --description=test
  
  5, Delete ha_router this time
  
  neutron router-delete harouter
  
  [1] https://github.com/openstack/neutron/blob/mitaka-
  eol/neutron/db/l3_hamode_db.py#L708
  
  [Regression Potential]
  
  The fixed patch [1] for neutron-server will no longer return ha_router
  which is missing ha_ports, so L488 will no longer have chance to call
  _safe_router_removed() for a ha_router, so the problem has been
  fundamentally fixed by this patch and no regression potential.
  
  Besides, this fixed patch has been in mitaka-eol branch now, and
  neutron-server mitaka package is based on neutron-8.4.0, so we need to
  backport it to xenial and mitaka.
  
  $ git tag --contains 8c77ee6b20dd38cc0246e854711cb91cffe3a069
  mitaka-eol
  
  [1] https://review.openstack.org/#/c/440799/2/neutron/db/l3_hamode_db.py
  [2] 
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488

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

Title:
  [SRU] Infinite loop trying to delete deleted HA router

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in neutron:
  In Progress
Status in OpenStack Security Advisory:
  Won't Fix
Status in neutron package in Ubuntu:
  Invalid
Status in neutron source package in Xenial:
  Triaged

Bug description:
  [Descriptoin]

  When deleting a router the logfile is filled up. See full log -
  http://paste.ubuntu.com/25429257/

  I can see the error 'Error while deleting router
  c0dab368-5ac8-4996-88c9-f5d345a774a6' occured 3343386 times from
  _safe_router_removed() [1]:

  $ grep -r 'Error while deleting router c0dab368-5ac8-4996-88c9-f5d345a774a6' 
|wc -l
  3343386

  This _safe_router_removed() is invoked by L488 [2], if
  _safe_router_removed() goes wrong it will return False, then
  self._resync_router(update) [3] will make the code
  _safe_router_removed be run again and again. So we saw so many errors
  'Error while deleting router X'.

  [1] 
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L361
  [2] 
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L488
  [3] 
https://github.com/openstack/neutron/blob/mitaka-eol/neutron/agent/l3/agent.py#L457

  [Test Case]

  That's because race condition between neutron server and L3 agent,
  after 

[Group.of.nepali.translators] [Bug 1713059] Re: drop db sync commands from OpenStack packages

[Corey Bryant]

** Also affects: cloud-archive/pike
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/ocata
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/newton
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

** Changed in: cloud-archive/mitaka
   Importance: Undecided => High

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

** Changed in: cloud-archive/newton
   Importance: Undecided => High

** Changed in: cloud-archive/newton
   Status: New => Triaged

** Changed in: cloud-archive/ocata
   Importance: Undecided => High

** Changed in: cloud-archive/ocata
   Status: New => Triaged

** Changed in: cloud-archive/pike
   Importance: Undecided => High

** Changed in: cloud-archive/pike
   Status: New => Triaged

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

Title:
  drop db sync commands from OpenStack packages

Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive newton series:
  Triaged
Status in Ubuntu Cloud Archive ocata series:
  Triaged
Status in Ubuntu Cloud Archive pike series:
  Triaged
Status in aodh package in Ubuntu:
  Fix Released
Status in ceilometer package in Ubuntu:
  Fix Released
Status in cinder package in Ubuntu:
  Fix Released
Status in glance package in Ubuntu:
  Fix Released
Status in ironic package in Ubuntu:
  Fix Released
Status in keystone package in Ubuntu:
  Fix Released
Status in manila package in Ubuntu:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in openstack-trove package in Ubuntu:
  Fix Released
Status in panko package in Ubuntu:
  Fix Released
Status in aodh source package in Xenial:
  Invalid
Status in ceilometer source package in Xenial:
  Invalid
Status in cinder source package in Xenial:
  Invalid
Status in glance source package in Xenial:
  Invalid
Status in ironic source package in Xenial:
  Invalid
Status in keystone source package in Xenial:
  Invalid
Status in manila source package in Xenial:
  Invalid
Status in nova source package in Xenial:
  Triaged
Status in openstack-trove source package in Xenial:
  Invalid
Status in panko source package in Xenial:
  Invalid
Status in aodh source package in Zesty:
  Invalid
Status in ceilometer source package in Zesty:
  Invalid
Status in cinder source package in Zesty:
  Invalid
Status in glance source package in Zesty:
  Invalid
Status in ironic source package in Zesty:
  Invalid
Status in keystone source package in Zesty:
  Invalid
Status in manila source package in Zesty:
  Invalid
Status in nova source package in Zesty:
  Triaged
Status in openstack-trove source package in Zesty:
  Invalid
Status in panko source package in Zesty:
  Invalid
Status in aodh source package in Artful:
  Fix Released
Status in ceilometer source package in Artful:
  Fix Released
Status in cinder source package in Artful:
  Fix Released
Status in glance source package in Artful:
  Fix Released
Status in ironic source package in Artful:
  Fix Released
Status in keystone source package in Artful:
  Fix Released
Status in manila source package in Artful:
  Fix Released
Status in nova source package in Artful:
  Fix Released
Status in openstack-trove source package in Artful:
  Fix Released
Status in panko source package in Artful:
  Fix Released

Bug description:
  [Impact]

  nova-compute service does not need access to the database, systems
  where nova.conf is configured without a database connection the nova-
  common package will fail to get configured

  [Test Case]

  Using this deployer bundle -> http://paste.ubuntu.com/25426891/
  juju-deployer -c bundle.yaml -d -v -s 10 xenial-mitaka
  # once everything is installed
  git clone https://github.com/openstack-charmers/openstack-charms-tools.git
  cd openstack-charms-tools/
  ./os-upgrade.py -o cloud:xenial-newton

  Expected result:

  nova-compute units upgrade their packages to newton without errors

  Actual result:

  nova-common fails to configure itself in the nova-compute units

  [Regression Potential]

  This change was tested in a staging environment and no regressions
  were detected, but any possible regression will express itself as a
  failure running "nova-manage db sync".

  [Other Info]
  The original reason this bug was opened is that nova db sync is executed when 
the 'connection' is not defined. Let's fix that and at the same time drop all 
db syncs from OpenStack packages in Pike.

  More on the nova issue:

  When the 'connection' configuration key is NOT defined in
  /etc/nova/nova.conf the nova-common.postinst script still tries to run
  'nova-manage db sync'

  root@juju-b24bc9-mno-18:~# grep connection /etc/nova/nova.conf
  root@juju-b24bc9-mno-18:~# 

[Group.of.nepali.translators] [Bug 1612600] Re: backuppc 3.3.1-2ubuntu3 breaks pool graphs on the Status page

[Launchpad Bug Tracker]

This bug was fixed in the package backuppc - 3.3.1-2ubuntu3.3

---
backuppc (3.3.1-2ubuntu3.3) xenial; urgency=medium

  * Fix debian/rules so the patch is actually applied. (LP: #1612600)

 -- Brian Murray   Mon, 21 Aug 2017 09:53:00 -0700

** Changed in: backuppc (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/1612600

Title:
  backuppc 3.3.1-2ubuntu3 breaks pool graphs on the Status page

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

Bug description:
  Upgraded system from 14.04 LTS to 16.04.1 LTS.

  As a result, the rrd pool size graphs stopped displaying, instead
  showing "default image" icons.

  Investigation has shown that this is due to the permissions conflict.
  Whatever user executes backuppc/index.cgi cannot run /usr/bin/rrdtool.

  The fix is as per
  https://sourceforge.net/p/backuppc/mailman/message/18724263/.

  Namely, here's a relevant code snapshot in
  /usr/share/backuppc/lib/BackupPC/CGI/GeneralInfo.pm:

$In{image} =~ /([0-9]+)/;
my $weeks = $1;
my $real = $<;# NEW
$< = $>; # NEW
print "Content-type: image/png\n\n";
print `/usr/bin/rrdtool graph - --imgformat=PNG --start=end-${weeks}w 
--end=-300 --title="BackupPC Pool Size (${weeks} weeks)" --base=1000 
--height=100 --width=600 --alt-autoscale-max --lower-limit=0 
--vertical-label="" --slope-mode --font TITLE:10:Times --font AXIS:8:Times 
--font LEGEND:8:Times --font UNIT:8:Times -c BACK#FF 
DEF:ao="$LogDir/pool.rrd":ckb:AVERAGE CDEF:a=ao,1024,* AREA:a#95B8DB:"CPool in 
bytes"  GPRINT:a:LAST:"Current\\:%8.2lf %s" GPRINT:a:AVERAGE:"Average\\:%8.2lf 
%s" GPRINT:a:MAX:"Maximum\\:%8.2lf %s\\n"`;
$< = $real; # NEW
return;

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1612600/+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 1238110] Re: makedumpfile needs porting for AArch64

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.5

---
makedumpfile (1:1.5.9-5ubuntu0.5) xenial; urgency=medium

  * Build on arm64. While this version of makedumpfile doesn't support
creating filtered dumps of Ubuntu arm64 kernels, it does satisfy
the dependency for kdump-tools, which will cleanly fallback to 'cp'
mode if makedumpfile fails. LP: #1238110, LP: #1694859.

 -- dann frazier   Mon, 17 Jul 2017 16:58:59
-0600

** Changed in: makedumpfile (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/1238110

Title:
  makedumpfile needs porting for AArch64

Status in Linaro AArch64 cross-distro work:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  kdump-tools is not installable on arm64 because it depends on makedumpfile, 
which is not currently built on arm64. Adding arm64 to the Architecture list in 
debian/control is all that is needed for it to build successfully.

  That said, xenial's version was too old to support filtering kdump-
  enabled xenial kernels (>= 4.10.0). So, this doesn't actually produce
  a *useful* makedumpfile, but does allow kdump-tools to be installed,
  which unblocks collection of (unfiltered) crash dump files.

  [Test Case]
  On an arm64 system:
   sudo apt install kdump-tools

  [Regression Risk]
  The only change here is to make a binary package available on arm64 that 
previously was not - regression risk to existing architectures should therefore 
be negligible.

  Note: Enabling a binary package for an architecture where it's known
  not to be useful - at last on it's own - is obviously non-ideal. I
  considered other options, but they all seem to add unnecessary
  regression risk:

  - Demoting the "Depends:" to a "Recommends:". I actually think we
  should do this going forward (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=865701), but this would be a change in behavior
  to people who may install kdump-tools w/ Recommends-disabled and
  expect to stil get makedumpfile.

  - Demoting only on arm64: This isn't possible unless we switch kdump-
  tools from Binary: any to Binary: all. I also think there are good
  reasons to do that in future releases (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=863858), but it seems overkill for just enabling
  arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-aarch64/+bug/1238110/+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 1694859] Re: arm64 kernel crashdump support

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.5

---
makedumpfile (1:1.5.9-5ubuntu0.5) xenial; urgency=medium

  * Build on arm64. While this version of makedumpfile doesn't support
creating filtered dumps of Ubuntu arm64 kernels, it does satisfy
the dependency for kdump-tools, which will cleanly fallback to 'cp'
mode if makedumpfile fails. LP: #1238110, LP: #1694859.

 -- dann frazier   Mon, 17 Jul 2017 16:58:59
-0600

** Changed in: makedumpfile (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/1694859

Title:
  arm64 kernel crashdump support

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in makedumpfile source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  In Progress
Status in linux source package in Yakkety:
  Won't Fix
Status in makedumpfile source package in Yakkety:
  Won't Fix
Status in kexec-tools source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in makedumpfile source package in Zesty:
  Fix Released

Bug description:
  Note: Updates are being staged at ppa:dannf/arm64-kdump.

  [Impact]
  It is not possible to collect a kernel crash dump from a crashed arm64 server 
for later debugging.

  [Test Case]
  sudo apt install kdump-tools
  (reboot, so crashkernel= is added to the kernel commandline)
  echo c | sudo tee /proc/sysrq-trigger

  Crash dump should occur, with artifacts collected in /var/crash.

  If you want to verify that the dump is usable, install the
  corresponding linux-image--dbgsym package and run:

  sudo crash /usr/lib/debug/boot/vmlinux-
  /var/crash//dump.

  crash should successfully load, placing you at a "crash>" prompt. At that 
prompt, you can issue the 'bt' command to see a backtrace.
  Note: you need crash from zesty (7.1.8-1ubuntu1) or later.

  [Regression Risk]
  = Kernel =
  3 patches here touch code outside of arch/arm64/:

  memblock: add memblock_clear_nomap()
  This adds a new function with no callers, so regression risk is negligible.
  (A later patch adds a call to it under arch/arm64/).

  memblock: add memblock_cap_memory_range()
  This refactors some of the code in memblock_mem_limit_remove_map() into a new 
function. The only existing caller of memblock_mem_limit_remove_map() is under 
arch/arm64/, so the regression risk outside of arm64 is negligible.

  efi/libstub/arm*: Set default address and size cells values for an empty dtb
  Because this code is for EFI platforms that support device-tree, it is 
de-facto ARM-specific (as noted in the patch title).

  For arm64, we have mitigated the risk by explicit regression testing on 
several platforms:
   - Qualcomm QDF2400
   - Cavium ThunderX CRB1S
   - HP m400 (X-Gene)
   - HiSilicon D05 (Hi07)

  = kexec-tools =
  == zesty ==
  For zesty, 10 patches are required to add kdump support.

  0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch:
  This modifies a function used on armhf & x86. The description explains the 
change, and why it does not impact those archs:

  -
  The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not
  be affected by this change because
  * arm
    The callback function only returns -1 or 0, and the return value of
    kexec_iomem_for_each_line() will never be used.
  * sh, x86
    The callback function may return (-1 for sh,) 0 or 1, but always returns
    1 once we have reached the maximum number of entries allowed.
    Even so the current kexec_iomem_for_each_line() counts them up.
    This change actually fixes this bug.
  -

  0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch:
  This generalizes a function that was duplicated by arm & x86 and makes it 
common so arm64 can use it.

  The remaining 8 of these only touch code in kexec/arch/arm64, so
  regression risk for other architectures is negligible.

  Finally, I have tested this update on both i386 and amd64 VMs. i386
  crashes do not currently work in zesty (filed LP: #1699874), and my
  test results show no change there. amd64 worked before, and continues
  to work with these changes.

  == yakkety ==
  Since yakkety is based on an older upstream, 6 additional patches are 
required:

  arm-fix-get_kernel_stext_sym-to-close-its-file.patch:
  This is a cleanup patch, cherry-picked because it allows later patches to 
apply w/o backporting. ARM-specific.

  kexec-add-max_size-to-memory_ranges.patch:
  Adds a new element to struct, to be used by later commits.

  

[Group.of.nepali.translators] [Bug 1713472] Re: linux-gcp: 4.10.0-1005.5 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-gcp: 4.10.0-1005.5 -proposed tracker

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

Bug description:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713470
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713472/+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 1714298] Re: Xenial update to 4.4.85 stable release

[Stefan Bader]

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.85 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.85 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.85 stable release shall be
- applied:
+ The following patches from the 4.4.85 stable release shall be applied:
+ * af_key: do not use GFP_KERNEL in atomic contexts
+ * dccp: purge write queue in dccp_destroy_sock()
+ * dccp: defer ccid_hc_tx_delete() at dismantle time
+ * ipv4: fix NULL dereference in free_fib_info_rcu()
+ * net_sched/sfq: update hierarchical backlog when drop packet
+ * ipv4: better IP_MAX_MTU enforcement
+ * sctp: fully initialize the IPv6 address in sctp_v6_to_addr()
+ * tipc: fix use-after-free
+ * ipv6: reset fn->rr_ptr when replacing route
+ * ipv6: repair fib6 tree in failure case
+ * tcp: when rearming RTO, if RTO time is in past then fire RTO ASAP
+ * irda: do not leak initialized list.dev to userspace
+ * net: sched: fix NULL pointer dereference when action calls some targets
+ * net_sched: fix order of queue length updates in qdisc_replace()
+ * mei: me: add broxton pci device ids
+ * mei: me: add lewisburg device ids
+ * Input: trackpoint - add new trackpoint firmware ID
+ * Input: elan_i2c - add ELAN0602 ACPI ID to support Lenovo Yoga310
+ * ALSA: core: Fix unexpected error at replacing user TLV
+ * ALSA: hda - Add stereo mic quirk for Lenovo G50-70 (17aa:3978)
+ * ARCv2: PAE40: Explicitly set MSB counterpart of SLC region ops addresses
+ * i2c: designware: Fix system suspend
+ * drm: Release driver tracking before making the object available again
+ * drm/atomic: If the atomic check fails, return its value first
+ * drm: rcar-du: lvds: Fix PLL frequency-related configuration
+ * drm: rcar-du: lvds: Rename PLLEN bit to PLLON
+ * drm: rcar-du: Fix crash in encoder failure error path
+ * drm: rcar-du: Fix display timing controller parameter
+ * drm: rcar-du: Fix H/V sync signal polarity configuration
+ * tracing: Fix freeing of filter in create_filter() when set_str is false
+ * cifs: Fix df output for users with quota limits
+ * cifs: return ENAMETOOLONG for overlong names in cifs_open()/cifs_lookup()
+ * nfsd: Limit end of page list when decoding NFSv4 WRITE
+ * perf/core: Fix group {cpu,task} validation
+ * Bluetooth: hidp: fix possible might sleep error in hidp_session_thread
+ * Bluetooth: cmtp: fix possible might sleep error in cmtp_session
+ * Bluetooth: bnep: fix possible might sleep error in bnep_session
+ * binder: use group leader instead of open thread
+ * binder: Use wake up hint for synchronous transactions.
+ * ANDROID: binder: fix proc->tsk check.
+ * iio: imu: adis16480: Fix acceleration scale factor for adis16480
+ * iio: hid-sensor-trigger: Fix the race with user space powering up sensors
+ * staging: rtl8188eu: add RNX-N150NUB support
+ * ASoC: simple-card: don't fail if sysclk setting is not supported
+ * ASoC: rsnd: disable SRC.out only when stop timing
+ * ASoC: rsnd: avoid pointless loop in rsnd_mod_interrupt()
+ * ASoC: rsnd: Add missing initialization of ADG req_rate
+ * ASoC: rsnd: ssi: 24bit data needs right-aligned settings
+ * ASoC: rsnd: don't call update callback if it was NULL
+ * ntb_transport: fix qp count bug
+ * ntb_transport: fix bug calculating num_qps_mw
+ * ACPI: ioapic: Clear on-stack resource before using it
+ * ACPI / APEI: Add missing synchronize_rcu() on NOTIFY_SCI removal
+ * Linux 4.4.85

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

Title:
  Xenial update to 4.4.85 stable release

Status in linux package in 

[Group.of.nepali.translators] [Bug 1714298] [NEW] Xenial update to 4.4.85 stable release

[Stefan Bader]

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.85 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.85 stable release shall be
applied:

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

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

** Also affects: linux (Ubuntu Xenial)
   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/1714298

Title:
  Xenial update to 4.4.85 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.85 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.85 stable release shall be
  applied:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714298/+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 1610168] Re: error: 'basic_string<_CharT, _Traits, _Allocator>' is missing exception specification

[Brian Murray]

** Also affects: libc++ (Ubuntu Xenial)
   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/1610168

Title:
  error: 'basic_string<_CharT, _Traits, _Allocator>' is missing
  exception specification

Status in libc++ package in Ubuntu:
  Confirmed
Status in libc++ source package in Xenial:
  New
Status in libc++ package in Debian:
  Fix Released

Bug description:
  This is mirroring Debian bug #808086 https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=808086

  Compiling any source file that includes  with clang 3.8 and
  -std=c++11 -stdlib=libc++ results in a compile error.

  While this is a minor bug in Debian (as it doesn't ship 3.8 yet),
  xenial does, and that's a major problem as it makes libc++ useless.

  clang: warning: argument unused during compilation: '-stdlib=libc++'
  In file included from test.cpp:1:
  In file included from /usr/include/c++/v1/iostream:38:
  In file included from /usr/include/c++/v1/ios:216:
  In file included from /usr/include/c++/v1/__locale:15:
  /usr/include/c++/v1/string:1938:44: error: 'basic_string<_CharT, _Traits, 
_Allocator>' is missing exception specification 
'noexcept(is_nothrow_copy_constructible::value)'
  basic_string<_CharT, _Traits, _Allocator>::basic_string(const allocator_type& 
__a)
     ^
  /usr/include/c++/v1/string:1326:76: note: previous declaration is here
  __attribute__ ((__visibility__("hidden"), __always_inline__)) explicit 
basic_string(const allocator_type& __a)
     ^
  1 error generated.

  --

  Update (30 Aug 2017): as per
  https://wiki.ubuntu.com/StableReleaseUpdates :

  [Impact]

  This bug makes it impossible to compile any C++11 source file that
  includes  with clang 3.8 using libc++. Any non-trivial C++11
  codebase is affected, making the whole libc++ package useless.

  [Test Case]

  See above. Create a C++ file that simply contains #include 
  and compile it with clang++ -std=c++11 -stdlib=libc++ file.cpp.

  [Regression Potential]

  The current  header simply does not work with clang-3.8 under
  any condition, so there is no regression potential.

  The regression potential for GCC is also extremely limited: no package
  whatsoever uses GCC in combination with libc++, and the fact that GCC
  5.4 -- currently in Xenial -- does not detect the error that Clang
  detects is just showing that GCC is bugged in this regard.

  [Other Info]

  The patch/workaround fixes the problem. See also the discussion at the
  linked Debian bug report as well as
  https://stackoverflow.com/q/37096062

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libc++/+bug/1610168/+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 1712867] Re: [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

[Andy Whitcroft]

** Also affects: linux-azure (Ubuntu Xenial)
   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/1712867

Title:
  [Hyper-V] 16.04 kexec-tools doesn't match linux-azure

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Xenial:
  New

Bug description:
  Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the 
following error:
  kdump-tools[1436]: ELF core (kcore) parse failed

  Perhaps the artful kexec-tools should be backported?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1712867/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

This bug was fixed in the package cups - 2.1.3-4ubuntu0.3

---
cups (2.1.3-4ubuntu0.3) xenial; urgency=high

  * Adding maintainer script debian/cups-daemon.prerm to deal with situations
where "old-version" (installed package) prerm script fails. (LP: #1642966).

cups (2.1.3-4ubuntu0.2) xenial; urgency=medium

  * Make cups.path unit be part of the cups.service, since cups.path
should stop if and when cups.service is stopped. LP: #1642966

cups (2.1.3-4ubuntu0.1) xenial-proposed; urgency=medium

  * Removed auto-shutdown-on-idle-also-with-webinterface-on.patch
as it causes CUPS to auto-shutdown when web interface support is
active (LP: #1598300).

 -- Eric Desrochers   Fri, 18 Aug 2017
12:08:28 -0400

** Changed in: cups (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/1642966

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Released
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This concerns only Xenial (16.04)!

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

  [Regression Potential]

  Regression risk is low, the fix mitigate cups failing to stop/restart
  on upgrade. No source code change, just adding a custom pre-removal
  maintainer script in case of upgrade failure.

  [Regression in Pending SRU page]

  * Regression in autopkgtest for c2esp (armhf): test log

  This autopkgtest seems always fails :

  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf

  c2esp [xenial/armhf]

  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻

  Additionally look at Till comment :
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129

  * Regression in autopkgtest for libreoffice (i386): test log

  It's a known issue, A regression in the kernel, which breaks libreoffice with 
java enabled on i386 :
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772

  ... so until this is fixed upstream in the 

[Group.of.nepali.translators] [Bug 1598300] Re: CUPS web interface stops responding after a while

[Launchpad Bug Tracker]

This bug was fixed in the package cups - 2.1.3-4ubuntu0.3

---
cups (2.1.3-4ubuntu0.3) xenial; urgency=high

  * Adding maintainer script debian/cups-daemon.prerm to deal with situations
where "old-version" (installed package) prerm script fails. (LP: #1642966).

cups (2.1.3-4ubuntu0.2) xenial; urgency=medium

  * Make cups.path unit be part of the cups.service, since cups.path
should stop if and when cups.service is stopped. LP: #1642966

cups (2.1.3-4ubuntu0.1) xenial-proposed; urgency=medium

  * Removed auto-shutdown-on-idle-also-with-webinterface-on.patch
as it causes CUPS to auto-shutdown when web interface support is
active (LP: #1598300).

 -- Eric Desrochers   Fri, 18 Aug 2017
12:08:28 -0400

** Changed in: cups (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/1598300

Title:
  CUPS web interface stops responding after a while

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

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

  [Regression in Pending SRU page]

  * Regression in autopkgtest for c2esp (armhf): test log

  This autopkgtest seems always fails :

  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf

  c2esp [xenial/armhf]

  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻

  Additionally look at Till comment :
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129

  * Regression in autopkgtest for libreoffice (i386): test log

  It's a known issue, A regression in the kernel, which breaks libreoffice with 
java enabled on i386 :
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772

  ... so until this is fixed upstream in the kernel and backported in an
  ubuntu kernel, I'm afraid the only option is to just ignore the
  failure.

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

[Group.of.nepali.translators] [Bug 1540008] Re: USB permissions not set at install time (udevd name changed?)

[Launchpad Bug Tracker]

This bug was fixed in the package nut - 2.7.4-5ubuntu2.1

---
nut (2.7.4-5ubuntu2.1) zesty; urgency=medium

  * debian/nut-server.postinst: The udevd process is called systemd-udevd for
quite sometimes already, properly detect whether it's running or not, this
should fix the devices permissions for USB UPS's (LP: #1540008)

 -- Christian Ehrhardt   Thu, 17 Aug
2017 15:26:30 +0200

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

Title:
  USB permissions not set at install time (udevd name changed?)

Status in nut package in Ubuntu:
  Fix Released
Status in nut source package in Trusty:
  In Progress
Status in nut source package in Xenial:
  In Progress
Status in nut source package in Yakkety:
  Won't Fix
Status in nut source package in Zesty:
  Fix Released
Status in nut package in Debian:
  New

Bug description:
  [Impact]

   * Installing nut provides rules to set up the devnodes accordingly, but
     on an install the trigger to run those is missed to be executed due to
     an error in postinst.

   * Fix is a backport from Debian repo
     (https://anonscm.debian.org/cgit/collab-maint/nut.git/commit/id=d31c6dcb) 
, which works in artful already

  [Test Case]

   * Plug in a usb controlled UPS of your choice
   * Install nut-server
   * The device node created should be mode 664 and group "nut", but it is
     not.
   * Install the proposed package with the fix
   * that should trigger the rules to run and it should now be created with
     proper permissions.

   * In the lack of special HW there is a fallback
   * Create a VM and give it some USB device
   * Start in one console  "sudo udevadm monitor"
   * On installing the nut-server package the USB events should be 
re-triggered, but they are not yet today - with the fixed package they are.

  [Regression Potential]

   * The postinst trigger never worked, now it will work. If on a system the
     rules fail to execute there might be an issue, but since the are only
     triggered (async udev) the install will not fail due to that. I think
     in the worst case they are just still not executed.
   * Vice versa once they are executed correctly the changed permission
     could be an issue for odd setups that relied on the broken permission,
     but I explained in the Regression potential section of bug 1099947 that
     is released together why I think that is no issue.

  [Other Info]

   * n/a

  
  1) $ lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  2) nut-server: 2.7.1-1ubuntu1; udev: 204-5ubuntu20.15

  3) On a fresh install of Ubuntu 14.04 (amd64), I installed the nut-
  server package while the UPS was already connected via USB. After
  installation, the permissions described by /lib/udev/rules.d/52-nut-
  usbups.rules should have changed the group of the corresponding
  /dev/bus/usb/*/* node to 'nut'.

  4) The owner/group for the /dev/bus/usb node remained root:root.
  Manually running 'udevadm trigger --subsystem-match=usb
  --action=change' changed the group to 'nut'. (From past experience
  tracking down related udev+nut bugs, unplugging and re-plugging the
  USB cable would yield similar results.)

  However, that udevadm command is included in the postinst for nut-
  server, and it is guarded with a pidof check for 'udevd':

  # ask udev to check for new udev rules
  [ -x /etc/init.d/udev ] && pidof udevd > /dev/null \
    && udevadm trigger --subsystem-match=usb --action=change

  This most likely needs to be amended to include the current process
  name, 'systemd-udevd'. I checked the control files, and unless the
  udevd process name has changed back, I believe this will affect vivid,
  wily and xenial as well as trusty. (I will let someone else add those
  later tags if that turns out to be the case.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1540008/+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 1708305] Re: Realtime feature mlockall: Cannot allocate memory

[Launchpad Bug Tracker]

This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.14

---
libvirt (1.3.1-1ubuntu10.14) xenial; urgency=medium

  * d/p/bug-1708305-qemu-Fix-memory-locking-limit-calculation.patch:
Remove memlock limit when using .
(LP: #1708305).

 -- Jorge Niedbalski   Thu, 10 Aug 2017
22:50:46 -0400

** Changed in: libvirt (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/1708305

Title:
  Realtime feature mlockall: Cannot allocate memory

Status in Ubuntu Cloud Archive:
  Fix Committed
Status in Ubuntu Cloud Archive mitaka series:
  In Progress
Status in Ubuntu Cloud Archive ocata series:
  In Progress
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Fix Released
Status in libvirt source package in Zesty:
  Fix Released
Status in libvirt source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Guest definitions that uses locked memory + hugepages fail to spawn

   * Backport upstream fix to solve that issue

  
  [Environment]

  root@buneary:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  Codename: xenial

  root@buneary:~# uname -r
  4.10.0-29-generic

  Reproducible also with the 4.4 kernel.

  [Detailed Description]

  When a guest memory backing stanza is defined using the  stanza + 
hugepages,
  as follows:

    
  
    
    
  
  
  
    

  (Full guest definition: http://paste.ubuntu.com/25229162/)

  The guest fails to start due to the following error:

  2017-08-02 20:25:03.714+: starting up libvirt version: 1.3.1, package: 
1ubuntu10.12 (Christian Ehrhardt  Wed, 19 Jul 
2017 08:28:14 +0200), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.14), 
hostname: buneary.seg
  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name reproducer2 -S -machine 
pc-i440fx-2.5,accel=kvm,usb=off -cpu host -m 124928 -realtime mlock=on -smp 
32,sockets=16,cores=1,threads=2 -object 
memory-backend-file,id=ram-node0,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,share=yes,size=64424509440,host-nodes=0,policy=bind
 -numa node,nodeid=0,cpus=0-15,memdev=ram-node0 -object 
memory-backend-file,id=ram-node1,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu,share=yes,size=66571993088,host-nodes=1,policy=bind
 -numa node,nodeid=1,cpus=16-31,memdev=ram-node1 -uuid 
2460778d-979b-4024-9a13-0c3ca04b18ec -no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-reproducer2/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive 
file=/var/lib/uvtool/libvirt/images/test-ds.qcow,format=qcow2,if=none,id=drive-virtio-disk0,cache=none
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-vnc 127.0.0.1:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  Domain id=14 is tainted: host-cpu
  char device redirected to /dev/pts/1 (label charserial0)

  mlockall: Cannot allocate memory

  2017-08-02T20:25:37.732772Z qemu-system-x86_64: locking memory failed
  2017-08-02 20:25:37.811+: shutting down

  This seems to be due to the setrlimit for RLIMIT_MEMLOCK is too low for 
mlockall
  to work given the large amount of memory.

  There is a libvirt upstream patch that enforces the existence of the
  hard_limit stanza when using with  in the memory backing settings.

  
https://github.com/libvirt/libvirt/commit/c2e60ad0e5124482942164e5fec088157f5e716a

  Memory locking can only work properly if the memory locking limit
  for the QEMU process has been raised appropriately: the default one
  is extremely low, so there's no way the guest will fit in there.

  The commit
  
https://github.com/libvirt/libvirt/commit/7e667664d28f90bf6916604a55ebad7e2d85305b
  is also required when using hugepages and the locked stanza.

  [Test Case]
   * Define a guest that uses the following stanzas (See for a full guest 
reference: http://paste.ubuntu.com/25288141/)

    120
    120

    
  
    
    
  
  
  
    

  * virsh define guest.xml
  * virsh start guest.xml
  * Without the fix, the following error will be raised and the guest
  will not start.

  root@buneary:/home/ubuntu# virsh start reproducer2
  error: Failed to start domain reproducer2
  error: internal error: process exited while connecting to monitor: 

[Group.of.nepali.translators] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

Marking Won't fix for Yakkety as it is EOL.

Removing sts-sru-needed tag until patches are ready.

** Changed in: rsyslog (Ubuntu Yakkety)
   Status: New => Won't Fix

** Tags removed: sts-sru-needed

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

Title:
  Add a trigger to reload rsyslog when a new configuration file is
  dropped in /etc/rsyslog.d

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Trusty:
  New
Status in rsyslog source package in Xenial:
  New
Status in rsyslog source package in Yakkety:
  Won't Fix
Status in rsyslog source package in Zesty:
  New
Status in rsyslog source package in Artful:
  Fix Released
Status in rsyslog package in Debian:
  Fix Released

Bug description:
  [Impact]
  Servers or cloud instances will not log important messages after initial 
deployment. Manual reboot or restart of services is necessary to get expected 
behaviour.

  [Test Case]
  1) Install, enable and start haproxy
  2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed
  3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT 
created
  4) Restart rsyslog service
  5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created
  6) Restart haproxy service and observe that log now is filled with entries

  With the patched deb steps 3,4 and 6 becomes irrelevant and everything
  works out of the box.

  [Regression Potential]
  Minimal.

  This patch merges a patch from Debian where a trigger is added to the
  rsyslog package that fires when other debs drop files into
  /etc/rsyslog.d.

  
  [Original Bug Description]
  rsyslog should reload its configuration when other packages drop 
configuration in /etc/rsyslog.d

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337

  https://anonscm.debian.org/cgit/collab-
  maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+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 1706426] Re: flashcache 3.1.3+git20150701-5 ADT test failure with linux 4.13.0-2.3

[Launchpad Bug Tracker]

This bug was fixed in the package flashcache -
3.1.3+git20150701-5ubuntu1

---
flashcache (3.1.3+git20150701-5ubuntu1) artful; urgency=medium

  * Initialize bi_op_flags in dm_io_request structures (LP: #1714185).
  * Fix DKMS compile for 4.13+ kernels (LP: #1706426).

 -- Stefan Bader   Wed, 30 Aug 2017 16:49:59
+0200

** Changed in: flashcache (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/1706426

Title:
  flashcache 3.1.3+git20150701-5 ADT test failure with linux 4.13.0-2.3

Status in flashcache package in Ubuntu:
  Fix Released
Status in flashcache source package in Xenial:
  In Progress

Bug description:
  SRU Justification (Xenial):

  Impact: Due to upstream changes the flashcache version in Xenial will
  not build the flashcache module for kernel version 4.13 or later. 4.13
  will becom the hwe-edge/hwe kernel at some point.

  Fix: Cherry-pick compat-4.13 patch from the Artful package into
  Xenial.

  Testcase:
  - dkms build of flashcache module for 4.4 and 4.8 or 4.10
  - quick functional test as described in bug #1714185

  ---

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/amd64/f/flashcache/20170725_182120_fab5e@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/i386/f/flashcache/20170725_185202_fab5e@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-bootstrap/artful/ppc64el/f/flashcache/20170725_155148_fab5e@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashcache/+bug/1706426/+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 1714185] Re: flashcache is not usable on kernel version 4.8 and later

[Launchpad Bug Tracker]

This bug was fixed in the package flashcache -
3.1.3+git20150701-5ubuntu1

---
flashcache (3.1.3+git20150701-5ubuntu1) artful; urgency=medium

  * Initialize bi_op_flags in dm_io_request structures (LP: #1714185).
  * Fix DKMS compile for 4.13+ kernels (LP: #1706426).

 -- Stefan Bader   Wed, 30 Aug 2017 16:49:59
+0200

** Changed in: flashcache (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/1714185

Title:
  flashcache is not usable on kernel version 4.8 and later

Status in flashcache package in Ubuntu:
  Fix Released
Status in flashcache source package in Xenial:
  In Progress
Status in flashcache source package in Zesty:
  In Progress

Bug description:
  SRU justification:

  Impact:
  The flashcache DKMS module is building but due to an incomplete adaptation 
for the bi_op/bi_opf split the resulting device-mapper logical volume is not 
properly writing back data to the backing device.
  !!! It is possible to write to the volume but the data is LOST !!!

  Fix:
  When setting up internal device-mapper IO structures we *must* also 
initialize bi_op_flags. At least when the structure is on the stack and is set 
up with individual assignments. Maybe it would not be required for the { ... } 
form but better be explicit in all cases.

  Testcase:
  - prereq: two block devices (disks or partitions), for testing this can also
be loop devices. also need flashcache-utils and flashcache-dkms
  - run "sudo flashcache-create -p back   "
  - run "sudo mkfs.ext4 /dev/mapper/"
  - run "sudo fsck -f /dev/mapper/"
  - run "sudo dmsetup remove " (this can take a bit)
  - run "sudo fsck -f "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashcache/+bug/1714185/+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 1713465] Re: linux-snapdragon: 4.4.0-1074.79 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

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

** Description changed:

  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 31. August 2017 12:31 UTC

** Description changed:

  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 31. August 2017 12:31 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-snapdragon: 4.4.0-1074.79 -proposed tracker

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

Bug description:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713465/+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 1713472] Re: linux-gcp: 4.10.0-1005.5 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

** Description changed:

  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713470
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 31. August 2017 12:00 UTC

** Description changed:

  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713470
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Thursday, 31. August 2017 12:00 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-gcp: 4.10.0-1005.5 -proposed tracker

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

Bug description:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713470
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713472/+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 1714185] Re: flashcache is not usable on kernel version 4.8 and later

[Andy Whitcroft]

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

** Also affects: flashcache (Ubuntu Zesty)
   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/1714185

Title:
  flashcache is not usable on kernel version 4.8 and later

Status in flashcache package in Ubuntu:
  In Progress
Status in flashcache source package in Xenial:
  In Progress
Status in flashcache source package in Zesty:
  In Progress

Bug description:
  SRU justification:

  Impact:
  The flashcache DKMS module is building but due to an incomplete adaptation 
for the bi_op/bi_opf split the resulting device-mapper logical volume is not 
properly writing back data to the backing device.
  !!! It is possible to write to the volume but the data is LOST !!!

  Fix:
  When setting up internal device-mapper IO structures we *must* also 
initialize bi_op_flags. At least when the structure is on the stack and is set 
up with individual assignments. Maybe it would not be required for the { ... } 
form but better be explicit in all cases.

  Testcase:
  - prereq: two block devices (disks or partitions), for testing this can also
be loop devices. also need flashcache-utils and flashcache-dkms
  - run "sudo flashcache-create -p back   "
  - run "sudo mkfs.ext4 /dev/mapper/"
  - run "sudo fsck -f /dev/mapper/"
  - run "sudo dmsetup remove " (this can take a bit)
  - run "sudo fsck -f "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashcache/+bug/1714185/+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 1713467] Re: linux-aws: 4.4.0-1033.42 -proposed tracker

[Po-Hsu Lin]

4.4.0-1033.42 - aws
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html

Issue to note in x86_64 (aws):
  libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 15, bad 
configuration 3
  ubuntu_lxc - Failed to start networking in ubuntu-cloud container

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

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

** Tags added: regression-testing-passed

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

Title:
  linux-aws: 4.4.0-1033.42 -proposed tracker

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

Bug description:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713467/+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 1668724] Proposed package removed from archive

[Andy Whitcroft]

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

** Changed in: cgroup-lite (Ubuntu Precise)
   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/1668724

Title:
  fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in cgroup-lite source package in Precise:
  Won't Fix
Status in cgroup-lite source package in Trusty:
  New
Status in cgroup-lite source package in Xenial:
  Fix Committed
Status in cgroup-lite source package in Yakkety:
  Fix Committed

Bug description:
  I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
  and have noticed that the cgroups-mount script for mounting the
  cgroups inside the containers has stopped working. This is because
  systemd now comounts multiple controllers on a single hierarchy, which
  prevents mounting them individually inside the container.

  ===  SRU Justification 
  Impact: nested containers fail to start
  Reproduce:  create a root owned container;  install lxc and cgroup-lite;  
create a container, and try to start it.  Starting will fail if cgroup-lite is 
running in the first level container without this patch.
  Regression potential:  should be low, it's possible that the regexp is simply 
wrong for some cases.
  ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+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 1713468] Re: linux-gke: 4.4.0-1029.29 -proposed tracker

[Po-Hsu Lin]

4.4.0-1029.29 - gke
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html

Issue to note in x86_64 (gce):
  libhugetlbfs - 1 failed (brk_near_huge bug 1653597), Killed by signal 15, bad 
configuration 3
  ubuntu_lxc - Failed to start networking in ubuntu-cloud container


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

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

** Tags added: regression-testing-passed

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

Title:
  linux-gke: 4.4.0-1029.29 -proposed tracker

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

Bug description:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713468/+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 1713468] Re: linux-gke: 4.4.0-1029.29 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-gke: 4.4.0-1029.29 -proposed tracker

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

Bug description:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1713462
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1713468/+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 1597245] Re: [SRU] update check-all-the-things to xenial

[Launchpad Bug Tracker]

This bug was fixed in the package check-all-the-things -
2015.12.10ubuntu3.is.2017.05.20

---
check-all-the-things (2015.12.10ubuntu3.is.2017.05.20) xenial-security; 
urgency=medium

   * SRU to Ubuntu 16.04, from Ubuntu artful,
 fixing security issues (LP: #1597245)

check-all-the-things (2017.05.20) unstable; urgency=medium

  * New release.
- The "Check Things Securely Yet Again" release
- Support BSD versions of the find command
- Support running in more types of terminals/places
- Support running commands in other dirs for safety
- Support properly disabling flags/checks
- Disable remarks about already disabled checks
- Update documentation, TODO items and URLs
- Print remarks more nicely in certain situations
- Print filenames and line numbers where possible
- Flag checks:
  + dangerous - rpmlint ocaml-lintian
  + run-in-tmp-dir - luacheck puppet-lint epubcheck erl-tidy
  + fixme-silent - flawfinder gettext-lint-* luacheck hlint
  + network - cme-check-dpkg
  + manual - gettext-lint-spell
- Fix complexity - prevent arbitrary code execution
- Fix perlcritic - disable code execution, only run when perl present,
   increase verbosity to be more useful
- Fix clang-tidy regression from version 2016.06.29
- Fix zzuf - incorrect path matches
- Fix yamllint - incorrect find argument grouping
- Fix ELF & Perl checks - add MIME types
- Fix grep checks - use short options for portability
- Fix xapian-check - crash due to use of format strings
- Fix uudecode - include filenames in command-line
- Fix insecure-recv-keys - typo in regex
- Fix appstreamcli - unknown command-line option
- Fix m64-m32 - reduce false positives
- Fix gettext-lint-spell - add missing dependency, drop *.pot
- Fix afl - check it is installed properly
- Fix embed-dirs - add inc/ dirs for Perl packages
- Add podchecker - check Perl POD documentation
- Add pscan - check C printf format strings
- Add leaktracer - check programs for memory leaks
- Add tmperamental - check programs for tmpfile issues
- Add govet - report suspicious Go source code
- Add golint - report Go source code lint
- Add goimports - check missing/unused Go import lines
- Add rubocop - check Ruby code against Ruby Style Guide
- Add roodi - check Ruby code for design issues
- Add gendarme - check Mono/.NET ECMA CIL files
- Add make-phony - find misspelled .PHONY targets
- Add mypy - check Python static typing hints
- Add pyroma - check Python packaging quality
- Add bandit - check Python security quality
- Add dodgy - check dodgy lines in Python code
- Add vulture - check for dead Python code
- Add pycodestyle - check Python code style
- Add pydocstyle - check Python documentation style
- Add proselint - check for English prose issues
- Add chktex - check typographic errors in LaTeX docs
- Add fitscheck/wcslint/volint - FITS/VOTable files
- Add putty-private-key & openssh-private-key-rsa1
- Remove ghc-mod - just a wrapper for hlint
- TODO items for wtf flake8-plugins xpi-addons-linter
  go-fix libdetectcoll sha1collisiondetection giffix
  haxelint dockerlint dockerfile_lint dockerfile_checker
  truffleHog pyt chap Devel::Plumber

check-all-the-things (2017.01.15) unstable; urgency=high

  * New release.
- The "Check Things Securely Not Portably" release
- Reset terminal modes after commands to avoid colour spew
- Improve compatibility with Python 3.6
- Update python checks to not work on other distros
  because the `python -m` command is insecure
- Update checkers removed from Debian - allow to run if installed
- Update lrzip-test/zstd-test - add MIME types
- Add lz4-test - check lz4 compressed files
- Add path-max - check for non-portable path size macros
- TODO items for deep-text-correcter sblint decopy

check-all-the-things (2016.12.25) unstable; urgency=medium

  * New release.
- The "Check Everywhere For Tangerines" release
- Improve the 'no specific checks' remark
- Update php-syntax-check - ignore no files warning
- Update empty - never print inode/x-empty as unchecked
- Update pylint - check text/x-python files too
- Update python checks to work on other distros
- Add make - check Makefiles with GNU make
- Add pkg-config - check pkg-config .pc files
- Add t1lint - check Type 1 font files
- Add zstd-test - check zstd compressed files validity
- TODO items for urlycue multivalent pdf-hul pdfavalidation
  huntbugs spotbugs find-sec-bugs binskim

check-all-the-things (2016.09.03) unstable; urgency=medium

  * New release.
- The "Reproducibly Depend On Thing Checkers" release
- Fixes reproducible builds by sorting Recommends/Suggests (Closes: #829297)
- Rename an option in line with final 'Remarks' section rename