date:20180110

[Group.of.nepali.translators] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

2018-01-10 Thread Timo Aaltonen

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

** Also affects: pulseaudio (Ubuntu Artful)
   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/1718824

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1708665] Re: prerotate.sh fails due to no shell for www-data user

2018-01-10 Thread Launchpad Bug Tracker

This bug was fixed in the package awstats - 7.6+dfsg-1ubuntu2

---
awstats (7.6+dfsg-1ubuntu2) bionic; urgency=medium

  [ Christian Ehrhardt ]
  * debian/README.Debian, debian/prerotate.sh: fix logrotate integration due to
change of www-data to /usr/sbin/nologin (Closes: #858461, LP: #1708665)

 -- Andreas Hasenack   Fri, 15 Dec 2017 18:55:12
-0200

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

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

Title:
  prerotate.sh fails due to no shell for www-data user

Status in awstats package in Ubuntu:
  Fix Released
Status in awstats source package in Xenial:
  In Progress
Status in awstats source package in Zesty:
  Won't Fix
Status in awstats source package in Artful:
  In Progress
Status in awstats package in Debian:
  New

Bug description:
  [Impact]
  The logrotate script that is responsible for updating awstats statistics does 
not run because the www-data user that it runs as does not have a valid shell.

  This update adjusts the su command line to specify the same shell as
  the script shebang line.

  [Test Case]
  To test, run the script:

  Version with the bug:
  $ sudo /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh
  No directory, logging in with HOME=/
  This account is currently not available.

  Fixed version:
  $ sudo /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh
  No directory, logging in with HOME=/
  Error while processing /etc/awstats/awstats.conf
  Error: SiteDomain parameter not defined in your config/domain file. You must 
edit it for using this version of AWStats.
  Setup ('/etc/awstats/awstats.conf' file, web server or permissions) may be 
wrong.
  Check config file, permissions and AWStats documentation (in 'docs' 
directory).

  Note the "fixed" version actually runs the script and complains about
  something else, unrelated to this bug. The admin must complete the
  installation of awstats before using it, but this test is enough to
  verify the fix.

  If you want to get a full run, you have to follow the instructions in the 
README.Debian file. Basically, at a minimum:
  - edit /etc/awstats/awstats.conf and give SiteDomain a value
  - change group ownership of /var/log/apache2 and /var/log/apache2/* to 
www-data (that's one solution). README.Debian has other ideas, and I would add 
using ACLs if your filesystem of choice supports them: "setfacl -m 
g:www-data:rx /var/log/apache2" and "setfacl -m g:www-data:r /var/log/apache2/*"

  [Regression Potential]
  Code that wasn't running before because of this bug will now run. If the user 
didn't complete the awstats configuration he/she will get more verbose cron 
emails.

  
  [Other Info]
  Users who have already worked around the issue by manually editing the 
logrotate file and adding "-s /bin/sh" or something similar will get a dpkg 
prompt when upgrading to this version:

  Configuration file '/etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.


  
  === Original description ===

  This was found in Ubuntu 16.04. I have not tested other versions.

  The /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh script does
  not run by default, because the 'www-data' user does not have a valid
  shell by default.

  root@www:~# bash -x /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh
  + UPDATE_SCRIPT=/usr/share/awstats/tools/update.sh
  + '[' -x /usr/share/awstats/tools/update.sh ']'
  + su -l -c /usr/share/awstats/tools/update.sh www-data
  This account is currently not available.

  We could give www-data a valid shell but my preferred fix is to edit
  /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh and explicitly
  specify the shell with '-s /bin/bash':

  diff -u ~/prerotate.sh /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh
  --- /root/prerotate.sh  2017-07-31 17:07:43.749559681 -0500
  +++ /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh   2017-07-31 
17:07:54.122034426 -0500
  @@ -2,5 +2,5 @@
   UPDATE_SCRIPT=/usr/share/awstats/tools/update.sh
   if [ -x $UPDATE_SCRIPT ]
   then
  -  su -l -c $UPDATE_SCRIPT www-data
  +  su -l -c $UPDATE_SCRIPT -s /bin/bash www-data
   fi

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

___
Mailing list:

[Group.of.nepali.translators] [Bug 1730544] Re: AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC

2018-01-10 Thread AceLan Kao

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

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

Title:
  AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-oem source package in Xenial:
  Fix Released

Bug description:
  From vendor's suggestion, there are some patches in v4.14-rc6 are
  required to enable the 2 NICs

  417a3ae net: aquantia: Bad udp rate on default interrupt coalescing
  b82ee71 net: aquantia: Enable coalescing management via ethtool interface
  6849540 net: aquantia: mmio unmap was not performed on driver removal
  4c8bb60 net: aquantia: Limit number of MSIX irqs to the number of cpus
  93d87b8 net: aquantia: Fixed transient link up/down/up notification
  5d8d84e net: aquantia: Add queue restarts stats counter
  65e665e net: aquantia: Reset nic statistics on interface up/down

  And to avoid conflict, cherry pick 2 more commits

  3aec641 aquantia: Fix Tx queue hangups
  65e665e net: aquantia: Reset nic statistics on interface up/down

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1730544/+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 1725421] Re: [mitaka] Nova lock/unlock should be hidden if nova api <2.9

2018-01-10 Thread Corey Bryant

I've updated the bug description and title as it was discussing 2
different scenarios.

** Description changed:

  [Impact]
  
  * Similar/related to lp:1505845, which was fixed for Newton.
    Lock/unlock options are displayed in Horizon despite Nova API <2.9,
    which causes user confusion.
+ * Additionally, when Nova API is >= 2.9, the actions "Lock Instance"
+   and "Unlock Instance" should not be shown at the same time.
  
  [Test Case]
  
-   1. Log into Horizon dashboard.
-   2. Create new instance.
-   3. Wait for instance to switch to 'running' state.
-   4. On the newly created instance, under Actions, you'll
-  see both 'Lock Instance' and 'Unlock Instance' are
-  available, even after locking the instance.
+ case 1:
+   1. Deploy nova and horizon both at mitaka level.
+   2. Log into Horizon dashboard.
+   3. Create new instance.
+   4. Wait for instance to switch to 'running' state.
+   5. On the newly created instance, under Actions, you'll
+  see both 'Lock Instance' and 'Unlock Instance' are
+  available, even after locking the instance.
+ 
+ case 2:
+   1. Deploy nova at kilo level and horizon at mitaka level (test with Nova 
API < 2.9)
+   2. Log into Horizon dashboard.
+   3. Create new instance.
+   4. Wait for instance to switch to 'running' state.
+   5. On the newly created instance, under Actions, you'll
+  'Lock Instance' and 'Unlock Instance' should be hidden.
  
  [Regression Potential]
  
  * Regression potential is low. This bug has been fixed in all releases of
    OpenStack starting with Newton. The patch did have to be modified
    slightly to apply to mitaka.
  
  [Discussion]

** Summary changed:

- [mitaka] Nova lock/unlock should be hidden if nova api <2.9
+ [mitaka] Hide nova lock/unlock if nova api <2.9 and when >= 2.9, "Lock/Unlock 
Instance" should not be shown at same time.

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

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

** Changed in: horizon (Ubuntu)
   Status: In Progress => Invalid

** Changed in: cloud-archive
   Status: New => Invalid

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

** Changed in: cloud-archive/mitaka
   Importance: Undecided => Medium

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

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

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

** Changed in: cloud-archive
   Importance: Medium => Undecided

** Changed in: horizon (Ubuntu Xenial)
 Assignee: (unassigned) => Shane Peters (shaner)

** Changed in: horizon (Ubuntu)
 Assignee: Shane Peters (shaner) => (unassigned)

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

Title:
  [mitaka] Hide nova lock/unlock if nova api <2.9 and when >= 2.9,
  "Lock/Unlock Instance" should not be shown at same time.

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in horizon package in Ubuntu:
  Invalid
Status in horizon source package in Xenial:
  Triaged

Bug description:
  [Impact]

  * Similar/related to lp:1505845, which was fixed for Newton.
    Lock/unlock options are displayed in Horizon despite Nova API <2.9,
    which causes user confusion.
  * Additionally, when Nova API is >= 2.9, the actions "Lock Instance"
and "Unlock Instance" should not be shown at the same time.

  [Test Case]

  case 1:
    1. Deploy nova and horizon both at mitaka level.
2. Log into Horizon dashboard.
    3. Create new instance.
    4. Wait for instance to switch to 'running' state.
    5. On the newly created instance, under Actions, you'll
   see both 'Lock Instance' and 'Unlock Instance' are
   available, even after locking the instance.

  case 2:
1. Deploy nova at kilo level and horizon at mitaka level (test with Nova 
API < 2.9)
2. Log into Horizon dashboard.
3. Create new instance.
4. Wait for instance to switch to 'running' state.
5. On the newly created instance, under Actions, you'll
   'Lock Instance' and 'Unlock Instance' should be hidden.

  [Regression Potential]

  * Regression potential is low. This bug has been fixed in all releases of
    OpenStack starting with Newton. The patch did have to be modified
    slightly to apply to mitaka.

  [Discussion]

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1725421/+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 1742094] Re: [16.04][classic] Redpine: wowlan feature doesn't work

2018-01-10 Thread Joseph Salisbury

** Tags added: kernel-da-key

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

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

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

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

Title:
  [16.04][classic] Redpine: wowlan feature doesn't work

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Steps to reproduce:

   1. Ensure WoWLAN is enabled in BIOS.
   2. Initiate connection to an AP (using nmcli)
   3. Configure the device for WoWLAN, run the command:
  $ sudo iw phy phy0 wowlan enable magic-packet
   4. Enter S5/S4/S3 (using poweroff, etc.)
   5. From another computer on the same network run the following command:
  $ wakeonlan {mac} (in my case `wakeonlan 00:23:a7:ec:b4:04`)

  Expected result: the device starts/resume

  This bug is only for tracking purporse, please do not triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742094/+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 1573766] Re: Enable the paste filter HTTPProxyToWSGI by default

2018-01-10 Thread Corey Bryant

This bug was fixed in the package nova - 2:13.1.4-0ubuntu4.2~cloud0
---

nova (2:13.1.4-0ubuntu4.2~cloud0) trusty-mitaka; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
nova (2:13.1.4-0ubuntu4.2) xenial; urgency=medium
.
[ Seyeong Kim ]
* Add supporting http_proxy_to_wsgi to api-paste.ini (LP: #1573766)
- d/p/0001-Add-http_proxy_to_wsgi-to-api-paste.patch
- d/p/0002-Add-proxy-middleware-to-application-pipeline.patch
.
[ Edward Hope-Morley ]
* Patch nova.db.sqlalchemy.api.compute_node_statistics() to
exclude deleted services from stats count. This is the same
fix as that backported to newton in bug 1692397 except that
the actual patch is not backportable due to the underlying
code changing extensively.
- d/p/exlude-deleted-service-from-stats-count.patch (LP: #1692397)

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

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

Title:
Enable the paste filter HTTPProxyToWSGI by default

Status in OpenStack nova-cloud-controller charm:
In Progress
Status in Ubuntu Cloud Archive:
Invalid
Status in Ubuntu Cloud Archive mitaka series:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Status in nova package in Ubuntu:
Invalid
Status in nova source package in Xenial:
Fix Released

Bug description:
[Impact]

Getting http link instead of https even if https setting is set.

[Test case]

1. deploy openstack ( with keystone charm option use-https,
https-service-endpoints)
2. create instance
3. nova --debug list
- check the result if https links are there.

[Regression Potential]

nova pkg will be affected by this patch. However, this patch modifies
only api-paste.ini by adding http_proxy_to_wsgi. To accept this patch,
nova service need to be restarted. Tested no vms are affected this
patch, but APIs or daemons are temporarily.

[Others]

related commits ( which are already in comments )

https://git.openstack.org/cgit/openstack/nova/commit/?id=b609a3b32ee8e68cef7e66fabff07ca8ad6d4649

https://git.openstack.org/cgit/openstack/nova/commit/?id=6051f30a7e61c32833667d3079744b2d4fd1ce7c

[Original Description]

oslo middleware provides a paste filter that sets the correct proxy
scheme and host. This is needed for the TLS proxy case.

Without this then enabling the TLS proxy in devstack will fail
configuring tempest because 'nova flavor-list' returns a http scheme
in Location in a redirect it returns.

I've proposed a temporary workaround in devstack using:

+iniset $NOVA_API_PASTE_INI filter:ssl_header_handler past
e.filter_factory oslo_middleware.http_proxy_to_wsgi:HTTPProxyToWSGI.factory
+iniset $NOVA_API_PASTE_INI composite:openstack_compute_ap
i_v21 keystone "ssl_header_handler cors compute_req_id faultwrap sizelimit
autht
oken keystonecontext osapi_compute_app_v21"

But this isn't a long-term solution because two copies of the default
paste filters will need to be maintained.

See https://review.openstack.org/#/c/301172

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1573766/+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 1692397] Re: hypervisor statistics could be incorrect

2018-01-10 Thread Corey Bryant

This bug was fixed in the package nova - 2:13.1.4-0ubuntu4.2~cloud0
---

 nova (2:13.1.4-0ubuntu4.2~cloud0) trusty-mitaka; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 nova (2:13.1.4-0ubuntu4.2) xenial; urgency=medium
 .
   [ Seyeong Kim ]
   * Add supporting http_proxy_to_wsgi to api-paste.ini (LP: #1573766)
 - d/p/0001-Add-http_proxy_to_wsgi-to-api-paste.patch
 - d/p/0002-Add-proxy-middleware-to-application-pipeline.patch
 .
   [ Edward Hope-Morley ]
   * Patch nova.db.sqlalchemy.api.compute_node_statistics() to
 exclude deleted services from stats count. This is the same
 fix as that backported to newton in bug 1692397 except that
 the actual patch is not backportable due to the underlying
 code changing extensively.
 - d/p/exlude-deleted-service-from-stats-count.patch (LP: #1692397)


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

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

Title:
  hypervisor statistics could be incorrect

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) newton series:
  Fix Committed
Status in OpenStack Compute (nova) ocata series:
  Fix Committed
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  If you deploy a nova-compute service to a node, delete that service
  (via the api), then deploy a new nova-compute service to that same
  node i.e. same hostname, the database will now have two service
  records one marked as deleted and the other not. So far so good until
  you do an 'openstack hypervisor stats show' at which point the api
  will aggregate the resource counts from both services. This has been
  fixed and backported all the way down to Newton so the problem still
  exists on Mitaka. I assume the reason why the patch was not backported
  to Mitaka is that the code in
  nova.db.sqlalchemy.apy.compute_node_statistics() changed quite a bit.
  However it only requires a one line change in the old code (that does
  the same thing as the new code) to fix this issue.

  [Test Case]

   * Deploy Mitaka with bundle http://pastebin.ubuntu.com/25968008/

   * Do 'openstack hypervisor stats show' and verify that count is 3

   * Do 'juju remove-unit nova-compute/2' to delete a compute service
  but not its physical host

   * Do 'openstack compute service delete ' to delete a compute
  service we just removed (choosing correct id)

   * Do 'openstack hypervisor stats show' and verify that count is 2

   * Do juju add-unit nova-compute --to 

   * Do 'openstack hypervisor stats show' and verify that count is 3
  (not 4 as it would be before fix)

  [Regression Potential]

  None anticipated other than for clients that were interpreting invalid
  counts as correct.

  [Other Info]
   
  ===

  Hypervisor statistics could be incorrect:

  When we killed a nova-compute service and deleted the service from nova DB, 
and then
  start the nova-compute service again, the result of Hypervisor/statistics API 
(nova hypervisor-stats) will be
  incorrect;

  How to reproduce:

  Step1. Check the correct statistics before we do anything:
  root@SZX1000291919:/opt/stack/nova# nova  hypervisor-stats
  +--+---+
  | Property | Value |
  +--+---+
  | count| 1 |
  | current_workload | 0 |
  | disk_available_least | 14|
  | free_disk_gb | 34|
  | free_ram_mb  | 6936  |
  | local_gb | 35|
  | local_gb_used| 1 |
  | memory_mb| 7960  |
  | memory_mb_used   | 1024  |
  | running_vms  | 1 |
  | vcpus| 8 |
  | vcpus_used   | 1 |
  +--+---+

  Step2. Kill the compute service:
  root@SZX1000291919:/var/log/nova# ps -ef | grep nova-com
  root 120419 120411  0 11:06 pts/27   00:00:00 sg libvirtd 
/usr/local/bin/nova-compute --config-file /etc/nova/nova.conf --log-file 
/var/log/nova/nova-compute.log
  root 120420 120419  0 11:06 pts/27   00:00:07 /usr/bin/python 
/usr/local/bin/nova-compute --config-file /etc/nova/nova.conf --log-file 
/var/log/nova/nova-compute.log

  root@SZX1000291919:/var/log/nova# kill -9 120419
  root@SZX1000291919:/var/log/nova# /usr/local/bin/stack: line 19: 120419 
Killed  sg libvirtd '/usr/local/bin/nova-compute --config-file 
/etc/nova/nova.conf --log-file /var/log/nova/nova-compute.log' > /dev/null 2>&1

  root@SZX1000291919:/var/log/nova# nova service-list

[Group.of.nepali.translators] [Bug 1582585] Re: the speed of query user from ldap server is very slow

2018-01-10 Thread Corey Bryant

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

** Changed in: cloud-archive/newton
   Status: New => Triaged

** Changed in: cloud-archive/newton
   Importance: Undecided => High

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

Title:
  the speed of query user from ldap server is very slow

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive newton series:
  Triaged
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystone package in Ubuntu:
  New
Status in keystone source package in Xenial:
  Triaged

Bug description:
  In our project, the speed of query user from ldap server is very
  slow,our ldap user number is 12,000,the query costs almost 45 seconds

  The reason is that keystone will generate the uuid for the ldap users one by 
one and insert db.And second query time later,it also goes to db,not use the 
cache.
  So adding the cache to improve the query speed

  After adding @MEMOIZE to the following function
  
https://github.com/openstack/keystone/blob/master/keystone/identity/core.py#L580.
  First query time almost costs 50 seconds,but second query time later it only 
costs 7 seconds.

  So it is very necessary to improve this feature

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1582585/+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 1582585] Re: the speed of query user from ldap server is very slow

2018-01-10 Thread Corey Bryant

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

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

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

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

** Changed in: cloud-archive/mitaka
   Importance: Undecided => High

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

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

Title:
  the speed of query user from ldap server is very slow

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystone package in Ubuntu:
  New
Status in keystone source package in Xenial:
  Triaged

Bug description:
  In our project, the speed of query user from ldap server is very
  slow,our ldap user number is 12,000,the query costs almost 45 seconds

  The reason is that keystone will generate the uuid for the ldap users one by 
one and insert db.And second query time later,it also goes to db,not use the 
cache.
  So adding the cache to improve the query speed

  After adding @MEMOIZE to the following function
  
https://github.com/openstack/keystone/blob/master/keystone/identity/core.py#L580.
  First query time almost costs 50 seconds,but second query time later it only 
costs 7 seconds.

  So it is very necessary to improve this feature

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1582585/+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 1742502] Re: 108 and 109 kernel hangs

2018-01-10 Thread Leann Ogasawara

** Tags added: pti

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

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

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

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

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

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

Title:
  108 and 109 kernel hangs

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

Bug description:
  Overnight I had 2 of 12  16.04 servers brick with the 108 kernel. They
  also do not work with 109.  They work fine with 104. The other 10
  worked fine on both 108 and 109.

  All are hosted on VMWARE. The two broken ones stop at the same place.
  I was able to go back to the 104 kernel to get them working and pin
  the kernel version.

  Just for fun, I set zswap.enabled=0 and they both crashed with kthread
  starved for jiffies. They are both multi-processor with lots of ram
  and disk.

  I have a task from the Ubuntu Kernel team to try this with 'nopti'.
  I'll report back.

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

43 matches

Mail list logo