[Group.of.nepali.translators] [Bug 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

[Robie Basak]

00:27  smb: is
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1648143/comments/26
correct? Wrong bug?


00:28  yeah, looked odd to me to, I don't see the link between that 
security fix and this bug

00:29  Let's reopen for now. If it's wrong, smb can re-close it
perhaps?


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

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

Title:
  tor in lxd: apparmor="DENIED" operation="change_onexec"
  namespace="root//CONTAINERNAME_" profile="unconfined"
  name="system_tor"

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in tor package in Ubuntu:
  Invalid
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Triaged
Status in tor source package in Xenial:
  Invalid
Status in apparmor source package in Yakkety:
  New
Status in linux source package in Yakkety:
  Triaged
Status in tor source package in Yakkety:
  Invalid

Bug description:
  Environment:
  

  Distribution: ubuntu
  Distribution version: 16.10
  lxc info:
  apiextensions:

  storage_zfs_remove_snapshots
  container_host_shutdown_timeout
  container_syscall_filtering
  auth_pki
  container_last_used_at
  etag
  patch
  usb_devices
  https_allowed_credentials
  image_compression_algorithm
  directory_manipulation
  container_cpu_time
  storage_zfs_use_refquota
  storage_lvm_mount_options
  network
  profile_usedby
  container_push
  apistatus: stable
  apiversion: "1.0"
  auth: trusted
  environment:
  addresses:
  163.172.48.149:8443
  172.20.10.1:8443
  172.20.11.1:8443
  172.20.12.1:8443
  172.20.22.1:8443
  172.20.21.1:8443
  10.8.0.1:8443
  architectures:
  x86_64
  i686
  certificate: |
  -BEGIN CERTIFICATE-
  -END CERTIFICATE-
  certificatefingerprint: 
3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b
  driver: lxc
  driverversion: 2.0.5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.8.0-27-generic
  server: lxd
  serverpid: 32694
  serverversion: 2.4.1
  storage: btrfs
  storageversion: 4.7.3
  config:
  core.https_address: '[::]:8443'
  core.trust_password: true

  Container: ubuntu 16.10

  
  Issue description
  --

  
  tor can't start in a non privileged container

  
  Logs from the container:
  -

  Dec 7 15:03:00 anonymous tor[302]: Configuration was valid
  Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process 
exited, code=exited, status=231/APPARMOR
  Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay 
network for TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed 
state.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 
'exit-code'.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off 
time over, scheduling restart.
  Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for 
TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset 
devices.list: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to 
set devices.allow on /system.slice/system-tor.slice/tor@default.service: 
Operation not permitted]
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/chr
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/blk
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted


  Logs from the host
  

  audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" 
  pid=12164 comm="(tor)"

  
  Steps to reproduce
  -

  install ubuntu container 16.10 on a ubuntu 16.10 host
  install tor in the container
  Launch tor

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

[Group.of.nepali.translators] [Bug 1658219] Re: flock not mediated by 'k'

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  flock not mediated by 'k'

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

Bug description:
  $ cat ./apparmor.profile 
  #include 

  profile test {
#include 

/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,

  }

  $ sudo apparmor_parser -r ./apparmor.profile

  $ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
  yes

  $ ls -l /tmp/test.lock 
  -rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock

  The flock command uses flock(LOCK_EX) and I expected it to be blocked
  due to the lack of 'k'.

  apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
  kernel on amd64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1658219/+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 1638996] Re: apparmor's raw_data file in securityfs is sometimes truncated

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  apparmor's raw_data file in securityfs is sometimes truncated

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  Hi,

  It looks like sometimes apparmor's securityfs output is sometimes
  truncated,

  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 ls -al
  total 0
  drwxr-xr-x  3 root root 0 Nov  3 16:45 .
  drwxr-xr-x 13 root root 0 Nov  3 16:44 ..
  -r--r--r--  1 root root 0 Nov  3 16:45 attach
  -r--r--r--  1 root root 0 Nov  3 16:45 mode
  -r--r--r--  1 root root 0 Nov  3 16:45 name
  drwxr-xr-x  3 root root 0 Nov  3 16:45 profiles
  -r--r--r--  1 root root 0 Nov  3 16:45 raw_abi
  -r--r--r--  1 root root 46234 Nov  3 16:45 raw_data
  -r--r--r--  1 root root 0 Nov  3 16:45 raw_hash
  -r--r--r--  1 root root 0 Nov  3 16:45 sha1
  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 cat raw_data > /tmp/out
  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 ls -al /tmp/out 
  -rw-r--r-- 1 root root 4009 Nov  3 16:55 /tmp/out

  and

  2016-11-03 10:58:01 tych0 jjohansen: hi, http://paste.ubuntu.com/23421551/
  2016-11-03 10:58:18 tych0 it looks like fstat is lying to me about the size 
of the policy
  2016-11-03 10:59:20 @jjohansen  tych0: hrmm interesting, can you zip up the 
/tmp/out file so I can see it looks like a complete policy file?
  2016-11-03 11:00:03 @jjohansen  something is definitely not right there. hrmmm
  2016-11-03 11:00:26 @jjohansen  the size is set by the input buffer size
  2016-11-03 11:00:28 tych0 jjohansen: http://files.tycho.ws/tmp/out
  2016-11-03 11:00:36 tych0 yeah, i assume
  2016-11-03 11:01:15 @jjohansen  my guess is something is messing up in the 
seq_file walk of the policy
  2016-11-03 11:02:38 @jjohansen  tych0: yep the file is truncated, can you 
open a bug and I will start looking for it
  2016-11-03 11:03:14 tych0 jjohansen: sure, just on linux?
  2016-11-03 11:03:35 @jjohansen  tych0: yeah for now, just linux
  2016-11-03 11:03:43 @jjohansen  we can add others if needed later
  2016-11-03 11:03:44 tych0 jjohansen: FWIW, somehow it seems racy, becasue 
sometimes it works and sometimes it doesn't

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638996/+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 1645037] Re: apparmor_parser hangs indefinitely when called by multiple threads

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  apparmor_parser hangs indefinitely when called by multiple threads

Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug surfaced when starting ~50 LXC container with LXD in parallel
  multiple times:

  # Create the containers
  for c in c foo{1..50}; do lxc launch images:ubuntu/xenial $c; done

  # Exectute this loop multiple times until you observe errors.
  for c in c foo{1..50}; do lxc restart $c & done

  After this you can

  ps aux | grep apparmor

  and you should see output similar to:

  root 19774  0.0  0.0  12524  1116 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19775  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19776  0.0  0.0  13592  3224 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19778  0.0  0.0  13592  3384 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19780  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19782  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19783  0.0  0.0  13592  3388 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19784  0.0  0.0  13592  3252 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19794  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25
  root 19795  0.0  0.0  13592  3256 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25

  apparmor_parser remains stuck even after all LXC/LXD commands have
  exited.

  dmesg output yields lines like:

  [41902.815174] audit: type=1400 audit(1480191089.678:43):
  apparmor="STATUS" operation="profile_load" profile="unconfined" name
  ="lxd-foo30_" pid=12545 comm="apparmor_parser"

  and cat /proc/12545/stack shows:

  [] aa_remove_profiles+0x88/0x270
  21:19   brauner  [] profile_remove+0x144/0x2e0
  21:19   brauner  [] __vfs_write+0x18/0x40
  21:19   brauner  [] vfs_write+0xb8/0x1b0
  21:19   brauner  [] SyS_write+0x55/0xc0
  21:19   brauner  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  21:19   brauner  [] 0x

  This looks like a potential kernel bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1645037/+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 1660833] Re: apparmor reference count bug in label_merge_insert()

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  apparmor reference count bug in label_merge_insert()

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  @new does not have a reference taken locally and should not have its  
  
  reference put locally either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660833/+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 1656121] Re: unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt from a unshared mount namespace

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  unexpected errno=13 and disconnected path when trying to open
  /proc/1/ns/mnt from a unshared mount namespace

Status in AppArmor:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  This bug is based on a discussion with jjohansen on IRC.

  While working on a feature for snapd
  (https://github.com/snapcore/snapd/pull/2624) we came across an
  unexpected EACCES that only seems to happen when apparmor is in the
  loop.

  The kernel log shows something interesting. The full log is available
  here: http://paste.ubuntu.com/23789099/

  Jan 12 23:16:43 autopkgtest kernel: [  498.616822] audit: type=1400
  audit(1484259403.009:67): apparmor="ALLOWED" operation="open"
  info="Failed name lookup - disconnected path" error=-13 profile="snap
  .test-snapd-tools.cmd//null-/usr/bin/snap//null-/usr/lib/snapd/snap-
  confine" name="" pid=25299 comm="snap-confine" requested_mask="r"
  denied_mask="r" fsuid=0 ouid=0

  The code that triggers this is reproduced below (also visible here
  https://github.com/snapcore/snapd/pull/2624/files)

  +void sc_reassociate_with_pid1_mount_ns()
   +{
   +int init_mnt_fd __attribute__ ((cleanup(sc_cleanup_close))) = -1;
   +int self_mnt_fd __attribute__ ((cleanup(sc_cleanup_close))) = -1;
   +
   +debug("checking if the current process shares mount namespace"
   +  "with the init process");
   +
   +init_mnt_fd = open("/proc/1/ns/mnt",
   +   O_RDONLY | O_CLOEXEC | O_NOFOLLOW | O_PATH);
   +if (init_mnt_fd < 0) {
   +die("cannot open mount namespace of the init process (O_PATH)");
   +}
   +self_mnt_fd = open("/proc/self/ns/mnt",
   +   O_RDONLY | O_CLOEXEC | O_NOFOLLOW | O_PATH);
   +if (self_mnt_fd < 0) {
   +die("cannot open mount namespace of the current process 
(O_PATH)");
   +}
   +char init_buf[128], self_buf[128];
   +memset(init_buf, 0, sizeof init_buf);
   +if (readlinkat(init_mnt_fd, "", init_buf, sizeof init_buf) < 0) {
   +die("cannot perform readlinkat() on the mount namespace file "
   +"descriptor of the init process");
   +}
   +memset(self_buf, 0, sizeof self_buf);
   +if (readlinkat(self_mnt_fd, "", self_buf, sizeof self_buf) < 0) {
   +die("cannot perform readlinkat() on the mount namespace file "
   +"descriptor of the current process");
   +}
   +if (memcmp(init_buf, self_buf, sizeof init_buf) != 0) {
   +debug("the current process does not share mount namespace with "
   +  "the init process, re-association required");
   +// NOTE: we cannot use O_NOFOLLOW here because that file will 
always be a
   +// symbolic link. We actually want to open it this way.
   +int init_mnt_fd_real
   +__attribute__ ((cleanup(sc_cleanup_close))) = -1;
   +init_mnt_fd_real = open("/proc/1/ns/mnt", O_RDONLY | O_CLOEXEC);
   +if (init_mnt_fd_real < 0) {
   +die("cannot open mount namespace of the init process");
   +}
   +if (setns(init_mnt_fd_real, CLONE_NEWNS) < 0) {
   +die("cannot re-associate the mount namespace with the 
init process");
   +}
   +} else {
   +debug("re-associating is not required");
   +}
   +}

  The specific part that causes the error is:

   +  init_mnt_fd_real = open("/proc/1/ns/mnt", O_RDONLY |
  O_CLOEXEC);

  The call to open returns -1 and errno set to 13 (EACCES) despite using
  attach_disconnected.

  The code in question is executed from a seguid root executable that
  runs under a complain-mode profile (it is started from a process that
  is already confined with such a profile). All of the profiles are
  using attach_disconnected.

  I can reproduce this issue each time by running:

  spread -debug -v qemu:ubuntu-16.04-64:tests/regression/lp-1644439

  Against the code in this pull request:

  https://github.com/snapcore/snapd/pull/2624

  Which is git://github.com/zyga/snapd in the 

[Group.of.nepali.translators] [Bug 1648903] Re: Permission denied and inconsistent behavior in complain mode with 'ip netns list' command

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  Permission denied and inconsistent behavior in complain mode with 'ip
  netns list' command

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

Bug description:
  On 16.04 with Ubuntu 4.4.0-53.74-generic 4.4.30

  With this profile:

  #include 

  profile test (attach_disconnected,complain) {
  #include 

  /{,usr/}{,s}bin/ip ixr,  # COMMENT OUT THIS RULE TO SEE WEIRDNESS

  capability sys_admin,
  capability net_admin,
  capability sys_ptrace,

  network netlink raw,

  ptrace (trace),

  / r,
  /run/netns/ rw,
  /run/netns/* rw,

  mount options=(rw, rshared) -> /run/netns/,
  mount options=(rw, bind) /run/netns/ -> /run/netns/,
  mount options=(rw, bind) / -> /run/netns/*,
  mount options=(rw, rslave) /,
  mount options=(rw, rslave), # LP: #1648245
  umount /sys/,
  umount /,

  
  /bin/dash ixr,
  }

  Everything is fine when I do:
  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  $

  and there are no ALLOWED entries in syslog.

  
  However, if I comment out the '/{,usr/}{,s}bin/ip ixr,' rule, I get a 
permission denied and a bunch of ALLOWED entries:

  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  open("/proc/self/ns/net"): Permission denied
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.862629] audit: type=1400 
audit(1481324889.782:469): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="test" pid=4314 comm="apparmor_parser"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870339] audit: type=1400 
audit(1481324889.790:470): apparmor="ALLOWED" operation="exec" profile="test" 
name="/bin/ip" pid=4317 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 
ouid=0 target="test//null-/bin/ip"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870559] audit: type=1400 
audit(1481324889.790:471): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/etc/ld.so.cache" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870628] audit: type=1400 
audit(1481324889.790:472): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libdl-2.23.so" 
pid=4317 comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870703] audit: type=1400 
audit(1481324889.790:473): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libc-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870861] audit: type=1400 
audit(1481324889.790:474): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/bin/ip" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870913] audit: type=1400 
audit(1481324889.790:475): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/ld-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871019] audit: type=1400 
audit(1481324889.790:476): apparmor="ALLOWED" operation="create" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="create" denied_mask="create"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871066] audit: type=1400 
audit(1481324889.790:477): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871099] audit: type=1400 
audit(1481324889.790:478): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871128] audit: type=1400 
audit(1481324889.790:479): apparmor="ALLOWED" 

[Group.of.nepali.translators] [Bug 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  tor in lxd: apparmor="DENIED" operation="change_onexec"
  namespace="root//CONTAINERNAME_" profile="unconfined"
  name="system_tor"

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in tor package in Ubuntu:
  Invalid
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Triaged
Status in tor source package in Xenial:
  Invalid
Status in apparmor source package in Yakkety:
  New
Status in linux source package in Yakkety:
  Fix Released
Status in tor source package in Yakkety:
  Invalid

Bug description:
  Environment:
  

  Distribution: ubuntu
  Distribution version: 16.10
  lxc info:
  apiextensions:

  storage_zfs_remove_snapshots
  container_host_shutdown_timeout
  container_syscall_filtering
  auth_pki
  container_last_used_at
  etag
  patch
  usb_devices
  https_allowed_credentials
  image_compression_algorithm
  directory_manipulation
  container_cpu_time
  storage_zfs_use_refquota
  storage_lvm_mount_options
  network
  profile_usedby
  container_push
  apistatus: stable
  apiversion: "1.0"
  auth: trusted
  environment:
  addresses:
  163.172.48.149:8443
  172.20.10.1:8443
  172.20.11.1:8443
  172.20.12.1:8443
  172.20.22.1:8443
  172.20.21.1:8443
  10.8.0.1:8443
  architectures:
  x86_64
  i686
  certificate: |
  -BEGIN CERTIFICATE-
  -END CERTIFICATE-
  certificatefingerprint: 
3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b
  driver: lxc
  driverversion: 2.0.5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.8.0-27-generic
  server: lxd
  serverpid: 32694
  serverversion: 2.4.1
  storage: btrfs
  storageversion: 4.7.3
  config:
  core.https_address: '[::]:8443'
  core.trust_password: true

  Container: ubuntu 16.10

  
  Issue description
  --

  
  tor can't start in a non privileged container

  
  Logs from the container:
  -

  Dec 7 15:03:00 anonymous tor[302]: Configuration was valid
  Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process 
exited, code=exited, status=231/APPARMOR
  Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay 
network for TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed 
state.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 
'exit-code'.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off 
time over, scheduling restart.
  Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for 
TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset 
devices.list: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to 
set devices.allow on /system.slice/system-tor.slice/tor@default.service: 
Operation not permitted]
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/chr
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/blk
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted


  Logs from the host
  

  audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" 
  pid=12164 comm="(tor)"

  
  Steps to reproduce
  -

  install ubuntu container 16.10 on a ubuntu 16.10 host
  install tor in the container
  

[Group.of.nepali.translators] [Bug 1660840] Re: apparmor oops in bind_mnt when dev_path lookup fails

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  apparmor oops in bind_mnt when dev_path lookup fails

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Bind mounts can oops when devname lookup fails because the devname is 
  
  unintialized and used in auditing the denial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660840/+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 1660834] Re: apparmor label leak when new label is unused

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  apparmor label leak when new label is unused

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  When a new label is created, it is created with a proxy in a circular 
  
  ref count that is broken by replacement. However if the label is not  
  
  used it will never be replaced and the circular ref count will never  
  
  be broken resulting in a leak.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660834/+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 1660836] Re: apparmor auditing denied access of special apparmor .null fi\ le

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  apparmor  auditing denied access of special apparmor .null fi\ le

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  When an fd is disallowed from being inherited during exec, instead of 
  
  closed it is duped to a special apparmor/.null file. This prevents the
  
  fd from being reused by another file in case the application expects  
  
  the original file on a give fd (eg stdin/stdout etc). This results in 
  
  a denial message like 
  
  [32375.561535] audit: type=1400 audit(1478825963.441:358): apparmor="DENIED" 
op\
  eration="file_inherit" namespace="root//lxd-t_" 
profile="/sbin/dhc\
  lient" name="/dev/pts/1" pid=16795 comm="dhclient" requested_mask="wr" 
denied_m\
  ask="wr" fsuid=165536 ouid=165536 
  

  
  Further access to the fd is resultin in the rather useless denial message 
  
  of
  
  [32375.566820] audit: type=1400 audit(1478825963.445:359): apparmor="DENIED" 
op\
  eration="file_perm" namespace="root//lxd-t_" 
profile="/sbin/dhclie\
  nt" name="/apparmor/.null" pid=16795 comm="dhclient" requested_mask="w" 
denied_\
  mask="w" fsuid=165536 ouid=0  
  

  
  since we have the original denial, the noisy and useless .null based  
  
  denials can be skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660836/+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 1660842] Re: apparmor not checking error if security_pin_fs() fails

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  apparmor not checking error if security_pin_fs() fails

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  The error condition of security_pin_fs() was not being checked which
  will result can result in an oops or use after free, due to the fs pin
  count not being incremented.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660842/+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 1660845] Re: apparmor reference count leak when securityfs_setup_d_inode\ () fails

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  apparmor reference count leak when securityfs_setup_d_inode\ () fails

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  apparmor is leaking the parent ns ref count, by directly returning the
  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660845/+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 1660846] Re: apparmor leaking securityfs pin count

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  apparmor leaking securityfs pin count

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  apparmor is leaking pinfs refcoutn when inode setup fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660846/+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 1660849] Re: apparmor refcount leak of profile namespace when removing profiles

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  apparmor refcount leak of profile namespace when removing profiles

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  When doing profile removal, the parent ns of the profiles is taken,
  but the reference isn't being put, resulting in the ns never being
  freed even after it is removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660849/+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 1661030] Re: regession tests failing after stackprofile test is run

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-45.48

---
linux (4.8.0-45.48) yakkety; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Stefan Bader   Fri, 24 Mar 2017 12:03:39
+0100

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

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

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

Title:
  regession tests failing after stackprofile test is run

Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Triaged
Status in apparmor source package in Yakkety:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in apparmor source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Incomplete

Bug description:
  from source, I'm running the tests and the makefile fails at the end
  with:

  running stackprofile
  Makefile:303: recipe for target 'tests' failed
  make: *** [tests] Error 1

  No idea why that is happening. It's breaking on our kernel team
  regression tests runs, so can this be investigated?  The source was
  fetched using "apt-get source apparmor".

  A full run is below:

  king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make
  USE_SYSTEM=1 tests

  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)
  (ioperm)
  (iopl)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12503 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12537 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12803 Segmentation fault  (core dumped) $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12833 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12869 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12905 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12941 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ
  Fatal Error (environ): Unable to run test sub-executable

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root

  running ptrace
 using ptrace v6 tests ...

  running pwrite

  running query_label
  Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #1)
  Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked 
as expected pass but known problem (xpass)
  

[Group.of.nepali.translators] [Bug 1677337] Re: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity

[Joseph Salisbury]

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

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

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

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

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

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

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

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

** Tags removed: needs-reverse-bisect
** Tags added: performing-bisect

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

Title:
  Mellanox Technologies MT27500 Family [ConnectX-3] no network
  connectivity

Status in linux package in Ubuntu:
  In Progress
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:
  In Progress

Bug description:
  After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
  Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
  brought up and assigned an ip via MAAS. This is where functionality
  stops on this kernel. Pinging the MAAS server  which is connected
  directly(no switch) fails. There's no traffic  from tcpdump.

  linux-image-generic-hwe-16.04 4.8.0.44.16 fails
  mainline kernel 4.10.0-041000-generic fails
  mainline kernel 4.11.0-041100rc1-generic resolves the issue.

  Both the test server (ppc64le) and MAAS server(amd64) need the
  upgraded kernel to work.

  === 4.4.0-70-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
   Subsystem: IBM MT27500 Family [ConnectX-3]
   Flags: bus master, fast devsel, latency 0, IRQ 473
   Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
   Memory at 2400 (64-bit, prefetchable) [size=128M]
   [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
   Kernel driver in use: mlx4_core
   Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   56000baseCR4/Full
   56000baseSR4/Full
   Supported pause frame use: Symmetric Receive-only
   Supports auto-negotiation: Yes
   Advertised link modes:  1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Link partner advertised link modes:  4baseCR4/Full
   Link partner advertised pause frame use: No
   Link partner advertised auto-negotiation: Yes
   Speed: 4Mb/s
   Duplex: Full
   Port: Direct Attach Copper
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: d
   Wake-on: d
   Current message level: 0x0014 (20)
    link ifdown
   Link detected: yes

  dmesg
  [3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
  [3.494624] mlx4_core: Initializing 0008:01:00.0
  [3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass

  [8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device 
supports 8.0GT/s
  [8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports 
x8
  [8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 
2014)
  [8.472907] mlx4_en 0008:01:00.0: Activating port:1
  [8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings
  [8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings
  [8.481694] mlx4_en: 0008:01:00.0: Port 1:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port
  [8.482320] mlx4_en 0008:01:00.0: registered PHC clock
  [8.485058] mlx4_en 0008:01:00.0: Activating port:2
  [8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings
  [8.491760] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings
  [8.491791] mlx4_en: 0008:01:00.0: Port 2:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.503650] mlx4_en: 0008:01:00.0: Port 2: Initializing port
  [8.511021] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0
  [8.530146] mlx4_core 

[Group.of.nepali.translators] [Bug 1677337] Re: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity

[Joseph Salisbury]

** Tags added: kernel-da-key needs-reverse-bisect

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

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

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

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1677337

Title:
  Mellanox Technologies MT27500 Family [ConnectX-3] no network
  connectivity

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

Bug description:
  After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
  Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
  brought up and assigned an ip via MAAS. This is where functionality
  stops on this kernel. Pinging the MAAS server  which is connected
  directly(no switch) fails. There's no traffic  from tcpdump.

  linux-image-generic-hwe-16.04 4.8.0.44.16 fails
  mainline kernel 4.10.0-041000-generic fails
  mainline kernel 4.11.0-041100rc1-generic resolves the issue.

  Both the test server (ppc64le) and MAAS server(amd64) need the
  upgraded kernel to work.

  === 4.4.0-70-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
   Subsystem: IBM MT27500 Family [ConnectX-3]
   Flags: bus master, fast devsel, latency 0, IRQ 473
   Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
   Memory at 2400 (64-bit, prefetchable) [size=128M]
   [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
   Kernel driver in use: mlx4_core
   Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   56000baseCR4/Full
   56000baseSR4/Full
   Supported pause frame use: Symmetric Receive-only
   Supports auto-negotiation: Yes
   Advertised link modes:  1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Link partner advertised link modes:  4baseCR4/Full
   Link partner advertised pause frame use: No
   Link partner advertised auto-negotiation: Yes
   Speed: 4Mb/s
   Duplex: Full
   Port: Direct Attach Copper
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: d
   Wake-on: d
   Current message level: 0x0014 (20)
    link ifdown
   Link detected: yes

  dmesg
  [3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
  [3.494624] mlx4_core: Initializing 0008:01:00.0
  [3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass

  [8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device 
supports 8.0GT/s
  [8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports 
x8
  [8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 
2014)
  [8.472907] mlx4_en 0008:01:00.0: Activating port:1
  [8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings
  [8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings
  [8.481694] mlx4_en: 0008:01:00.0: Port 1:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port
  [8.482320] mlx4_en 0008:01:00.0: registered PHC clock
  [8.485058] mlx4_en 0008:01:00.0: Activating port:2
  [8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings
  [8.491760] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings
  [8.491791] mlx4_en: 0008:01:00.0: Port 2:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.503650] mlx4_en: 0008:01:00.0: Port 2: Initializing port
  [8.511021] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0
  [8.530146] mlx4_core 0008:01:00.0 enP8p1s0d1: renamed from eth1

  === 4.11.0-041100rc1-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
  Subsystem: IBM MT27500 Family [ConnectX-3]
  Flags: bus master, fast devsel, latency 0, IRQ 473
  Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
  Memory at 2400 (64-bit, prefetchable) [size=128M]
  [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
  Kernel driver in use: mlx4_core
  Kernel 

[Group.of.nepali.translators] [Bug 1564778] Re: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is also in package libsan

[Michael Terry]

I've just uploaded all three (zesty, yakkety, and xenial) fixes.  Better
to just fix this now while the number of uploads is even smaller.  :)

I agreed with Nish about the versions, so I fixed them.

** Also affects: sane-backends (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: sane-backends (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: sane-backends (Ubuntu Zesty)
   Importance: High
   Status: In Progress

** Description changed:

- Unknown error. I Don't know
+ [ Impact ]
  
- ProblemType: Package
- DistroRelease: Ubuntu 16.04
- Package: libsane-common 1.0.25+git20150528-1ubuntu2
- ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
- Uname: Linux 4.4.0-16-generic i686
- NonfreeKernelModules: wl
- ApportVersion: 2.20.1-0ubuntu1
- Architecture: i386
- Date: Fri Apr  1 13:53:51 2016
- ErrorMessage: trying to overwrite '/etc/sane.d/hp.conf', which is also in 
package libsane:i386 1.0.23-3ubuntu3.1
- InstallationDate: Installed on 2013-06-17 (1019 days ago)
- InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
- PackageArchitecture: all
- RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1
-  apt  1.2.9
- SourcePackage: sane-backends
- Title: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to 
install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is also in 
package libsane:i386 1.0.23-3ubuntu3.1
- UpgradeStatus: Upgraded to xenial on 2016-03-28 (3 days ago)
+ This is a packaging error when upgrading from trusty to xenial.  You may
+ see a file conflict error because a file moved from libsane to libsane-
+ common.  This is fairly common, as you can see from the dupes and
+ affect-count.
+ 
+ [ Test Case ]
+ 
+ Install libsane and libsane-common on trusty.  Upgrade to xenial.
+ 
+ [ Regression Potential ]
+ 
+ Tiny.  This is just a Breaks/Conflict packaging error.  No code changes.

** Description changed:

  [ Impact ]
  
  This is a packaging error when upgrading from trusty to xenial.  You may
  see a file conflict error because a file moved from libsane to libsane-
  common.  This is fairly common, as you can see from the dupes and
  affect-count.
+ 
+ As described in comment #4, only xenial really needs to be patched.  But
+ since it shares the same version of sane-backends as yakkety and zesty,
+ it's nice to update both of those so that upgraders get a clean path.
  
  [ Test Case ]
  
  Install libsane and libsane-common on trusty.  Upgrade to xenial.
  
  [ Regression Potential ]
  
  Tiny.  This is just a Breaks/Conflict packaging error.  No code changes.

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

Title:
  package libsane-common 1.0.25+git20150528-1ubuntu2 failed to
  install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is
  also in package libsane:i386 1.0.23-3ubuntu3.1

Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Xenial:
  New
Status in sane-backends source package in Yakkety:
  New
Status in sane-backends source package in Zesty:
  In Progress

Bug description:
  [ Impact ]

  This is a packaging error when upgrading from trusty to xenial.  You
  may see a file conflict error because a file moved from libsane to
  libsane-common.  This is fairly common, as you can see from the dupes
  and affect-count.

  As described in comment #4, only xenial really needs to be patched.
  But since it shares the same version of sane-backends as yakkety and
  zesty, it's nice to update both of those so that upgraders get a clean
  path.

  [ Test Case ]

  Install libsane and libsane-common on trusty.  Upgrade to xenial.

  [ Regression Potential ]

  Tiny.  This is just a Breaks/Conflict packaging error.  No code
  changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1564778/+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 1675391] Re: [SRU] New stable micro release 2.28

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.28+16.10

---
snapcraft (2.28+16.10) yakkety; urgency=medium

  [ Sergio Schvezov ]
  * python plugin: use stage headers if applicable. (#1156)
  * docs: use correct target to generate docs. (#1159)
  * packaging: snapcraft as a snap (#1158)
  * tour: make it work when its a snap. (#1217)
  * cleanbuild: don't copy cache into container. (#1216)
  * kernel plugin: fix modprobe output parsing. (#1208)
  * kernel plugin: use default per arch targets. (#1209)
  * python plugin: support pbr/setup.cfg projects. (#1202)
  * cleanbuild: packaging independent detection. (#1199)
  * tests: remove repo.Ubuntu patch for plugins. (#1194)
  * store: enable delta uploads by default. (#1196)
  * repo: refactor into a package. (#1192)
  * core: resolve ld link first. (#1189)
  * store: enable retries for store calls. (#1184)
  * New upstream release 2.28 (LP: #1675391)

  [ Joe Talbott ]
  * store: set User-Agent header in store requests. (#1188)
  * store: Add track support to commands. (#1161)
  * state: asset tracking - store versions of stage-packages. (#1142)
  * store: remove 'Series' from channel map output (#1151)
  * repo: support versioned stage-packages. (#1157)
  * parser: use the project loader code to find the origin's snapcraft.yaml 
(#1141)
  * cli: rename `history` to 'list-revisions' with `revisions` alias. (#1160)
  * repo: add version support for build-packages (#1185)
  * project: use a more likely to be found global build-package (#1218)

  [ Paolo Pisati ]
  * demos:  add the minimal config changes to boot a dragonboard410c (#1147)
  * kernel plugin: if no dtb target is set when the arch is arm.* build them 
all. (#1148)
  * kernel plugin: rework MAKEFLAGS from the environment (#1150)

  [ Kyle Fazzari ]
  * contribution guide: add commit message template (#1153)
  * demos: make ROS demos support exiting after success. (#1201)
  * catkin plugin: support building with an underlay. (#1140)
  * demos: add ROS content sharing demo. (#1186)
  * repo: fixup with python, not sed (#1181)
  * repo: ignore symlinks to libc. (#1174)
  * sources: update documentation for source-subdir (#1177)

  [ Olivier Tilloy ]
  * project: expose parallel_build_count to scriptlets. (#1154)

  [ Leo Arias ]
  * docs: build and push the API docs to github pages. (#1126)
  * tests: pass the autopkgtest secret to the container (#1162)
  * tests: update the ftp source for integration test (#1169)
  * ci: install wget in the container that triggers the beta tests. (#1167)
  * demos: add a message to exit the mosquitto subscriber. (#1173)
  * demos: add the mount-observe plug to be able to run godd. (#1172)
  * tests: support bzr branches for external tests. (#1128)
  * docs: update the directory where the API pages are generated (#1163)
  * demos: remove the tomcat demo snap. (#1176)
  * tests: make the kernel unit tests architecture independent. (#1178)
  * tests: support snap directory in external tests (#1180)
  * tests: run the master tests against the staging server (#1164)
  * tests: take into account the new current link. (#1187)
  * ci: run the CLA check in a docker container. (#1191)
  * tests: add manual tests for the kernel snaps (#1198)
  * ci: allow to run individual autopkgtest suites (#1200)
  * tests: expect failures for the tests that can't be run in arm64. (#1145)

  [ Jonathan Cave ]
  * plainbox-provider plugin: run validate (#1095)

  [ Michael Hudson-Doyle ]
  * core: fix symlink resolution in get_core_dynamic_linker. (#1170)

  [ pachulo ]
  * sources: add optional "source-checksum" property (#980)

  [ Colin Watson ]
  * godeps plugin: add git to build-packages. (#1179)

 -- Sergio Schvezov   Thu, 23 Mar 2017
16:11:14 -0300

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

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

Title:
   [SRU] New stable micro release 2.28

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

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

  The list of bugs and features in this release are defined at
  https://launchpad.net/snapcraft/+milestone/2.28 and
  https://launchpad.net/snapcraft/+milestone/2.28

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

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

[Group.of.nepali.translators] [Bug 1675391] Re: [SRU] New stable micro release 2.28

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.28

---
snapcraft (2.28) xenial; urgency=medium

  [ Sergio Schvezov ]
  * python plugin: use stage headers if applicable. (#1156)
  * docs: use correct target to generate docs. (#1159)
  * packaging: snapcraft as a snap (#1158)
  * tour: make it work when its a snap. (#1217)
  * cleanbuild: don't copy cache into container. (#1216)
  * kernel plugin: fix modprobe output parsing. (#1208)
  * kernel plugin: use default per arch targets. (#1209)
  * python plugin: support pbr/setup.cfg projects. (#1202)
  * cleanbuild: packaging independent detection. (#1199)
  * tests: remove repo.Ubuntu patch for plugins. (#1194)
  * store: enable delta uploads by default. (#1196)
  * repo: refactor into a package. (#1192)
  * core: resolve ld link first. (#1189)
  * store: enable retries for store calls. (#1184)
  * New upstream release 2.28 (LP: #1675391)

  [ Joe Talbott ]
  * store: set User-Agent header in store requests. (#1188)
  * store: Add track support to commands. (#1161)
  * state: asset tracking - store versions of stage-packages. (#1142)
  * store: remove 'Series' from channel map output (#1151)
  * repo: support versioned stage-packages. (#1157)
  * parser: use the project loader code to find the origin's snapcraft.yaml 
(#1141)
  * cli: rename `history` to 'list-revisions' with `revisions` alias. (#1160)
  * repo: add version support for build-packages (#1185)
  * project: use a more likely to be found global build-package (#1218)

  [ Paolo Pisati ]
  * demos:  add the minimal config changes to boot a dragonboard410c (#1147)
  * kernel plugin: if no dtb target is set when the arch is arm.* build them 
all. (#1148)
  * kernel plugin: rework MAKEFLAGS from the environment (#1150)

  [ Kyle Fazzari ]
  * contribution guide: add commit message template (#1153)
  * demos: make ROS demos support exiting after success. (#1201)
  * catkin plugin: support building with an underlay. (#1140)
  * demos: add ROS content sharing demo. (#1186)
  * repo: fixup with python, not sed (#1181)
  * repo: ignore symlinks to libc. (#1174)
  * sources: update documentation for source-subdir (#1177)

  [ Olivier Tilloy ]
  * project: expose parallel_build_count to scriptlets. (#1154)

  [ Leo Arias ]
  * docs: build and push the API docs to github pages. (#1126)
  * tests: pass the autopkgtest secret to the container (#1162)
  * tests: update the ftp source for integration test (#1169)
  * ci: install wget in the container that triggers the beta tests. (#1167)
  * demos: add a message to exit the mosquitto subscriber. (#1173)
  * demos: add the mount-observe plug to be able to run godd. (#1172)
  * tests: support bzr branches for external tests. (#1128)
  * docs: update the directory where the API pages are generated (#1163)
  * demos: remove the tomcat demo snap. (#1176)
  * tests: make the kernel unit tests architecture independent. (#1178)
  * tests: support snap directory in external tests (#1180)
  * tests: run the master tests against the staging server (#1164)
  * tests: take into account the new current link. (#1187)
  * ci: run the CLA check in a docker container. (#1191)
  * tests: add manual tests for the kernel snaps (#1198)
  * ci: allow to run individual autopkgtest suites (#1200)
  * tests: expect failures for the tests that can't be run in arm64. (#1145)

  [ Jonathan Cave ]
  * plainbox-provider plugin: run validate (#1095)

  [ Michael Hudson-Doyle ]
  * core: fix symlink resolution in get_core_dynamic_linker. (#1170)

  [ pachulo ]
  * sources: add optional "source-checksum" property (#980)

  [ Colin Watson ]
  * godeps plugin: add git to build-packages. (#1179)

 -- Sergio Schvezov   Thu, 23 Mar 2017
16:11:14 -0300

** Changed in: snapcraft (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/1675391

Title:
   [SRU] New stable micro release 2.28

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

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

  The list of bugs and features in this release are defined at
  https://launchpad.net/snapcraft/+milestone/2.28 and
  https://launchpad.net/snapcraft/+milestone/2.28

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

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

[Group.of.nepali.translators] [Bug 1650522] Re: walinuxagent 2.1.5 needs to have AutoUpdate On

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.6-0ubuntu1~16.04.1

---
walinuxagent (2.2.6-0ubuntu1~16.04.1) xenial; urgency=medium

  * Backport zesty version to xenial.
  * New upstream release (LP: #1661750)
  * debian/control:
- Change the maintainer to Ubuntu Developers (LP: #1657528)
- Add the dependency of isc-dhcp-client as our maintainer scripts assume
  it's installed (LP: #1673862).
- Add trailing commas to dependencies, add whitespaces.
  * Rename ephemeral-disk-warning.sh to ephemeral-disk-warning (lintian error).
  * debian/docs:
- Remove LICENSE.txt as it's redundant.
  * debian/postinst:
- Stop checking for update-initramfs existence using the absolute path, use
  the 'command' command instead to make lintian happy.
  * Remove debian/patches/disable-auto-update.patch:
- We now ship with auto-updates enabled (LP: #1650522).
  * debian/maintscript:
- Add a maintscript to rename the old logrotate file on upgrade from an
  ancient version of walinuxagent (LP: #1673152).

 -- Łukasz 'sil2100' Zemczak   Wed, 15 Mar
2017 10:19:34 +0100

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

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

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

Title:
  walinuxagent 2.1.5 needs to have AutoUpdate On

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  Fix Released
Status in walinuxagent source package in Xenial:
  Fix Released
Status in walinuxagent source package in Yakkety:
  Fix Released

Bug description:
  Re-using the same bug for release with 2.2.6 to get the auto-updates
  enabled.

  [Original Description]

  From Daniel Sol:

  "
  I was working on one of my 16.10 servers today and I was trying to get
  the Linux agent to take it latest goal state update and it was not
  doing anything. I looked in ./etc/waagent.conf and found it was disabled:

  # Enable or disable self-update, default is enabled
  AutoUpdate.Enabled=n
  AutoUpdate.GAFamily=Prod
  "

  After some discussion we have agreed Ubuntu packages for yakkety,
  xenial & trusty should enable AutoUpdate.

  [SRU TEMPLATE]

  [Impact]

  Version 2.1.5 is already the latest walinuxagent version for yakkety,
  xenial & trusty. This change just turns AutoUpdates on, which were set
  to off by the ubuntu packaging process (being on by default upstream)

  [Test case 1]: Upgrade testing
  1.) Launch instance on Azure
  2.) Upgrade walinuxagent from -proposed
  3.) Confirm that "waagent" is running, check /var/log/waagent.log
  4.) Reboot, repeat step 3
  5.) Capture instance and provsion new instances; repeat step 3

  [Test Case 2]: New instance
  1.) Build new cloud image from -proposed
  2.) Boot instance
  3.) Confirm that instance provisioned

  More on the test plan:
  https://wiki.ubuntu.com/walinuxagentUpdates

  [Upstream Testing]
  The Canonical Cloud Image team has been working with Microsoft to ensure that 
this package is well tested. Validation will be performed by both Microsoft and 
the Canonical Cloud Image team.

  [Regression Potential]
  Currently, WALinuxAgent uses Python 2. With the 2.1.x branch, WALinuxAgent 
started using Python 3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1650522/+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 1661750] Re: WaLinuxAgent 2.2.6

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.6-0ubuntu1~16.04.1

---
walinuxagent (2.2.6-0ubuntu1~16.04.1) xenial; urgency=medium

  * Backport zesty version to xenial.
  * New upstream release (LP: #1661750)
  * debian/control:
- Change the maintainer to Ubuntu Developers (LP: #1657528)
- Add the dependency of isc-dhcp-client as our maintainer scripts assume
  it's installed (LP: #1673862).
- Add trailing commas to dependencies, add whitespaces.
  * Rename ephemeral-disk-warning.sh to ephemeral-disk-warning (lintian error).
  * debian/docs:
- Remove LICENSE.txt as it's redundant.
  * debian/postinst:
- Stop checking for update-initramfs existence using the absolute path, use
  the 'command' command instead to make lintian happy.
  * Remove debian/patches/disable-auto-update.patch:
- We now ship with auto-updates enabled (LP: #1650522).
  * debian/maintscript:
- Add a maintscript to rename the old logrotate file on upgrade from an
  ancient version of walinuxagent (LP: #1673152).

 -- Łukasz 'sil2100' Zemczak   Wed, 15 Mar
2017 10:19:34 +0100

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

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

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

Title:
  WaLinuxAgent 2.2.6

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  Fix Released
Status in walinuxagent source package in Xenial:
  Fix Released
Status in walinuxagent source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The new version introduces a lot of useful fixes. As with each
  release, we want to include the latest agent on all of our supported
  series.

  [Test Case]

  1.) Build new cloud image with -proposed package
  2.) Boot instance
  3.) Confirm that instance provisioned
  4.) Run standard tests and regression tests
  5.) Repeat from step 2 for all other Azure VM Sizes.

  All the preformed test cases can be found on the dedicated wikipage
  here: https://wiki.ubuntu.com/walinuxagentUpdates

  [Regression Potential]

  As with each new upstream release there is always a risk of
  regressions, especially when the minor version gets bumped.

  Original description:

  
  Hi,
  It gives me great pleasure to announce another release for WALA, 2.2.6.

  The details are below and the download can be found here.

  I also owe you an apology, we did release 2.2.3, about 1 week ago,
  however I was backlogged on email and never sent my usual introduction
  of the release. We have now just released 2.2.4 which contained some
  additional fixes, I will raise a bug for this.

  We would like you to take the 2.2.6 version and test it within your
  images, please can you file any bugs in Github, as this is monitored
  by our dev team.

  If you have any questions please reach out to me directly or raise it
  through Github.

  Thank you for all your contributions here!

  Dan & VmAgent Team

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1661750/+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 1657528] Re: Maintainer field in debian/control is incorrect

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.6-0ubuntu1~16.04.1

---
walinuxagent (2.2.6-0ubuntu1~16.04.1) xenial; urgency=medium

  * Backport zesty version to xenial.
  * New upstream release (LP: #1661750)
  * debian/control:
- Change the maintainer to Ubuntu Developers (LP: #1657528)
- Add the dependency of isc-dhcp-client as our maintainer scripts assume
  it's installed (LP: #1673862).
- Add trailing commas to dependencies, add whitespaces.
  * Rename ephemeral-disk-warning.sh to ephemeral-disk-warning (lintian error).
  * debian/docs:
- Remove LICENSE.txt as it's redundant.
  * debian/postinst:
- Stop checking for update-initramfs existence using the absolute path, use
  the 'command' command instead to make lintian happy.
  * Remove debian/patches/disable-auto-update.patch:
- We now ship with auto-updates enabled (LP: #1650522).
  * debian/maintscript:
- Add a maintscript to rename the old logrotate file on upgrade from an
  ancient version of walinuxagent (LP: #1673152).

 -- Łukasz 'sil2100' Zemczak   Wed, 15 Mar
2017 10:19:34 +0100

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

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

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

Title:
  Maintainer field in debian/control is incorrect

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  Fix Released
Status in walinuxagent source package in Xenial:
  Fix Released
Status in walinuxagent source package in Yakkety:
  Fix Released

Bug description:
  [ Impact ]

  No particular impact on users but since for walinuxagent we always
  keep all the supported series in sync, we want to SRU this change as
  well.

  [ Test Case ]

  None, packaging change.

  [ Regression Potential ]

  None.

  Original description:

  The current debian/control in Zesty says:

  > Maintainer: Ben Howard 

  I think this is wrong now? Ubuntu packages are team maintained anyway.
  I don't know if we have a particular policy on what the maintainer
  field should say. It should probably just point to some appropriate
  mailing list, similar to how update-maintainer does it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1657528/+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 1673862] Re: Missing package dependency on isc-dhcp-client

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.6-0ubuntu1~16.04.1

---
walinuxagent (2.2.6-0ubuntu1~16.04.1) xenial; urgency=medium

  * Backport zesty version to xenial.
  * New upstream release (LP: #1661750)
  * debian/control:
- Change the maintainer to Ubuntu Developers (LP: #1657528)
- Add the dependency of isc-dhcp-client as our maintainer scripts assume
  it's installed (LP: #1673862).
- Add trailing commas to dependencies, add whitespaces.
  * Rename ephemeral-disk-warning.sh to ephemeral-disk-warning (lintian error).
  * debian/docs:
- Remove LICENSE.txt as it's redundant.
  * debian/postinst:
- Stop checking for update-initramfs existence using the absolute path, use
  the 'command' command instead to make lintian happy.
  * Remove debian/patches/disable-auto-update.patch:
- We now ship with auto-updates enabled (LP: #1650522).
  * debian/maintscript:
- Add a maintscript to rename the old logrotate file on upgrade from an
  ancient version of walinuxagent (LP: #1673152).

 -- Łukasz 'sil2100' Zemczak   Wed, 15 Mar
2017 10:19:34 +0100

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

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

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

Title:
  Missing package dependency on isc-dhcp-client

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  Fix Released
Status in walinuxagent source package in Xenial:
  Fix Released
Status in walinuxagent source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The isc-dhcp-client package is pulled in as part of ubuntu-minimal. On
  systems where ubuntu-minimal is not installed (like on certain
  chroots), the walinuxagent package fails to install as the maintainer
  scripts implicitly require /etc/dhcp/dhclient.conf to exist.

  sed: can't read /etc/dhcp/dhclient.conf: No such file or directory

  [Test Case]

  Install the package with the added dependency on a system without isc-
  dhcp-client installed and check if it installs correctly.

  [Regression Potential]

  There should be no regression potential with this change as the new
  dependency is present on all everyday Ubuntu systems and azure images.
  Currently the package is used only on ubuntu-minimal environments so
  everything works as expected - the addition of this package only makes
  it now possible to install on systems without ubuntu-minimal
  installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1673862/+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 1673152] Re: duplicate logrotate files/entries

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.6-0ubuntu1~16.04.1

---
walinuxagent (2.2.6-0ubuntu1~16.04.1) xenial; urgency=medium

  * Backport zesty version to xenial.
  * New upstream release (LP: #1661750)
  * debian/control:
- Change the maintainer to Ubuntu Developers (LP: #1657528)
- Add the dependency of isc-dhcp-client as our maintainer scripts assume
  it's installed (LP: #1673862).
- Add trailing commas to dependencies, add whitespaces.
  * Rename ephemeral-disk-warning.sh to ephemeral-disk-warning (lintian error).
  * debian/docs:
- Remove LICENSE.txt as it's redundant.
  * debian/postinst:
- Stop checking for update-initramfs existence using the absolute path, use
  the 'command' command instead to make lintian happy.
  * Remove debian/patches/disable-auto-update.patch:
- We now ship with auto-updates enabled (LP: #1650522).
  * debian/maintscript:
- Add a maintscript to rename the old logrotate file on upgrade from an
  ancient version of walinuxagent (LP: #1673152).

 -- Łukasz 'sil2100' Zemczak   Wed, 15 Mar
2017 10:19:34 +0100

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

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

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

Title:
  duplicate logrotate files/entries

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  Fix Released
Status in walinuxagent source package in Xenial:
  Fix Released
Status in walinuxagent source package in Yakkety:
  Fix Released

Bug description:
  [ Impact ]

  We always keep all the supported series in sync, we want to SRU this
  change as well. In certain cases, when upgrading from a very old
  walinuxagent, the logrotate files are duplicate - which is never a
  good thing.

  [ Test Case ]

  Easiest way would be to install an ancient trusty walinuxagent package
  and then upgrade to the latest proposed one and check if the old
  logrotate configuration file is still present.

   * Download walinuxagent 2.0.8-0ubuntu1~14.04.0
   * Install the package through dpkg (possibly dpkg --force-all -i since 
otherwise the old version will not install)
   * Check if /etc/logrotate.d/waagent is present
   * Upgrade walinuxagent to 2.2.6
   * Make sure that /etc/logrotate.d/waagent is gone and 
/etc/logrotate.d/waagent.logrotate is present

  [ Regression Potential ]

  The logrotate configuration can be lost or invalid - but if that would
  happen then the bug will fail verification.

  Original description:

  I am getting the following errors from cron after upgrading my VM to 
walinuxagent 2.2.2-0ubuntu0~14.04.1 (the previous version was 
2.0.8-0ubuntu1~14.04.0).
  /etc/cron.daily/logrotate:
  error: waagent.logrotate:1 duplicate log entry for /var/log/waagent.log

  Indeed, there are two duplicate logrotate files that both appear to belong to 
the walinuxagent package:
  $ dpkg -S /etc/logrotate.d/waagent*
  walinuxagent: /etc/logrotate.d/waagent
  walinuxagent: /etc/logrotate.d/waagent.logrotate
  $ cmp /etc/logrotate.d/waagent*
  $ cat /etc/logrotate.d/waagent
  /var/log/waagent.log {
  compress
  monthly
  rotate 6
  notifempty
  missingok
  }

  I'm on 14.04 LTS:
  $ lsb_release -rd
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1673152/+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 1650522] Re: walinuxagent 2.1.5 needs to have AutoUpdate On

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.6-0ubuntu1~16.10.1

---
walinuxagent (2.2.6-0ubuntu1~16.10.1) yakkety; urgency=medium

  * Backport zesty version to yakkety.
  * New upstream release (LP: #1661750).
  * debian/control:
- Change the maintainer to Ubuntu Developers (LP: #1657528).
- Add the dependency of isc-dhcp-client as our maintainer scripts assume
  it's installed (LP: #1673862).
- Add trailing commas to dependencies, add whitespaces.
  * Rename ephemeral-disk-warning.sh to ephemeral-disk-warning (lintian error).
  * debian/docs:
- Remove LICENSE.txt as it's redundant.
  * debian/postinst:
- Stop checking for update-initramfs existence using the absolute path, use
  the 'command' command instead to make lintian happy.
  * Remove debian/patches/disable-auto-update.patch:
- We now ship with auto-updates enabled (LP: #1650522).
  * debian/maintscript:
- Add a maintscript to rename the old logrotate file on upgrade from an
  ancient version of walinuxagent (LP: #1673152).

 -- Łukasz 'sil2100' Zemczak   Wed, 15 Mar
2017 10:19:34 +0100

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

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

Title:
  walinuxagent 2.1.5 needs to have AutoUpdate On

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  Fix Released
Status in walinuxagent source package in Xenial:
  Fix Released
Status in walinuxagent source package in Yakkety:
  Fix Released

Bug description:
  Re-using the same bug for release with 2.2.6 to get the auto-updates
  enabled.

  [Original Description]

  From Daniel Sol:

  "
  I was working on one of my 16.10 servers today and I was trying to get
  the Linux agent to take it latest goal state update and it was not
  doing anything. I looked in ./etc/waagent.conf and found it was disabled:

  # Enable or disable self-update, default is enabled
  AutoUpdate.Enabled=n
  AutoUpdate.GAFamily=Prod
  "

  After some discussion we have agreed Ubuntu packages for yakkety,
  xenial & trusty should enable AutoUpdate.

  [SRU TEMPLATE]

  [Impact]

  Version 2.1.5 is already the latest walinuxagent version for yakkety,
  xenial & trusty. This change just turns AutoUpdates on, which were set
  to off by the ubuntu packaging process (being on by default upstream)

  [Test case 1]: Upgrade testing
  1.) Launch instance on Azure
  2.) Upgrade walinuxagent from -proposed
  3.) Confirm that "waagent" is running, check /var/log/waagent.log
  4.) Reboot, repeat step 3
  5.) Capture instance and provsion new instances; repeat step 3

  [Test Case 2]: New instance
  1.) Build new cloud image from -proposed
  2.) Boot instance
  3.) Confirm that instance provisioned

  More on the test plan:
  https://wiki.ubuntu.com/walinuxagentUpdates

  [Upstream Testing]
  The Canonical Cloud Image team has been working with Microsoft to ensure that 
this package is well tested. Validation will be performed by both Microsoft and 
the Canonical Cloud Image team.

  [Regression Potential]
  Currently, WALinuxAgent uses Python 2. With the 2.1.x branch, WALinuxAgent 
started using Python 3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1650522/+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 1657528] Re: Maintainer field in debian/control is incorrect

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.6-0ubuntu1~16.10.1

---
walinuxagent (2.2.6-0ubuntu1~16.10.1) yakkety; urgency=medium

  * Backport zesty version to yakkety.
  * New upstream release (LP: #1661750).
  * debian/control:
- Change the maintainer to Ubuntu Developers (LP: #1657528).
- Add the dependency of isc-dhcp-client as our maintainer scripts assume
  it's installed (LP: #1673862).
- Add trailing commas to dependencies, add whitespaces.
  * Rename ephemeral-disk-warning.sh to ephemeral-disk-warning (lintian error).
  * debian/docs:
- Remove LICENSE.txt as it's redundant.
  * debian/postinst:
- Stop checking for update-initramfs existence using the absolute path, use
  the 'command' command instead to make lintian happy.
  * Remove debian/patches/disable-auto-update.patch:
- We now ship with auto-updates enabled (LP: #1650522).
  * debian/maintscript:
- Add a maintscript to rename the old logrotate file on upgrade from an
  ancient version of walinuxagent (LP: #1673152).

 -- Łukasz 'sil2100' Zemczak   Wed, 15 Mar
2017 10:19:34 +0100

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

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

Title:
  Maintainer field in debian/control is incorrect

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  Fix Released
Status in walinuxagent source package in Xenial:
  Fix Released
Status in walinuxagent source package in Yakkety:
  Fix Released

Bug description:
  [ Impact ]

  No particular impact on users but since for walinuxagent we always
  keep all the supported series in sync, we want to SRU this change as
  well.

  [ Test Case ]

  None, packaging change.

  [ Regression Potential ]

  None.

  Original description:

  The current debian/control in Zesty says:

  > Maintainer: Ben Howard 

  I think this is wrong now? Ubuntu packages are team maintained anyway.
  I don't know if we have a particular policy on what the maintainer
  field should say. It should probably just point to some appropriate
  mailing list, similar to how update-maintainer does it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1657528/+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 1661750] Re: WaLinuxAgent 2.2.6

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.6-0ubuntu1~16.10.1

---
walinuxagent (2.2.6-0ubuntu1~16.10.1) yakkety; urgency=medium

  * Backport zesty version to yakkety.
  * New upstream release (LP: #1661750).
  * debian/control:
- Change the maintainer to Ubuntu Developers (LP: #1657528).
- Add the dependency of isc-dhcp-client as our maintainer scripts assume
  it's installed (LP: #1673862).
- Add trailing commas to dependencies, add whitespaces.
  * Rename ephemeral-disk-warning.sh to ephemeral-disk-warning (lintian error).
  * debian/docs:
- Remove LICENSE.txt as it's redundant.
  * debian/postinst:
- Stop checking for update-initramfs existence using the absolute path, use
  the 'command' command instead to make lintian happy.
  * Remove debian/patches/disable-auto-update.patch:
- We now ship with auto-updates enabled (LP: #1650522).
  * debian/maintscript:
- Add a maintscript to rename the old logrotate file on upgrade from an
  ancient version of walinuxagent (LP: #1673152).

 -- Łukasz 'sil2100' Zemczak   Wed, 15 Mar
2017 10:19:34 +0100

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

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

Title:
  WaLinuxAgent 2.2.6

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  Fix Released
Status in walinuxagent source package in Xenial:
  Fix Released
Status in walinuxagent source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The new version introduces a lot of useful fixes. As with each
  release, we want to include the latest agent on all of our supported
  series.

  [Test Case]

  1.) Build new cloud image with -proposed package
  2.) Boot instance
  3.) Confirm that instance provisioned
  4.) Run standard tests and regression tests
  5.) Repeat from step 2 for all other Azure VM Sizes.

  All the preformed test cases can be found on the dedicated wikipage
  here: https://wiki.ubuntu.com/walinuxagentUpdates

  [Regression Potential]

  As with each new upstream release there is always a risk of
  regressions, especially when the minor version gets bumped.

  Original description:

  
  Hi,
  It gives me great pleasure to announce another release for WALA, 2.2.6.

  The details are below and the download can be found here.

  I also owe you an apology, we did release 2.2.3, about 1 week ago,
  however I was backlogged on email and never sent my usual introduction
  of the release. We have now just released 2.2.4 which contained some
  additional fixes, I will raise a bug for this.

  We would like you to take the 2.2.6 version and test it within your
  images, please can you file any bugs in Github, as this is monitored
  by our dev team.

  If you have any questions please reach out to me directly or raise it
  through Github.

  Thank you for all your contributions here!

  Dan & VmAgent Team

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1661750/+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 1673152] Re: duplicate logrotate files/entries

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.6-0ubuntu1~16.10.1

---
walinuxagent (2.2.6-0ubuntu1~16.10.1) yakkety; urgency=medium

  * Backport zesty version to yakkety.
  * New upstream release (LP: #1661750).
  * debian/control:
- Change the maintainer to Ubuntu Developers (LP: #1657528).
- Add the dependency of isc-dhcp-client as our maintainer scripts assume
  it's installed (LP: #1673862).
- Add trailing commas to dependencies, add whitespaces.
  * Rename ephemeral-disk-warning.sh to ephemeral-disk-warning (lintian error).
  * debian/docs:
- Remove LICENSE.txt as it's redundant.
  * debian/postinst:
- Stop checking for update-initramfs existence using the absolute path, use
  the 'command' command instead to make lintian happy.
  * Remove debian/patches/disable-auto-update.patch:
- We now ship with auto-updates enabled (LP: #1650522).
  * debian/maintscript:
- Add a maintscript to rename the old logrotate file on upgrade from an
  ancient version of walinuxagent (LP: #1673152).

 -- Łukasz 'sil2100' Zemczak   Wed, 15 Mar
2017 10:19:34 +0100

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

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

Title:
  duplicate logrotate files/entries

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  Fix Released
Status in walinuxagent source package in Xenial:
  Fix Released
Status in walinuxagent source package in Yakkety:
  Fix Released

Bug description:
  [ Impact ]

  We always keep all the supported series in sync, we want to SRU this
  change as well. In certain cases, when upgrading from a very old
  walinuxagent, the logrotate files are duplicate - which is never a
  good thing.

  [ Test Case ]

  Easiest way would be to install an ancient trusty walinuxagent package
  and then upgrade to the latest proposed one and check if the old
  logrotate configuration file is still present.

   * Download walinuxagent 2.0.8-0ubuntu1~14.04.0
   * Install the package through dpkg (possibly dpkg --force-all -i since 
otherwise the old version will not install)
   * Check if /etc/logrotate.d/waagent is present
   * Upgrade walinuxagent to 2.2.6
   * Make sure that /etc/logrotate.d/waagent is gone and 
/etc/logrotate.d/waagent.logrotate is present

  [ Regression Potential ]

  The logrotate configuration can be lost or invalid - but if that would
  happen then the bug will fail verification.

  Original description:

  I am getting the following errors from cron after upgrading my VM to 
walinuxagent 2.2.2-0ubuntu0~14.04.1 (the previous version was 
2.0.8-0ubuntu1~14.04.0).
  /etc/cron.daily/logrotate:
  error: waagent.logrotate:1 duplicate log entry for /var/log/waagent.log

  Indeed, there are two duplicate logrotate files that both appear to belong to 
the walinuxagent package:
  $ dpkg -S /etc/logrotate.d/waagent*
  walinuxagent: /etc/logrotate.d/waagent
  walinuxagent: /etc/logrotate.d/waagent.logrotate
  $ cmp /etc/logrotate.d/waagent*
  $ cat /etc/logrotate.d/waagent
  /var/log/waagent.log {
  compress
  monthly
  rotate 6
  notifempty
  missingok
  }

  I'm on 14.04 LTS:
  $ lsb_release -rd
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1673152/+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 1673862] Re: Missing package dependency on isc-dhcp-client

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.6-0ubuntu1~16.10.1

---
walinuxagent (2.2.6-0ubuntu1~16.10.1) yakkety; urgency=medium

  * Backport zesty version to yakkety.
  * New upstream release (LP: #1661750).
  * debian/control:
- Change the maintainer to Ubuntu Developers (LP: #1657528).
- Add the dependency of isc-dhcp-client as our maintainer scripts assume
  it's installed (LP: #1673862).
- Add trailing commas to dependencies, add whitespaces.
  * Rename ephemeral-disk-warning.sh to ephemeral-disk-warning (lintian error).
  * debian/docs:
- Remove LICENSE.txt as it's redundant.
  * debian/postinst:
- Stop checking for update-initramfs existence using the absolute path, use
  the 'command' command instead to make lintian happy.
  * Remove debian/patches/disable-auto-update.patch:
- We now ship with auto-updates enabled (LP: #1650522).
  * debian/maintscript:
- Add a maintscript to rename the old logrotate file on upgrade from an
  ancient version of walinuxagent (LP: #1673152).

 -- Łukasz 'sil2100' Zemczak   Wed, 15 Mar
2017 10:19:34 +0100

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

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

Title:
  Missing package dependency on isc-dhcp-client

Status in walinuxagent package in Ubuntu:
  Fix Released
Status in walinuxagent source package in Trusty:
  Fix Released
Status in walinuxagent source package in Xenial:
  Fix Released
Status in walinuxagent source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The isc-dhcp-client package is pulled in as part of ubuntu-minimal. On
  systems where ubuntu-minimal is not installed (like on certain
  chroots), the walinuxagent package fails to install as the maintainer
  scripts implicitly require /etc/dhcp/dhclient.conf to exist.

  sed: can't read /etc/dhcp/dhclient.conf: No such file or directory

  [Test Case]

  Install the package with the added dependency on a system without isc-
  dhcp-client installed and check if it installs correctly.

  [Regression Potential]

  There should be no regression potential with this change as the new
  dependency is present on all everyday Ubuntu systems and azure images.
  Currently the package is used only on ubuntu-minimal environments so
  everything works as expected - the addition of this package only makes
  it now possible to install on systems without ubuntu-minimal
  installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1673862/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[Dimitri John Ledkov]

As far as I can tell the patch for hwdb sensitivity for Dell Latitude
E7470 is shipped in zesty now.

Is anything else required to have this resolved in zesty? Or hwdb update
is all that is needed here? If that is the case, then we can remove all
the other packages marked as affected and simply SRU the hwdb update.

** Also affects: xserver-xorg-input-synaptics (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

** Also affects: xserver-xorg-input-synaptics (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Changed in: systemd (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/1590590

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in xserver-xorg-input-synaptics source package in Xenial:
  New
Status in linux source package in Yakkety:
  New
Status in systemd source package in Yakkety:
  New
Status in xserver-xorg-input-synaptics source package in Yakkety:
  New

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

[Dan Streetman]

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

Status in linux package in Ubuntu:
  Triaged
Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Triaged
Status in linux-aws source package in Xenial:
  Fix Committed

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:

[Group.of.nepali.translators] [Bug 1668129] Re: Amazon I3 Instance Buffer I/O error on dev nvme0n1

[Amanpreet Singh]

I think I changed the status by mistake (Did not know I could do that),
and I'm unable to revert it :/

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

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

Title:
  Amazon I3 Instance Buffer I/O error on dev nvme0n1

Status in linux package in Ubuntu:
  Triaged
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux-aws source package in Xenial:
  Fix Committed

Bug description:
  On the AWS i3 instance class - when putting the new NVME storage disks
  under high IO load - seeing data corruption and errors in dmesg

  [  662.884390] blk_update_request: I/O error, dev nvme0n1, sector 120063912
  [  662.887824] Buffer I/O error on dev nvme0n1, logical block 14971093, lost 
async page write
  [  662.891254] Buffer I/O error on dev nvme0n1, logical block 14971094, lost 
async page write
  [  662.895591] Buffer I/O error on dev nvme0n1, logical block 14971095, lost 
async page write
  [  662.899873] Buffer I/O error on dev nvme0n1, logical block 14971096, lost 
async page write
  [  662.904179] Buffer I/O error on dev nvme0n1, logical block 14971097, lost 
async page write
  [  662.908458] Buffer I/O error on dev nvme0n1, logical block 14971098, lost 
async page write
  [  662.912287] Buffer I/O error on dev nvme0n1, logical block 14971099, lost 
async page write
  [  662.916047] Buffer I/O error on dev nvme0n1, logical block 14971100, lost 
async page write
  [  662.920285] Buffer I/O error on dev nvme0n1, logical block 14971101, lost 
async page write
  [  662.924565] Buffer I/O error on dev nvme0n1, logical block 14971102, lost 
async page write
  [  663.645530] blk_update_request: I/O error, dev nvme0n1, sector 120756912
  
  [ 1012.752265] blk_update_request: I/O error, dev nvme0n1, sector 3744
  [ 1012.755396] buffer_io_error: 194552 callbacks suppressed
  [ 1012.755398] Buffer I/O error on dev nvme0n1, logical block 20, lost async 
page write
  [ 1012.759248] Buffer I/O error on dev nvme0n1, logical block 21, lost async 
page write
  [ 1012.763368] Buffer I/O error on dev nvme0n1, logical block 22, lost async 
page write
  [ 1012.767271] Buffer I/O error on dev nvme0n1, logical block 23, lost async 
page write
  [ 1012.771314] Buffer I/O error on dev nvme0n1, logical block 24, lost async 
page write

  Able to replicate this with a bonnie++ stress test.

  bonnie++ -d /mnt/test/ -r 1000

  Linux i-0d76e144d85f487cf 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 02:12 seq
   crw-rw 1 root audio 116, 33 Feb 27 02:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-bc62b2aa
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: i3.2xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=cfda0544-9803-41e7-badb-43563085ff3a ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/12/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
 

[Group.of.nepali.translators] [Bug 1673357] Re: Munin core plugin "if_" doesn't work

[Robie Basak]

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

** Also affects: munin (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/1673357

Title:
  Munin core plugin "if_" doesn't work

Status in munin package in Ubuntu:
  Fix Released
Status in munin source package in Xenial:
  New
Status in munin source package in Yakkety:
  New

Bug description:
  The munin core plugin for network interface traffic metric, "if_",
  registers invalid values on the master side because the configuration
  phase does not report valid network speed interface. Reports negative
  range (up.max is negative, while up.min is 0), and thus registers as
  NaN by the master, even though the node itself sends valid numbers:

  # munin-run if_ens3 config
  .
  .
  .
  up.min 0
  up.max -100
  up.info Traffic of the ens3 interface. Maximum speed is -1 Mb/s.
  down.max -100

  
  # munin-run if_ens3

  down.value 107758093
  up.value 77710387

  
  See also: https://github.com/mail-in-a-box/mailinabox/issues/896

  The bug has been fixed upstream:

  https://github.com/munin-
  monitoring/munin/commit/290d5ac2be02ced4d09fda68dc561fcf082c9cbf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1673357/+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 1649925] Re: Support for the G200eW3 server chipset needed

[Robie Basak]

Presumably this is also Won't Fix for the proposed SRUs then? Marking as
such and unsubscribing ~ubuntu-sponsors.

** Changed in: xserver-xorg-video-mga (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: xserver-xorg-video-mga (Ubuntu Yakkety)
   Status: New => Won't Fix

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

Title:
  Support for the G200eW3 server chipset needed

Status in HWE Next:
  Won't Fix
Status in xserver-xorg-video-mga package in Ubuntu:
  Won't Fix
Status in xserver-xorg-video-mga source package in Xenial:
  Won't Fix
Status in xserver-xorg-video-mga source package in Yakkety:
  Won't Fix

Bug description:
  Available in upstream git at

  https://cgit.freedesktop.org/xorg/driver/xf86-video-
  mga/commit/?id=12781f2e3deb7f6d86fde53134384996a6004894

  but not in any releases yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-mga 1:1.6.4-1build2
  ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Dec 14 10:23:13 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: rtl8812au, 4.3.8.12175.20140902+dfsg: added
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9]
  InstallationDate: Installed on 2016-01-06 (342 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: LENOVO 3443CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=1f36140c-def2-49da-a1f8-0e14cfc2d84c ro quiet splash 
intel_pstate=disable vt.handoff=7
  SourcePackage: xserver-xorg-video-mga
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
  Identifier  "Configured Video Device"
  Driver "modesetting"
  #Option "TearFree" "true" 
   EndSection
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3443CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET93WW(2.53):bd02/04/2013:svnLENOVO:pn3443CTO:pvrThinkPadX1Carbon:rvnLENOVO:rn3443CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3443CTO
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.73+git20161127.23d10b82-0ubuntu0ricotz~xenial
  version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.2-1ubuntu1~xenial0
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.2-1ubuntu1~xenial0
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.8.99+git20161127.487aa62a-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20161127.bde94605-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git20161127.1516d35b-0ubuntu0ricotz~xenial
  xserver.bootTime: Wed Dec 14 09:59:26 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1649925/+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 1506166] Re: Bracketed paste should be per-terminal [PATCH]

[Robie Basak]

Thank you for the patch and sorry for the delay. We're making an effort
to clear out languishing items in the sponsorship queue today.

vte needs fixing in Zesty before we can fix it in older releases. Please
see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

We also need a working test case for the vte (as opposed to vte3) case.

But I'm trying to get an initial response to as many outstanding
requests today as I can, so I'll move on for now. Please try to follow
the SRU procedure if you can, provide a test case for this fix, provide
debdiffs for all of Zesty, Yakkety, Xenial and if you wish Trusty, and
then resubscribe ~ubuntu-sponsors to the bug when done.

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

** Also affects: vte3 (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/1506166

Title:
  Bracketed paste should be per-terminal [PATCH]

Status in Gnome Virtual Terminal Emulator:
  Fix Released
Status in vte package in Ubuntu:
  Confirmed
Status in vte3 package in Ubuntu:
  Fix Released
Status in vte source package in Trusty:
  Confirmed
Status in vte3 source package in Trusty:
  Fix Released
Status in vte source package in Xenial:
  Confirmed
Status in vte source package in Yakkety:
  New
Status in vte3 source package in Yakkety:
  New

Bug description:
  [Impact]

  Bracketed paste mode (\e[?2004h) should be per-terminal (as it is for
  xterm), not per-screen. This was fixed upstream for vte3 0.36.2,
  however Trusty ships vte3 0.34.2 and it didn't make it:

  https://bugzilla.gnome.org/show_bug.cgi?id=729533

  This bug is causing annoying garbage appended to every paste in mc:

  https://www.midnight-commander.org/ticket/3207

  I have backported the fix to Trusty, tested it in my PPA and would
  appreciate if someone could sponsor an upload in updates, since Trusty
  is LTS after all.

  [Test Case]

  Select some text ("test") and copy it into the clipboard buffer. After
  that, install mc if you don't have it already and start it:

  sudo apt-get install mc
  mc

  Press CTRL+O to swap the panels, right click with the mouse button and
  pick "Paste" from the context menu. You will see that "~0test~1" is
  pasted into the console instead of "test" as it should be.

  For more details, see the bug report on mc bug tracker referenced
  above.

  [Regression Potential]

  The patch is taken from the vte3 bug tracker; it has been in trunk for
  more than a year and is contained in vte3 0.36.2+ releases. Nobody has
  reported any problems caused by this change so far...

To manage notifications about this bug go to:
https://bugs.launchpad.net/vte/+bug/1506166/+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 1590799] Re: nfs-kernel-server does not start because of dependency failure

[Louis Bouchard]

Adding a Trusty task & marking it invalid so we know that it doesn't
concern Trusty (no systemd there)

** Also affects: nfs-utils (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: nfs-utils (Ubuntu Trusty)
   Status: New => Invalid

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

Title:
  nfs-kernel-server does not start because of dependency failure

Status in nfs-utils package in Ubuntu:
  Fix Released
Status in nfs-utils source package in Trusty:
  Invalid
Status in nfs-utils source package in Xenial:
  In Progress
Status in nfs-utils source package in Yakkety:
  In Progress
Status in nfs-utils source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * nfs-mountd doesn't get started because of a race condition happening when 
rpcbind.socket is not specified as a needed service for it to start.
   * nfs-server using rpcbind.target instead of using rpcbind.socket. Target 
should not be used (Comment #24)

  [Test Case]

   * Install nfs-kernel-server inside a xenial lxc guest and restart it until 
nfs-mountd doesn't start complaining on rpc error.
   * Comment #25

  [Regression Potential]

   * Cons: Systemd dependencies could brake for nfs-server and nfs-mountd.
   * Pros: Patches have been accepted upstream (and tested).

  [Other Info]
   
  # Original Bug Description

  Immediately after boot:

  root@feynmann:~# systemctl status nfs-kernel-server
  ● nfs-server.service - NFS server and services
     Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor 
preset: enabled)
     Active: inactive (dead)

  Jun 09 14:35:47 feynmann systemd[1]: Dependency failed for NFS server and 
services.
  Jun 09 14:35:47 feynmann systemd[1]: nfs-server.service: Job 
nfs-server.service/start failed

  root@feynmann:~# systemctl status nfs-mountd.service
  ● nfs-mountd.service - NFS Mount Daemon
     Loaded: loaded (/lib/systemd/system/nfs-mountd.service; static; vendor 
preset: enabled)
     Active: failed (Result: exit-code) since Thu 2016-06-09 14:35:47 BST; 7min 
ago
    Process: 1321 ExecStart=/usr/sbin/rpc.mountd $RPCMOUNTDARGS (code=exited, 
status=1/FAILURE)

  Jun 09 14:35:47 feynmann systemd[1]: Starting NFS Mount Daemon...
  Jun 09 14:35:47 feynmann rpc.mountd[1321]: mountd: could not create listeners
  Jun 09 14:35:47 feynmann systemd[1]: nfs-mountd.service: Control process 
exited, code=exited
  Jun 09 14:35:47 feynmann systemd[1]: Failed to start NFS Mount Daemon.
  Jun 09 14:35:47 feynmann systemd[1]: nfs-mountd.service: Unit entered failed 
state.
  Jun 09 14:35:47 feynmann systemd[1]: nfs-mountd.service: Failed with result 
'exit-code'.

  root@feynmann:~# systemctl list-dependencies nfs-kernel-server
  nfs-kernel-server.service
  ● ├─auth-rpcgss-module.service
  ● ├─nfs-config.service
  ● ├─nfs-idmapd.service
  ● ├─nfs-mountd.service
  ● ├─proc-fs-nfsd.mount
  ● ├─rpc-svcgssd.service
  ● ├─system.slice
  ● ├─network.target
  ● └─rpcbind.target
  ●   └─rpcbind.service

  root@feynmann:~# systemctl list-dependencies nfs-mountd.service
  nfs-mountd.service
  ● ├─nfs-config.service
  ● ├─nfs-server.service
  ● ├─proc-fs-nfsd.mount
  ● └─system.slice
  root@feynmann:~#

  root@feynmann:~# lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  root@feynmann:~# apt-cache policy nfs-kernel-server
  nfs-kernel-server:
    Installed: 1:1.2.8-9ubuntu12
    Candidate: 1:1.2.8-9ubuntu12
    Version table:
   *** 1:1.2.8-9ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Additional comments:

  1. There seems to be a circular dependency between nfs-mountd and 
nfs-kernel-server
  2. I can get it working by changing the AFter,Requires in 
/lib/ssystemd/system/nfs-{mountd|server}.service files. I have managed to get 
nfs-kernel-server to start but not nfs-mountd.
  3. /usr/lib/systemd/scripts/nfs-utils_env.sh references 
/etc/sysconfig/nfs which is Centos/RedHat location of this file. Also 
/etc/default/nfs does not exist. (possibly unrelated to this bug)
  4. A file "/lib/systemd/system/-.slice" exists. this file prevents 
execution of 'ls *' or 'grep xxx *' commands in that directory. I am unsure 
whether this is intended by the systemd developers but it is unfriendly when 
investigating this bug.

  Attempted solution:

  1. Edit /lib/systemd/system/nfs-server.service (original lines are
  commented out:

  [Unit]
  Description=NFS server and services
  DefaultDependencies=no
  Requires=network.target proc-fs-nfsd.mount rpcbind.target
  # Requires=nfs-mountd.service
  Wants=nfs-idmapd.service

  After=local-fs.target
  #After=network.target proc-fs-nfsd.mount rpcbind.target nfs-mountd.service
  After=network.target proc-fs-nfsd.mount rpcbind.target
  After=nfs-idmapd.service