date:20170515

[Group.of.nepali.translators] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-05-15 Thread Timo Aaltonen

** No longer affects: debhelper (Ubuntu)

** No longer affects: debhelper (Ubuntu Xenial)

** No longer affects: dh-autoreconf (Ubuntu Xenial)

** No longer affects: dh-autoreconf (Ubuntu)

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont1 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  New
Status in libxfont1 source package in Xenial:
  New
Status in llvm-toolchain-4.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in vulkan source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+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 1672200] Re: Kernel error on i915 gpu driver

2017-05-15 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => Expired

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

Title:
  Kernel error on i915 gpu driver

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

Bug description:
  The following error (warning?) shows up in dmesg during every boot:

  [3.244312] [ cut here ]
  [3.244397] WARNING: CPU: 0 PID: 170 at 
/build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/i915/intel_fbdev.c:406 
intel_fb_initial_config+0x2d4/0x5f0 [i915]()
  [3.244410] WARN_ON(!encoder->crtc)
  [3.244413] Modules linked in:
  [3.244419]  i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt fb_sys_fops b44 drm ahci ssb psmouse pata_acpi libahci mii wmi fjes 
video
  [3.244451] CPU: 0 PID: 170 Comm: kworker/u4:6 Not tainted 
4.4.0-66-generic #87-Ubuntu
  [3.244462] Hardware name: Hewlett-Packard HP Compaq nx7400 
(RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006
  [3.244477] Workqueue: events_unbound async_run_entry_fn
  [3.244484]  c1adf967 ebf0fd93 0286 f5da5d04 c13ac15f f5da5d44 
f8d3b99c f5da5d34
  [3.244499]  c1070457 f8d46600 f5da5d64 00aa f8d3b99c 0196 
f8ceb9a4 f8ceb9a4
  [3.244514]   0001 0001 f5da5d50 c10704ce 0009 
f5da5d44 f8d46600
  [3.244530] Call Trace:
  [3.244541]  [] dump_stack+0x58/0x79
  [3.244550]  [] warn_slowpath_common+0x87/0xc0
  [3.244615]  [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244678]  [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244687]  [] warn_slowpath_fmt+0x3e/0x60
  [3.244750]  [] intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244759]  [] ? idr_alloc+0xa4/0x120
  [3.244823]  [] ? intel_crtc_fb_gamma_get+0x40/0x40 [i915]
  [3.244847]  [] drm_setup_crtcs+0x21f/0xa90 [drm_kms_helper]
  [3.244866]  [] ? 
drm_helper_probe_single_connector_modes_merge_bits+0x1e3/0x480 [drm_kms_helper]
  [3.244879]  [] ? schedule+0x2d/0x80
  [3.244898]  [] drm_fb_helper_initial_config+0xbc/0x400 
[drm_kms_helper]
  [3.244911]  [] ? put_prev_entity+0x33/0xcc0
  [3.244919]  [] ? pick_next_task_fair+0x501/0x520
  [3.244982]  [] intel_fbdev_initial_config+0x19/0x20 [i915]
  [3.244991]  [] async_run_entry_fn+0x4e/0x170
  [3.245000]  [] process_one_work+0x121/0x3f0
  [3.245009]  [] worker_thread+0x37/0x490
  [3.245017]  [] ? process_one_work+0x3f0/0x3f0
  [3.245025]  [] kthread+0xa6/0xc0
  [3.245034]  [] ret_from_kernel_thread+0x21/0x38
  [3.245042]  [] ? kthread_create_on_node+0x170/0x170
  [3.245049] ---[ end trace 0bd04c67fb0cdbfa ]---
  [3.251264] fbcon: inteldrmfb (fb0) is primary device
  [3.251911] [ cut here ]
  [3.251933] WARNING: CPU: 0 PID: 170 at 
/build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/drm_atomic_helper.c:723 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]()
  [3.251945] Modules linked in: i915 i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops b44 drm ahci ssb psmouse 
pata_acpi libahci mii wmi fjes video
  [3.251949] CPU: 0 PID: 170 Comm: kworker/u4:6 Tainted: GW   
4.4.0-66-generic #87-Ubuntu
  [3.251950] Hardware name: Hewlett-Packard HP Compaq nx7400 
(RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006
  [3.251956] Workqueue: events_unbound async_run_entry_fn
  [3.251962]  c1adf967 ebf0fd93 0286 f5da5b3c c13ac15f  
f85c51f0 f5da5b6c
  [3.251966]  c1070457 c19d054c  00aa f85c51f0 02d3 
f85bb98a f85bb98a
  [3.251970]  f67f8800  f07fc400 f5da5b7c c1070562 0009 
 f5da5ba4
  [3.251971] Call Trace:
  [3.251977]  [] dump_stack+0x58/0x79
  [3.251981]  [] warn_slowpath_common+0x87/0xc0
  [3.251994]  [] ? 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252007]  [] ? 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252010]  [] warn_slowpath_null+0x22/0x30
  [3.252023]  [] 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252023]  [] ? intel_pre_plane_update+0xd8/0x130 [i915]
  [3.252023]  [] intel_atomic_commit+0x52a/0x6a0 [i915]
  [3.252023]  [] ? drm_atomic_check_only+0x1ae/0x600 [drm]
  [3.252023]  [] ? drm_modeset_lock+0x49/0xd0 [drm]
  [3.252023]  [] ? drm_atomic_set_crtc_for_connector+0x5c/0xe0 
[drm]
  [3.252023]  [] drm_atomic_commit+0x32/0x60 [drm]
  [3.252023]  [] restore_fbdev_mode+0x253/0x290 [drm_kms_helper]
  [3.252023]  [] ? drm_modeset_lock_all_ctx+0x94/0xb0 [drm]
  [3.252023]  [] 
drm_fb_helper_

[Group.of.nepali.translators] [Bug 1672200] Re: Kernel error on i915 gpu driver

2017-05-15 Thread Launchpad Bug Tracker

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Kernel error on i915 gpu driver

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

Bug description:
  The following error (warning?) shows up in dmesg during every boot:

  [3.244312] [ cut here ]
  [3.244397] WARNING: CPU: 0 PID: 170 at 
/build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/i915/intel_fbdev.c:406 
intel_fb_initial_config+0x2d4/0x5f0 [i915]()
  [3.244410] WARN_ON(!encoder->crtc)
  [3.244413] Modules linked in:
  [3.244419]  i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt fb_sys_fops b44 drm ahci ssb psmouse pata_acpi libahci mii wmi fjes 
video
  [3.244451] CPU: 0 PID: 170 Comm: kworker/u4:6 Not tainted 
4.4.0-66-generic #87-Ubuntu
  [3.244462] Hardware name: Hewlett-Packard HP Compaq nx7400 
(RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006
  [3.244477] Workqueue: events_unbound async_run_entry_fn
  [3.244484]  c1adf967 ebf0fd93 0286 f5da5d04 c13ac15f f5da5d44 
f8d3b99c f5da5d34
  [3.244499]  c1070457 f8d46600 f5da5d64 00aa f8d3b99c 0196 
f8ceb9a4 f8ceb9a4
  [3.244514]   0001 0001 f5da5d50 c10704ce 0009 
f5da5d44 f8d46600
  [3.244530] Call Trace:
  [3.244541]  [] dump_stack+0x58/0x79
  [3.244550]  [] warn_slowpath_common+0x87/0xc0
  [3.244615]  [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244678]  [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244687]  [] warn_slowpath_fmt+0x3e/0x60
  [3.244750]  [] intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244759]  [] ? idr_alloc+0xa4/0x120
  [3.244823]  [] ? intel_crtc_fb_gamma_get+0x40/0x40 [i915]
  [3.244847]  [] drm_setup_crtcs+0x21f/0xa90 [drm_kms_helper]
  [3.244866]  [] ? 
drm_helper_probe_single_connector_modes_merge_bits+0x1e3/0x480 [drm_kms_helper]
  [3.244879]  [] ? schedule+0x2d/0x80
  [3.244898]  [] drm_fb_helper_initial_config+0xbc/0x400 
[drm_kms_helper]
  [3.244911]  [] ? put_prev_entity+0x33/0xcc0
  [3.244919]  [] ? pick_next_task_fair+0x501/0x520
  [3.244982]  [] intel_fbdev_initial_config+0x19/0x20 [i915]
  [3.244991]  [] async_run_entry_fn+0x4e/0x170
  [3.245000]  [] process_one_work+0x121/0x3f0
  [3.245009]  [] worker_thread+0x37/0x490
  [3.245017]  [] ? process_one_work+0x3f0/0x3f0
  [3.245025]  [] kthread+0xa6/0xc0
  [3.245034]  [] ret_from_kernel_thread+0x21/0x38
  [3.245042]  [] ? kthread_create_on_node+0x170/0x170
  [3.245049] ---[ end trace 0bd04c67fb0cdbfa ]---
  [3.251264] fbcon: inteldrmfb (fb0) is primary device
  [3.251911] [ cut here ]
  [3.251933] WARNING: CPU: 0 PID: 170 at 
/build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/drm_atomic_helper.c:723 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]()
  [3.251945] Modules linked in: i915 i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops b44 drm ahci ssb psmouse 
pata_acpi libahci mii wmi fjes video
  [3.251949] CPU: 0 PID: 170 Comm: kworker/u4:6 Tainted: GW   
4.4.0-66-generic #87-Ubuntu
  [3.251950] Hardware name: Hewlett-Packard HP Compaq nx7400 
(RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006
  [3.251956] Workqueue: events_unbound async_run_entry_fn
  [3.251962]  c1adf967 ebf0fd93 0286 f5da5b3c c13ac15f  
f85c51f0 f5da5b6c
  [3.251966]  c1070457 c19d054c  00aa f85c51f0 02d3 
f85bb98a f85bb98a
  [3.251970]  f67f8800  f07fc400 f5da5b7c c1070562 0009 
 f5da5ba4
  [3.251971] Call Trace:
  [3.251977]  [] dump_stack+0x58/0x79
  [3.251981]  [] warn_slowpath_common+0x87/0xc0
  [3.251994]  [] ? 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252007]  [] ? 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252010]  [] warn_slowpath_null+0x22/0x30
  [3.252023]  [] 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252023]  [] ? intel_pre_plane_update+0xd8/0x130 [i915]
  [3.252023]  [] intel_atomic_commit+0x52a/0x6a0 [i915]
  [3.252023]  [] ? drm_atomic_check_only+0x1ae/0x600 [drm]
  [3.252023]  [] ? drm_modeset_lock+0x49/0xd0 [drm]
  [3.252023]  [] ? drm_atomic_set_crtc_for_connector+0x5c/0xe0 
[drm]
  [3.252023]  [] drm_atomic_commit+0x32/0x60 [drm]
  [3.252023]  [] restore_fbdev_mode+0x253/0x290 [drm_kms_helper]
  [3.252023]  [] ? drm_modeset_lock_all_ctx+0x94/0xb0 [drm]
  [3.252023]  [] 
drm_fb_helper_restore_fbdev_

[Group.of.nepali.translators] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2017-05-15 Thread Joseph Salisbury

** Also affects: linux via
   http://bugzilla.kernel.org/109691
   Importance: Unknown
   Status: Unknown

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1521173/+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 1689517] Re: Displayport daisy chained displays get recognized as the same

2017-05-15 Thread Joseph Salisbury

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.68

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

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

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

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

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

** Tags added: kernel-da-key

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

Title:
  Displayport daisy chained displays get recognized as the same

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

Bug description:
  Hi,

  I'm using Ubuntu 16.04.2 LTS.

  Since I upgraded to 4.4.0-77, my daisy chained displays seem to get
  recognized as the same. Before, I've been using 4.4.0-72. Booting the
  older Kernel using grub also still works.

  I'm using two Dell U2715H Displays daisy chained. (DP1-1 and DP1-8)
  Both with 2560x1440px. Simultaneously, I use my Notebook Display with
  1920x1080px. (eDP1) I have a script, which I run manually after
  startx, which sets up my environment. It does:

  xrandr --output DP1-1 --mode 2560x1440
  xrandr --output DP1-8 --mode 2560x1440
  xrandr --output DP1-8 --left-of eDP1
  xrandr --output DP1-1 --left-of DP1-8

  On 4.4.0-77 both, DP1-1 and DP1-8 show the same picture (left-of eDP1);
  whereas on 4.4.0-72,
  DP1-1 shows the picture left of DP1-8,
  and DP1-8 shows the picture left of eDP1
  as expected.

  If I take a screenshot using xfce4-screenshooter, everything seems
  fine.

  I attached the output from xrandr on both kernels, screenshots from
  both pictures and reference pictures taken with my camera for you to
  see what actually happens.

  Thanks.

  Screen 0: minimum 8 x 8, current 7040 x 1440, maximum 32767 x 32767
  eDP1 connected 1920x1080+5120+0 (normal left inverted right x axis y axis) 
309mm x 173mm
 1920x1080 60.05*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP1-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 2048x1152 60.00  
 1920x1200 59.88  
 1920x1080 60.0050.0059.9430.0025.0024.0029.97  
  23.98  
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1200x960  59.99  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  DP1-8 connected 2560x1440+2560+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 2048x1152 60.00  
 1920x1200 59.88  
 1920x1080 60.0050.0059.9430.0025.0024.0029.97  
  23.98  
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1200x960  59.99  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.0

[Group.of.nepali.translators] [Bug 1623664] Re: [SRU] Fix Race between L3 agent and neutron-ns-cleanup

2017-05-15 Thread Launchpad Bug Tracker

This bug was fixed in the package neutron-lbaas - 2:9.0.0-0ubuntu2

---
neutron-lbaas (2:9.0.0-0ubuntu2) yakkety; urgency=medium

  * debian/neutron-lbaas-common.install: Remove cron jobs since
it will cause a race with L3 agents and neutron. (LP: #1623664).

 -- Chuck Short   Mon, 27 Mar 2017 13:33:56 -0400

** Changed in: neutron (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/1623664

Title:
  [SRU] Fix Race between L3 agent and neutron-ns-cleanup

Status in Ubuntu Cloud Archive:
  New
Status in neutron:
  Invalid
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron-lbaas package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  Fix Released
Status in neutron-lbaas source package in Xenial:
  Fix Released
Status in neutron source package in Yakkety:
  Fix Released
Status in neutron-lbaas source package in Yakkety:
  Fix Released
Status in neutron source package in Zesty:
  Fix Released

Bug description:
  I suspect a race between the neutron L3 agent and the neutron-netns-
  cleanup script, which runs as a CRON job in Ubuntu. Here's a stack
  trace in the router delete code path:

  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager [-] Error during 
notification for neutron.agent.metadata.driver.before_router_removed router, 
before_delete
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Traceback (most 
recent call last):
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/callbacks/manager.py", line 141, in 
_notify_loop
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager 
callback(resource, event, trigger, **kwargs)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/metadata/driver.py", line 176, 
in before_router_removed
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager 
router.iptables_manager.apply()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 423, in apply
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager return 
self._apply()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 431, in _apply
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager return 
self._apply_synchronized()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 457, in _apply_synchronized
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager save_output 
= self.execute(args, run_as_root=True)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 159, in 
execute
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager raise 
RuntimeError(m)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager RuntimeError:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Command: 
['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 
'netns', 'exec', 'qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8', 
'iptables-save']
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Exit code: 1
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stdin:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stdout:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stderr: Cannot 
open network namespace "qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8": No such 
file or directory
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent [-] Error while 
deleting router 69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent Traceback (most 
recent call last):
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 344, in 
_safe_router_removed
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent 
self._router_removed(router_id)
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 360, in 
_router_removed
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent self, router=ri)
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent   File 
"/usr/lib/python2.7/dist-packages/neutron/callbacks/registry.py", line 44, in 
notify
  2016-08-03 03:3

[Group.of.nepali.translators] [Bug 1623664] Re: [SRU] Fix Race between L3 agent and neutron-ns-cleanup

2017-05-15 Thread Launchpad Bug Tracker

This bug was fixed in the package neutron-lbaas - 2:8.3.0-0ubuntu3

---
neutron-lbaas (2:8.3.0-0ubuntu3) xenial; urgency=medium

  * debian/neutron-lbaas-common.install: Remove cron jobs since
it will cause a race with L3 agents and neutron. (LP: #1623664)

 -- Chuck Short   Mon, 27 Mar 2017 14:23:58 -0400

** Changed in: neutron-lbaas (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: neutron-lbaas (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/1623664

Title:
  [SRU] Fix Race between L3 agent and neutron-ns-cleanup

Status in Ubuntu Cloud Archive:
  New
Status in neutron:
  Invalid
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron-lbaas package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  Fix Released
Status in neutron-lbaas source package in Xenial:
  Fix Released
Status in neutron source package in Yakkety:
  Fix Released
Status in neutron-lbaas source package in Yakkety:
  Fix Released
Status in neutron source package in Zesty:
  Fix Released

Bug description:
  I suspect a race between the neutron L3 agent and the neutron-netns-
  cleanup script, which runs as a CRON job in Ubuntu. Here's a stack
  trace in the router delete code path:

  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager [-] Error during 
notification for neutron.agent.metadata.driver.before_router_removed router, 
before_delete
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Traceback (most 
recent call last):
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/callbacks/manager.py", line 141, in 
_notify_loop
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager 
callback(resource, event, trigger, **kwargs)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/metadata/driver.py", line 176, 
in before_router_removed
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager 
router.iptables_manager.apply()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 423, in apply
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager return 
self._apply()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 431, in _apply
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager return 
self._apply_synchronized()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 457, in _apply_synchronized
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager save_output 
= self.execute(args, run_as_root=True)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 159, in 
execute
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager raise 
RuntimeError(m)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager RuntimeError:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Command: 
['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 
'netns', 'exec', 'qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8', 
'iptables-save']
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Exit code: 1
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stdin:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stdout:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stderr: Cannot 
open network namespace "qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8": No such 
file or directory
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent [-] Error while 
deleting router 69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent Traceback (most 
recent call last):
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 344, in 
_safe_router_removed
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent 
self._router_removed(router_id)
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 360, in 
_router_removed
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent self, router=ri)
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent   File 
"/usr/l

[Group.of.nepali.translators] [Bug 1648242] Re: [SRU] Failure to retry update_ha_routers_states

2017-05-15 Thread Launchpad Bug Tracker

This bug was fixed in the package neutron - 2:8.4.0-0ubuntu2

---
neutron (2:8.4.0-0ubuntu2) xenial; urgency=medium

  [ Edward Hope-Morley ]
  * Backport fix for Failure to retry update_ha_routers_states (LP: #1648242)
- d/p/add-check-for-ha-state.patch

  [ Chuck Short ]
  * d/neutron-common.install, d/neutron-dhcp-agent.install:
Remove cron jobs since they will cause a race when
using an L3 agent. The L3 agent cleans up after itself now.
(LP: #1623664)

 -- Chuck Short   Wed, 19 Apr 2017 11:39:09 +0100

** Changed in: neutron (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/1648242

Title:
  [SRU] Failure to retry update_ha_routers_states

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  Fix Released

Bug description:
  [Impact]

Mitigates risk of incorrect ha_state reported by l3-agent for HA
routers in case where rmq connection is lost during update
window. Fix is already in Ubuntu for O and N but upstream
backport just missed the Mitaka PR hence this SRU.

  [Test Case]

* deploy Openstack Mitaka (Xenial) with l3-ha enabled and min/max l3
  -agents-per-router set to 3

* configure network, router, boot instance with floating ip and
  start pinging

* check that status is 1 agent showing active and 2 showing standby

* trigger some router failovers while rabbit server stopped e.g.

  - go to l3-agent hosting your router and do:

ip netns exec qrouter-${router} ip link set dev  down

check other units to see if ha iface has been failed over

ip netns exec qrouter-${router} ip link set dev  up
 
* ensure ping still running

* eventually all agents will be xxx/standby

* start rabbit server

* wait for correct ha_state to be set (takes a few seconds)

  [Regression Potential]

   I do not envisage any regression from this patch. One potential side-effect 
is
   mildy increased rmq traffic but should be negligible.

  
  

  Version: Mitaka

  While performing failover testing of L3 HA routers, we've discovered
  an issue with regards to the failure of an agent to report its state.

  In this scenario, we have a router (7629f5d7-b205-4af5-8e0e-
  a3c4d15e7677) scheduled to (3) L3 agents:

  
+--+--++---+--+
  | id   | host 
| admin_state_up | alive | ha_state |
  
+--+--++---+--+
  | 4434f999-51d0-4bbb-843c-5430255d5c64 | 
726404-infra03-neutron-agents-container-a8bb0b1f | True   | :-)   | 
active  |
  | 710e7768-df47-4bfe-917f-ca35c138209a | 
726402-infra01-neutron-agents-container-fc937477 | True   | :-)   | 
standby   |
  | 7f0888ba-1e8a-4a36-8394-6448b8c606fb | 
726403-infra02-neutron-agents-container-0338af5a | True   | :-)   | 
standby   |
  
+--+--++---+--+

  The infra03 node was shut down completely and abruptly. The router
  transitioned to master on infra02 as indicated in these log messages:

  2016-12-06 16:15:06.457 18450 INFO neutron.agent.linux.interface [-] Device 
qg-d48918fa-eb already exists
  2016-12-07 15:16:51.145 18450 INFO neutron.agent.l3.ha [-] Router 
c8b5d5b7-ab57-4f56-9838-0900dc304af6 transitioned to master
  2016-12-07 15:16:51.811 18450 INFO eventlet.wsgi.server [-]  - - 
[07/Dec/2016 15:16:51] "GET / HTTP/1.1" 200 115 0.666464
  2016-12-07 15:18:29.167 18450 INFO neutron.agent.l3.ha [-] Router 
c8b5d5b7-ab57-4f56-9838-0900dc304af6 transitioned to backup
  2016-12-07 15:18:29.229 18450 INFO eventlet.wsgi.server [-]  - - 
[07/Dec/2016 15:18:29] "GET / HTTP/1.1" 200 115 0.062110
  2016-12-07 15:21:48.870 18450 INFO neutron.agent.l3.ha [-] Router 
7629f5d7-b205-4af5-8e0e-a3c4d15e7677 transitioned to master
  2016-12-07 15:21:49.537 18450 INFO eventlet.wsgi.server [-]  - - 
[07/Dec/2016 15:21:49] "GET / HTTP/1.1" 200 115 0.667920
  2016-12-07 15:22:08.796 18450 INFO neutron.agent.l3.ha [-] Router 
4676e7a5-279c-4114-8674-209f7fd5ab1a transitioned to master
  2016-12-07 15:22:09.515 18450 INFO eventlet.wsgi.server [-]  - - 
[07/Dec/2016 15:22:09] "GET / HTTP/1.1" 200 115 0.719848

  Traffic to/from VMs through the new master router functioned as
  expected. However, the ha_state remained 'standby':

  
+-

[Group.of.nepali.translators] [Bug 1623664] Re: [SRU] Fix Race between L3 agent and neutron-ns-cleanup

2017-05-15 Thread Launchpad Bug Tracker

This bug was fixed in the package neutron - 2:9.2.0-0ubuntu2

---
neutron (2:9.2.0-0ubuntu2) yakkety; urgency=medium

  * d/neutron-common.install, d/neutron-dhcp-agent.install:
Remove cron jobs since they will cause a race when
using an L3 agent. The L3 agent cleans up after itself now.
(LP: #1623664)

 -- Chuck Short   Mon, 27 Mar 2017 13:20:57 -0400

** Changed in: neutron (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/1623664

Title:
  [SRU] Fix Race between L3 agent and neutron-ns-cleanup

Status in Ubuntu Cloud Archive:
  New
Status in neutron:
  Invalid
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron-lbaas package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  Fix Released
Status in neutron-lbaas source package in Xenial:
  Fix Released
Status in neutron source package in Yakkety:
  Fix Released
Status in neutron-lbaas source package in Yakkety:
  Fix Released
Status in neutron source package in Zesty:
  Fix Released

Bug description:
  I suspect a race between the neutron L3 agent and the neutron-netns-
  cleanup script, which runs as a CRON job in Ubuntu. Here's a stack
  trace in the router delete code path:

  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager [-] Error during 
notification for neutron.agent.metadata.driver.before_router_removed router, 
before_delete
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Traceback (most 
recent call last):
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/callbacks/manager.py", line 141, in 
_notify_loop
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager 
callback(resource, event, trigger, **kwargs)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/metadata/driver.py", line 176, 
in before_router_removed
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager 
router.iptables_manager.apply()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 423, in apply
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager return 
self._apply()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 431, in _apply
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager return 
self._apply_synchronized()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 457, in _apply_synchronized
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager save_output 
= self.execute(args, run_as_root=True)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 159, in 
execute
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager raise 
RuntimeError(m)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager RuntimeError:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Command: 
['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 
'netns', 'exec', 'qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8', 
'iptables-save']
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Exit code: 1
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stdin:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stdout:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stderr: Cannot 
open network namespace "qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8": No such 
file or directory
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent [-] Error while 
deleting router 69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent Traceback (most 
recent call last):
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 344, in 
_safe_router_removed
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent 
self._router_removed(router_id)
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 360, in 
_router_removed
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent self, router=ri)
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent   File 
"/usr/lib/python2.7/dist-packages/neutron/callbac

[Group.of.nepali.translators] [Bug 1623664] Re: [SRU] Fix Race between L3 agent and neutron-ns-cleanup

2017-05-15 Thread Launchpad Bug Tracker

This bug was fixed in the package neutron - 2:10.0.0-0ubuntu5.1

---
neutron (2:10.0.0-0ubuntu5.1) zesty; urgency=medium

  * d/rules: Revert the majority of changes made under 2:10.0.0-0ubuntu5
as these break default configuration and are the root cause of
the autopkgtest failures.

neutron (2:10.0.0-0ubuntu5) zesty; urgency=medium

  * d/rules: Fix failing unit tests.

neutron (2:10.0.0-0ubuntu4) zesty; urgency=medium

  * d/neutron-common.install, d/neutron-dhcp-agent.install:
Remove cron jobs since they will cause a race when
using an L3 agent. (LP: #1623664)

 -- James Page   Wed, 19 Apr 2017 11:49:10 +0100

** Changed in: neutron (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/1623664

Title:
  [SRU] Fix Race between L3 agent and neutron-ns-cleanup

Status in Ubuntu Cloud Archive:
  New
Status in neutron:
  Invalid
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron-lbaas package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  Fix Committed
Status in neutron-lbaas source package in Xenial:
  Fix Released
Status in neutron source package in Yakkety:
  Fix Released
Status in neutron-lbaas source package in Yakkety:
  Fix Released
Status in neutron source package in Zesty:
  Fix Released

Bug description:
  I suspect a race between the neutron L3 agent and the neutron-netns-
  cleanup script, which runs as a CRON job in Ubuntu. Here's a stack
  trace in the router delete code path:

  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager [-] Error during 
notification for neutron.agent.metadata.driver.before_router_removed router, 
before_delete
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Traceback (most 
recent call last):
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/callbacks/manager.py", line 141, in 
_notify_loop
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager 
callback(resource, event, trigger, **kwargs)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/metadata/driver.py", line 176, 
in before_router_removed
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager 
router.iptables_manager.apply()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 423, in apply
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager return 
self._apply()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 431, in _apply
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager return 
self._apply_synchronized()
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/iptables_manager.py", 
line 457, in _apply_synchronized
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager save_output 
= self.execute(args, run_as_root=True)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 159, in 
execute
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager raise 
RuntimeError(m)
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager RuntimeError:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Command: 
['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 
'netns', 'exec', 'qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8', 
'iptables-save']
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Exit code: 1
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stdin:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stdout:
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager Stderr: Cannot 
open network namespace "qrouter-69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8": No such 
file or directory
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager
  2016-08-03 03:30:03.392 2595 ERROR neutron.callbacks.manager
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent [-] Error while 
deleting router 69ef3d5c-1ad1-42fb-8a1e-8d949837bbf8
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent Traceback (most 
recent call last):
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/agent.py", line 344, in 
_safe_router_removed
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent 
self._router_removed(router_id)
  2016-08-03 03:30:03.393 2595 ERROR neutron.agent.l3.agent   File 
"/usr/lib/python2.7/di

[Group.of.nepali.translators] [Bug 1686651] Re: linux-aws: 4.4.0-1017.26 -proposed tracker

2017-05-15 Thread Brad Figg

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1686645
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686651/+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 1689946] Re: Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op

2017-05-15 Thread Frank Heimes

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Status: New => In Progress

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

Title:
  Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with
  split op

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
   State: Open by: mdate on 19 March 2017 12:33:34 

  On a Bolt adapter in a system with Ubuntu 16.04, I've formatted the
  Bolt for T10 and am using it to do a dd with a 2M block size.

  Here are the commands:
  nvme format /dev/nvme0n1 --lbaf=1 --pil=0 --ms=0 --pi=2

  dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1

  I get an error on the dd.
root@x1623bp1:~# dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct 
count=1
dd: error writing '/dev/nvme0n1': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 0.0525061 s, 0.0 kB/s

  dmesg shows:
  [589997.985151] blk_update_request: I/O error, dev nvme0n1, sector 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1689946/+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 1689946] Re: Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op

2017-05-15 Thread Joseph Salisbury

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Joseph Salisbury (jsalisbury)

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

Title:
  Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with
  split op

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
   State: Open by: mdate on 19 March 2017 12:33:34 

  On a Bolt adapter in a system with Ubuntu 16.04, I've formatted the
  Bolt for T10 and am using it to do a dd with a 2M block size.

  Here are the commands:
  nvme format /dev/nvme0n1 --lbaf=1 --pil=0 --ms=0 --pi=2

  dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1

  I get an error on the dd.
root@x1623bp1:~# dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct 
count=1
dd: error writing '/dev/nvme0n1': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 0.0525061 s, 0.0 kB/s

  dmesg shows:
  [589997.985151] blk_update_request: I/O error, dev nvme0n1, sector 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689946/+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 1690846] Re: version in repository is outdated and has vulnerabilities

2017-05-15 Thread LocutusOfBorg

Subscribing security team because of the CVEs

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

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

** Changed in: borgbackup (Ubuntu Zesty)
   Status: New => Fix Committed

** Description changed:

+ [Impact]
+ 
  The current version in 16.10 universe is 1.0.7 which has two known
  vulnerabilities (CVE-2016-10099 and CVE-2016-10100) fixed in upstream
  version 1.0.9 (released ~6 months ago). The current upstream version is
  1.0.10 (released ~3 months ago) and contains various other bugfixes.
+ 
+ [CHANGELOG]
+ Version 1.0.10 (2017-02-13)
+ ---
+ 
+ Bug fixes:
+ 
+ - Manifest timestamps are now monotonically increasing,
+   this fixes issues when the system clock jumps backwards
+   or is set inconsistently across computers accessing the same repository, 
#2115
+ - Fixed testing regression in 1.0.10rc1 that lead to a hard dependency on
+   py.test >= 3.0, #2112
+ 
+ New features:
+ 
+ - "key export" can now generate a printable HTML page with both a QR code and
+   a human-readable "paperkey" representation (and custom text) through the
+   ``--qr-html`` option.
+ 
+   The same functionality is also available through `paperkey.html 
`_,
+   which is the same HTML page generated by ``--qr-html``. It works with 
existing
+   "key export" files and key files.
+ 
+ Other changes:
+ 
+ - docs:
+ 
+   - language clarification - "borg create --one-file-system" option does not 
respect
+ mount points, but considers different file systems instead, #2141
+ - setup.py: build_api: sort file list for determinism
+ 
+ Version 1.0.10rc1 (2017-01-29)
+ --
+ 
+ Bug fixes:
+ 
+ - borg serve: fix transmission data loss of pipe writes, #1268
+   This affects only the cygwin platform (not Linux, BSD, OS X).
+ - Avoid triggering an ObjectiveFS bug in xattr retrieval, #1992
+ - When running out of buffer memory when reading xattrs, only skip the
+   current file, #1993
+ - Fixed "borg upgrade --tam" crashing with unencrypted repositories. Since
+   :ref:`the issue ` is not relevant for unencrypted repositories,
+   it now does nothing and prints an error, #1981.
+ - Fixed change-passphrase crashing with unencrypted repositories, #1978
+ - Fixed "borg check repo::archive" indicating success if "archive" does not 
exist, #1997
+ - borg check: print non-exit-code warning if --last or --prefix aren't 
fulfilled
+ - fix bad parsing of wrong repo location syntax
+ - create: don't create hard link refs to failed files,
+   mount: handle invalid hard link refs, #2092
+ - detect mingw byte order, #2073
+ - creating a new segment: use "xb" mode, #2099
+ - mount: umount on SIGINT/^C when in foreground, #2082
+ 
+ Other changes:
+ 
+ - binary: use fixed AND freshly compiled pyinstaller bootloader, #2002
+ - xattr: ignore empty names returned by llistxattr(2) et al
+ - Enable the fault handler: install handlers for the SIGSEGV, SIGFPE, SIGABRT,
+   SIGBUS and SIGILL signals to dump the Python traceback.
+ - Also print a traceback on SIGUSR2.
+ - borg change-passphrase: print key location (simplify making a backup of it)
+ - officially support Python 3.6 (setup.py: add Python 3.6 qualifier)
+ - tests:
+ 
+   - vagrant / travis / tox: add Python 3.6 based testing
+   - vagrant: fix openbsd repo, #2042
+   - vagrant: fix the freebsd64 machine, #2037 #2067
+   - vagrant: use python 3.5.3 to build binaries, #2078
+   - vagrant: use osxfuse 3.5.4 for tests / to build binaries
+ vagrant: improve darwin64 VM settings
+   - travis: fix osxfuse install (fixes OS X testing on Travis CI)
+   - travis: require succeeding OS X tests, #2028
+   - travis: use latest pythons for OS X based testing
+   - use pytest-xdist to parallelize testing
+   - fix xattr test race condition, #2047
+   - setup.cfg: fix pytest deprecation warning, #2050
+ - docs:
+ 
+   - language clarification - VM backup FAQ
+   - borg create: document how to backup stdin, #2013
+   - borg upgrade: fix incorrect title levels
+   - add CVE numbers for issues fixed in 1.0.9, #2106
+ - fix typos (taken from Debian package patch)
+ - remote: include data hexdump in "unexpected RPC data" error message
+ - remote: log SSH command line at debug level
+ - API_VERSION: use numberspaces, #2023
+ - remove .github from pypi package, #2051
+ - add pip and setuptools to requirements file, #2030
+ - SyncFile: fix use of fd object after close (cosmetic)
+ - Manifest.in: simplify, exclude \*.{so,dll,orig}, #2066
+ - ignore posix_fadvise errors in repository.py, #2095
+   (works around issues with docker on ARM)
+ - make LoggedIO.close_segment reentrant, avoid reentrance
+ 
+ 
+ Version 1.0.9 (2016-12-20)
+ --
+ 
+ Security fixes:
+ 
+ - A flaw in the cryptographic authentication scheme in Borg allowed an 
attacker
+   to spoof the manifest. See :ref:`tam_vuln` above for the steps you should
+   take.
+ 
+   CVE-2

[Group.of.nepali.translators] [Bug 1555258] Re: Request contained command arguments

2017-05-15 Thread Launchpad Bug Tracker

This bug was fixed in the package nagios-nrpe - 3.0.1-3ubuntu0.17.04.1

---
nagios-nrpe (3.0.1-3ubuntu0.17.04.1) zesty; urgency=medium

  * debian/rules : Add "--enable-command-args". (LP: #1555258)
This update enables the command-args support in nrpe
by not ignoring option "dont_blame_nrpe=1". By default,
the option is set as follow : "dont_blame_nrpe=0", which
has the same effect of having the command-args support
disabled at compile time like Debian does. Ubuntu has decided
to deviate from Debian upstream for that particular case to
allow/unblock the Ubuntu users of nrpe to make the choice for
themselves whether to accept the security risks that the feature
involve by manually enabling command-args in nrpe.cfg or not.
For more details as of why Debian has decided to disable the
feature can be found in debian/NEWS. (closes: #756479)

 -- Eric Desrochers   Tue, 02 May 2017
09:09:29 -0400

** Changed in: nagios-nrpe (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/1555258

Title:
  Request contained command arguments

Status in nagios-nrpe package in Ubuntu:
  Fix Released
Status in nagios-nrpe source package in Xenial:
  Fix Committed
Status in nagios-nrpe source package in Yakkety:
  Fix Committed
Status in nagios-nrpe source package in Zesty:
  Fix Released
Status in nagios-nrpe source package in Artful:
  Fix Released
Status in nagios-nrpe package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Debian upstream maintainer decided to compile without 
"-enable-command-args" as describe in debian/NEWS file. This decision have the 
effect of ignoring the following directive : "dont_blame_nrpe=1" in nrpe.cfg by 
not allowing command argument in the deamon.
  Debian disabled the option because there were concerns about security 
problems and that this feature is often used wrong [0] but there are Ubuntu 
users out there that know what they're doing and depend on this feature.

   * The expectation is for Ubuntu to deviate from Debian upstream
  decision to accommodate Ubuntu Nagios users.

  * Doug's comment explain well the situation :
  
https://bugs.launchpad.net/ubuntu/xenial/+source/nagios-nrpe/+bug/1555258/comments/6

  [0] - Debian Bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756479

  [Test Case]

   * This require a Nagios environment setup (Server and at least 1
  client)

   * Command example run at server side using "dont_blame_nrpe" set to either 0 
(false) or 1 (true) in nrpe.cfg
  $ /usr/lib/nagios/plugins/check_nrpe -H x.x.x.x -p 5664 -c check_procs -a 
rsyslogd 1 0
  CHECK_NRPE: Received 0 bytes from daemon.  Check the remote server logs for 
error messages.

  Server logs:
  nrpe[83523]: Connection from y.y.y.y port 43186
  nrpe[83523]: Host address is in allowed_hosts
  nrpe[83523]: Handling the connection...
  ==> nrpe[83523]: Error: Request contained command arguments!
  ==> nrpe[83523]: Client request was invalid, bailing out..

  [Regression Potential]

   * This update enables the command-args (at compile time) support in nrpe by 
NOT ignoring option "dont_blame_nrpe=1" IFF set manually.
     Note that by default, the option is DISABLE in the configuration file 
(nrpe.cfg) : "dont_blame_nrpe=0".

   * For users using the default value "dont_blame_nrpe=0", so no behavioural 
change. With regard to the risk, I would say it is LOW.
     The option is disable by default meaning that it doesn't introduce any 
security risk for users that doesn't rely on this feature.
     But it doesn't prevent the risk that non-experimented users enable the 
option without considering all the security risk aspects.

   * For users choosing to manually enable this option, the risk is
  HIGHER, but we assume that before enabling this option the users are
  considering the PROS and CONS.

   * Deviating from Debian upstream for that particular case will allow to 
unblock experimented Ubuntu users (who know what they are doing) of nrpe to 
make the choice for themselves whether to
     accept the security risks that the feature involve by manually enabling 
command-args in nrpe.cfg or not.

   * Canonical Security team feedbacks :
     
https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1555258/comments/9

     ...
     If this feature is enabled in an SRU, the upload must include the fix for 
CVE-2013-1362:
     ...

   * COMMAND ARGUMENTS
     NRPE 2.0 includes the ability for clients to supply arguments to commands 
which should be run. Please note that this feature should be considered a 
security risk, and you should only use it if you know what you're doing!
     
https://github.com/NagiosEnterprises/nrpe/blob/master/SECURITY.md#command-arguments

  Note that Artful and Zesty already has the commit mention

[Group.of.nepali.translators] [Bug 1686257] Re: gdm3 fails to start when default session-name=ubuntu

2017-05-15 Thread Launchpad Bug Tracker

This bug was fixed in the package gdm3 - 3.20.1-1ubuntu2.1

---
gdm3 (3.20.1-1ubuntu2.1) yakkety; urgency=medium

  * Add git_restore-session-name-override.patch:
- Explicitly set gdm's session-name to 'gnome'. This fixes the login
  screen not starting when the default session is set to something else,
  such as when a Ubuntu (Unity) user installs gnome-shell and chooses
  gdm but does not install ubuntu-gnome-desktop (LP: #1686257)

 -- Jeremy Bicha   Tue, 02 May 2017 09:05:59 -0400

** Changed in: gdm3 (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: gdm3 (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/1686257

Title:
  gdm3 fails to start when default session-name=ubuntu

Status in gdm:
  Fix Released
Status in Ubuntu GNOME:
  In Progress
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gdm3 source package in Xenial:
  Fix Released
Status in gdm3 source package in Yakkety:
  Fix Released
Status in gdm3 source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  If a person installs gnome-shell (and not ubuntu-gnome-desktop) on Ubuntu and 
choose gdm3, they will be unable to log in.

  Workaround: install ubuntu-gnome-default-settings

  This reverts a change that was made in gdm 3.16.

  Test Case
  -
  From Ubuntu (Unity), run
  sudo apt install gdm3

  Choose gdm3 when prompted.
  Restart.
  You should get a login screen. Your desktop session (Unity or whatever) 
should still be the same as whatever you last successfully logged in with.

  Regression Potential
  
  This patch was accepted upstream. It only affects the default session for the 
'gdm' system user.

  Other Info
  --
  ubuntu-settings contains this in 
/usr/share/glib-2.0/10_ubuntu-settings.gchema.override

  [org.gnome.desktop.session]
  session-name="ubuntu"

  gdm3 fails to start unless session-name="gnome"

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1686257/+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 1686257] Re: gdm3 fails to start when default session-name=ubuntu

2017-05-15 Thread Launchpad Bug Tracker

This bug was fixed in the package gdm3 - 3.24.1-0ubuntu0.1

---
gdm3 (3.24.1-0ubuntu0.1) zesty; urgency=medium

  * New upstream release (LP: #1685500)
  * Drop git_dont-cache-ignore-wayland.patch:
- Applied in new release
  * Add git_fix-crash-if-session-does-not-start.patch:
- Backport 3.24 commit to fix a crash bug
  * Add git_restore-session-name-override.patch:
- Explicitly set gdm's session-name to 'gnome'. This fixes the login
  screen not starting when the default session is set to something else,
  such as when a Ubuntu (Unity) user installs gnome-shell and chooses
  gdm but does not install ubuntu-gnome-desktop (LP: #1686257)

 -- Jeremy Bicha   Tue, 02 May 2017 09:04:14 -0400

** Changed in: gdm3 (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/1686257

Title:
  gdm3 fails to start when default session-name=ubuntu

Status in gdm:
  Fix Released
Status in Ubuntu GNOME:
  In Progress
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gdm3 source package in Xenial:
  Fix Released
Status in gdm3 source package in Yakkety:
  Fix Released
Status in gdm3 source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  If a person installs gnome-shell (and not ubuntu-gnome-desktop) on Ubuntu and 
choose gdm3, they will be unable to log in.

  Workaround: install ubuntu-gnome-default-settings

  This reverts a change that was made in gdm 3.16.

  Test Case
  -
  From Ubuntu (Unity), run
  sudo apt install gdm3

  Choose gdm3 when prompted.
  Restart.
  You should get a login screen. Your desktop session (Unity or whatever) 
should still be the same as whatever you last successfully logged in with.

  Regression Potential
  
  This patch was accepted upstream. It only affects the default session for the 
'gdm' system user.

  Other Info
  --
  ubuntu-settings contains this in 
/usr/share/glib-2.0/10_ubuntu-settings.gchema.override

  [org.gnome.desktop.session]
  session-name="ubuntu"

  gdm3 fails to start unless session-name="gnome"

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1686257/+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 1690846] Re: version in repository is outdated and has vulnerabilities

2017-05-15 Thread LocutusOfBorg

** Also affects: borgbackup (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  version in repository is outdated and has vulnerabilities

Status in borgbackup package in Ubuntu:
  Fix Released
Status in borgbackup source package in Xenial:
  New
Status in borgbackup source package in Yakkety:
  New
Status in borgbackup source package in Zesty:
  New

Bug description:
  The current version in 16.10 universe is 1.0.7 which has two known
  vulnerabilities (CVE-2016-10099 and CVE-2016-10100) fixed in upstream
  version 1.0.9 (released ~6 months ago). The current upstream version
  is 1.0.10 (released ~3 months ago) and contains various other
  bugfixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/borgbackup/+bug/1690846/+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 1689759] Re: CVE 2017-8422 - kauth: Local privilege escalation

2017-05-15 Thread Marc Deslauriers

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

Title:
  CVE 2017-8422 - kauth: Local privilege escalation

Status in kauth package in Ubuntu:
  Fix Released
Status in kde4libs package in Ubuntu:
  Fix Released
Status in kauth source package in Trusty:
  Invalid
Status in kde4libs source package in Trusty:
  Fix Released
Status in kauth source package in Xenial:
  In Progress
Status in kde4libs source package in Xenial:
  Fix Released
Status in kauth source package in Yakkety:
  Confirmed
Status in kde4libs source package in Yakkety:
  Fix Released
Status in kauth source package in Zesty:
  Fix Released
Status in kde4libs source package in Zesty:
  Fix Released
Status in kauth source package in Artful:
  Fix Released
Status in kde4libs source package in Artful:
  Fix Released

Bug description:
  KDE Project Security Advisory
  =

  Title:  kauth: Local privilege escalation
  Risk Rating:High
  CVE:CVE-2017-8422
  Versions:   kauth < 5.34, kdelibs < 4.14.32
  Date:   10 May 2017

  
  Overview
  
  KAuth contains a logic flaw in which the service invoking dbus
  is not properly checked.

  This allows spoofing the identity of the caller and with some
  carefully crafted calls can lead to gaining root from an
  unprivileged account.

  Solution
  
  Update to kauth >= 5.34 and kdelibs >= 4.14.32 (when released)

  Or apply the following patches:
kauth: 
https://commits.kde.org/kauth/df875f725293af53399f5146362eb158b4f9216a
  kdelibs: 
https://commits.kde.org/kdelibs/264e97625abe2e0334f97de17f6ffb52582888ab

  Credits
  ===
  Thanks to Sebastian Krahmer from SUSE for the report and
  to Albert Astals Cid from KDE for the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kauth/+bug/1689759/+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 1673569] Re: [OSSA-2017-002] Failed notification payload is dumped in logs with auth secrets (CVE-2017-7214)

2017-05-15 Thread Corey Bryant

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

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

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

Title:
  [OSSA-2017-002] Failed notification payload is dumped in logs with
  auth secrets (CVE-2017-7214)

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  New
Status in Ubuntu Cloud Archive newton series:
  New
Status in Ubuntu Cloud Archive ocata series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) mitaka series:
  Fix Released
Status in OpenStack Compute (nova) newton series:
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  Fix Released
Status in OpenStack Security Advisory:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  New
Status in nova source package in Yakkety:
  New
Status in nova source package in Zesty:
  Fix Released
Status in nova source package in Artful:
  Fix Released

Bug description:
  Noticed here:

  http://logs.openstack.org/08/445308/3/check/gate-tempest-dsvm-py35
  -ubuntu-
  xenial/7bf0d72/logs/screen-n-api.txt.gz#_2017-03-16_05_31_09_399

  I noticed this while investigating public nova bug 1673375, but it
  looks like that bug is caused by a ValueError coming from the
  oslo.messaging notification code, related to a circular reference in
  the json blob:

  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging Traceback 
(most recent call last):
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/notify/messaging.py", 
line 70, in notify
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
retry=retry)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/transport.py", line 104, 
in _send_notification
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
retry=retry)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/_drivers/amqpdriver.py", 
line 509, in send_notification
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
envelope=(version == 2.0), notify=True, retry=retry)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/_drivers/amqpdriver.py", 
line 457, in _send
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging msg = 
rpc_common.serialize_msg(msg)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/_drivers/common.py", 
line 293, in serialize_msg
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
_MESSAGE_KEY: jsonutils.dumps(raw_msg)}
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_serialization/jsonutils.py", line 
190, in dumps
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
return json.dumps(obj, default=default, **kwargs)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/lib/python3.5/json/__init__.py", line 237, in dumps
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
**kw).encode(obj)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/lib/python3.5/json/encoder.py", line 198, in encode
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
chunks = self.iterencode(o, _one_shot=True)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/lib/python3.5/json/encoder.py", line 256, in iterencode
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
return _iterencode(o, 0)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
ValueError: Circular reference detected
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging

  The security issue here is that the notification payload that's logged
  has all kinds of auth secrets in it, like tokens and passwords.

  From logstash it looks like this is only hitting master (pike) right
  now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1673569/+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/ListHe

[Group.of.nepali.translators] [Bug 1689759] Re: CVE 2017-8422 - kauth: Local privilege escalation

2017-05-15 Thread Launchpad Bug Tracker

This bug was fixed in the package kde4libs - 4:4.14.16-0ubuntu3.2

---
kde4libs (4:4.14.16-0ubuntu3.2) xenial-security; urgency=medium

  * SECURITY UPDATE: Local privilege escalation (LP: #1689759)
- debian/patches/kauth-local-privilege-esc-CVE-2017-8422.patch
- Thanks to Sebastian Krahmer for reporting this issue,
  Albert Astals Cid for fixing this issue.
- CVE-2017-8422

 -- Rik Mills   Sat, 13 May 2017 09:37:09 +0100

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

** Changed in: kde4libs (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/1689759

Title:
  CVE 2017-8422 - kauth: Local privilege escalation

Status in kauth package in Ubuntu:
  Fix Released
Status in kde4libs package in Ubuntu:
  Fix Released
Status in kauth source package in Trusty:
  Invalid
Status in kde4libs source package in Trusty:
  In Progress
Status in kauth source package in Xenial:
  In Progress
Status in kde4libs source package in Xenial:
  Fix Released
Status in kauth source package in Yakkety:
  Confirmed
Status in kde4libs source package in Yakkety:
  Fix Released
Status in kauth source package in Zesty:
  Fix Released
Status in kde4libs source package in Zesty:
  Fix Released
Status in kauth source package in Artful:
  Fix Released
Status in kde4libs source package in Artful:
  Fix Released

Bug description:
  KDE Project Security Advisory
  =

  Title:  kauth: Local privilege escalation
  Risk Rating:High
  CVE:CVE-2017-8422
  Versions:   kauth < 5.34, kdelibs < 4.14.32
  Date:   10 May 2017

  
  Overview
  
  KAuth contains a logic flaw in which the service invoking dbus
  is not properly checked.

  This allows spoofing the identity of the caller and with some
  carefully crafted calls can lead to gaining root from an
  unprivileged account.

  Solution
  
  Update to kauth >= 5.34 and kdelibs >= 4.14.32 (when released)

  Or apply the following patches:
kauth: 
https://commits.kde.org/kauth/df875f725293af53399f5146362eb158b4f9216a
  kdelibs: 
https://commits.kde.org/kdelibs/264e97625abe2e0334f97de17f6ffb52582888ab

  Credits
  ===
  Thanks to Sebastian Krahmer from SUSE for the report and
  to Albert Astals Cid from KDE for the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kauth/+bug/1689759/+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 1673569] Re: [OSSA-2017-002] Failed notification payload is dumped in logs with auth secrets (CVE-2017-7214)

2017-05-15 Thread Corey Bryant

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

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

Title:
  [OSSA-2017-002] Failed notification payload is dumped in logs with
  auth secrets (CVE-2017-7214)

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive mitaka series:
  New
Status in Ubuntu Cloud Archive newton series:
  New
Status in Ubuntu Cloud Archive ocata series:
  New
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) mitaka series:
  Fix Released
Status in OpenStack Compute (nova) newton series:
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  Fix Released
Status in OpenStack Security Advisory:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  New
Status in nova source package in Yakkety:
  New
Status in nova source package in Zesty:
  New
Status in nova source package in Artful:
  Fix Released

Bug description:
  Noticed here:

  http://logs.openstack.org/08/445308/3/check/gate-tempest-dsvm-py35
  -ubuntu-
  xenial/7bf0d72/logs/screen-n-api.txt.gz#_2017-03-16_05_31_09_399

  I noticed this while investigating public nova bug 1673375, but it
  looks like that bug is caused by a ValueError coming from the
  oslo.messaging notification code, related to a circular reference in
  the json blob:

  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging Traceback 
(most recent call last):
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/notify/messaging.py", 
line 70, in notify
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
retry=retry)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/transport.py", line 104, 
in _send_notification
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
retry=retry)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/_drivers/amqpdriver.py", 
line 509, in send_notification
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
envelope=(version == 2.0), notify=True, retry=retry)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/_drivers/amqpdriver.py", 
line 457, in _send
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging msg = 
rpc_common.serialize_msg(msg)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/_drivers/common.py", 
line 293, in serialize_msg
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
_MESSAGE_KEY: jsonutils.dumps(raw_msg)}
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_serialization/jsonutils.py", line 
190, in dumps
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
return json.dumps(obj, default=default, **kwargs)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/lib/python3.5/json/__init__.py", line 237, in dumps
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
**kw).encode(obj)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/lib/python3.5/json/encoder.py", line 198, in encode
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
chunks = self.iterencode(o, _one_shot=True)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/lib/python3.5/json/encoder.py", line 256, in iterencode
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
return _iterencode(o, 0)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
ValueError: Circular reference detected
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging

  The security issue here is that the notification payload that's logged
  has all kinds of auth secrets in it, like tokens and passwords.

  From logstash it looks like this is only hitting master (pike) right
  now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1673569/+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 1673569] Re: [OSSA-2017-002] Failed notification payload is dumped in logs with auth secrets (CVE-2017-7214)

2017-05-15 Thread Corey Bryant

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

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

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

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

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

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

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

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

** Also affects: nova (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  [OSSA-2017-002] Failed notification payload is dumped in logs with
  auth secrets (CVE-2017-7214)

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive mitaka series:
  New
Status in Ubuntu Cloud Archive newton series:
  New
Status in Ubuntu Cloud Archive ocata series:
  New
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) mitaka series:
  Fix Released
Status in OpenStack Compute (nova) newton series:
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  Fix Released
Status in OpenStack Security Advisory:
  Fix Released
Status in nova package in Ubuntu:
  New
Status in nova source package in Xenial:
  New
Status in nova source package in Yakkety:
  New
Status in nova source package in Zesty:
  New
Status in nova source package in Artful:
  New

Bug description:
  Noticed here:

  http://logs.openstack.org/08/445308/3/check/gate-tempest-dsvm-py35
  -ubuntu-
  xenial/7bf0d72/logs/screen-n-api.txt.gz#_2017-03-16_05_31_09_399

  I noticed this while investigating public nova bug 1673375, but it
  looks like that bug is caused by a ValueError coming from the
  oslo.messaging notification code, related to a circular reference in
  the json blob:

  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging Traceback 
(most recent call last):
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/notify/messaging.py", 
line 70, in notify
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
retry=retry)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/transport.py", line 104, 
in _send_notification
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
retry=retry)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/_drivers/amqpdriver.py", 
line 509, in send_notification
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
envelope=(version == 2.0), notify=True, retry=retry)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/_drivers/amqpdriver.py", 
line 457, in _send
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging msg = 
rpc_common.serialize_msg(msg)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_messaging/_drivers/common.py", 
line 293, in serialize_msg
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
_MESSAGE_KEY: jsonutils.dumps(raw_msg)}
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/local/lib/python3.5/dist-packages/oslo_serialization/jsonutils.py", line 
190, in dumps
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
return json.dumps(obj, default=default, **kwargs)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/lib/python3.5/json/__init__.py", line 237, in dumps
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
**kw).encode(obj)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/lib/python3.5/json/encoder.py", line 198, in encode
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
chunks = self.iterencode(o, _one_shot=True)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging   File 
"/usr/lib/python3.5/json/encoder.py", line 256, in iterencode
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
return _iterencode(o, 0)
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging 
ValueError: Circular reference detected
  2017-03-16 05:31:09.399 23355 ERROR oslo_messaging.notify.messaging

  The security issue here is that the notification payload that's logged
  ha

[Group.of.nepali.translators] [Bug 1631561] Re: [SRU] volume usage audit print excessive debug log for deleted resources

2017-05-15 Thread James Page

This bug was fixed in the package cinder - 2:8.1.1-0ubuntu3~cloud0
---

 cinder (2:8.1.1-0ubuntu3~cloud0) trusty-mitaka; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 cinder (2:8.1.1-0ubuntu3) xenial; urgency=medium
 .
   *  d/p/log-message-cleanup-for-volume-usage-audit.patch:
  Fixes broken tests introduced by 8.1.1-0ubuntu2 (LP: #1631561).
 .
 cinder (2:8.1.1-0ubuntu2) xenial; urgency=medium
 .
   * d/p/log-message-cleanup-for-volume-usage-audit.patch:
 Fixes LP: #1631561.


** Changed in: cloud-archive/mitaka
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] volume usage audit print excessive debug log for deleted
  resources

Status in Cinder:
  Fix Released
Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in Ubuntu Cloud Archive newton series:
  Fix Committed
Status in cinder package in Ubuntu:
  Fix Released
Status in cinder source package in Xenial:
  Fix Released
Status in cinder source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  * Current volume usage audit tool queries all
  volumes/snapshots/backups including those resources have been deleted,
  as a result, every single deleted resource would trigger a few
  debug/exception level messages, which is too much for a running
  production cluster at hour/day period.

  * notify_snapshot_usage() doesn't handles the case when
   when the source volume for the snapshot has been deleted.

  The following exception is raised:

  2017-02-17 20:20:10.067 1921 ERROR cinder 
[req-7e273ce0-1ae8-410e-a814-0f444364c028 - - - - -] Exists snapshot 
notification failed: Volume 2c84e585-9947-4ad9-bd93-2fc3a5cf9a08 could not be 
found.
  2017-02-17 20:20:10.067 1921 ERROR cinder Traceback (most recent call last):
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/cinder/cmd/volume_usage_audit.py", line 188, 
in main
  2017-02-17 20:20:10.067 1921 ERROR cinder extra_info)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/cinder/volume/utils.py", line 174, in 
notify_about_snapshot_usage
  2017-02-17 20:20:10.067 1921 ERROR cinder usage_info = 
_usage_from_snapshot(snapshot, **extra_usage_info)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/cinder/volume/utils.py", line 151, in 
_usage_from_snapshot
  2017-02-17 20:20:10.067 1921 ERROR cinder 'availability_zone': 
snapshot.volume['availability_zone'],
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 67, in 
getter
  2017-02-17 20:20:10.067 1921 ERROR cinder self.obj_load_attr(name)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/cinder/objects/snapshot.py", line 196, in 
obj_load_attr
  2017-02-17 20:20:10.067 1921 ERROR cinder self.volume_id)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 181, in 
wrapper
  2017-02-17 20:20:10.067 1921 ERROR cinder result = fn(cls, context, *args, 
**kwargs)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/cinder/objects/base.py", line 166, in 
get_by_id
  2017-02-17 20:20:10.067 1921 ERROR cinder orm_obj = db.get_by_id(context, 
model, id, *args, **kwargs)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/cinder/db/api.py", line 1127, in get_by_id
  2017-02-17 20:20:10.067 1921 ERROR cinder return IMPL.get_by_id(context, 
model, id, *args, **kwargs)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 193, in 
wrapper
  2017-02-17 20:20:10.067 1921 ERROR cinder return f(*args, **kwargs)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 4451, in 
get_by_id
  2017-02-17 20:20:10.067 1921 ERROR cinder return _GET_METHODS[model](context, 
id, *args, **kwargs)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 193, in 
wrapper
  2017-02-17 20:20:10.067 1921 ERROR cinder return f(*args, **kwargs)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 1480, in 
volume_get
  2017-02-17 20:20:10.067 1921 ERROR cinder return _volume_get(context, 
volume_id)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.py", line 193, in 
wrapper
  2017-02-17 20:20:10.067 1921 ERROR cinder return f(*args, **kwargs)
  2017-02-17 20:20:10.067 1921 ERROR cinder File 
"/usr/lib/python2.7/dist-p

[Group.of.nepali.translators] [Bug 1623700] Re: [SRU] multipath iscsi does not logout of sessions on xenial

2017-05-15 Thread James Page

This bug was fixed in the package python-os-brick - 1.6.1-0ubuntu1.2~cloud0
---

 python-os-brick (1.6.1-0ubuntu1.2~cloud0) xenial-newton; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 python-os-brick (1.6.1-0ubuntu1.2) yakkety; urgency=medium
 .
   * d/p/stop-calling-multipath-r-when-attaching-detaching-iS.patch
Backport fix for stopping calling 'multipath -r' (LP: #1623700)


** Changed in: cloud-archive/newton
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] multipath iscsi does not logout of sessions on xenial

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in os-brick:
  Fix Released
Status in python-os-brick package in Ubuntu:
  Fix Released
Status in python-os-brick source package in Xenial:
  Fix Released
Status in python-os-brick source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * multipath-tools has a bug that 'multipath -r' can cause
  /dev/mapper/ to be deleted and re-created momentarily (bug
  #1621340 is used to track this problem), thus os.stat(mdev) right
  after _rescan_multipath ('multipath -r') in os-brick can fail if it is
  executed before multipath dev being re-created. This will also lead to
  multipath iscsi does not logout of sessions on xenial.

  [Test Case]

   * Enable cinder multipath by adding iscsi_ip_address and 
iscsi_secondary_ip_addresses in cinder.conf
   * Enable nova multipath by adding iscsi_use_multipath=True in [libvirt] 
secion of nova.conf
   * Detach a iSCSI volume
   * Check that devices/symlinks do not get messed up mentioned below, or check 
that multipath device /dev/mapper/ doesn't be deleted and re-created 
momentarily

  [Regression Potential]

   * multipath-tools loads devices on its own, we shouldn't need to be
  forcing multipathd to do reload, so there is no regression potential.

  stack@xenial-devstack-master-master-20160914-092014:~$ sudo iscsiadm -m 
session
  tcp: [5] 10.0.1.10:3260,1 
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
  tcp: [6] 10.0.5.10:3260,1 
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
  tcp: [7] 10.0.1.11:3260,1 
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
  tcp: [8] 10.0.5.11:3260,1 
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)

  stack@xenial-devstack-master-master-20160914-092014:~$ sudo iscsiadm -m node
  10.0.1.11:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
  10.0.5.11:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
  10.0.5.10:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
  10.0.1.10:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873

  stack@xenial-devstack-master-master-20160914-092014:~$ sudo tail -f 
/var/log/syslog
  Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get udev uid: 
Invalid argument
  Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get sysfs uid: 
Invalid argument
  Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get sgio uid: 
No such file or directory
  Sep 14 22:33:14 xenial-qemu-tester systemd[1347]: 
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device: Dev 
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and 
/sys/devices/virtual/block/dm-0
  Sep 14 22:33:14 xenial-qemu-tester systemd[1347]: 
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device: Dev 
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and 
/sys/devices/virtual/block/dm-0
  Sep 14 22:33:14 xenial-qemu-tester systemd[1]: 
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device: Dev 
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and 
/sys/devices/virtual/block/dm-0
  Sep 14 22:33:14 xenial-qemu-tester systemd[1]: 
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device: Dev 
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and 
/sys/devices/virtual/block/dm-0
  Sep 14 22:33:14 xenial-qemu-tester kernel: [22362.163521] audit: type=1400 
audit(1473892394.556:21): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="libvirt-6e1017a7-6dea-418f-ad9b-879da08

[Group.of.nepali.translators] [Bug 1623700] Re: [SRU] multipath iscsi does not logout of sessions on xenial

2017-05-15 Thread James Page

This bug was fixed in the package python-os-brick - 1.2.0-2ubuntu0.3~cloud0
---

 python-os-brick (1.2.0-2ubuntu0.3~cloud0) trusty-mitaka; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 python-os-brick (1.2.0-2ubuntu0.3) xenial; urgency=medium
 .
   * d/p/Stop-calling-multipath-r-when-attaching-detaching-iS.patch: Backport
 Backport fix for stopping calling 'multipath -r' (LP: #1623700)


** Changed in: cloud-archive/mitaka
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] multipath iscsi does not logout of sessions on xenial

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in os-brick:
  Fix Released
Status in python-os-brick package in Ubuntu:
  Fix Released
Status in python-os-brick source package in Xenial:
  Fix Released
Status in python-os-brick source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * multipath-tools has a bug that 'multipath -r' can cause
  /dev/mapper/ to be deleted and re-created momentarily (bug
  #1621340 is used to track this problem), thus os.stat(mdev) right
  after _rescan_multipath ('multipath -r') in os-brick can fail if it is
  executed before multipath dev being re-created. This will also lead to
  multipath iscsi does not logout of sessions on xenial.

  [Test Case]

   * Enable cinder multipath by adding iscsi_ip_address and 
iscsi_secondary_ip_addresses in cinder.conf
   * Enable nova multipath by adding iscsi_use_multipath=True in [libvirt] 
secion of nova.conf
   * Detach a iSCSI volume
   * Check that devices/symlinks do not get messed up mentioned below, or check 
that multipath device /dev/mapper/ doesn't be deleted and re-created 
momentarily

  [Regression Potential]

   * multipath-tools loads devices on its own, we shouldn't need to be
  forcing multipathd to do reload, so there is no regression potential.

  stack@xenial-devstack-master-master-20160914-092014:~$ sudo iscsiadm -m 
session
  tcp: [5] 10.0.1.10:3260,1 
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
  tcp: [6] 10.0.5.10:3260,1 
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
  tcp: [7] 10.0.1.11:3260,1 
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)
  tcp: [8] 10.0.5.11:3260,1 
iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873 (non-flash)

  stack@xenial-devstack-master-master-20160914-092014:~$ sudo iscsiadm -m node
  10.0.1.11:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
  10.0.5.11:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
  10.0.5.10:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873
  10.0.1.10:3260,-1 iqn.2010-06.com.purestorage:flasharray.3adbe40b49bac873

  stack@xenial-devstack-master-master-20160914-092014:~$ sudo tail -f 
/var/log/syslog
  Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get udev uid: 
Invalid argument
  Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get sysfs uid: 
Invalid argument
  Sep 14 22:33:14 xenial-qemu-tester multipath: dm-0: failed to get sgio uid: 
No such file or directory
  Sep 14 22:33:14 xenial-qemu-tester systemd[1347]: 
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device: Dev 
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and 
/sys/devices/virtual/block/dm-0
  Sep 14 22:33:14 xenial-qemu-tester systemd[1347]: 
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device: Dev 
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and 
/sys/devices/virtual/block/dm-0
  Sep 14 22:33:14 xenial-qemu-tester systemd[1]: 
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device: Dev 
dev-disk-by\x2did-scsi\x2d3624a93709a738ed78583fd12003fb774.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and 
/sys/devices/virtual/block/dm-0
  Sep 14 22:33:14 xenial-qemu-tester systemd[1]: 
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device: Dev 
dev-disk-by\x2did-wwn\x2d0x624a93709a738ed78583fd12003fb774.device appeared 
twice with different sysfs paths 
/sys/devices/platform/host6/session5/target6:0:0/6:0:0:1/block/sda and 
/sys/devices/virtual/block/dm-0
  Sep 14 22:33:14 xenial-qemu-tester kernel: [22362.163521] audit: type=1400 
audit(1473892394.556:21): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="libvirt-6e1017a7-6dea-418f-ad

[Group.of.nepali.translators] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[Group.of.nepali.translators] [Bug 1672200] Re: Kernel error on i915 gpu driver

[Group.of.nepali.translators] [Bug 1672200] Re: Kernel error on i915 gpu driver

[Group.of.nepali.translators] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[Group.of.nepali.translators] [Bug 1689517] Re: Displayport daisy chained displays get recognized as the same

[Group.of.nepali.translators] [Bug 1623664] Re: [SRU] Fix Race between L3 agent and neutron-ns-cleanup

[Group.of.nepali.translators] [Bug 1623664] Re: [SRU] Fix Race between L3 agent and neutron-ns-cleanup

[Group.of.nepali.translators] [Bug 1648242] Re: [SRU] Failure to retry update_ha_routers_states

[Group.of.nepali.translators] [Bug 1623664] Re: [SRU] Fix Race between L3 agent and neutron-ns-cleanup

[Group.of.nepali.translators] [Bug 1623664] Re: [SRU] Fix Race between L3 agent and neutron-ns-cleanup

[Group.of.nepali.translators] [Bug 1686651] Re: linux-aws: 4.4.0-1017.26 -proposed tracker

[Group.of.nepali.translators] [Bug 1689946] Re: Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op

[Group.of.nepali.translators] [Bug 1689946] Re: Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op

[Group.of.nepali.translators] [Bug 1690846] Re: version in repository is outdated and has vulnerabilities

[Group.of.nepali.translators] [Bug 1555258] Re: Request contained command arguments

[Group.of.nepali.translators] [Bug 1686257] Re: gdm3 fails to start when default session-name=ubuntu

[Group.of.nepali.translators] [Bug 1686257] Re: gdm3 fails to start when default session-name=ubuntu

[Group.of.nepali.translators] [Bug 1690846] Re: version in repository is outdated and has vulnerabilities

[Group.of.nepali.translators] [Bug 1689759] Re: CVE 2017-8422 - kauth: Local privilege escalation

[Group.of.nepali.translators] [Bug 1673569] Re: [OSSA-2017-002] Failed notification payload is dumped in logs with auth secrets (CVE-2017-7214)

[Group.of.nepali.translators] [Bug 1689759] Re: CVE 2017-8422 - kauth: Local privilege escalation

[Group.of.nepali.translators] [Bug 1673569] Re: [OSSA-2017-002] Failed notification payload is dumped in logs with auth secrets (CVE-2017-7214)

[Group.of.nepali.translators] [Bug 1673569] Re: [OSSA-2017-002] Failed notification payload is dumped in logs with auth secrets (CVE-2017-7214)

[Group.of.nepali.translators] [Bug 1631561] Re: [SRU] volume usage audit print excessive debug log for deleted resources

[Group.of.nepali.translators] [Bug 1623700] Re: [SRU] multipath iscsi does not logout of sessions on xenial

[Group.of.nepali.translators] [Bug 1623700] Re: [SRU] multipath iscsi does not logout of sessions on xenial

26 matches

Site Navigation

Mail list logo

Footer information