date:20170619

[Group.of.nepali.translators] [Bug 1698442] Re: linux-azure: 4.11.0-1001.1 -proposed tracker

2017-06-19 Thread Brad Figg

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

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

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

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

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

** Description changed:

  This bug is for tracking the 4.11.0-1001.1 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Tuesday, 20. June 2017 06:34 UTC

** Description changed:

  This bug is for tracking the 4.11.0-1001.1 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Tuesday, 20. June 2017 06:34 UTC
+ phase: Uploaded

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

Title:
  linux-azure: 4.11.0-1001.1 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1698442/+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 1684092] Re: cloud-init in xenial generates bond configs that do not appear to work

2017-06-19 Thread Launchpad Bug Tracker

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

** Changed in: cloud-init (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  cloud-init in xenial generates bond configs that do not appear to work

Status in cloud-init package in Ubuntu:
  Expired
Status in cloud-init source package in Xenial:
  Expired

Bug description:
  cloud-init  0.7.9-48-g1c795b9-0ubuntu1~16.04.1

  Cloud init generated /etc/network/interfaces.d/50-cloud-init.cfg for a
  network configuration of two vlan'ed networks, on top of a bond, of
  two interfaces.

  The generated config did not work, as the bond specified "bond-slaves
  none", there were also bond_* settings specified on the interfaces,
  which I believe are redundant.

  Comparing the config generated by this cloud-init with another
  instance of similar type, I have removed the extrac bond_* settings
  from the cloud init generated config, and also specified "bond-salves"
  on the bond stanza, and disabled the cloud-init network config via
  snippet as advised at the top of the file.

  This made networking come up.

  I will attach, the generated 50-cloud-init.cfg; diff of applied
  differences; as well as the journal logs of both boots (broken and
  working).

  Imho cloud-init should generate bond-slaves stanzas with the
  interfaces names.

  However, further investigation suggests that changing bond-slaves from
  none to list of interfaces is a red herring. And instead the generated
  configuration is just fine, as long as network config is disabled in
  cloud-init (e.g. echo 'network: {config: disabled}' >
  /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg). So cloud-init
  generates the right eni.d drop-in file, but fails to correctly online
  these devices?! seems like "ifup -a" is all that is needed here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1684092/+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 1684092] Re: cloud-init in xenial generates bond configs that do not appear to work

2017-06-19 Thread Launchpad Bug Tracker

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

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Incomplete => Expired

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

Title:
  cloud-init in xenial generates bond configs that do not appear to work

Status in cloud-init package in Ubuntu:
  Expired
Status in cloud-init source package in Xenial:
  Expired

Bug description:
  cloud-init  0.7.9-48-g1c795b9-0ubuntu1~16.04.1

  Cloud init generated /etc/network/interfaces.d/50-cloud-init.cfg for a
  network configuration of two vlan'ed networks, on top of a bond, of
  two interfaces.

  The generated config did not work, as the bond specified "bond-slaves
  none", there were also bond_* settings specified on the interfaces,
  which I believe are redundant.

  Comparing the config generated by this cloud-init with another
  instance of similar type, I have removed the extrac bond_* settings
  from the cloud init generated config, and also specified "bond-salves"
  on the bond stanza, and disabled the cloud-init network config via
  snippet as advised at the top of the file.

  This made networking come up.

  I will attach, the generated 50-cloud-init.cfg; diff of applied
  differences; as well as the journal logs of both boots (broken and
  working).

  Imho cloud-init should generate bond-slaves stanzas with the
  interfaces names.

  However, further investigation suggests that changing bond-slaves from
  none to list of interfaces is a red herring. And instead the generated
  configuration is just fine, as long as network config is disabled in
  cloud-init (e.g. echo 'network: {config: disabled}' >
  /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg). So cloud-init
  generates the right eni.d drop-in file, but fails to correctly online
  these devices?! seems like "ifup -a" is all that is needed here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1684092/+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 1699005] [NEW] Update to 1.13

2017-06-19 Thread Robert Ancell

Public bug reported:

[Impact]
Older versions of Ubuntu are running older versions of snapd-glib. There have 
since been bug fixes and support for newer API that was added to snapd since 
release.

[Test Case]
1. Attempt to use new API in snapd-glib

Expected result:
New API is available

Observed result:
New API is not available

[Regression Potential]
There is a risk of breaking existing use cases. This is reduced by the 
regression tests in the package and the newer versions of snapd-glib working in 
newer releases.

** Affects: snapd-glib (Ubuntu)
 Importance: Wishlist
 Status: Fix Released

** Affects: snapd-glib (Ubuntu Xenial)
 Importance: Wishlist
 Assignee: Robert Ancell (robert-ancell)
 Status: In Progress

** Affects: snapd-glib (Ubuntu Yakkety)
 Importance: Wishlist
 Status: Won't Fix

** Affects: snapd-glib (Ubuntu Zesty)
 Importance: Wishlist
 Assignee: Robert Ancell (robert-ancell)
 Status: In Progress

** Also affects: snapd-glib (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: snapd-glib (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: snapd-glib (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: snapd-glib (Ubuntu Yakkety)
   Importance: Undecided => Wishlist

** Changed in: snapd-glib (Ubuntu Zesty)
   Importance: Undecided => Wishlist

** Changed in: snapd-glib (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: snapd-glib (Ubuntu)
   Status: New => Fix Released

** Changed in: snapd-glib (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Update to 1.13

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  In Progress
Status in snapd-glib source package in Yakkety:
  Won't Fix
Status in snapd-glib source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Older versions of Ubuntu are running older versions of snapd-glib. There have 
since been bug fixes and support for newer API that was added to snapd since 
release.

  [Test Case]
  1. Attempt to use new API in snapd-glib

  Expected result:
  New API is available

  Observed result:
  New API is not available

  [Regression Potential]
  There is a risk of breaking existing use cases. This is reduced by the 
regression tests in the package and the newer versions of snapd-glib working in 
newer releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1699005/+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 1582767] Re: apparmor permissions missing for winbind

2017-06-19 Thread Bug Watch Updater

** Changed in: ntp (Debian)
   Status: New => Fix Released

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

Title:
  apparmor permissions missing for winbind

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Won't Fix
Status in ntp package in Debian:
  Fix Released

Bug description:
  When using Winbind, ntpd needs to access the Winbind pipe:

  May 17 16:23:15 bo kernel: [   27.598551] type=1400
  audit(1463494995.048:18): apparmor="DENIED" operation="connect"
  profile="/usr/sbin/ntpd" name="/run/samba/winbindd/pipe" pid=1517
  comm="ntpd" requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0

  Would there be any reason not to allow this ? I added the following
  line to /etc/apparmor/init/network-interface-security/usr.sbin.ntpd:

  /run/samba/winbindd/pipe rw,

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1582767/+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 1692837] Re: Ubuntu 16.04.02: powerpc-ibm-utils: drmgr does not scale with large number of virtual adapters

2017-06-19 Thread Launchpad Bug Tracker

This bug was fixed in the package powerpc-utils - 1.3.2-1ubuntu2

---
powerpc-utils (1.3.2-1ubuntu2) artful; urgency=medium

* d/p/in-kernel-dlpar.patch: fix FTBFS.

-- Steve Langasek Mon, 19 Jun 2017
14:18:01 -0700

** Changed in: powerpc-utils (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/1692837

Title:
Ubuntu 16.04.02: powerpc-ibm-utils: drmgr does not scale with large
number of virtual adapters

Status in The Ubuntu-power-systems project:
Confirmed
Status in powerpc-utils package in Ubuntu:
Fix Released
Status in powerpc-utils source package in Xenial:
New
Status in powerpc-utils source package in Yakkety:
New
Status in powerpc-utils source package in Zesty:
New

Bug description:
== Comment: #0 - Jeremy A. Arnold
---Problem Description---
The time to run commands such as "drmgr -c slot -s U8247.22L.211E15A-V1-C210
-a -w 1" increases linearly with the number of slots on the system. For cloud
environments with a large number of VMs hosted by a single NovaLink partition
(or a small number of VIOS partitions), the number of virtual slots in the
NovaLink partition can grow large, and the long drmgr time can be a major
factor in the time to deploy new VMs.

In one recent test, the call above took about 29 seconds to complete
on a system with around 100 VMs. Earlier in the run (when there was
less than 10 VMs) it only took about 2 seconds.

I'm not at all an expert on this area, but it would appear that drmgr
is iterating through all of the slots in order to find the one that
was requested. Some evidence for this is provided by running:

sudo time /usr/sbin/drmgr -c slot -s U8247.22L.211E15A-V1-C210 -Q

This is taking about 14 seconds elapsed time (it may have been slower
during the actual run due to concurrent executions of drmgr) on a
system with about 232 virtual adapter slots. The time is similar if I
make a request for a slot that does not exist (e.g. change C210 to
C250), so it would appear that nearly all of the runtime is for
looking up the slot and not for actually retrieving information about
it.

Adding -d20 to the above command provides additional debug data. This
shows that the majority of the time is between these two lines of
output:

---
Could not find DRC property group in path:
/proc/device-tree/pci@800201f.
DR nodes list
---

For reference, the following command can identify the correct entry in
the device tree in about 0.02 seconds. Obviously drmgr has more to do
than just this, but this suggests that there is no fundamental reason
the time has to scale with the number of slots:

time (find /sys/firmware/devicetree/base/vdevice -name "ibm\,loc-code" |
xargs grep "^U8247.22L.211E15A-V1-C210-T1$")

---uname output---
Linux cs-tul10-neo 4.4.21-customv1.29 #6 SMP Wed Apr 12 14:40:02 CDT 2017
ppc64le ppc64le ppc64le GNU/Linux

Machine Type = 8247-22L

---Debugger---
A debugger is not configured

---Steps to Reproduce---
I used PowerVC to deploy 100 VMs to a NovaLink system and viewed
/var/log/drmgr to observe how long the drmgr calls took during the test.

I believe it would be sufficient to add 200 virtual adapters to an
LPAR and then run "/usr/sbin/drmgr -c slot -s -Q"

I'm happy to collect additional data in my environment if it would be helpful.

Userspace tool common name: /usr/sbin/drmgr

The userspace tool has the following bit modes: 64-bit

Userspace rpm: powerpc-ibm-utils

Userspace tool obtained from project website: na

== Comment: #4 - Amartey S. Pearson
I have a proposed fix for this in a github fork. In short, the algorithm
used to populate the dr_nodes needs to be fixed. It currently walks the entire
bus for every theoretical DRC (1000's of times). The fix is to walk the bus
once.

https://github.com/apearson-ibm/powerpc-
utils/commit/6fefb6acb6fb302c97d71faef75a12674a50209a

This addresses both drmgr and lsslot as the change is in common code.
An example of the improvement we see:

Here we have a system with 196 populated virtual slots. An lsslot
takes 6.5 seconds.

root@neo33-2:/usr/sbin# time /usr/sbin/lsslot -c slot | wc -l
196
real0m6.495s
user0m1.108s
sys 0m5.384s

With the fix, the lsslot now takes 0.18 seconds, and scales well as
more slots are added.

root@neo33-2:~/powerpc-utils# time /usr/local/sbin/lsslot -c slot | wc -l
196
real0m0.186s
user0m0.028s
sys 0m0.156s

== Comment: #7 - Anna A. Sortland
We tried the patch in our test environment and it worked great.

== Comment: #11 - Nathan D. Fontenot - 2017-05-18
13:30:42 ==
Patch submitted upstream.

https://groups.google.com/forum/#!topic/powerpc-utils-
devel/sd1gdvb

[Group.of.nepali.translators] [Bug 1696434] Re: drmgr command fails during the scale-up test on Novalink System (Brazos)

2017-06-19 Thread Launchpad Bug Tracker

This bug was fixed in the package powerpc-utils - 1.3.2-1ubuntu2

---
powerpc-utils (1.3.2-1ubuntu2) artful; urgency=medium

  * d/p/in-kernel-dlpar.patch: fix FTBFS.

 -- Steve Langasek   Mon, 19 Jun 2017
14:18:01 -0700

** Changed in: powerpc-utils (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/1696434

Title:
  drmgr command fails during the scale-up test on Novalink System
  (Brazos)

Status in The Ubuntu-power-systems project:
  Confirmed
Status in powerpc-utils package in Ubuntu:
  Fix Released
Status in powerpc-utils source package in Xenial:
  New
Status in powerpc-utils source package in Yakkety:
  New
Status in powerpc-utils source package in Zesty:
  New

Bug description:
  Problem:

  During the scale-up test to 1000 VMs I could see 20 deploys failed due
  to following command failure..

  Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9119.MHE.1085B07-V1-C1030' -a 
-w 3 returned 19. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 
'U9119.MHE.1085B07-V1-C1030' -a -w 3
  Validating I/O DLPAR capability...yes.
  kernel I/O op failed, rc = 26 len = 26.

  I have been looking through the logs on this system to piece together
  what is happening when the dlpar add failures occur. From what I am
  seeing we are trying to dlpar add a virtual network device and getting
  a error when trying to add the device to the system.

  > ## May 17 05:18:00 2017 ##
  > drmgr: -c slot -s U9119.MHE.1085B07-V1-C1030 -a -w 3 
  > Validating I/O DLPAR capability...yes.
  > Getting node types 0x0003
  > Could not find DRC property group in path: /proc/device-tree/ibm,serial.
  > Acquiring drc index 0x3406
  > get-sensor for 3406: 0, 2
  > Setting allocation state to 'alloc usable'
  > Setting indicator state to 'unisolate'
  > Configuring connector for drc index 3406
  > Adding device-tree node /proc/device-tree/vdevice/l-lan@3406
  > ofdt update: add_node /vdevice/l-lan@3406 ibm,loc-code 30 
U9119.MHE.1085B07-V1-C1030-T1
  > Getting node types 0x0003
  > performing kernel op for U9119.MHE.1085B07-V1-C1030, file is 
/sys/bus/pci/slots/control/add_slot
  > kernel I/O op failed, rc = 26 len = 26.
  > No such device
  > Releasing drc index 0x3406
  > get-sensor for 3406: 0, 1
  > Setting isolation state to 'isolate'
  > Setting allocation state to 'alloc unusable'
  > get-sensor for 3406: 0, 2
  > drc_index 3406 sensor-state: 2
  > Resource is not available to the partition.
  > Removing device-tree node /proc/device-tree/vdevice/l-lan@3406
  > ## May 17 05:20:11 2017 ##

  From the drmgr log, you can see that we get a ENODEV return code when
  performing the kernel operation to add the device to the system.

  > performing kernel op for U9119.MHE.1085B07-V1-C1030, file is 
/sys/bus/pci/slots/control/add_slot
  > kernel I/O op failed, rc = 26 len = 26.
  > No such device

  This indicates that the rpadlpar_io kernel modules was unable to find
  the device in the device tree. This doesn not seem right because
  earlier in the drmgr logs we add the device to the device tree.
  Additionally, the drmgr code validates that the add succeeds by
  retrieveing the newly added device node from the device tree as a
  sanity check. There are no failures reported for this.

  > Adding device-tree node /proc/device-tree/vdevice/l-lan@3406
  > ofdt update: add_node /vdevice/l-lan@3406 ibm,loc-code 30 
U9119.MHE.1085B07-V1-C1030-T1
  > Getting node types 0x0003

  I started scale-up testing and I could see deploys are going fine.
  Will post a comment here if I see further drmgr failures.

  Patches have been submitted upstream.

  https://groups.google.com/forum/#!topic/powerpc-utils-
  devel/GNEi65WBwkQ

  and

  https://groups.google.com/forum/#!topic/powerpc-utils-
  devel/hJfUb5wYPsE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696434/+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 1692837] Re: Ubuntu 16.04.02: powerpc-ibm-utils: drmgr does not scale with large number of virtual adapters

2017-06-19 Thread Steve Langasek

** Also affects: powerpc-utils (Ubuntu Xenial)
Importance: Undecided
Status: New

** Also affects: powerpc-utils (Ubuntu Zesty)
Importance: Undecided
Status: New

** Also affects: powerpc-utils (Ubuntu Yakkety)
Importance: Undecided
Status: New

Title:
Ubuntu 16.04.02: powerpc-ibm-utils: drmgr does not scale with large
number of virtual adapters

Status in The Ubuntu-power-systems project:
Confirmed
Status in powerpc-utils package in Ubuntu:
Confirmed
Status in powerpc-utils source package in Xenial:
New
Status in powerpc-utils source package in Yakkety:
New
Status in powerpc-utils source package in Zesty:
New