date:20161130

This bug was fixed in the package libvirt - 2.1.0-1ubuntu14

---
libvirt (2.1.0-1ubuntu14) zesty; urgency=medium

  * d/p/u/apparmor-fix-name-resolution.patch rework the fix to base
on the apparmor nameservice abstraction to be future proof (LP: #1546674).
  * d/p/ubuntu/apparmor-fix-new-devicetypes.patch add new block device types to
virt-aa-helpers profile (LP: #1641618)
  * d/p/u/apparmor-fix-other-seclabels.patch refresh to the now upstream
accepted solution (LP: #1633207).

 -- Christian Ehrhardt   Thu, 24 Nov
2016 08:06:38 +0100

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

Title:
  virt-aa-helper Apparmor profile missing rules for name resolution

Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * Apparmor denies several hostname related accesses by libvirt causing 
 severe slowdowns in some cases.

  [Test Case]

  * Note: while there are various ways to trigger it - many have seen the 
issue, but often it is unclear when exactly it will trigger or does no 
more. So some of the repo-cases have proven to be unreliable - thanks 
Simon for this Repro howto listed here. (simplified as it turned out 
zvols are not needed according to comment #22)

  1) Sync Xenial cloud-image
  uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily 
arch=amd64 label=daily release=xenial

  2) Create a test guest with:
  uvt-kvm create --memory 2048 --cpu 4 --password=ubuntu xenial-kernel-test 
release=xenial arch=amd64 label=daily

  3) strop it and add an extra volume in a way like this snippet
 $ virsh shutdown xenial-kernel-test
 $ virsh edit xenial-kernel-test
  



  

  4) start the guest
  virsh start xenial-kernel-test

  6) check for apparmor denial messages
  dmesg | tail | grep apparmor

  Without the fix, Apparmor would report denials when accessing
  /etc/nsswitch.conf, /etc/host.conf, /etc/gai.conf,
  /run/resolvconf/resolv.conf and /dev/zdX (where X corresponds to the
  zvol number). Starting the guest should be much slower than usual.

  With the fix in place no related Apparmor denials show up.

  [Regression Potential]

   * The fix is rather small and "only" opens up apparmor confinement a bit. 
 That makes us assume that the potential for regression should be 
 minimal.

  ###

  Original description:

  With libvirt-bin 1.3.1, starting a QEMU guest results in those AA
  denials:

  Feb 17 12:06:23 simon-laptop kernel: [15734.513696] audit: type=1400 
audit(1455728783.639:73): apparmor="DENIED" operation="open" 
profile="/usr/lib/libvirt/virt-aa-helper" name="/etc/nsswitch.conf" pid=23156 
comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 17 12:06:23 simon-laptop kernel: [15734.513718] audit: type=1400 
audit(1455728783.639:74): apparmor="DENIED" operation="open" 
profile="/usr/lib/libvirt/virt-aa-helper" name="/etc/host.conf" pid=23156 
comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 17 12:06:23 simon-laptop kernel: [15734.513734] audit: type=1400 
audit(1455728783.639:75): apparmor="DENIED" operation="open" 
profile="/usr/lib/libvirt/virt-aa-helper" name="/run/resolvconf/resolv.conf" 
pid=23156 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 
ouid=0
  Feb 17 12:06:23 simon-laptop kernel: [15734.513885] audit: type=1400 
audit(1455728783.639:76): apparmor="DENIED" operation="open" 
profile="/usr/lib/libvirt/virt-aa-helper" name="/run/resolvconf/resolv.conf" 
pid=23156 comm="virt-aa-helper" requested_mask="r" denied_mask="r" fsuid=0 
ouid=0

  virt-aa-helper's AA profile hasn't changed recently so it seems like
  the helper is doing more in this release.

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy apparmor libvirt-bin
  apparmor:
    Installed: 2.10-3ubuntu1
    Candidate: 2.10-3ubuntu1
    Version table:
   *** 2.10-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  libvirt-bin:
    Installed: 1.3.1-1ubuntu1
    Candidate: 1.3.1-1ubuntu1
    Version table:
   *** 1.3.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libvirt-bin 1.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1
  Uname: Linux 4.4.0-5-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3

[Group.of.nepali.translators] [Bug 1642763] Re: keepalived raising VIP apply error

This bug was fixed in the package keepalived - 1:1.2.24-1ubuntu1

---
keepalived (1:1.2.24-1ubuntu1) zesty; urgency=medium

* debian/patches/fix_message_truncation_with_large_pagesizes.patch:
Resolve "Netlink: error: message truncated" messages. Thanks to
David Wilder . Closes LP: #1642763.

-- Nishanth Aravamudan Tue, 29 Nov
2016 09:45:12 -0800

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

Title:
keepalived raising VIP apply error

Status in keepalived package in Ubuntu:
Fix Released
Status in keepalived source package in Xenial:
In Progress
Status in keepalived source package in Yakkety:
In Progress

Bug description:
[Impact]

* keepalived on ppc64el (due to a large page size) experiences
"Netlink: error: message truncated" messages.

* These Netlink truncations result in keepalived thinking that the
the underlying device does not exist, even though it does.

[Test Case]

* Creating 100 veth interfaces ppc64el and verify if "Netlink: error:
message truncated" errors are emitted. If so, the bug is present. If
not, the bug is fixed.

[Regression Potential]

* This is code issue, fixed upstream, in the keepalived code when the
system page size exceeds 4096. The upstream fix was backported to all
releases and should only properly limit the size of the buffer used
for netlink to at most 8192 on systems with a page size greater than
8192. I believe risk of regression is very low.

* Using the tests provided by David Wilder, I ran on both x86_64 and
ppc64el LXD containers. Without the backported changes, I saw no
issues on x86_64, and the reported issue on ppc64el (as expected, as a
page size greater than 4K is required to see the buffer size issue).
With the backported changes, both architectures show no issue with the
provided testcase.

---

== Comment: #0 - Andrew Thorstensen - 2016-11-17 09:50:25 ==

---Problem Description---
Using Ubuntu 16.04 on ppc64le, we are building a 'neutron network node' using
the VRRP configuration (built on keepalived).

Information on this OpenStack configuration can be found here:
https://wiki.openstack.org/wiki/Neutron/L3_High_Availability_VRRP

When we run, the configuration is failing to apply via keepalived.

The logs post the following:
Nov 17 02:58:31 p8test-lp1 Keepalived_vrrp[54542]: VRRP is trying to assign
VIP to unknown qr-a5f5ba96-52 interface !!! go out and fix your conf !!!

However, the device DOES exist. But the keepalived config just
doesn't always deploy it.

ii keepalived 1:1.2.19-1
ppc64el Failover and monitoring daemon for LVS clusters

This configuration sometimes works, but does sometimes fail on Ubuntu
16.04.1

---uname output---
Linux p8test-lp1 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:38:24 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux

---Additional Hardware Info---
This is a Power8 system with Ubuntu 16.04.1 installed. Though we see no
indication that this is specific to Power.

Machine Type = S822L

Machine Type = 8286-42A

---Steps to Reproduce---
Install openstack. Run the network node in a VRRP HA configuration. Create
a router and assign a global IP.

== Comment: #5 - David J. Wilder - 2016-11-17 15:58:04 ==
The problem is fixed in this upstream commit:

https://github.com/acassen/keepalived/commit/9f327bbf3e86def1055a106eda0633638bda0345

On systems with a page size larger than 4096 keepalived may report:

"Netlink: error: message truncated" messages

This error was reported on a ppc64le in an OpenStack/Nutron environment.
Ppc64le is using a 64k pages size. I found that keepalived's netlink recvmsg
buffer was too small causing messages to be truncated. The size of the read
buffer for the netlink socket should be based on page size however, it should
not exceed 8192. See the comment in the patch.

I tested the fix by creating 100 veth interfaces and verifying the errors
did not return.

Signed-off-by: David Wilder
Signed-off-by: Quentin Armitage
...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1642763/+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 1645431] Re: [SRU] microrelease exception for src:php7.0 (7.0.13)

2016-11-30 Thread Nish Aravamudan

7.0.13-2ubuntu1 has migrated to zesty release.

** Changed in: php7.0 (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: php7.0 (Ubuntu)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

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

Title:
  [SRU] microrelease exception for src:php7.0 (7.0.13)

Status in php7.0 package in Ubuntu:
  Fix Released
Status in php7.0 source package in Xenial:
  In Progress
Status in php7.0 source package in Yakkety:
  In Progress

Bug description:
  There have been a number of microreleases of PHP 7.0 upstream since
  the last update to Xenial (which corresponded to the merge in
  Yakkety). Ase we have re-merged again in Zesty, it feels appropriate
  to provide another MRE update to php7.0. A number of critical security
  and bug-fixes are present in each 7.0.x. Rather than backporting
  individual patches (e.g., Bug # 1569509), I believe it makes
  significantly more sense to follow the upstream 7.0.x. Upstream PHP is
  demonstrating an improved approach of bugfixes only in 7.0.x:

   - 7.0.13: http://php.net/ChangeLog-7.php

  The upstream CI is at: https://travis-ci.org/php/php-src and is run
  regularly.

  Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php,
  cgi, fpm and cli. We have also updated the packing to run the source
  tests during the build itself.

  I do not believe there is a firm statement from upstream on API/ABI
  stability, but the general approach seems to be a BC-break would
  result in 7.1.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1645431/+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 1634496] Re: proc_keys_show crash when reading /proc/keys

2016-11-30 Thread Colin Ian King

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

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

Title:
  proc_keys_show crash when reading /proc/keys

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  Running stress-ng /proc test trips the following crash:

  [ 5315.044206] Kernel panic - not syncing: stack-protector: Kernel stack is 
corrupted in: 8956b1ae
  [ 5315.044206] 
  [ 5315.044883] CPU: 0 PID: 4820 Comm:  Tainted: P   OE   
4.8.0-25-generic #27-Ubuntu
  [ 5315.045361] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu2 04/01/2014
  [ 5315.045911]  0086 b337622b 8fe574f37c78 
8962f5d2
  [ 5315.046371]  b3405b00 89e83530 8fe574f37d00 
8939e71c
  [ 5315.046841]  8fe50010 8fe574f37d10 8fe574f37ca8 
b337622b
  [ 5315.047305] Call Trace:
  [ 5315.047457]  [] dump_stack+0x63/0x81
  [ 5315.047763]  [] panic+0xe4/0x226
  [ 5315.048049]  [] ? proc_keys_show+0x3ce/0x3d0
  [ 5315.048398]  [] __stack_chk_fail+0x19/0x30
  [ 5315.048735]  [] proc_keys_show+0x3ce/0x3d0
  [ 5315.049072]  [] ? key_validate+0x50/0x50
  [ 5315.049396]  [] ? key_default_cmp+0x20/0x20
  [ 5315.049737]  [] seq_read+0x102/0x3c0
  [ 5315.050042]  [] proc_reg_read+0x42/0x70
  [ 5315.050363]  [] __vfs_read+0x18/0x40
  [ 5315.050674]  [] vfs_read+0x96/0x130
  [ 5315.050977]  [] SyS_read+0x55/0xc0
  [ 5315.051275]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  [ 5315.051735] Kernel Offset: 0x820 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [ 5315.052563] ---[ end Kernel panic - not syncing: stack-protector: Kernel 
stack is corrupted in: 8956b1ae
  [ 5315.052563] 

  "The proc_keys_show function in security/keys/proc.c in the Linux
  kernel through 4.8.2, when the GNU Compiler Collection (gcc) stack
  protector is enabled, uses an incorrect buffer size for certain
  timeout data, which allows local users to cause a denial of service
  (stack memory corruption and panic) by reading the /proc/keys file."

  Fix detailed in: https://bugzilla.redhat.com/show_bug.cgi?id=1373966
  see: https://bugzilla.redhat.com/attachment.cgi?id=1200212=diff

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1634496/+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 1646150] Re: linux: 4.4.0-52.73 -proposed tracker

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-51.72-generic/s2lp3__4.4.0-51.72__2016-11-30_23-18-00/results-index.html

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

** Description changed:

  This bug is for tracking the 4.4.0-52.73 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 --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 30. November 2016 23:16 UTC

** Description changed:

  This bug is for tracking the 4.4.0-52.73 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
  derivative-trackers-created: true
  phase: Uploaded
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 30. November 2016 23:16 UTC

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

Title:
  linux: 4.4.0-52.73 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-52.73 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
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1646150/+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 1593235] Re: ovs/gre, vxlan, geneve: interface deletion are not notified via netlink with linux >= 4.3

2016-11-30 Thread Joseph Salisbury

These commits have all landed in Yakkety, so it looks like they are only
now needed in Xenial.

** No longer affects: linux (Ubuntu Wily)

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

Title:
  ovs/gre,vxlan, geneve: interface deletion are not notified via netlink
  with linux >= 4.3

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  These upstream patches are needed:

  ovs/gre,geneve: fix error path when creating an iface
  
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=106da663ff495e0aea3ac15b8317aa410754fcac

  ovs/vxlan: fix rtnl notifications on iface deletion
  
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=cf5da330bbdd0c06b05c525a3d1d58ccd82c87a6

  ovs/gre: fix rtnl notifications on iface deletion
  
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=da6f1da819d4b9c081a477dec74dc468a0b44290

  ovs/geneve: fix rtnl notifications on iface deletion
  
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=41009481b690493c169ce85f591b9d32c6fd9422
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 16 15:43 seq
   crw-rw 1 root audio 116, 33 Jun 16 15:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/6WIND-hostname ro console=ttyS0,115200n8 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.8.2-0-g33fbe13 by qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.5
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.8.2-0-g33fbe13byqemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.5:cvnQEMU:ct1:cvrpc-i440fx-2.5:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.5
  dmi.sys.vendor: QEMU

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

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

Title:
  linux: 4.4.0-52.73 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-52.73 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 --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1646150/+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 1646197] Re: Update initrds after installing linux-firmware

This bug was fixed in the package linux-firmware - 1.162

---
linux-firmware (1.162) zesty; urgency=medium

  * Rebase against 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
87941021a622c882b1921df85d6115940a4e568a
- Update Intel OPA hfi1 firmware file
- brcm: add firmware for BCM43430 802.11n chipset
- amdgpu: update tonga and fiji VCE firmware to 52.8.3
- Add a metadata consistency check script
- WHENCE: Correct filename of LICENCE.moxa
- Add copy of GPL v2 and references to the GPL-2 and GPL-3 files
- WHENCE: Specify source directories for cis, isci, and usbdux firmware
- WHENCE: Remove references to source for emi62 firmware
- WHENCE: Remove references to two nvidia firmware files that were never 
added
- Remove unused 'LICENCE.mwl8335'
- WHENCE: Adjust some licence file references to satisfy check_whence.py
- WHENCE: Fix metadata for snd-soc-skl firmware
- WHENCE: List new radeon CI and SI smc firmware
- WHENCE: List symlink 'qat_mmp.bin'
- WHENCE: Add reference to 'qca/NOTICE.txt'
- README: Say that files must be listed in WHENCE, and how to check it
- radeon: update SMC firmware for SI parts
- radeon: update SMC firmware for CI parts
- amdgpu: update SMC firmware for VI parts
- mediatek: update MT8173 VPU firmware for idle state
- amdgpu: add new smc firmware for newer tonga and iceland chips
- linux-firmware: rockchip: update dptx firmware to v3.1
- rockchip/dptx: update WHENCE to version 3.1
- linux-firmware: update BYT audio firmware
- rtlwifi: Add updates for RTL8723BE and RTL8821AE
- linux-firmware: Update firmware patch for Intel Bluetooth 7265 (C0)
- linux-firmware: Update firmware patch for Intel Bluetooth 7265 (D1)
- linux-firmware: Update firmware patch for Intel Bluetooth 7260 (B5/B6)
- linux-firmware: Update firmware file for Intel Bluetooth 8260
- linux-firmware: Update firmware file for Intel Bluetooth 8265

  * Trigger update-initramfs following linux-firmware install (LP: #1646197)
- UBUNTU: Add postinst script to update initrds

  * Don't install build scripts, and move GPL license files to the license
install directory.
- UBUNTU: Build and license file installation changes

 -- Seth Forshee   Wed, 30 Nov 2016 14:50:27
-0600

** Changed in: linux-firmware (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/1646197

Title:
  Update initrds after installing linux-firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Precise:
  Fix Committed
Status in linux-firmware source package in Trusty:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Yakkety:
  Fix Committed
Status in linux-firmware source package in Zesty:
  Fix Released

Bug description:
  linux-firmware should have a postinst script to call update-initramfs
  to update/remove firmware files in the initrds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1646197/+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 1646150] Re: linux: 4.4.0-52.73 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

** Description changed:

  This bug is for tracking the 4.4.0-52.73 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
  
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Wednesday, 30. November 2016 15:45 UTC
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 30. November 2016 21:16 UTC

** Description changed:

  This bug is for tracking the 4.4.0-52.73 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 --
  derivative-trackers-created: true
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 30. November 2016 21:16 UTC
+ phase: Uploaded

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

Title:
  linux: 4.4.0-52.73 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-52.73 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 --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1646150/+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 1646197] Re: Update initrds after installing linux-firmware

2016-11-30 Thread Seth Forshee

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

** Also affects: linux-firmware (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-firmware (Ubuntu Zesty)
   Importance: Medium
 Assignee: Seth Forshee (sforshee)
   Status: In Progress

** Also affects: linux-firmware (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-firmware (Ubuntu Yakkety)
   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/1646197

Title:
  Update initrds after installing linux-firmware

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Precise:
  Confirmed
Status in linux-firmware source package in Trusty:
  Confirmed
Status in linux-firmware source package in Xenial:
  In Progress
Status in linux-firmware source package in Yakkety:
  Confirmed
Status in linux-firmware source package in Zesty:
  In Progress

Bug description:
  linux-firmware should have a postinst script to call update-initramfs
  to update/remove firmware files in the initrds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1646197/+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 1645906] Re: new dist-upgrader tarballs necessary so they are signed with 4k key

2016-11-30 Thread Brian Murray

I've uploaded an update to ubuntu-release-upgrader to zesty, but its
autopkgtest is failing because it can't verify the xenial tarball.  Once
the xenial update is released, we should rerun the zesty autopkgtests.

** Also affects: update-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-upgrader (Ubuntu Precise)
   Status: New => Invalid

** Changed in: update-manager (Ubuntu)
   Status: New => Invalid

** Changed in: update-manager (Ubuntu Precise)
   Status: New => In Progress

** Changed in: update-manager (Ubuntu Precise)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: update-manager (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: update-manager (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: update-manager (Ubuntu Yakkety)
   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/1645906

Title:
  new dist-upgrader tarballs necessary so they are signed with 4k key

Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader source package in Precise:
  Invalid
Status in update-manager source package in Precise:
  In Progress
Status in ubuntu-release-upgrader source package in Trusty:
  In Progress
Status in update-manager source package in Trusty:
  Invalid
Status in ubuntu-release-upgrader source package in Xenial:
  In Progress
Status in update-manager source package in Xenial:
  Invalid
Status in ubuntu-release-upgrader source package in Yakkety:
  Fix Committed
Status in update-manager source package in Yakkety:
  Invalid

Bug description:
  With the ubuntu-archive-publishing change in
  https://code.launchpad.net/~xnox/ubuntu-archive-publishing/migrate-
  dist-upgrade-to-4k/+merge/311181 the signing process for the dist-
  upgrader tarball has been changed.  This change should be tested now,
  rather than doing an ubuntu-release-upgrader change months from now
  and wondering why things aren't working (if they are broken).

  Due to the way the gpg signature is generated we can't just remove it
  and have it regenerated as the timestamp for the signature will not
  change, so the change will not propogate to the mirrors.  Hence the
  need for a mostly no change (mirrors and demotions may change) upload
  of ubuntu-release-upgrader.

  Test Case
  -
  1) run do-release-upgrade -p --frontend DistUpgradeViewText
  2) ensure the tarball for the next release e.g. xenial.tar.gz is downloaded 
and the signature verification passes

  Regression Potential
  
  It's possible the signing is wrong and the verification of the signature will 
fail thereby causing release upgrades to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1645906/+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 1629085] Re: CVE-2016-5180: out-of-bounds write in ares_create_query and ares_mkquery

2016-11-30 Thread Marc Deslauriers

** Changed in: c-ares (Ubuntu)
   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/1629085

Title:
  CVE-2016-5180: out-of-bounds write in ares_create_query and
  ares_mkquery

Status in c-ares package in Ubuntu:
  Fix Released
Status in c-ares source package in Precise:
  Fix Released
Status in c-ares source package in Trusty:
  Fix Released
Status in c-ares source package in Xenial:
  Fix Released
Status in c-ares source package in Yakkety:
  Fix Released
Status in c-ares package in Debian:
  Fix Released

Bug description:
  A new upstream version of c-ares has been released which addresses a
  security vulnerability.

  From: Daniel Stenberg 
  Date: Thu, 29 Sep 2016 16:02:10 +0200 (CEST)

  `ares_create_query` single byte out of buffer write
  =

  Project c-ares Security Advisory, September 29, 2016 -
  [Permalink](https://c-ares.haxx.se/adv_20160929.html)

  VULNERABILITY
  -

  When a string is passed in to `ares_create_query` or `ares_mkquery` and uses
  an escaped trailing dot, like "hello\.", c-ares calculates the string length
  wrong and subsequently writes outside of the the allocated buffer with one
  byte. The wrongly written byte is the least significant byte of the 'dnsclass'
  argument; most commonly 1.

  We have been seen proof of concept code showing how this can be exploited in a
  real-world system, but we are not aware of any such instances having actually
  happened in the wild.

  INFO
  

  The Common Vulnerabilities and Exposures (CVE) project has assigned the name
  CVE-2016-5180 to this issue.

  AFFECTED VERSIONS
  -

  This flaw exists in the following c-ares versions.

  - Affected versions: libcurl 1.0.0 to and including 1.11.0
  - Not affected versions: c-ares >= 1.12.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c-ares/+bug/1629085/+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 1629085] Re: CVE-2016-5180: out-of-bounds write in ares_create_query and ares_mkquery

This bug was fixed in the package c-ares - 1.11.0-1ubuntu0.1

---
c-ares (1.11.0-1ubuntu0.1) yakkety-security; urgency=medium

  * SECURITY UPDATE: denial of service and possible execution via hostname
with an escaped trailing dot (LP: #1629085)
- debian/patches/CVE-2016-5180.patch: properly handle escaped dot in
  ares_create_query.c.
- CVE-2016-5180

 -- Marc Deslauriers   Thu, 06 Oct 2016
10:08:23 -0400

** Changed in: c-ares (Ubuntu Yakkety)
   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/1629085

Title:
  CVE-2016-5180: out-of-bounds write in ares_create_query and
  ares_mkquery

Status in c-ares package in Ubuntu:
  Confirmed
Status in c-ares source package in Precise:
  Fix Released
Status in c-ares source package in Trusty:
  Fix Released
Status in c-ares source package in Xenial:
  Fix Released
Status in c-ares source package in Yakkety:
  Fix Released
Status in c-ares package in Debian:
  Fix Released

Bug description:
  A new upstream version of c-ares has been released which addresses a
  security vulnerability.

  From: Daniel Stenberg 
  Date: Thu, 29 Sep 2016 16:02:10 +0200 (CEST)

  `ares_create_query` single byte out of buffer write
  =

  Project c-ares Security Advisory, September 29, 2016 -
  [Permalink](https://c-ares.haxx.se/adv_20160929.html)

  VULNERABILITY
  -

  When a string is passed in to `ares_create_query` or `ares_mkquery` and uses
  an escaped trailing dot, like "hello\.", c-ares calculates the string length
  wrong and subsequently writes outside of the the allocated buffer with one
  byte. The wrongly written byte is the least significant byte of the 'dnsclass'
  argument; most commonly 1.

  We have been seen proof of concept code showing how this can be exploited in a
  real-world system, but we are not aware of any such instances having actually
  happened in the wild.

  INFO
  

  The Common Vulnerabilities and Exposures (CVE) project has assigned the name
  CVE-2016-5180 to this issue.

  AFFECTED VERSIONS
  -

  This flaw exists in the following c-ares versions.

  - Affected versions: libcurl 1.0.0 to and including 1.11.0
  - Not affected versions: c-ares >= 1.12.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c-ares/+bug/1629085/+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 1646195] [NEW] linux-hwe-edge: 4.8.0-29.31~16.04.1 -proposed tracker

Public bug reported:

This bug is for tracking the 4.8.0-29.31~16.04.1 upload package. This
bug will contain status and testing results related to that upload.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


** Tags: block-proposed-xenial kernel-release-tracking-bug xenial

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

** Tags added: block-proposed-xenial

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in:

[Group.of.nepali.translators] [Bug 1629085] Re: CVE-2016-5180: out-of-bounds write in ares_create_query and ares_mkquery

This bug was fixed in the package c-ares - 1.10.0-2ubuntu0.1

---
c-ares (1.10.0-2ubuntu0.1) trusty-security; urgency=medium

  * SECURITY UPDATE: denial of service and possible execution via hostname
with an escaped trailing dot (LP: #1629085)
- debian/patches/CVE-2016-5180.patch: properly handle escaped dot in
  ares_create_query.c.
- CVE-2016-5180

 -- Marc Deslauriers   Thu, 06 Oct 2016
10:15:41 -0400

** Changed in: c-ares (Ubuntu Xenial)
   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/1629085

Title:
  CVE-2016-5180: out-of-bounds write in ares_create_query and
  ares_mkquery

Status in c-ares package in Ubuntu:
  Confirmed
Status in c-ares source package in Precise:
  Fix Released
Status in c-ares source package in Trusty:
  Fix Released
Status in c-ares source package in Xenial:
  Fix Released
Status in c-ares source package in Yakkety:
  Fix Released
Status in c-ares package in Debian:
  Fix Released

Bug description:
  A new upstream version of c-ares has been released which addresses a
  security vulnerability.

  From: Daniel Stenberg 
  Date: Thu, 29 Sep 2016 16:02:10 +0200 (CEST)

  `ares_create_query` single byte out of buffer write
  =

  Project c-ares Security Advisory, September 29, 2016 -
  [Permalink](https://c-ares.haxx.se/adv_20160929.html)

  VULNERABILITY
  -

  When a string is passed in to `ares_create_query` or `ares_mkquery` and uses
  an escaped trailing dot, like "hello\.", c-ares calculates the string length
  wrong and subsequently writes outside of the the allocated buffer with one
  byte. The wrongly written byte is the least significant byte of the 'dnsclass'
  argument; most commonly 1.

  We have been seen proof of concept code showing how this can be exploited in a
  real-world system, but we are not aware of any such instances having actually
  happened in the wild.

  INFO
  

  The Common Vulnerabilities and Exposures (CVE) project has assigned the name
  CVE-2016-5180 to this issue.

  AFFECTED VERSIONS
  -

  This flaw exists in the following c-ares versions.

  - Affected versions: libcurl 1.0.0 to and including 1.11.0
  - Not affected versions: c-ares >= 1.12.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c-ares/+bug/1629085/+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 1629085] Re: CVE-2016-5180: out-of-bounds write in ares_create_query and ares_mkquery

This bug was fixed in the package c-ares - 1.7.5-1ubuntu0.1

---
c-ares (1.7.5-1ubuntu0.1) precise-security; urgency=medium

  * SECURITY UPDATE: denial of service and possible execution via hostname
with an escaped trailing dot (LP: #1629085)
- debian/patches/CVE-2016-5180.patch: properly handle escaped dot in
  ares_mkquery.c.
- CVE-2016-5180

 -- Marc Deslauriers   Thu, 06 Oct 2016
10:23:45 -0400

** Changed in: c-ares (Ubuntu Precise)
   Status: Confirmed => Fix Released

** Changed in: c-ares (Ubuntu Trusty)
   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/1629085

Title:
  CVE-2016-5180: out-of-bounds write in ares_create_query and
  ares_mkquery

Status in c-ares package in Ubuntu:
  Confirmed
Status in c-ares source package in Precise:
  Fix Released
Status in c-ares source package in Trusty:
  Fix Released
Status in c-ares source package in Xenial:
  Fix Released
Status in c-ares source package in Yakkety:
  Fix Released
Status in c-ares package in Debian:
  Fix Released

Bug description:
  A new upstream version of c-ares has been released which addresses a
  security vulnerability.

  From: Daniel Stenberg 
  Date: Thu, 29 Sep 2016 16:02:10 +0200 (CEST)

  `ares_create_query` single byte out of buffer write
  =

  Project c-ares Security Advisory, September 29, 2016 -
  [Permalink](https://c-ares.haxx.se/adv_20160929.html)

  VULNERABILITY
  -

  When a string is passed in to `ares_create_query` or `ares_mkquery` and uses
  an escaped trailing dot, like "hello\.", c-ares calculates the string length
  wrong and subsequently writes outside of the the allocated buffer with one
  byte. The wrongly written byte is the least significant byte of the 'dnsclass'
  argument; most commonly 1.

  We have been seen proof of concept code showing how this can be exploited in a
  real-world system, but we are not aware of any such instances having actually
  happened in the wild.

  INFO
  

  The Common Vulnerabilities and Exposures (CVE) project has assigned the name
  CVE-2016-5180 to this issue.

  AFFECTED VERSIONS
  -

  This flaw exists in the following c-ares versions.

  - Affected versions: libcurl 1.0.0 to and including 1.11.0
  - Not affected versions: c-ares >= 1.12.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/c-ares/+bug/1629085/+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 1646190] Re: linux: 4.8.0-29.31 -proposed tracker

** Changed in: kernel-sru-workflow
   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/1646190

Title:
  linux: 4.8.0-29.31 -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-29.31 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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 30. November 2016 17:32 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1646190/+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 1646191] [NEW] linux-hwe-edge: 4.8.0-29.31~16.04.1 -proposed tracker

Public bug reported:

This bug is for tracking the 4.8.0-29.31~16.04.1 upload package. This
bug will contain status and testing results related to that upload.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


** Tags: block-proposed-xenial kernel-release-tracking-bug xenial

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

** Tags added: block-proposed-xenial

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in:

[Group.of.nepali.translators] [Bug 1646190] [NEW] linux: 4.8.0-29.31 -proposed tracker

Public bug reported:

This bug is for tracking the 4.8.0-29.31 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

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

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

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

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


** Tags: block-proposed-xenial kernel-release-tracking-bug xenial

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

** Tags added: block-proposed-xenial

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in:

[Group.of.nepali.translators] [Bug 1587261] Re: [SRU] Swift bucket X-Timestamp not set by Rados Gateway

This bug was fixed in the package ceph - 10.2.3-0ubuntu2.1

---
ceph (10.2.3-0ubuntu2.1) yakkety; urgency=medium

  * rgw: Fixes for creation times for buckets (LP: #1587261).
- d/p/rgw_rados-creation_time.patch: Backport fix from upstream master.
  Fix logic error that leads to creation time being 0 instead of current
  time when creating buckets.

ceph (10.2.3-0ubuntu2) yakkety; urgency=medium

  * d/control: Add Pre-Depends on ceph-common to ceph-osd to ensure
that ceph user and group are created prior to unpacking of udev
rules (LP: #1631328).
  * d/control: Drop surplus Recommends on ceph-common for ceph-mon, as
it already has a in-direct Depends via ceph-base.

 -- Frode Nordahl   Fri, 28 Oct 2016
07:52:07 +0200

** Changed in: ceph (Ubuntu Yakkety)
   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/1587261

Title:
  [SRU] Swift bucket X-Timestamp not set by Rados Gateway

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in ceph package in Ubuntu:
  Fix Released
Status in ceph source package in Xenial:
  Fix Released
Status in ceph source package in Yakkety:
  Fix Released
Status in ceph source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * A basic characteristic of a object store is the ability to create
     buckets and objects and to query for information about said
     buckets and objects.

   * In the current version of the ceph radosgw package it is not
     possible to get creation time for buckets. This is a serious
     defect and makes it impossible to use Ubuntu with ceph as a
     object store for some applications.

   * The issue has been fixed in upstream master

   * The proposed debdiff solves the issue by including patches cherry
     picked and adapted from upstream master branch fixing this issue.

  [Test Case]

   * Use Juju to deploy Ceph cluster with radosgw and relation to OpenStack
     Keystone. Example bundle: http://pastebin.ubuntu.com/23374308/

   * Install OpenStack Swift client

  sudo apt-get install python-swiftclient

   * Load OpenStack Credentials pointing to your test deployment

  wget 
https://raw.githubusercontent.com/openstack-charmers/openstack-bundles/master/development/shared/novarc
  . novarc

   * Create swift bucket

  swift post test

   * Display information about newly created bucket

  swift stat test

   * Observe that key 'X-Timestamp' has value 0.0

   * Delete bucket

  swift delete test

   * Install patched radosgw packages on 'ceph-radosgw' unit and repeat

   * Verify that key 'X-Timestamp' now has a value > 0.0 and corrensponding
 to the unixtime of when you created the bucket.

  [Regression Potential]

   * The patch is simple and I see little potential for any regression as a
     result of it being applied.

  [Original bug description]
  When creating a swift/radosgw bucket in horizon the bucket gets created, but 
shows up with a creation date of 19700101

  In the apache log one can observe

  curl -i http://10.11.140.241:80/swift/v1/bucket1 -I -H "X-Auth-Token:  ...
  Container HEAD failed: http://10.11.140.241:80/swift/v1/bucket1 404 Not Found

  However a manual curl call succeeds. Also the radosgw.log shows
  successful PUT/GET requests.

  I get similar results using the swift command line utility with
  containers inheriting a creation date of 19700101 even though I can
  see the correct date being passed to rados in the headers of the
  request.

  Also similarly issues with ceilometer intergration, similarly linked:

  2016-05-31 06:28:16.931 1117922 WARNING ceilometer.agent.manager [-] Continue 
after error from storage.containers.objects: Account GET failed: 
http://10.101.140.241:80/swift/v1/AUTH_025d6aa2af18415a87c012211edb7fea?format=json
 404 Not Found  [first 60 chars of response] 
{"Code":"NoSuchBucket","BucketName":"AUTH_025d6aa2af18415a87
  2016-05-31 06:28:16.931 1117922 ERROR ceilometer.agent.manager Traceback 
(most recent call last):

  This is using charm version: 86 against Openstack Mitaka

  This also seems pretty reproduceable with any ceph, ceph-rados and
  mitaka install via the juju charms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1587261/+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 1643524] Re: linux-hwe-edge: 4.8.0-28.30~16.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/upload-to-ppa
   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/1643524

Title:
  linux-hwe-edge: 4.8.0-28.30~16.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.8.0-28.30~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1643524/+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 1643524] Re: linux-hwe-edge: 4.8.0-28.30~16.04.1 -proposed tracker

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-28.30~16.04.1-generic/modoc__4.8.0-28.30~16.04.1__2016-11-30_16-19-00/results-index.html

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

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

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

** Tags added: regression-testing-passed

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

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

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

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

Title:
  linux-hwe-edge: 4.8.0-28.30~16.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.8.0-28.30~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1643524/+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 1645911] Re: linux-firmware package causes sound issues with after initramfs update

2016-11-30 Thread Seth Forshee

My plan for now is to release a new linux-firmware with that firmware
removed, then restore it after we get a fix in the kernel. Will provide
a test package shortly.

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

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

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

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

** Changed in: linux-firmware (Ubuntu)
   Status: Confirmed => Invalid

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

** Changed in: linux-firmware (Ubuntu Xenial)
   Importance: Undecided => High

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

** Changed in: linux-firmware (Ubuntu Xenial)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  linux-firmware package causes sound issues with after initramfs update

Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Confirmed

Bug description:
  On laptops with Kaby Lake processors and Sunrise point chipsets
  (System76 Lemu7), updating to the current (1.157.5) version of the
  linux-firmware package and then updating initramfs causes sound
  issues.  This can manifest in two ways:

  1: Volume hotkeys and controls appear to work, but actual playback volume 
remains the same.
 Three HDMI devices appear in the sound-settings gui, despite no HDMI 
device connected (and only 1 HDMI port)
  2: 'Dummy Output' is the only device in the sound-settings gui, and there is 
no sound output at all.

  In both cases dmesg shows error output relating to snd_hda_codec_hdmi.

  This bug only affects Xenial, not Yakkety.  Xenial still exhibits the
  above symptoms after installing the current Yakkety linux-firmware
  package.

  I believe the issue is related to the Kaby Lake firmware.  In testing,
  I was able to remove '/lib/firmware/i915/kbl_dmc_ver1_01.bin', run
  'sudo update-initramfs -u', and reboot to get sound working correctly
  again.

  Perhaps this firmware is needed for the upcoming Union Point chipsets,
  but causes problems with the for Kaby Lake processor laptops running
  the 4.4.0 kernel and Sunrise Point chipsets.  There is either a bug in
  the new Kaby Lake firmware or it is being erroneously applied to
  inappropriate hardware.

  I have received a number of reports of users running into this bug,
  presumably anyone who updated to the latest kernel and linux-firmware
  packages at the same time.  Based on testing, next kernel update could
  trigger the bug for many more users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645911/+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 1634964] Re: Allow fuse user namespace mounts by default in xenial

2016-11-30 Thread Seth Forshee

Not actually released yet since the patches were reverted.

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

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

Title:
  Allow fuse user namespace mounts by default in xenial

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

Bug description:
  This is a requirement for supporting snaps within lxd containers in
  xenial. It is already allowed in yakkety, so enablement in xenial
  consists of backporting some changes and changing the fuse
  userns_mounts parameter to be enabled by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634964/+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 1646154] [NEW] linux-raspi2: -proposed tracker

Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


** Tags: block-proposed-xenial kernel-release-tracking-bug xenial

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

** Tags added: block-proposed-xenial

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) =>

[Group.of.nepali.translators] [Bug 1627656] Re: missing alembic migrations due to use of git based workflows

2016-11-30 Thread OpenStack Infra

Reviewed:  https://review.openstack.org/376378
Committed: 
https://git.openstack.org/cgit/openstack/networking-sfc/commit/?id=a640a99527ee2c51179278823b50661bc6038278
Submitter: Jenkins
Branch:master

commit a640a99527ee2c51179278823b50661bc6038278
Author: James Page 
Date:   Mon Sep 26 11:23:11 2016 +0100

Include alembic migrations in module

Explicitly include all alembic data in installed python module,
ensuring that installations direct from git repositories are
fully functional when compared to use of sdist generated tarballs
from tarballs.openstack.org or pypi.

Closes-Bug: 1627656

Change-Id: I246672cd6a343583daa96720e433c8c0a62086fc


** Changed in: networking-sfc
   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/1627656

Title:
  missing alembic migrations due to use of git based workflows

Status in networking-l2gw:
  New
Status in networking-odl:
  Fix Released
Status in networking-sfc:
  Fix Released
Status in tap-as-a-service:
  New
Status in networking-l2gw package in Ubuntu:
  Fix Released
Status in networking-odl package in Ubuntu:
  Fix Released
Status in neutron-taas package in Ubuntu:
  Fix Released
Status in networking-l2gw source package in Xenial:
  New
Status in networking-odl source package in Xenial:
  Triaged
Status in neutron-taas source package in Xenial:
  Invalid
Status in networking-l2gw source package in Yakkety:
  Fix Released
Status in networking-odl source package in Yakkety:
  Fix Released
Status in neutron-taas source package in Yakkety:
  Fix Released

Bug description:
  Various openstack related packages are missing required neutron
  database migrations due to the direct use of a git based workflow of
  merging upstream tags and generating orig.tar.xz directly from the git
  tree for packaging.  This is *not* the same process as generated a
  sdist tarball, and as a result, files that need to reside in the
  python module get missed - this includes alembic migrations.

  Known impacts:

networking-odl
vmware-nsx (bug 1574610)

  A simple fix is to switch to using the upstream published release
  artefacts, rather than directly using git.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-l2gw/+bug/1627656/+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 1646155] [NEW] linux-snapdragon: -proposed tracker

Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


** Tags: block-proposed-xenial kernel-release-tracking-bug xenial

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

** Tags added: block-proposed-xenial

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee:

[Group.of.nepali.translators] [Bug 1646150] [NEW] linux: 4.4.0-52.73 -proposed tracker

Public bug reported:

This bug is for tracking the 4.4.0-52.73 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

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

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

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

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


** Tags: block-proposed-xenial kernel-release-tracking-bug xenial

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

** Tags added: block-proposed-xenial

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in:

[Group.of.nepali.translators] [Bug 1640418] Re: WiFi LED doesn't work on some Edge Gateway units

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

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

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

Title:
  WiFi LED doesn't work on some Edge Gateway units

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

Bug description:
  This bug is for Xenial kernel 4.4 only.

  In commit 66df604dbbb24104ca3c5e0b4198a246c6a7f5d6, DMI ID is used to
  determine whether we're running on an Edge Gateway or not, and driver
  toggles LED only when an Edge Gateway is detected. In some recent
  models the DMI strings are no longer the same, thus WiFi LED stops
  working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1640418/+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 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

2016-11-30 Thread Julian Andres Klode

These are different bugs.Or rather, we definitely fixed the

if float(percent) != self.percent or status_str != self.status:
Aug 8 13:49:44 ubuntu /plugininstall.py: ValueError: could not convert string 
to float: '0,'

thing here. And to keep our sanity (especially WRT to the SRU fixing
that), we do need this bug closed, otherwise everything becomes a mess.

** Changed in: apt (Ubuntu)
   Status: Triaged => 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/1611010

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  In Progress
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  [Impact]
  Breaks installation in some non-English locales.

  [Test case]
  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  [Regression potential]
  Very low, we're running this in 1.3 since a long time. The fix depends on 
another one that restricts the Date parser to accept only UTC time zones in 
Release files, though (we do not understand the other ones anyway), and thus 
might reject some repositories it silently accepted in a wrong way previously 
(we have not seen anyone report a regression yet since uploading that in June).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1611010/+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 1613787] Re: xfrm: ipsec crash when updating spd thresholds

2016-11-30 Thread Joseph Salisbury

Yakkety bug task removed per comment #11

** No longer affects: linux (Ubuntu Yakkety)

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

Title:
  xfrm: ipsec crash when updating spd thresholds

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Fixed upstream by this commit (only in IPsec tree for now):

  
https://git.kernel.org/cgit/linux/kernel/git/klassert/ipsec.git/commit/?id=6916fb3b10b3cbe3b1f9f5b680675f53e4e299eb
  http://patchwork.ozlabs.org/patch/654026/

  To update the thresholds: 'ip xfrm policy set hthresh4 24 32'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613787/+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 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

2016-11-30 Thread Phillip Susi

It looks like this has regressed on 17.10, see bug #1638142.


** Changed in: ubiquity (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: apt (Ubuntu)
   Status: Fix Released => 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/1611010

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Triaged
Status in ubiquity package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  In Progress
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  [Impact]
  Breaks installation in some non-English locales.

  [Test case]
  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  [Regression potential]
  Very low, we're running this in 1.3 since a long time. The fix depends on 
another one that restricts the Date parser to accept only UTC time zones in 
Release files, though (we do not understand the other ones anyway), and thus 
might reject some repositories it silently accepted in a wrong way previously 
(we have not seen anyone report a regression yet since uploading that in June).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1611010/+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 1482938] Re: im-config gcin qt5

This bug was fixed in the package im-config - 0.29-1ubuntu16.1

---
im-config (0.29-1ubuntu16.1) yakkety-proposed; urgency=medium

  * debian/patches/fix-uim-qt5.patch:
- Fix uim Qt5 immodule path (LP: #1642001).
  * debian/patches/gcin-qt5.patch:
- Add gcin Qt5 immodule (LP: #1482938).

 -- Gunnar Hjalmarsson   Wed, 16 Nov 2016 10:41:00
+0100

** Changed in: im-config (Ubuntu Yakkety)
   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/1482938

Title:
  im-config gcin qt5

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Xenial:
  Fix Committed
Status in im-config source package in Yakkety:
  Fix Released
Status in im-config package in Debian:
  Fix Released

Bug description:
  [Impact]

  missing

  QT_IM_MODULE=gcin

  in /usr/share/im-config/data/26_gcin.rc

  QT5 needs this.

  Fix uploaded to yakkety queue; xenial patch attached to bug #1642001.

  [Test Case]

  After the change, this command:

  grep -A3 QT_IM_MODULE /usr/share/im-config/data/26_gcin.rc

  should output:

  QT_IM_MODULE=xim
  # use immodule when available for Qt5
  for IM_CONFIG_MARKER in 
/usr/lib/*/qt5/plugins/platforminputcontexts/libgcinplatforminputcontextplugin.so
 ; do
  if [ -e $IM_CONFIG_MARKER ]; then
  QT_IM_MODULE=gcin
  break
  fi
  done

  [Regression Potential]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1482938/+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 1644153] Re: SSL handshake fails on xenial, yakkety, zesty

This bug was fixed in the package python-jujuclient - 0.50.5-0ubuntu2

---
python-jujuclient (0.50.5-0ubuntu2) zesty; urgency=medium

  * Add patch to use TLSv1.2 since Juju dropped TLSv1 (LP: #1644153)

 -- Christopher Glass (Ubuntu)   Wed, 23 Nov 2016
12:43:10 +

** Changed in: python-jujuclient (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/1644153

Title:
  SSL handshake fails on xenial, yakkety, zesty

Status in python-jujuclient:
  New
Status in python-jujuclient package in Ubuntu:
  Fix Released
Status in python-jujuclient source package in Xenial:
  Fix Committed
Status in python-jujuclient source package in Yakkety:
  Fix Committed
Status in python-jujuclient source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * The python Juju client cannot make SSL connections to the server anymore, 
because TLS v1.0 was deprecated on the server.
   * Switching to TLS v1.2 fixes the problem entirely.
   * Example failure: http://pastebin.ubuntu.com/23521446/

  [Test case]

  Steps to reproduce (works in a container, needs a valid juju
  environment):

   * Install juju 1.25: sudo apt-get install juju-1-default juju-1.25
   * Install the package: sudo apt-get install python-jujuclient
   * Set up an environment (ec2 works for instance)
   * Bootstrap environment: "juju bootstrap # Note your environment's name"
   * Run: python -c 'from jujuclient import Environment; 
Environment.connect("")'

  [Regression Potential]

   * None - the package is completely unusable in its current state
  because of server changes. It can't get any worse :)

  [Other Info]

   * The attached patch is the minimal fix - forcing Python to connect over TLS 
1.2 instead of forcing TLS 1.0.
   * TLS 1.2 connectivity is available in all targeted releases.
   * lp:python-jujuclient (upstream) is not affected by the problem, but the 
code is much diverged from the version in the archives, with way too many 
changes for a SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+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 1642001] Re: uim-qt5 check is broken

This bug was fixed in the package im-config - 0.29-1ubuntu16.1

---
im-config (0.29-1ubuntu16.1) yakkety-proposed; urgency=medium

  * debian/patches/fix-uim-qt5.patch:
- Fix uim Qt5 immodule path (LP: #1642001).
  * debian/patches/gcin-qt5.patch:
- Add gcin Qt5 immodule (LP: #1482938).

 -- Gunnar Hjalmarsson   Wed, 16 Nov 2016 10:41:00
+0100

** Changed in: im-config (Ubuntu Yakkety)
   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/1642001

Title:
  uim-qt5 check is broken

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Xenial:
  Fix Committed
Status in im-config source package in Yakkety:
  Fix Released
Status in im-config package in Debian:
  Fix Released

Bug description:
  [Impact]

  XIM support check for Qt5 in UIM is broken — it uses the same paths as
  for Qt4, but they've been changed.

  Fix uploaded to yakkety queue; xenial patch attached.

  [Test Case]

  After the change, this command:

  grep platforminputcontexts /usr/share/im-config/data/24_uim.rc

  should output:

  for IM_CONFIG_MARKER in
  
/usr/lib/*/qt5/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so
  ; do

  [Regression Potential]

  None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1642001/+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 1587261] Re: [SRU] Swift bucket X-Timestamp not set by Rados Gateway

This bug was fixed in the package ceph - 10.2.3-0ubuntu0.16.04.2

---
ceph (10.2.3-0ubuntu0.16.04.2) xenial; urgency=medium

  * rgw: Fixes for creation times for buckets (LP: #1587261):
- d/p/rgw_rados-creation_time.patch: Backport fix from upstream master.
  Fix logic error that leads to creation time being 0 instead of current
  time when creating buckets.

ceph (10.2.3-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream stable release (LP: #1628809).
- d/p/*: Refresh.
- d/p/rocksdb-flags.patch: Dropped, accepted upstream.
- d/p/32bit-ftbfs.patch: Cherry pick fix for 32bit arch compat.
- d/ceph-{fs-common,fuse}.install: Fix install locations
  for mount{.fuse}.ceph.
  * Limit the amount of data per chunk in omap push operations to 64k,
ensuring that OSD threads don't hit timeouts during recovery
operations (LP: #1628750):
- d/p/osd-limit-omap-data-in-push-op.patch: Cherry pick fix from
  upstream master branch.

 -- Frode Nordahl   Fri, 28 Oct 2016
13:50:40 +0200

** Changed in: ceph (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/1587261

Title:
  [SRU] Swift bucket X-Timestamp not set by Rados Gateway

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in ceph package in Ubuntu:
  Fix Released
Status in ceph source package in Xenial:
  Fix Released
Status in ceph source package in Yakkety:
  Fix Committed
Status in ceph source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * A basic characteristic of a object store is the ability to create
     buckets and objects and to query for information about said
     buckets and objects.

   * In the current version of the ceph radosgw package it is not
     possible to get creation time for buckets. This is a serious
     defect and makes it impossible to use Ubuntu with ceph as a
     object store for some applications.

   * The issue has been fixed in upstream master

   * The proposed debdiff solves the issue by including patches cherry
     picked and adapted from upstream master branch fixing this issue.

  [Test Case]

   * Use Juju to deploy Ceph cluster with radosgw and relation to OpenStack
     Keystone. Example bundle: http://pastebin.ubuntu.com/23374308/

   * Install OpenStack Swift client

  sudo apt-get install python-swiftclient

   * Load OpenStack Credentials pointing to your test deployment

  wget 
https://raw.githubusercontent.com/openstack-charmers/openstack-bundles/master/development/shared/novarc
  . novarc

   * Create swift bucket

  swift post test

   * Display information about newly created bucket

  swift stat test

   * Observe that key 'X-Timestamp' has value 0.0

   * Delete bucket

  swift delete test

   * Install patched radosgw packages on 'ceph-radosgw' unit and repeat

   * Verify that key 'X-Timestamp' now has a value > 0.0 and corrensponding
 to the unixtime of when you created the bucket.

  [Regression Potential]

   * The patch is simple and I see little potential for any regression as a
     result of it being applied.

  [Original bug description]
  When creating a swift/radosgw bucket in horizon the bucket gets created, but 
shows up with a creation date of 19700101

  In the apache log one can observe

  curl -i http://10.11.140.241:80/swift/v1/bucket1 -I -H "X-Auth-Token:  ...
  Container HEAD failed: http://10.11.140.241:80/swift/v1/bucket1 404 Not Found

  However a manual curl call succeeds. Also the radosgw.log shows
  successful PUT/GET requests.

  I get similar results using the swift command line utility with
  containers inheriting a creation date of 19700101 even though I can
  see the correct date being passed to rados in the headers of the
  request.

  Also similarly issues with ceilometer intergration, similarly linked:

  2016-05-31 06:28:16.931 1117922 WARNING ceilometer.agent.manager [-] Continue 
after error from storage.containers.objects: Account GET failed: 
http://10.101.140.241:80/swift/v1/AUTH_025d6aa2af18415a87c012211edb7fea?format=json
 404 Not Found  [first 60 chars of response] 
{"Code":"NoSuchBucket","BucketName":"AUTH_025d6aa2af18415a87
  2016-05-31 06:28:16.931 1117922 ERROR ceilometer.agent.manager Traceback 
(most recent call last):

  This is using charm version: 86 against Openstack Mitaka

  This also seems pretty reproduceable with any ceph, ceph-rados and
  mitaka install via the juju charms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1587261/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to :

[Group.of.nepali.translators] [Bug 1628809] Re: [SRU] ceph 10.2.3

This bug was fixed in the package ceph - 10.2.3-0ubuntu0.16.04.2

---
ceph (10.2.3-0ubuntu0.16.04.2) xenial; urgency=medium

  * rgw: Fixes for creation times for buckets (LP: #1587261):
- d/p/rgw_rados-creation_time.patch: Backport fix from upstream master.
  Fix logic error that leads to creation time being 0 instead of current
  time when creating buckets.

ceph (10.2.3-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream stable release (LP: #1628809).
- d/p/*: Refresh.
- d/p/rocksdb-flags.patch: Dropped, accepted upstream.
- d/p/32bit-ftbfs.patch: Cherry pick fix for 32bit arch compat.
- d/ceph-{fs-common,fuse}.install: Fix install locations
  for mount{.fuse}.ceph.
  * Limit the amount of data per chunk in omap push operations to 64k,
ensuring that OSD threads don't hit timeouts during recovery
operations (LP: #1628750):
- d/p/osd-limit-omap-data-in-push-op.patch: Cherry pick fix from
  upstream master branch.

 -- Frode Nordahl   Fri, 28 Oct 2016
13:50:40 +0200

** Changed in: ceph (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/1628809

Title:
  [SRU] ceph 10.2.3

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in ceph package in Ubuntu:
  Fix Released
Status in ceph source package in Xenial:
  Fix Released
Status in ceph source package in Yakkety:
  Fix Released

Bug description:
  This point release fixes several important bugs in RBD mirroring, RGW
  multi-site, CephFS, and RADOS.

  We recommend that all v10.2.x users upgrade.

  Notable changes in this release include:
  * build/ops: 60-ceph-partuuid-workaround-rules still needed by debian jessie 
(udev 215-17) (#16351, runsisi, Loic Dachary)
  * build/ops: ceph Resource Agent does not work with systemd (#14828, Nathan 
Cutler)
  * build/ops: ceph-base requires parted (#16095, Ken Dreyer)
  * build/ops: ceph-osd-prestart.sh contains Upstart-specific code (#15984, 
Nathan Cutler)
  * build/ops: mount.ceph: move from ceph-base to ceph-common and add symlink 
in /sbin for SUSE (#16598, #16645, Nathan Cutler, Dan Horák, Ricardo Dias, Kefu 
Chai)
  * build/ops: need rocksdb commit 7ca731b12ce for ppc64le build (#17092, 
Nathan Cutler)
  * build/ops: rpm: OBS needs ExclusiveArch (#16936, Michel Normand)
  * cli: ceph command line tool chokes on ceph –w (the dash is unicode 'en 
dash' , copy-paste to reproduce) (#12287, Oleh Prypin, Kefu Chai)
  * common: expose buffer const_iterator symbols (#16899, Noah Watkins)
  * common: global-init: fixup chown of the run directory along with log and 
asok files (#15607, Karol Mroz)
  * fs: ceph-fuse: link to libtcmalloc or jemalloc (#16655, Yan, Zheng)
  * fs: client: crash in unmount when fuse_use_invalidate_cb is enabled 
(#16137, Yan, Zheng)
  * fs: client: fstat cap release (#15723, Yan, Zheng, Noah Watkins)
  * fs: essential backports for OpenStack Manila (#15406, #15614, #15615, John 
Spray, Ramana Raja, Xiaoxi Chen)
  * fs: fix double-unlock on shutdown (#17126, Greg Farnum)
  * fs: fix mdsmap print_summary with standby replays (#15705, John Spray)
  * fs: fuse mounted file systems fails SAMBA CTDB ping_pong rw test with 
v9.0.2 (#12653, #15634, Yan, Zheng)
  * librados: Add cleanup message with time to rados bench output (#15704, 
Vikhyat Umrao)
  * librados: Missing export for rados_aio_get_version in 
src/include/rados/librados.h (#15535, Jim Wright)
  * librados: osd: bad flags can crash the osd (#16012, Sage Weil)
  * librbd: Close journal and object map before flagging exclusive lock as 
released (#16450, Jason Dillaman)
  * librbd: Crash when utilizing advisory locking API functions (#16364, Jason 
Dillaman)
  * librbd: ExclusiveLock object leaked when switching to snapshot (#16446, 
Jason Dillaman)
  * librbd: FAILED assert(object_no < m_object_map.size()) (#16561, Jason 
Dillaman)
  * librbd: Image removal doesn't necessarily clean up all rbd_mirroring 
entries (#16471, Jason Dillaman)
  * librbd: Object map/fast-diff invalidated if journal replays the same snap 
remove event (#16350, Jason Dillaman)
  * librbd: Timeout sending mirroring notification shouldn't result in failure 
(#16470, Jason Dillaman)
  * librbd: Whitelist EBUSY error from snap unprotect for journal replay 
(#16445, Jason Dillaman)
  * librbd: cancel all tasks should wait until finisher is done (#16517, Haomai 
Wang)
  * librbd: delay acquiring lock if image watch has failed (#16923, Jason 
Dillaman)
  * librbd: fix missing return statement if failed to get mirror image state 
(#16600, runsisi)
  * librbd: flag image as updated after proxying maintenance op (#16404, Jason 
Dillaman)
  * librbd: mkfs.xfs slow performance with discards and object map (#16707,

[Group.of.nepali.translators] [Bug 1628750] Re: Please backport fixes from 10.2.3 and tip for RadosGW

This bug was fixed in the package ceph - 10.2.3-0ubuntu0.16.04.2

---
ceph (10.2.3-0ubuntu0.16.04.2) xenial; urgency=medium

* rgw: Fixes for creation times for buckets (LP: #1587261):
- d/p/rgw_rados-creation_time.patch: Backport fix from upstream master.
Fix logic error that leads to creation time being 0 instead of current
time when creating buckets.

ceph (10.2.3-0ubuntu0.16.04.1) xenial; urgency=medium

* New upstream stable release (LP: #1628809).
- d/p/*: Refresh.
- d/p/rocksdb-flags.patch: Dropped, accepted upstream.
- d/p/32bit-ftbfs.patch: Cherry pick fix for 32bit arch compat.
- d/ceph-{fs-common,fuse}.install: Fix install locations
for mount{.fuse}.ceph.
* Limit the amount of data per chunk in omap push operations to 64k,
ensuring that OSD threads don't hit timeouts during recovery
operations (LP: #1628750):
- d/p/osd-limit-omap-data-in-push-op.patch: Cherry pick fix from
upstream master branch.

-- Frode Nordahl Fri, 28 Oct 2016
13:50:40 +0200

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

Title:
Please backport fixes from 10.2.3 and tip for RadosGW

Status in Ubuntu Cloud Archive:
Invalid
Status in Ubuntu Cloud Archive mitaka series:
Fix Committed
Status in ceph package in Ubuntu:
Fix Released
Status in ceph source package in Xenial:
Fix Released
Status in ceph source package in Yakkety:
Fix Released

Bug description:
[Impact]
In ceph deployments with large numbers of objects (typically generated by use
of radosgw for object storage), during recovery options when servers or disks
fail, it quite possible for OSD recovering data to hit their suicide timeout
and shutdown because of the number of objects each was trying to recover in a
single chuck between heartbeats. As a result, clusters go read-only due to
data availability.

[Test Case]
Non-trivial to reproduce - see original bug report.

[Regression Potential]
Medium; the fix for this problem is to reduce the number of operations per
chunk to 64000, limiting the chance that an OSD will not heatbeat and suicide
itself as a result. This is configurable so can be tuned on a per environment
basis.

The patch has been accepted into the Ceph master branch, but is not
currently targetted as a stable fix for Jewel.

>> Original Bug Report <<

We've run into significant issues with RadosGW at scale; we have a
customer who has ½ billion objects in ~20Tb of data and whenever they
lose an OSD for whatever reason, even for a very short period of time,
ceph was taking hours and hours to recover. The whole time it was
recovering requests to RadosGW were hanging.

I ended up cherry picking 3 patches; 2 from 10.2.3 and one from trunk:

* d/p/fix-pg-temp.patch: cherry pick
56bbcb1aa11a2beb951de396b0de9e3373d91c57 from jewel.
* d/p/only-update-up_thru-if-newer.patch:
6554d462059b68ab983c0c8355c465e98ca45440 from jewel.
* d/p/limit-omap-data-in-push-op.patch:
38609de1ec5281602d925d20c392ba4094fdf9d3 from master.

The 2 from 10.2.3 are because pg_temp was implicated in one of the
longer outages we had.

The last one is what I think actually got us to a point where ceph was
stable and I found it via the following URL chain:

http://lists.opennebula.org/pipermail/ceph-users-ceph.com/2016-June/010230.html
-> http://tracker.ceph.com/issues/16128
-> https://github.com/ceph/ceph/pull/9894
->
https://github.com/ceph/ceph/commit/38609de1ec5281602d925d20c392ba4094fdf9d3

With these 3 patches applied the customer has been stable for 4 days
now but I've yet to restart the entire cluster (only the stuck OSDs)
so it's hard to be completely sure that all our issues are resolved
but also which of the patches fixed things.

I've attached the debdiff I used for reference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1628750/+subscriptions

[Group.of.nepali.translators] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

2016-11-30 Thread Iain Lane

unity-gtk-module needs to update the systemd environment now too

** Description changed:

+ [ Description ]
+
+ In Xenial, when dbus-user-session is installed, dbus' upstart job still
+ starts a new bus. Things get confused about which bus to talk to.
+
+ [ Fix ]
+
+ Already fixed in Yakkety. Cherry-pick the upstart job. On top of
+ Yakkety's version, call `dbus-update-activation-environment --verbose
+ --systemd GTK_MODULES', because Xenial does not have the change in
+ upstart to automatically publish to the systemd activation environment.
+
+ [ QA ]
+
+ Install dbus-user-session, press print screen. It should be delayed if
+ you are experiencing this bug, and not delayed otherwise.
+
+ Remove dbus-user-session, make sure the session still works properly -
+ the global menu works, everything launches properly, etc.
+
+ [ Regression potential ]
+
+ This change alters the way that the session bus is launched, even if you
+ aren't using dbus-user-session. Even though this same change is deployed
+ in ≥ yakkety, be aware of this. In yakkety we have installed dbus-user-
+ session by default, so the case where you don't have it isn't as well
+ tested. I would suggest focusing some testing on the non dbus-user-
+ session case.
+
+ [ Original report ]
+
After installing the deb (and then the snap), certain things in the
unity7 session take a very long time (30 to 60 secs), such as launching
chromium and ctrl-alt-t for a new terminal session.

Removing both the deb and the snap followed by a reboot does not fix the
symptoms.

Xenial amd64 laptop

** Also affects: unity-gtk-module (Ubuntu)
Importance: Undecided
Status: New

** Changed in: unity-gtk-module (Ubuntu)
Status: New => Fix Released

** Changed in: unity-gtk-module (Ubuntu Xenial)
Status: New => In Progress

Title:
Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
Confirmed
Status in dbus package in Ubuntu:
Fix Released
Status in unity-gtk-module package in Ubuntu:
Fix Released
Status in dbus source package in Xenial:
In Progress
Status in unity-gtk-module source package in Xenial:
In Progress

Bug description:
[ Description ]

In Xenial, when dbus-user-session is installed, dbus' upstart job
still starts a new bus. Things get confused about which bus to talk
to.

[ Fix ]

Already fixed in Yakkety. Cherry-pick the upstart job. On top of
Yakkety's version, call `dbus-update-activation-environment --verbose
--systemd GTK_MODULES', because Xenial does not have the change in
upstart to automatically publish to the systemd activation
environment.

[ QA ]

Install dbus-user-session, press print screen. It should be delayed if
you are experiencing this bug, and not delayed otherwise.

Remove dbus-user-session, make sure the session still works properly -
the global menu works, everything launches properly, etc.

[ Regression potential ]

This change alters the way that the session bus is launched, even if
you aren't using dbus-user-session. Even though this same change is
deployed in ≥ yakkety, be aware of this. In yakkety we have installed
dbus-user-session by default, so the case where you don't have it
isn't as well tested. I would suggest focusing some testing on the non
dbus-user-session case.

[ Original report ]

After installing the deb (and then the snap), certain things in the
unity7 session take a very long time (30 to 60 secs), such as
launching chromium and ctrl-alt-t for a new terminal session.

Removing both the deb and the snap followed by a reboot does not fix
the symptoms.

Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions

[Group.of.nepali.translators] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

2016-11-30 Thread Iain Lane

** Changed in: dbus (Ubuntu)
 Assignee: Ted Gould (ted) => (unassigned)

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

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

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  In Progress

Bug description:
  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

2016-11-30 Thread Martin Pitt

As xenial-release and yakkety-release have the same ido version, I
forward-copied the xenial SRU to yakkety. This needs to be verified too,
so that both can eventually be released. Otherwise x would have a higher
version than y.

** Also affects: ido (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: ido (Ubuntu Yakkety)
   Status: New => Fix Committed

** Tags removed: verification-done wily
** Tags added: verification-done-xenial verification-neededd

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

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Xenial:
  Fix Committed
Status in ido source package in Yakkety:
  Fix Committed

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1620888] Re: [SRU] NameError: global name '_LE' is not defined when running trove-guestagent

This bug was fixed in the package openstack-trove - 1:5.1.1-0ubuntu2

---
openstack-trove (1:5.1.1-0ubuntu2) xenial; urgency=medium

  * d/p/add-missing-import.patch: Cherry-pick patch from upstream
to add missing '_LE' import for trove-guestagent (LP: #1620888).

 -- Corey Bryant   Thu, 27 Oct 2016 17:42:56
+0200

** Changed in: openstack-trove (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/1620888

Title:
  [SRU] NameError: global name '_LE' is not defined when running trove-
  guestagent

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in OpenStack DBaaS (Trove):
  Fix Released
Status in openstack-trove package in Ubuntu:
  Invalid
Status in openstack-trove source package in Xenial:
  Fix Released

Bug description:
  [Description]
  When we run trove-guestagent, it will throw exception as follow:

  2016-09-06 12:53:49.178 8485 CRITICAL root [-] NameError: global name '_LE' 
is not defined
  2016-09-06 12:53:49.178 8485 ERROR root Traceback (most recent call last):
  2016-09-06 12:53:49.178 8485 ERROR root   File 
"/usr/local/bin/trove-guestagent", line 10, in 
  2016-09-06 12:53:49.178 8485 ERROR root sys.exit(main())
  2016-09-06 12:53:49.178 8485 ERROR root   File 
"/usr/local/lib/python2.7/dist-packages/trove/cmd/guest.py", line 43, in main
  2016-09-06 12:53:49.178 8485 ERROR root msg = (_LE("Manager class not 
registered for datastore manager %s") %
  2016-09-06 12:53:49.178 8485 ERROR root NameError: global name '_LE' is not 
defined
  2016-09-06 12:53:49.178 8485 ERROR root

  [Testcase]
  Run trove-guestagent.

  [Regression potential]
  None. The fix just adds a missing import.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1620888/+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 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)