[Group.of.nepali.translators] [Bug 1651199] Re: 16.04 - Kernel panic on docker server

[Fumihito YOSHIDA]

This bugs seems reported at upstream
https://github.com/docker/docker/issues/27875 , linked.

** Bug watch added: github.com/docker/docker/issues #27875
   https://github.com/docker/docker/issues/27875

** Also affects: linux via
   https://github.com/docker/docker/issues/27875
   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/1651199

Title:
  16.04 - Kernel panic on docker server

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

Bug description:
  [31016.057405] BUG: unable to handle kernel paging request at 82c4801e6bda
  [31016.061249] IP: [] __xen_evtchn_do_upcall+0x43/0x80
  [31016.061380] PGD 0 
  [31016.061380] Oops: 0010 [#1] SMP 
  [31016.061380] Modules linked in: binfmt_misc xt_REDIRECT nf_nat_redirect 
veth xt_comment xt_mark ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user 
xfrm_algo xt_addrtype iptable_filter xt_conntrack br_netfilter bridge stp llc 
overlay xt_nat xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables isofs ppdev serio_raw 
parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd ixgbevf psmouse floppy
  [31016.061380] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.4.0-53-generic 
#74-Ubuntu
  [31016.061380] Hardware name: Xen HVM domU, BIOS 4.2.amazon 11/11/2016
  [31016.061380] task: 880406496040 ti: 8804064e task.ti: 
8804064e
  [31016.061380] RIP: 0010:[]  [] 
__xen_evtchn_do_upcall+0x43/0x80
  [31016.061380] RSP: 0018:88040fc43f78  EFLAGS: 00010082
  [31016.061380] RAX:  RBX: 88040fc4b840 RCX: 
0001
  [31016.061380] RDX: fffe RSI: 000123a0 RDI: 
88040fc43f30
  [31016.061380] RBP: 88040fc43f90 R08: f24a R09: 
0001
  [31016.061380] R10: 0001 R11:  R12: 
0001
  [31016.061380] R13: 0003 R14:  R15: 
8804064e
  [31016.178419] FS:  () GS:88040fc4() 
knlGS:
  [31016.178419] CS:  0010 DS:  ES:  CR0: 80050033
  [31016.178419] CR2: 82c4801e6bda CR3: 000204f2f000 CR4: 
001406e0
  [31016.178419] DR0:  DR1:  DR2: 

  [31016.178419] DR3:  DR6: fffe0ff0 DR7: 
0400
  [31016.178419] Stack:
  [31016.178419]   0003  
88040fc43fa8
  [31016.178419]  814d6bc0 81f36a00 8804064e3e90 
81837f32
  [31016.178419]  8804064e3de8   8804064e  

  [31016.178419] Call Trace:
  [31016.178419]   
  [31016.178419]  [] xen_evtchn_do_upcall+0x30/0x40
  [31016.178419]  [] xen_hvm_callback_vector+0x82/0x90
  [31016.178419]   
  [31016.178419]  [] ? native_safe_halt+0x6/0x10
  [31016.178419]  [] default_idle+0x1e/0xe0
  [31016.239315]  [] arch_cpu_idle+0xf/0x20
  [31016.239899]  [] default_idle_call+0x2a/0x40
  [31016.239899]  [] cpu_startup_entry+0x2f1/0x350
  [31016.239899]  [] start_secondary+0x154/0x190
  [31016.239899] Code: 01 00 00 00 65 44 8b 2d dc 56 b3 7e c6 03 00 44 89 e0 65 
0f c1 05 2e d8 b3 7e 85 c0 75 35 48 8b 05 63 ce d0 00 44 89 ef ff 50 50 <9c> 58 
0f 1f 44 00 00 f6 c4 02 75 23 65 8b 05 0a d8 b3 7e 65 c7 
  [31016.239899] RIP  [] __xen_evtchn_do_upcall+0x43/0x80
  [31016.239899]  RSP 
  [31016.239899] CR2: 82c4801e6bda
  [31016.239899] ---[ end trace 5b3e8ea32013e327 ]---
  [31016.239899] Kernel panic - not syncing: Fatal exception in interrupt
  [31016.239899] Kernel Offset: disabled

  
  We believe this appeared in the last 1-2mo of releases, since this started 
happening after we did a `apt-get upgrade` on our machines after a bit of a 
pause. These are EC2 m4.xlarge servers running Ubuntu 16.04.1. They are 
Kubernetes minions, so I assume docker is likely the trigger.

  Unfortunately there aren't really any interesting logs in journalctl
  from the previous boot prior to the panic.

  Let me know what I can do to debug further.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 19 15:56 seq
   crw-rw 1 root audio 116, 33 Dec 19 15:56 timer
  AplayDevices: 

[Group.of.nepali.translators] [Bug 1648875] Re: linux-snapdragon: 4.4.0-1042.46 -proposed tracker

[Po-Hsu Lin]

** 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/1648875

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1648867
  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/1648875/+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 1648872] Re: linux-raspi2: 4.4.0-1038.45 -proposed tracker

[Po-Hsu Lin]

** 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/1648872

Title:
  linux-raspi2: 4.4.0-1038.45 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1648867
  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/1648872/+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 1648867] Re: linux: 4.4.0-57.78 -proposed tracker

[Po-Hsu Lin]

Regression test CMPL, some failures in aarch64 was caused by the proxy
setting, still waiting IS to help us on this.

The failure in kernel security test is expected for the CVE issue.

http://kernel.ubuntu.com/testing/tracker-index.html

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: 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/1648867/+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 1641562] Re: [SRU] Add 0cf3:e009 to btusb

[AceLan Kao]

Bt 4.0 keyboard can be paired with kernel 4.4.0-57

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

** Changed in: hwe-next
   Status: New => Fix Released

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

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

Title:
  [SRU] Add 0cf3:e009 to btusb

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

Bug description:
  Otherwise can't pair this bluetooth device with BLE devices, need to
  backport to Xenial and Yakkety.

  commit 935199348048902124d0b288788c3a45e78b69ab
  Author: Kai-Heng Feng 
  Date:   Tue Aug 16 12:50:06 2016 +0800

  Bluetooth: btusb: Add support for 0cf3:e009
  
  Device 0cf3:e009 is one of the QCA ROME family.
  
  T:  Bus=01 Lev=01 Prnt=01 Port=07 Cnt=04 Dev#=  4 Spd=12  MxCh= 0
  D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=0cf3 ProdID=e009 Rev=00.01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  
  Signed-off-by: Kai-Heng Feng 
  Signed-off-by: Marcel Holtmann 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1641562/+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 1548425] Re: update-manager crashed with AttributeError in check_hovering(): 'tuple' object has no attribute 'get_tags'

[Brian Murray]

The reason this wasn't fixed in Ubuntu 16.04 is because it doesn't
affect the proper Ubuntu archive, rather only users who have the gnome3
ppa enabled which provides a newer version of gtk.  That being said
given that there are tens of thousands of reports about this at the
Error Tracker let's get this fixed.

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

** Changed in: update-manager (Ubuntu Xenial)
   Importance: Undecided => Medium

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

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

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

Title:
  update-manager crashed with AttributeError in check_hovering():
  'tuple' object has no attribute 'get_tags'

Status in Ubuntu GNOME:
  Confirmed
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  In Progress
Status in update-manager source package in Yakkety:
  Fix Released

Bug description:
  Unexpectedly crash on close.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: update-manager 1:15.10.3
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Feb 22 14:36:11 2016
  ExecutablePath: /usr/bin/update-manager
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'733'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'817'
   b'com.ubuntu.update-manager' b'launch-time' b'1456162554'
  InstallationDate: Installed on 2015-11-10 (104 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151108)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/update-manager
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/update-manager']
  SourcePackage: update-manager
  Title: update-manager crashed with AttributeError in check_hovering(): 
'tuple' object has no attribute 'get_tags'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio bluetooth cdrom clamav dip firebird gdm lp lpadmin 
plugdev pulse sambashare src ssh sudo tty users utmp uucp uuidd vboxusers video 
www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1548425/+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 1651199] Re: 16.04 - Kernel panic on docker server

[Joseph Salisbury]

Also, is there a prior kernel version you've identified that does not
exhibit this bug?

** Tags added: kernel-da-key

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

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

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

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

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

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

Title:
  16.04 - Kernel panic on docker server

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

Bug description:
  [31016.057405] BUG: unable to handle kernel paging request at 82c4801e6bda
  [31016.061249] IP: [] __xen_evtchn_do_upcall+0x43/0x80
  [31016.061380] PGD 0 
  [31016.061380] Oops: 0010 [#1] SMP 
  [31016.061380] Modules linked in: binfmt_misc xt_REDIRECT nf_nat_redirect 
veth xt_comment xt_mark ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user 
xfrm_algo xt_addrtype iptable_filter xt_conntrack br_netfilter bridge stp llc 
overlay xt_nat xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables isofs ppdev serio_raw 
parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd ixgbevf psmouse floppy
  [31016.061380] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.4.0-53-generic 
#74-Ubuntu
  [31016.061380] Hardware name: Xen HVM domU, BIOS 4.2.amazon 11/11/2016
  [31016.061380] task: 880406496040 ti: 8804064e task.ti: 
8804064e
  [31016.061380] RIP: 0010:[]  [] 
__xen_evtchn_do_upcall+0x43/0x80
  [31016.061380] RSP: 0018:88040fc43f78  EFLAGS: 00010082
  [31016.061380] RAX:  RBX: 88040fc4b840 RCX: 
0001
  [31016.061380] RDX: fffe RSI: 000123a0 RDI: 
88040fc43f30
  [31016.061380] RBP: 88040fc43f90 R08: f24a R09: 
0001
  [31016.061380] R10: 0001 R11:  R12: 
0001
  [31016.061380] R13: 0003 R14:  R15: 
8804064e
  [31016.178419] FS:  () GS:88040fc4() 
knlGS:
  [31016.178419] CS:  0010 DS:  ES:  CR0: 80050033
  [31016.178419] CR2: 82c4801e6bda CR3: 000204f2f000 CR4: 
001406e0
  [31016.178419] DR0:  DR1:  DR2: 

  [31016.178419] DR3:  DR6: fffe0ff0 DR7: 
0400
  [31016.178419] Stack:
  [31016.178419]   0003  
88040fc43fa8
  [31016.178419]  814d6bc0 81f36a00 8804064e3e90 
81837f32
  [31016.178419]  8804064e3de8   8804064e  

  [31016.178419] Call Trace:
  [31016.178419]   
  [31016.178419]  [] xen_evtchn_do_upcall+0x30/0x40
  [31016.178419]  [] xen_hvm_callback_vector+0x82/0x90
  [31016.178419]   
  [31016.178419]  [] ? native_safe_halt+0x6/0x10
  [31016.178419]  [] default_idle+0x1e/0xe0
  [31016.239315]  [] arch_cpu_idle+0xf/0x20
  [31016.239899]  [] default_idle_call+0x2a/0x40
  [31016.239899]  [] cpu_startup_entry+0x2f1/0x350
  [31016.239899]  [] start_secondary+0x154/0x190
  [31016.239899] Code: 01 00 00 00 65 44 8b 2d dc 56 b3 7e c6 03 00 44 89 e0 65 
0f c1 05 2e d8 b3 7e 85 c0 75 35 48 8b 05 63 ce d0 00 44 89 ef ff 50 50 <9c> 58 
0f 1f 44 00 00 f6 c4 02 75 23 65 8b 05 0a d8 b3 7e 65 c7 
  [31016.239899] RIP  [] __xen_evtchn_do_upcall+0x43/0x80
  [31016.239899]  RSP 
  [31016.239899] CR2: 82c4801e6bda
  [31016.239899] ---[ end trace 5b3e8ea32013e327 ]---
  [31016.239899] Kernel panic - not syncing: Fatal exception in interrupt
  [31016.239899] Kernel Offset: disabled

  
  We believe this appeared in the last 1-2mo of releases, since this started 
happening after we did a `apt-get upgrade` on our machines after a bit of a 
pause. These are EC2 m4.xlarge servers running Ubuntu 16.04.1. They are 
Kubernetes minions, so I assume docker is likely the trigger.

  Unfortunately there aren't really any interesting logs in journalctl
  from the previous boot prior to the panic.

  Let me know what I can do to debug further.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  

[Group.of.nepali.translators] [Bug 1354694] Re: useradd crashes if group list contains whitespace on Fedora

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init -
0.7.8-68-gca3ae67-0ubuntu1

---
cloud-init (0.7.8-68-gca3ae67-0ubuntu1) zesty; urgency=medium

  * New upstream snapshot.
- user-groups: fix bug when groups was provided as string and had spaces
  (LP: #1354694)

 -- Scott Moser   Mon, 19 Dec 2016 12:35:13 -0500

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  useradd crashes if group list contains whitespace on Fedora

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  See downstream: https://bugzilla.redhat.com/show_bug.cgi?id=1126365

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1354694/+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 1645698] Re: [SRU] network-manager

[Jeremy Bicha]

Thank you Aron! I uploaded all 3 branches.

I pushed my changelog updates to https://git.launchpad.net/~jbicha
/network-manager

I'm unsubscribing ubuntu-sponsors now. If there is anything else that
needs sponsoring, feel free to resubscribe.

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

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: network-manager (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Yakkety)
   Importance: Undecided => High

** Tags added: yakkety

** Description changed:

  [Impact]
  
- This SRU would try to have the latest upstream point release of 1.2.x
- land in Xenial, which is the successor of the current 1.2.2 version,
- fixing quite some bugs that's suitable to land in the sable branch.
+ This SRU would try to have the latest well-tested upstream point release
+ (1.2.4) of 1.2.x land in Xenial, which is the successor of the current
+ 1.2.2 version, fixing quite some bugs that's suitable to land in the
+ stable branch.
  
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2
+ 
+ For xenial, we'll also backporting a patch from 1.2.6 that should fix a
+ no-networking-after-resuming-from-sleep issue. This patch was applied to
+ Debian testing and zesty in 1.4.2-3ubuntu1.
+ 
+ For yakkety, this is an update to 1.2.6. Once 1.2.6 has been in use for
+ a while without new problems, we'll look into doing a separate SRU for
+ Xenial.
  
  [Test Case]
  
  After installing the updated version, users should be able to avoid some
  mem leaks in some cases and have generally improved DNS related
  experiences.
  
  [Regression Potential]
  
  This version has been in yakkety for sometime, and there's no report of
  regressions until now.

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

Title:
  [SRU] network-manager

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  In Progress

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.4) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  For xenial, we'll also backporting a patch from 1.2.6 that should fix
  a no-networking-after-resuming-from-sleep issue. This patch was
  applied to Debian testing and zesty in 1.4.2-3ubuntu1.

  For yakkety, this is an update to 1.2.6. Once 1.2.6 has been in use
  for a while without new problems, we'll look into doing a separate SRU
  for Xenial.

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This version has been in yakkety for sometime, and there's no report
  of regressions until now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+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 1649361] Re: linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker

[Steve Beattie]

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1649358
  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/1649361/+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 1632786] Re: [Hyper-V] do not lose pending heartbeat vmbus packets

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.19.0-78.86

---
linux (3.19.0-78.86) vivid; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1647787

  * CVE-2016-7916
- proc: prevent accessing /proc//environ until it's ready

  * CVE-2016-6213
- mnt: Add a per mount namespace limit on the number of mounts

  * [Hyper-V] do not lose pending heartbeat vmbus packets (LP: #1632786)
- hv: do not lose pending heartbeat vmbus packets

  * ipv6: connected routes are missing after a down/up cycle on the loopback
(LP: #1634545)
- ipv6: correctly add local routes when lo goes up

 -- Luis Henriques   Tue, 06 Dec 2016
16:25:45 +

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

Title:
  [Hyper-V] do not lose pending heartbeat vmbus packets

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

Bug description:
  Hyper-V hosts can continue sending heartbeat packets to guests
  independent of whether earlier packets have responses, which led to a
  potential issue of these packets being dropped when responses took too
  long to process. Lost heartbeats will lead to the host diagnosing that
  the guest is dead and should be shut down and restarted.

  The following patch was submitted upstream but has not yet been
  accepted. I will add the upstream commit ID once the patch goes into
  linux-next:

  From: Long Li 

  The host keeps sending heartbeat packets independent of the
  guest responding to them.  Even though we respond to the heartbeat messages at
  interrupt level, we can have situations where there maybe multiple heartbeat
  messages pending that have not been responded to. For instance this occurs 
when the
  VM is paused and the host continues to send the heartbeat messages.
  Address this issue by draining and responding to all
  the heartbeat messages that maybe pending.

  Signed-off-by: Long Li 
  Signed-off-by: K. Y. Srinivasan 
  CC: Stable 
  ---
  V2: Submit the patch to stable as well - Joshua R. Poulson 


   drivers/hv/hv_util.c |   10 +++---
   1 files changed, 7 insertions(+), 3 deletions(-)

  diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
  index 4aa3cb6..bcd0630 100644
  --- a/drivers/hv/hv_util.c
  +++ b/drivers/hv/hv_util.c
  @@ -314,10 +314,14 @@ static void heartbeat_onchannelcallback(void *context)
  u8 *hbeat_txf_buf = util_heartbeat.recv_buffer;
  struct icmsg_negotiate *negop = NULL;

  -   vmbus_recvpacket(channel, hbeat_txf_buf,
  -PAGE_SIZE, , );
  +   while (1) {
  +
  +   vmbus_recvpacket(channel, hbeat_txf_buf,
  +PAGE_SIZE, , );
  +
  +   if (!recvlen)
  +   break;

  -   if (recvlen > 0) {
  icmsghdrp = (struct icmsg_hdr *)_txf_buf[
  sizeof(struct vmbuspipe_hdr)];

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632786/+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 1632786] Re: [Hyper-V] do not lose pending heartbeat vmbus packets

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-106.153

---
linux (3.13.0-106.153) trusty; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1647749

  * CVE-2016-7916
- proc: prevent accessing /proc//environ until it's ready

  * CVE-2016-6213
- mnt: Add a per mount namespace limit on the number of mounts

  * aio completions are dropped (LP: #1641129)
- aio: fix reqs_available handling

  * [Hyper-V] do not lose pending heartbeat vmbus packets (LP: #1632786)
- hv: do not lose pending heartbeat vmbus packets

  * ipv6: connected routes are missing after a down/up cycle on the loopback
(LP: #1634545)
- ipv6: reallocate addrconf router for ipv6 address when lo device up
- ipv6: correctly add local routes when lo goes up

  * audit: prevent a new auditd to stop an old auditd still alive (LP: #1633404)
- audit: stop an old auditd being starved out by a new auditd

  * Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later
causes 'invalid argument' error (LP: #1634892)
- neigh: fix setting of default gc_* values

  * move nvme driver to linux-image (LP: #1640275)
- [Config] Add nvme to the generic inclusion list

 -- Luis Henriques   Tue, 06 Dec 2016
15:00:27 +

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

Title:
  [Hyper-V] do not lose pending heartbeat vmbus packets

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

Bug description:
  Hyper-V hosts can continue sending heartbeat packets to guests
  independent of whether earlier packets have responses, which led to a
  potential issue of these packets being dropped when responses took too
  long to process. Lost heartbeats will lead to the host diagnosing that
  the guest is dead and should be shut down and restarted.

  The following patch was submitted upstream but has not yet been
  accepted. I will add the upstream commit ID once the patch goes into
  linux-next:

  From: Long Li 

  The host keeps sending heartbeat packets independent of the
  guest responding to them.  Even though we respond to the heartbeat messages at
  interrupt level, we can have situations where there maybe multiple heartbeat
  messages pending that have not been responded to. For instance this occurs 
when the
  VM is paused and the host continues to send the heartbeat messages.
  Address this issue by draining and responding to all
  the heartbeat messages that maybe pending.

  Signed-off-by: Long Li 
  Signed-off-by: K. Y. Srinivasan 
  CC: Stable 
  ---
  V2: Submit the patch to stable as well - Joshua R. Poulson 


   drivers/hv/hv_util.c |   10 +++---
   1 files changed, 7 insertions(+), 3 deletions(-)

  diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
  index 4aa3cb6..bcd0630 100644
  --- a/drivers/hv/hv_util.c
  +++ b/drivers/hv/hv_util.c
  @@ -314,10 +314,14 @@ static void heartbeat_onchannelcallback(void *context)
  u8 *hbeat_txf_buf = util_heartbeat.recv_buffer;
  struct icmsg_negotiate *negop = NULL;

  -   vmbus_recvpacket(channel, hbeat_txf_buf,
  -PAGE_SIZE, , );
  +   while (1) {
  +
  +   vmbus_recvpacket(channel, hbeat_txf_buf,
  +PAGE_SIZE, , );
  +
  +   if (!recvlen)
  +   break;

  -   if (recvlen > 0) {
  icmsghdrp = (struct icmsg_hdr *)_txf_buf[
  sizeof(struct vmbuspipe_hdr)];

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632786/+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 1634545] Re: ipv6: connected routes are missing after a down/up cycle on the loopback

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-106.153

---
linux (3.13.0-106.153) trusty; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1647749

  * CVE-2016-7916
- proc: prevent accessing /proc//environ until it's ready

  * CVE-2016-6213
- mnt: Add a per mount namespace limit on the number of mounts

  * aio completions are dropped (LP: #1641129)
- aio: fix reqs_available handling

  * [Hyper-V] do not lose pending heartbeat vmbus packets (LP: #1632786)
- hv: do not lose pending heartbeat vmbus packets

  * ipv6: connected routes are missing after a down/up cycle on the loopback
(LP: #1634545)
- ipv6: reallocate addrconf router for ipv6 address when lo device up
- ipv6: correctly add local routes when lo goes up

  * audit: prevent a new auditd to stop an old auditd still alive (LP: #1633404)
- audit: stop an old auditd being starved out by a new auditd

  * Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later
causes 'invalid argument' error (LP: #1634892)
- neigh: fix setting of default gc_* values

  * move nvme driver to linux-image (LP: #1640275)
- [Config] Add nvme to the generic inclusion list

 -- Luis Henriques   Tue, 06 Dec 2016
15:00:27 +

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-6213

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-7916

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

Title:
  ipv6: connected routes are missing after a down/up cycle on the
  loopback

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

Bug description:
  This upstream patch is missing:
  
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=a220445f9f4382c36a53d8ef3e08165fa27f7e2c

  ipv6: correctly add local routes when lo goes up

  The goal of the patch is to fix this scenario:
   ip link add dummy1 type dummy
   ip link set dummy1 up
   ip link set lo down ; ip link set lo up

  After that sequence, the local route to the link layer address of dummy1 is
  not there anymore.

  When the loopback is set down, all local routes are deleted by
  addrconf_ifdown()/rt6_ifdown(). At this time, the rt6_info entry still
  exists, because the corresponding idev has a reference on it. After the rcu
  grace period, dst_rcu_free() is called, and thus ___dst_free(), which will
  set obsolete to DST_OBSOLETE_DEAD.

  In this case, init_loopback() is called before dst_rcu_free(), thus
  obsolete is still sets to something <= 0. So, the function doesn't add the
  route again. To avoid that race, let's check the rt6 refcnt instead.

  Fixes: 25fb6ca4ed9c ("net IPv6 : Fix broken IPv6 routing table after loopback 
down-up")
  Fixes: a881ae1f625c ("ipv6: don't call addrconf_dst_alloc again when enable 
lo")
  Fixes: 33d99113b110 ("ipv6: reallocate addrconf router for ipv6 address when 
lo device up")
  Reported-by: Francesco Santoro 
  Reported-by: Samuel Gauthier 
  CC: Balakumaran Kannan 
  CC: Maruthi Thotad 
  CC: Sabrina Dubroca 
  CC: Hannes Frederic Sowa 
  CC: Weilong Chen 
  CC: Gao feng 
  Signed-off-by: Nicolas Dichtel 
  Signed-off-by: David S. Miller 

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

[Steve Beattie]

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

Title:
  linux: 4.4.0-57.78 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: 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/1648867/+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 1648872] Re: linux-raspi2: 4.4.0-1038.45 -proposed tracker

[Steve Beattie]

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

Title:
  linux-raspi2: 4.4.0-1038.45 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1648867
  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/1648872/+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 1648875] Re: linux-snapdragon: 4.4.0-1042.46 -proposed tracker

[Steve Beattie]

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1648867
  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/1648875/+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 1632786] Re: [Hyper-V] do not lose pending heartbeat vmbus packets

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.2.0-119.162

---
linux (3.2.0-119.162) precise; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1647713

  * CVE-2016-7916
- proc: prevent accessing /proc//environ until it's ready

  * [Hyper-V] do not lose pending heartbeat vmbus packets (LP: #1632786)
- hv: do not lose pending heartbeat vmbus packets

 -- Luis Henriques   Tue, 06 Dec 2016
13:30:22 +

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-7916

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

Title:
  [Hyper-V] do not lose pending heartbeat vmbus packets

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

Bug description:
  Hyper-V hosts can continue sending heartbeat packets to guests
  independent of whether earlier packets have responses, which led to a
  potential issue of these packets being dropped when responses took too
  long to process. Lost heartbeats will lead to the host diagnosing that
  the guest is dead and should be shut down and restarted.

  The following patch was submitted upstream but has not yet been
  accepted. I will add the upstream commit ID once the patch goes into
  linux-next:

  From: Long Li 

  The host keeps sending heartbeat packets independent of the
  guest responding to them.  Even though we respond to the heartbeat messages at
  interrupt level, we can have situations where there maybe multiple heartbeat
  messages pending that have not been responded to. For instance this occurs 
when the
  VM is paused and the host continues to send the heartbeat messages.
  Address this issue by draining and responding to all
  the heartbeat messages that maybe pending.

  Signed-off-by: Long Li 
  Signed-off-by: K. Y. Srinivasan 
  CC: Stable 
  ---
  V2: Submit the patch to stable as well - Joshua R. Poulson 


   drivers/hv/hv_util.c |   10 +++---
   1 files changed, 7 insertions(+), 3 deletions(-)

  diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
  index 4aa3cb6..bcd0630 100644
  --- a/drivers/hv/hv_util.c
  +++ b/drivers/hv/hv_util.c
  @@ -314,10 +314,14 @@ static void heartbeat_onchannelcallback(void *context)
  u8 *hbeat_txf_buf = util_heartbeat.recv_buffer;
  struct icmsg_negotiate *negop = NULL;

  -   vmbus_recvpacket(channel, hbeat_txf_buf,
  -PAGE_SIZE, , );
  +   while (1) {
  +
  +   vmbus_recvpacket(channel, hbeat_txf_buf,
  +PAGE_SIZE, , );
  +
  +   if (!recvlen)
  +   break;

  -   if (recvlen > 0) {
  icmsghdrp = (struct icmsg_hdr *)_txf_buf[
  sizeof(struct vmbuspipe_hdr)];

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632786/+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 1647400] Re: system freeze when swapping to encrypted swap partition

[Luis Henriques]

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

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

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

Title:
  system freeze when swapping to encrypted swap partition

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == Comment: #0 - Bernd-Rainer Bresser  - 2016-12-05 
04:27:00 ==
  +++ This bug was initially created as a clone of Bug #147836 +++

  ---Problem Description---
  When the system is installed with encrypted swap partition the attempt to 
swap ends in a system freeze. No error, no dump, the system needs to be 
reloaded.
   
  Contact Information = Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM 
   
  ---uname output---
  Linux s38lp65 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = z13 LPAR 
   
  ---System Hang---
   System is frozen. No error, no dump, the system needs to be reloaded.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. install a system with encrypted swap partition. This can be done using 
the installer or via manual updates to /etc/fstab and /etc/crypttab.

  2. Verify encrypted swap partition exists
   cryptsetup status kvmibm-swap
  /dev/mapper/kvmibm-swap is active and is in use.
type:PLAIN
cipher:  aes-xts-plain64:sha256
keysize: 256 bits
device:  /dev/dasda2
offset:  0 sectors
size:8388672 sectors
mode:read/write

  3. force swapping
  this can be done by a command like this (if the system has 8GB memory)
  dd if=/dev/zero of=/dev/null ibs=16k obs=8G count=2MB
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Location:
   
   
  *Additional Instructions for Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Bernd-Rainer Bresser  - 2016-12-05 
04:33:24 ==
  - the problem was originally found on KVM for IBM z 1.1.3
  - test on Ubuntu 16.04.1 showed the same issue here
  - on KVM for IBM z 1.1.3 the problem could be solved/circumvented by reverting
 commit 564e81a57f9788b1475127012e0fd44e9049e342
Author: Tetsuo Handa 
Date:   Fri Feb 5 15:36:30 2016 -0800
  mm, vmstat: fix wrong WQ sleep when memory reclaim doesn't make 
any progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1647400/+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 1584485] Re: Upgrading samba to latest security fixes together with winbind in nsswitch.conf can harm entire OS

[Launchpad Bug Tracker]

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

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

  * SECURITY UPDATE: remote code execution via heap overflow in NDR parsing
- debian/patches/CVE-2016-2123.patch: check lengths in
  librpc/ndr/ndr_dnsp.c.
- CVE-2016-2123
  * SECURITY UPDATE: unconditional privilege delegation to Kerberos servers
- debian/patches/CVE-2016-2125.patch: don't use GSS_C_DELEG_FLAG in
  source4/scripting/bin/nsupdate-gss, source3/librpc/crypto/gse.c,
  source4/auth/gensec/gensec_gssapi.c.
- CVE-2016-2125
  * SECURITY UPDATE: privilege elevation in Kerberos PAC validation
- debian/patches/CVE-2016-2126.patch: only allow known checksum types
  in auth/kerberos/kerberos_pac.c.
- CVE-2016-2126

 -- Marc Deslauriers   Mon, 12 Dec 2016
08:40:01 -0500

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2123

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2125

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-2126

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

Title:
  Upgrading samba to latest security fixes together with winbind in
  nsswitch.conf can harm entire OS

Status in samba package in Ubuntu:
  Fix Released
Status in samba source package in Trusty:
  Fix Released
Status in samba source package in Xenial:
  Fix Committed
Status in samba source package in Yakkety:
  Fix Committed
Status in samba package in Debian:
  New

Bug description:
  [Impact]

  * Upgrading samba when using winbind as NSS service can break OS.
  * Probably not triggered if "compat" is BEFORE "winbind" in nsswitch.conf.
  * Huge impact due to big version different between winbind and libraries.

  [Test Case 1]

  Verify that the regression reported in bug 1644428 has not recurred.

  [Test Case 2]

  1) Start an ubuntu Trusty container
  2) cp /etc/apt/sources.list /etc/apt/sources.list.back
  3) Disable the trusty-updates and trusty-security archives in 
/etc/apt/sources.list
  4) sudo apt-get update
  5) sudo apt-get install samba winbind libnss-winbind libpam-winbind
  6) Set /etc/nsswitch.conf to : passwd: winbind compat
  7) Restart the services
     7.1) sudo restart smbd
     7.2) sudo restart nmbd
     7.3) sudo restart winbind
  8) cp /etc/apt/sources.list.back /etc/apt/sources.list
  9) sudo apt-get update
  7) sudo apt-get install samba winbind libnss-winbind libpam-winbind

  While installing, you will see things similar to this :

  > Unpacking libnss-winbind:amd64 (2:4.3.11+dfsg-0ubuntu0.14.04.1) over 
(2:4.1.6+dfsg-1ubuntu2) ...
  > dpkg-deb: error: subprocess tar was killed by signal (Segmentation fault), 
core dumped
  > dpkg: error processing archive 
/var/cache/apt/archives/libpam-winbind_2%3a4.3.11+dfsg-0ubuntu0.14.04.1_amd64.deb
 (-
  > -unpack):
  >  subprocess dpkg-deb --control returned error exit status 2
  > dpkg-deb: error: subprocess tar was killed by signal (Segmentation fault), 
core dumped

  [Regression Potential]

  * "preinst" and "postrm" maintainer scripts are acting only in "upgrade"
  * uninstalling packages and reinstalling would bypass this change

  [Other Info]

  * Original Bug Description:

  It was brought to my attention that, because of latest security fixes
  for samba:

  https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1577739

  samba (2:4.3.9+dfsg-0ubuntu0.14.04.1) trusty-security; urgency=medium
  samba (2:4.3.8+dfsg-0ubuntu0.14.04.2) trusty-security; urgency=medium
  samba (2:4.1.6+dfsg-1ubuntu2.14.04.13) trusty-security; urgency=medium

  when library symbols changed, a samba upgrade MAY jeopardize an entire
  Ubuntu OS installation IF /etc/nsswitch.conf uses winbind as a service
  (specially if used before compat mechanism).

  

  How to reproduce easily:

  $ cat /etc/nsswitch.conf
  passwd: winbind compat
  shadow: compat
  group: winbind compat

  (winbind is usually used after compat, in this case it was used
  before)

  to have samba version "4.1.6+dfsg-1ubuntu2.14.04.13" installed and do
  a:

  $ sudo apt-get update

  and FINALLY:

  https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/comments/1

  Leading into an unusable system in the following state:

  https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/comments/2

  ## state

  Workaround:

  DO REMOVE winbind from /etc/nsswitch.conf (and possibly from pam.d
  with "pam-auth-update") before ANY attempt of upgrading samba to
  latest version.

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

___
Mailing list: 

[Group.of.nepali.translators] [Bug 1644557] Re: crypto : tolerate new crypto hardware for z Systems

[Tim Gardner]

commit b3e8652bcbfa04807e44708d4d0c8cdad39c9215 ('s390/zcrypt: Introduce
CEX6 toleration') will be released in v4.10-rc1

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: Canonical Kernel (canonical-kernel) => (unassigned)

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

Title:
  crypto : tolerate new crypto hardware for z Systems

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  crypto : tolerate new crypto hardware for z Systems

  cherrypick patches from v4.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1644557/+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 1460715] Re: MBR disk setup fails because sfdisk no longer accepts M as a valid unit

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.2

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.2) xenial-proposed; urgency=medium

  * cherry-pick 18203bf: disk_setup: Use sectors as unit when formatting
MBR disks with sfdisk. (LP: #1460715)
  * cherry-pick 6e92c5f: net/cmdline: Consider ip= or ip6= on command
line not only ip= (LP: #1639930)
  * cherry-pick 8c6878a: tests: fix assumptions that expected no eth0 in
system. (LP: #1644043)
  * cherry-pick 2d2ec70: OpenStack: extend physical types to include
hyperv, hw_veb, vhost_user. (LP: #1642679)

 -- Scott Moser   Thu, 01 Dec 2016 16:57:39 -0500

** Changed in: cloud-init (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/1460715

Title:
  MBR disk setup fails because sfdisk no longer accepts M as a valid
  unit

Status in cloud-init:
  Fix Committed
Status in Ubuntu Image:
  Invalid
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  In Progress

Bug description:
  === Begin SRU Template ===
  [Impact]
  Cloud-init has function to partition disks on devices.
  Creating partitions on a disk no longer works with sfdisk as recent versions 
of
  sfdisk no accept the unit 'M' as input, this function is broken.

  [Test Case]
  1. Launch an instance with provided user-data

     On Azure, this will work:
   #cloud-config
   disk_setup:
     ephemeral0:
     table_type: mbr
     layout: [66, [33, 82]]
     overwrite: True
   fs_setup:
     - device: ephemeral0.1
   filesystem: ext4
     - device: ephemeral0.2
   filesystem: swap
   mounts:
     - ["ephemeral0.1", "/mnt2"]
     - ["ephemeral0.2", "none", "swap", "sw", "0", "0"]

     On a typical kvm openstack use:
   #cloud-config
   disk_setup:
     /dev/vdb:
     table_type: mbr
     layout: [66, [33, 82]]
     overwrite: True
   fs_setup:
     - device: /dev/vdb1
   filesystem: ext4
     - device: /dev/vdb2
   filesystem: swap
   mounts:
     - ["/dev/vdb1", "/mnt2"]
     - ["/dev/vdb2", "none", "swap", "sw", "0", "0"]

  2. Add proposed, update, and reboot as fresh instance.

     # enable proposed
     echo deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc)-proposed main 
| sudo tee /etc/apt/sources.list.d/proposed.list
     sudo apt-get -qy update && sudo apt-get -qy install cloud-init https://bugs.launchpad.net/cloud-init/+bug/1460715/+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 1485752] Re: drop oneiric /run compatibility link

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.27ubuntu1.3

---
cloud-initramfs-tools (0.27ubuntu1.3) xenial; urgency=medium

  * sync with upstream at 0.32ubuntu1 (revno 129)
* overlayroot: fix overlayroot=crypt with newer initramfs-tools
  (LP: #1634310)
* overlayroot: support random seed from systemd systemd-random-seed.service
* cloud-initramfs-dyn-netconf: Further adjustments to support
  IPV6 and the new DEVICE6 and net6-DEVICE.conf files.  (LP: #1621615)
* overlayroot: support 'overlay' filesystem explicitly rather than
  relying on ubuntu specific kernel module 'overlayfs'.  (LP: #1493188)
* overlayroot: write debug to /run/initramfs not /dev/.initramfs but
  support writing to /dev/.initramfs if that is all there is. (LP: #1485752)
* overlayroot: fix overlayroot if recurse=0 was not provided.
  This fuctionality was lost since workdir support was added. (LP: #1619459)
* whitespace cleanup.

 -- Scott Moser   Mon, 28 Nov 2016 20:12:51 -0500

** Changed in: cloud-initramfs-tools (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/1485752

Title:
  drop oneiric /run compatibility link

Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  overlayfs writes some log information to the tmpfs that was intended
  to be then viewable after the pivot_root to the real root.
  The path used was /dev/.initramfs.  Due to changes in initramfs-tools
  under this bug, that path was no longer supported.  And the logging
  was busted.

  There was no functional problem with this except in the crypt use
  case as described in bug 1634310.

  [Test Case]
  1.) Start an instance of a cloud image.

  2.) Enable proposed and install overlayroot to show fix.
  $ rel=$(lsb_release -sc)
  $ echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
  $ sudo tee /etc/apt/sources.list.d/proposed.list
  $ sudo apt update -qy && sudo apt install -qy overlayroot http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/overlayroot/scripts/init-bottom/overlayroot
  [2] 
http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/revision/112

  === End SRU Template ===

  Drop: Maintain compatibility with pre- /run configurations -- this was
  for compatibility with oneiric which is now long gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1485752/+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 1493188] Re: "overlayfs" no longer exists

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.27ubuntu1.3

---
cloud-initramfs-tools (0.27ubuntu1.3) xenial; urgency=medium

  * sync with upstream at 0.32ubuntu1 (revno 129)
* overlayroot: fix overlayroot=crypt with newer initramfs-tools
  (LP: #1634310)
* overlayroot: support random seed from systemd systemd-random-seed.service
* cloud-initramfs-dyn-netconf: Further adjustments to support
  IPV6 and the new DEVICE6 and net6-DEVICE.conf files.  (LP: #1621615)
* overlayroot: support 'overlay' filesystem explicitly rather than
  relying on ubuntu specific kernel module 'overlayfs'.  (LP: #1493188)
* overlayroot: write debug to /run/initramfs not /dev/.initramfs but
  support writing to /dev/.initramfs if that is all there is. (LP: #1485752)
* overlayroot: fix overlayroot if recurse=0 was not provided.
  This fuctionality was lost since workdir support was added. (LP: #1619459)
* whitespace cleanup.

 -- Scott Moser   Mon, 28 Nov 2016 20:12:51 -0500

** Changed in: cloud-initramfs-tools (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/1493188

Title:
  "overlayfs" no longer exists

Status in cloud-initramfs-tools:
  Fix Released
Status in cloud-utils:
  Fix Committed
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-utils package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released
Status in cloud-utils source package in Xenial:
  Confirmed
Status in cloud-initramfs-tools source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  The 16.10 kernel dropped a legacy kernel module alias that allowed usage of
  the 'overlay' filesystem via name 'overlayfs'.  This broke overlayroot as
  it explicitly tried to to use 'overlayfs' by name in loading of modules and
  also in entry in /etc/fstab.

  Without this fix, overlayroot will simply not work on any upstream kernel
  or Ubuntu kernel of 16.10 (yakkety) or later.

  [Test Case]
  Note, not applying proposed as shown in step 3 below will recreate failure.

  1.) Start an instance of a cloud image.

  2.) get a suitable 4.8 kernel
  On 16.10 or later, this is already done.  On 16.04, we currently need to
  install the kernel team's PPA to get one.

  $ sudo apt-add-repository -y ppa:canonical-kernel-team/ppa
  $ sudo apt update -q && sudo apt install -y linux-virtual-hwe-16.04-edge 
http://archive.ubuntu.com/ubuntu $rel-proposed main" |
  $ sudo tee /etc/apt/sources.list.d/proposed.list
  $ sudo apt update -qy && sudo apt install -qy overlayroot http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/overlayroot/scripts/init-bottom/overlayroot
  [2] 
http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/revision/115

  === End SRU Template ===

  As mentioned in LP: #1411294, it's now called 'overlay' instead of 
'overlayfs'.
  Ubuntu had patched the kernel for compatibility.

  The Ubuntu kernels as of 4.8 (16.10 kernel) and possibly a bit before
  no longer have a overlayfs module either.  Thus, this is now affecting
  yakkety.

  (The original reporter is @~gpo-9.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1493188/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Launchpad Bug Tracker]

This bug was fixed in the package open-iscsi -
2.0.873+git0.3b4b4500-14ubuntu3.3

---
open-iscsi (2.0.873+git0.3b4b4500-14ubuntu3.3) xenial; urgency=medium

  * Fix syntax error in previous changes. LP: #1621507

 -- LaMont Jones   Fri, 09 Dec 2016 11:44:56 +0100

** Changed in: open-iscsi (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: isc-dhcp (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/1621507

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU

  ifupdown:
  bug 1629972: networking.service takes down lo on stop

  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)

  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD

  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  [Stable Fix]

  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.

  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

  [Tests for verification]

  Whoever checks the last one off, please mark verification done.

  MAAS test cases:
   X / Y
  [+]/[+] MAAS on IPv6-only network
  [+]/[+] MAAS on IPv4-only network
  [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)

  Non-MAAS test cases:
   X / Y
  [+]/[+] ip="" and ip6 not present
  [+]/[+] ip=:eth0:dhcp and ip6 not present
  [+]/[+] d-i install with iSCSI remote root should complete normally
  [+]/[+] Validate normal boot without remote root
  [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=)
  [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=)
  [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of 
booting device)52-54-00-53-5d-24
  [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be 

[Group.of.nepali.translators] [Bug 1619459] Re: workdir only used for root mount not recursed

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.27ubuntu1.3

---
cloud-initramfs-tools (0.27ubuntu1.3) xenial; urgency=medium

  * sync with upstream at 0.32ubuntu1 (revno 129)
* overlayroot: fix overlayroot=crypt with newer initramfs-tools
  (LP: #1634310)
* overlayroot: support random seed from systemd systemd-random-seed.service
* cloud-initramfs-dyn-netconf: Further adjustments to support
  IPV6 and the new DEVICE6 and net6-DEVICE.conf files.  (LP: #1621615)
* overlayroot: support 'overlay' filesystem explicitly rather than
  relying on ubuntu specific kernel module 'overlayfs'.  (LP: #1493188)
* overlayroot: write debug to /run/initramfs not /dev/.initramfs but
  support writing to /dev/.initramfs if that is all there is. (LP: #1485752)
* overlayroot: fix overlayroot if recurse=0 was not provided.
  This fuctionality was lost since workdir support was added. (LP: #1619459)
* whitespace cleanup.

 -- Scott Moser   Mon, 28 Nov 2016 20:12:51 -0500

** Changed in: cloud-initramfs-tools (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/1619459

Title:
  workdir only used for root mount not recursed

Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  The impact on xenial would only be seen if there were multiple filesystems
  mounted.  In the 16.04 cloud image that is used on openstack or many other
  clouds, there is only one partition.  But in the 16.10  image there is
  a separate uefi partition that caused havoc to overlayroot as the 'workdir'
  option was not correctly supported.

  [Test Case]
  The following should work, but currently does not.
  Note, to test the fix, between step 1 and 2, you'll need to enable
  proposed and install overlayroot.

  1. Start an instance of a cloud image with 2 disks.
     On openstack by default you get 2 disks (an ephemeral and a root).
     Cloud-init will configure the ephemeral to be a /mnt.

  2. remove cloud-init's configuration of /etc/fstab options
  These can cause issue with the way overlayroot does its mounts.
  So just remove the special options that cloud-init writes.

  $ sed -i.dist s/,x-systemd.requires=cloud-
  init.service,comment=cloudconfig// /etc/fstab

  if you do not do that, then /mnt will not get mounted, and journalctl
  will show a ordering cycle on the mount.  The following will show failed.
     systemctl status 'media-root\x2dro-mnt.mount'

  Note, this is a separate bug, mentioned here only for
  completeness.

  3. Enable proposed and install overlayroot to show fix.
  $ rel=$(lsb_release -sc)
  $ echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
  $ sudo tee /etc/apt/sources.list.d/proposed.list
  $ sudo apt update -qy && sudo apt install -qy overlayroot  /etc/overlayroot.local.conf &&
  reboot'

  you'll see it hang. the reason i believe is the info written to
  /etc/fstab for the non-root mounts does not include workdir
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1619459/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Launchpad Bug Tracker]

This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu12.6

---
isc-dhcp (4.3.3-5ubuntu12.6) xenial; urgency=medium

  * debian/initramfs/lib/etc/dhcp/dhclient-enter-hooks.d/config: clean up
script to remove IPv4 bits that would never be called; since for this SRU
we only do IPv6. (LP: #1621507)

isc-dhcp (4.3.3-5ubuntu12.5) xenial; urgency=medium

  * debian/initramfs/lib/etc/dhcp/dhclient-enter-hooks.d/config: fix script to
not write to /run/net-$iface.conf when dealing with IPv6; which should only
write to a /run/net6-$iface.conf file. (LP: #1621507)
  * debian/README.Debian: document what this config script is and why a hook is
shipped for the initramfs.

 -- Mathieu Trudel-Lapierre   Thu, 08 Dec 2016
17:43:34 +0100

** Changed in: initramfs-tools (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/1621507

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU

  ifupdown:
  bug 1629972: networking.service takes down lo on stop

  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)

  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD

  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  [Stable Fix]

  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.

  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

  [Tests for verification]

  Whoever checks the last one off, please mark verification done.

  MAAS test cases:
   X / Y
  [+]/[+] MAAS on IPv6-only network
  [+]/[+] MAAS on IPv4-only network
  [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6)
  [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4)

  Non-MAAS test cases:
   X / Y
  [+]/[+] ip="" and ip6 not present
  [+]/[+] ip=:eth0:dhcp and ip6 not present
  [+]/[+] d-i install with iSCSI remote root should complete normally
  [+]/[+] Validate normal boot 

[Group.of.nepali.translators] [Bug 1621615] Re: network not configured when ipv6 netbooted into cloud-init

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.27ubuntu1.3

---
cloud-initramfs-tools (0.27ubuntu1.3) xenial; urgency=medium

  * sync with upstream at 0.32ubuntu1 (revno 129)
* overlayroot: fix overlayroot=crypt with newer initramfs-tools
  (LP: #1634310)
* overlayroot: support random seed from systemd systemd-random-seed.service
* cloud-initramfs-dyn-netconf: Further adjustments to support
  IPV6 and the new DEVICE6 and net6-DEVICE.conf files.  (LP: #1621615)
* overlayroot: support 'overlay' filesystem explicitly rather than
  relying on ubuntu specific kernel module 'overlayfs'.  (LP: #1493188)
* overlayroot: write debug to /run/initramfs not /dev/.initramfs but
  support writing to /dev/.initramfs if that is all there is. (LP: #1485752)
* overlayroot: fix overlayroot if recurse=0 was not provided.
  This fuctionality was lost since workdir support was added. (LP: #1619459)
* whitespace cleanup.

 -- Scott Moser   Mon, 28 Nov 2016 20:12:51 -0500

** Changed in: cloud-initramfs-tools (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/1621615

Title:
  network not configured when ipv6 netbooted into cloud-init

Status in cloud-init:
  Fix Committed
Status in MAAS:
  In Progress
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Committed
Status in cloud-initramfs-tools source package in Yakkety:
  Fix Committed

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 talks of
  how IPv6 netboot with iscsi root disk doesn't work, blocking IPv6-only
  MAAS.

  After I hand-walked busybox through getting an IPv6 address,
  everything worked just fine until cloud-init couldn't fetch the
  instance data, because it insisted on bringing up the interface in
  IPv4, and there is no IPv4 DHCP on that vlan.

  Please work with initramfs and friends on getting IPv6 netboot to
  actually configure the interface.  This may be as simple as teaching
  it about "inet6 dhcp" interfaces, and bolting the pieces together.
  Note that "use radvd" is not really an option for our use case.

  Related bugs:
   * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 
addresses
   * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
   * bug 1639930: initramfs network configuration ignored if only ip6= on 
kernel command line 

  [Impact]

  It is not possible to enlist, commmission, or deploy with MAAS in an
  IPv6-only environment. Anyone wanting to netboot with a network root
  filesystem in an IPv6-only environment is affected.

  This upload addresses this by accepting, using, and forwarding any
  IPV6* variables from the initramfs boot.  (See
  https://launchpad.net/bugs/1621507)

  [Test Case]

  See Bug 1229458. Configure radvd, dhcpd, and tftpd for your IPv6-only
  netbooting world. Pass the boot process an IPv6 address to fetch
  instance-data from, and see it fail to configure the network.

  [Regression Potential]

  1) If the booting host is in a dual-boot environment, and the
  instance-dat URL uses a hostname that has both A and  RRsets, the
  booting host may try to talk IPv6 to get instance data.  If the
  instance-data providing host is only allowing that to happen over
  IPv4, it will fail. (It also represents a configuraiton issue on the
  providing host...)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1621615/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

[Launchpad Bug Tracker]

This bug was fixed in the package ifupdown - 0.8.10ubuntu1.2

---
ifupdown (0.8.10ubuntu1.2) xenial; urgency=medium

  * networking.service: exclude loopback device lo in ExecStop (LP: #1629972)
This prevents the stop of networking.service from taking down the
loopback 'lo' interface.

 -- Scott Moser   Wed, 30 Nov 2016 12:23:26 -0500

** Changed in: ifupdown (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/1629972

Title:
  networking stop incorrectly disconnects from (network) root filesystem

Status in MAAS:
  Triaged
Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  Fix Released
Status in ifupdown source package in Yakkety:
  Fix Released
Status in ifupdown package in Debian:
  New

Bug description:
  === Begin SRU Template ===
  [Impact]
  The systemd networking.service unit will bring down the loopback device (lo)
  when it is stopped.  This behavior differs from the behavior in other
  Ubuntu releases (upstart's networking.conf), where 'lo' is not taken down.

  The problem that was seen was that iscsi root over ipv6 would hang on
  shutdown.  

  [Test Case]
  Test is fairly simple and can be demonstrated in lxc container.
  The key is really that the lo device should not have its link set down
  after stopping networking.service.  So, below:
out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty

  should not show 'empty', but should have LOOPBACK,UP,LOWER in its
  output.

  $ release=yakkety; name=y1
  $ lxc launch ubuntu-daily:$release $name
  $ sleep 10
  $ lxc exec $name /bin/bash

  ## show only things that are up (note output has LOOPBACK,UP,LOWER_UP)
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  % ip address show dev lo up
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever

  ## Stop the service and show lo link is down (no 'UP' or 'LOWER_UP').
  % systemctl stop networking.service
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state DOWN mode DEFAULT group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
  empty

  ## Now enable proposed, install update, reboot and show.
  % rel=$(lsb_release -sc)
  % echo "deb http://archive.ubuntu.com/ubuntu $rel-proposed main" |
  sudo tee /etc/apt/sources.list.d/proposed.list
  % sudo apt update -qy && sudo apt install -qy ifupdown  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % ip address show dev lo up
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  % systemctl stop networking.service
  % ip link show dev lo
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  % out=$(ip address show dev lo up); [ -n "$out" ] && echo "$out" || echo empty
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever

  
  [Regression Potential]
  Should be pretty low.  zesty and  yakkety-proposed have this.
  Taking down 'lo' is often cause of problems, and never the solution to
  problems as far as I'm aware.

  [Other Info]

  === End SRU Template ===

  With the switch to systemd, all support for iscsi root (and other)
  filesystems disappeared, since shutdown yanks the rug out from under
  us.

  Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i
  creates..), the DEV check should be expanded to include iscsi devices,
  and networking.service ExecStop should honor those checks.

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1621507: ipv6 network boot does not work

To manage 

[Group.of.nepali.translators] [Bug 1634310] Re: crypt:dev=/dev/vdb parameter does not work with randomly generated passphrase

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.27ubuntu1.3

---
cloud-initramfs-tools (0.27ubuntu1.3) xenial; urgency=medium

  * sync with upstream at 0.32ubuntu1 (revno 129)
* overlayroot: fix overlayroot=crypt with newer initramfs-tools
  (LP: #1634310)
* overlayroot: support random seed from systemd systemd-random-seed.service
* cloud-initramfs-dyn-netconf: Further adjustments to support
  IPV6 and the new DEVICE6 and net6-DEVICE.conf files.  (LP: #1621615)
* overlayroot: support 'overlay' filesystem explicitly rather than
  relying on ubuntu specific kernel module 'overlayfs'.  (LP: #1493188)
* overlayroot: write debug to /run/initramfs not /dev/.initramfs but
  support writing to /dev/.initramfs if that is all there is. (LP: #1485752)
* overlayroot: fix overlayroot if recurse=0 was not provided.
  This fuctionality was lost since workdir support was added. (LP: #1619459)
* whitespace cleanup.

 -- Scott Moser   Mon, 28 Nov 2016 20:12:51 -0500

** Changed in: cloud-initramfs-tools (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/1634310

Title:
  crypt:dev=/dev/vdb parameter does not work with randomly generated
  passphrase

Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released
Status in cloud-initramfs-tools source package in Yakkety:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Using overlay to put overlay data onto an encrypted volume with a randomly
  generated password does not function as documented.

  [Test Case]
  The following should work, but currently does not.
  Note, to test the fix, between step 1 and 2, you'll need to enable
  proposed and install overlayroot.

  1. Start an instance of a cloud image with 2 disks.
     One disk is the root disk, one disk is the target.
     This can be done locally with qemu or within openstack or any other cloud.

  2. configure overlayroot to write to target disk, reboot

 # remove the entry in /etc/fstab for the device we're using
 $ sudo sed -i.dist '/comment=cloudconfig/d' /etc/fstab

     $ target=/dev/vdb
     $ echo "overlayroot=crypt:dev=$target" | sudo tee 
/etc/overlayroot.local.conf
     $ sudo reboot

  3. log back in and look around

     a.) check that 'overlayroot' is in /proc/mounts
     $ awk '$1 == "overlayroot" { print $0 }' /proc/mounts
     overlayroot / overlay 
rw,relatime,lowerdir=/media/root-ro,upperdir=/media/root-rw/overlay,workdir=/media/root-rw/overlay-workdir/_
 0 0

     b.) check that the upperdir listed (/media/root-rw) is encrypted
     $ df -h /media/root-rw/
     Filesystem  Size  Used Avail Use% Mounted on
     /dev/mapper/secure   40G   50M   38G   1% /media/root-rw

     c.) check /run/initramfs/overlayroot.log
     $ grep success /run/initramfs/overlayroot.log
     [success]: configured root with 'crypt:dev=/dev/vdb' using overlay per 
/dev/vda1/etc/overlayroot.local.conf
     d.) show password file.
     $ pf=$(echo /run/initramfs/overlayroot.??);
     $ for f in $pf; do ls -l $f; sudo cat $f; done
     -rw--- 1 root root 128 Nov 29 20:22 
/run/initramfs/overlayroot.4bHuqg
     8c420e20a49254..659eb663e

  [Regression Potential]
  The most likely path for failure on this I would think is related to setting
  of PERSIST_DIR.  If PERSIST_DIR was not set correctly, then the logging
  would likely fail and the password file would not be created.
  That should be caught and logged with:
   log_fail "failed creation of password file";

  [Other Info]
  The full overlayroot/init-bottom/overlayroot can be seen at [1].  The
  specific change that fixed the issue is in revision 126 at [2]

  [1] 
http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/overlayroot/scripts/init-bottom/overlayroot
  [2] 
http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/revision/126
  === End SRU Template ===

  For the life of me I cannot get the parameter crypt:dev=/dev/vdb to
  work in /etc/overlayroot.conf.

  I have tried the line

  overlayroot=crypt:dev=/dev/vdb,pass=somepass,mkfs=0

  Which works when I create the LUKS device ahead of time, and set the
  passphrase 'somepass'. But when I try

  overlayroot=crypt:dev=/dev/vdb,mkfs=1

  or just

  overlayroot=crypt:dev=/dev/vdb

  I get no overlay after reboot. I have also tried the "debug=1"
  parameter and I'm not getting any debug output either. Where are the
  logs and/or where should I be able to see the debug output?

  As Dustin has so eloquently documented, it defeats the privacy of your
  encryption if you have to specify the 

[Group.of.nepali.translators] [Bug 1639930] Re: initramfs network configuration ignored if only ip6= on kernel command line

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.2

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.2) xenial-proposed; urgency=medium

  * cherry-pick 18203bf: disk_setup: Use sectors as unit when formatting
MBR disks with sfdisk. (LP: #1460715)
  * cherry-pick 6e92c5f: net/cmdline: Consider ip= or ip6= on command
line not only ip= (LP: #1639930)
  * cherry-pick 8c6878a: tests: fix assumptions that expected no eth0 in
system. (LP: #1644043)
  * cherry-pick 2d2ec70: OpenStack: extend physical types to include
hyperv, hw_veb, vhost_user. (LP: #1642679)

 -- Scott Moser   Thu, 01 Dec 2016 16:57:39 -0500

** Changed in: cloud-init (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/1639930

Title:
  initramfs network configuration ignored if only ip6= on kernel command
  line

Status in cloud-init:
  Fix Committed
Status in MAAS:
  New
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  In Progress

Bug description:
  === Begin SRU Template ===
  [Impact]
  On a system booted with both ip6= and ip= on the kernel command line
  cloud-init will raise an exception and fail to process user-data and
  have its normal affect on boot.

  That is because cloud-init previously raised an exception when more
  than one file in /run/net*.conf declared the same DEVICE.  Changes to
  isc-dhcp and initramfs-tools have changed their behavior and cloud-init
  has to adjust to allow DEVICE6= and DEVICE= in separate files.

  [Test Case]
  Boot a system on a network with both ipv4 and ipv6 dhcp servers,
  and pass kernel command line with:
    ip=dhcp ip6=dhcp

  [Regression Potential]
  Regression seems unlikely as this is relaxing a check.  Where previously
  an exception would have been raised, cloud-init will now go on.

  So it seems most likely, something that didn't work before (due to raised
  exception) would now still not work, but with failures.  That is not
  expected, but that would likely be where regressions were found.

  === End SRU Template ===

  In changes made under bug 1621615 (specifically a1cdebdea), we now
  expect that there may be a 'ip6=' argument on the kernel command line.
  The changes made did not test the case where there is 'ip6=' and no
  'ip='.

  The code currently will return with no network configuration found if
  there is only ip6=...

  Related bugs:
   * bug 1621615: network not configured when ipv6 netbooted into cloud-init
   * bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 
addresses
   * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1639930/+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 1642679] Re: The OpenStack network_config.json implementation fails on Hyper-V compute nodes

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.2

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.2) xenial-proposed; urgency=medium

  * cherry-pick 18203bf: disk_setup: Use sectors as unit when formatting
MBR disks with sfdisk. (LP: #1460715)
  * cherry-pick 6e92c5f: net/cmdline: Consider ip= or ip6= on command
line not only ip= (LP: #1639930)
  * cherry-pick 8c6878a: tests: fix assumptions that expected no eth0 in
system. (LP: #1644043)
  * cherry-pick 2d2ec70: OpenStack: extend physical types to include
hyperv, hw_veb, vhost_user. (LP: #1642679)

 -- Scott Moser   Thu, 01 Dec 2016 16:57:39 -0500

** Changed in: cloud-init (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/1642679

Title:
  The OpenStack network_config.json implementation fails on Hyper-V
  compute nodes

Status in cloud-init:
  Confirmed
Status in OpenStack Compute (nova):
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  === Begin SRU Template ===
  [Impact]
  When a config drive provides network_data.json on Azure OpenStack,
  cloud-init will fail to configure networking.

  Console log and /var/log/cloud-init.log will show:
   ValueError: Unknown network_data link type: hyperv

  This woudl also occur when the type of the network device as declared
  to cloud-init was 'hw_veb', 'hyperv', or 'vhostuser'.

  [Test Case]
  Launch an instance with config drive on hyperv cloud.

  [Regression Potential]
  Low to none.   cloud-init is relaxing requirements and will accept things
  now that it previously complained were invalid.
  === End SRU Template ===

  We have discovered an issue when booting Xenial instances on OpenStack
  environments (Liberty or newer) and Hyper-V compute nodes using config
  drive as metadata source.

  When applying the network_config.json, cloud-init fails with this error:
  http://paste.openstack.org/show/RvHZJqn48JBb0TO9QznL/

  The fix would be to add 'hyperv' as a link type here:
  /usr/lib/python3/dist-packages/cloudinit/sources/helpers/openstack.py, line 
587

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1642679/+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 1644043] Re: Read Kernel Config tests missing MAC Address

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.2

---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.2) xenial-proposed; urgency=medium

  * cherry-pick 18203bf: disk_setup: Use sectors as unit when formatting
MBR disks with sfdisk. (LP: #1460715)
  * cherry-pick 6e92c5f: net/cmdline: Consider ip= or ip6= on command
line not only ip= (LP: #1639930)
  * cherry-pick 8c6878a: tests: fix assumptions that expected no eth0 in
system. (LP: #1644043)
  * cherry-pick 2d2ec70: OpenStack: extend physical types to include
hyperv, hw_veb, vhost_user. (LP: #1642679)

 -- Scott Moser   Thu, 01 Dec 2016 16:57:39 -0500

** Changed in: cloud-init (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/1644043

Title:
  Read Kernel Config tests missing MAC Address

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  In Progress

Bug description:
  http://pad.lv/1644043
  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1644043
  
  === Begin SRU Template ===
  [Impact] 
  Unit tests would fail, causing build failure.

  [Test Case]
  Run cloud-init tests a system with a network device named 'eth0'
  Building cloud-init runs the unit tests, so even just building on
  such a system is sufficient.

  lxc provides such an environment.

  Generally, the build worked, so unit tests passed.

  [Regression Potential] 
  None: unit test changes only.

  === End SRU Template ===

  
  Unittests are broken [1] preventing cloud-init from building currently. The 
issue is the kernel config tests are looking for a MAC address that is not 
there.

  [1] https://jenkins.ubuntu.com/server/job/cloud-init-integration-
  lts/35/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1644043/+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 1650336] Re: NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

[Joseph Salisbury]

** 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 => Confirmed

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

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

** Tags added: performing-bisect xenial

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

Title:
  NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

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

Bug description:
  On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
  crash on boot when in /etc/fstab a nfsv4 entry is active

  When comment the line or set to noauto the kernel boot with no error
  and mounting the nfs shares (after uncomment ) is also possible
  without error

  4.4.0-54 boots without this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650336/+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 1649361] Re: linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker

[Luis Henriques]

ADT isn't testing hwe-edge yet

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1649358
  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/1649361/+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 1433906] Re: Acer, Inc ID 5986:055a is useless after 14.04.2 installed.

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-December/081567.html

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

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

** Also affects: linux-lts-vivid (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-xenial (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

Title:
  Acer, Inc ID 5986:055a is useless after 14.04.2 installed.

Status in HWE Next:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-vivid package in Ubuntu:
  Triaged
Status in linux-lts-xenial package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  New
Status in linux-lts-vivid source package in Yakkety:
  New
Status in linux-lts-xenial source package in Yakkety:
  New
Status in linux package in Arch Linux:
  New
Status in Fedora:
  Unknown

Bug description:
  CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic)
  CID : 201408-15472 Lenovo E555 (A+A) with 14.04.2 (utopic)

  Steps:
  1. Install 14.04.2 on E450 or E555.
  2. Log in system and open a terminal.
  3. $ gst-launch-0.10 v4l2src ! xvimagesink

  Expected result:
  Camara is activated

  Actual result:
  $  gst-launch-0.10 v4l2src ! xvimagesink
  Setting pipeline to PAUSED ...
  ERROR: Pipeline doesn't want to pause.
  ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Cannot 
identify device '/dev/video0'.
  Additional debug info:
  v4l2_calls.c(497): gst_v4l2_open (): 
/GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
  system error: No such file or directory
  Setting pipeline to NULL ...
  Freeing pipeline ...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: 
boot/vmlinuz-3.16.0-30-generic]
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 19 02:21:31 2015
  InstallationDate: Installed on 2015-03-16 (2 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1433906/+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 1645698] Re: [SRU] network-manager 1.2.4

[Aron Xu]

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

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

Title:
  [SRU] network-manager 1.2.4

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  Triaged

Bug description:
  [Impact]

  This SRU would try to have the latest upstream point release of 1.2.x
  land in Xenial, which is the successor of the current 1.2.2 version,
  fixing quite some bugs that's suitable to land in the sable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This version has been in yakkety for sometime, and there's no report
  of regressions until now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1645698/+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 1649361] Re: linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker

[Brad Figg]

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1649358
  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/1649361/+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 1649361] Re: linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the 4.8.0-32.34~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1649358
  phase: Packaging
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Monday, 19. December 2016 10:46 UTC

** Description changed:

  This bug is for tracking the 4.8.0-32.34~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1649358
- phase: Packaging
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Monday, 19. December 2016 10:46 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1649358
  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/1649361/+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 1650054] Re: Dell Precision 5520 & 3520 freezes at login screent

[Luis Henriques]

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

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

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

Title:
  Dell Precision 5520 & 3520 freezes at login screent

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

Bug description:
  When Precision 5520 & 3520 run on iGPU (Intel video only) mode, they
  hang at login screen, i.e. bbswitch tries to turn off the dGPU

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