[Yahoo-eng-team] [Bug 1669450] Re: Python modals are not animated like angular modals

[OpenStack Infra]

Reviewed:  https://review.openstack.org/440603
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=8be1ec5e706b07b47f13b8c97c70327b25b09552
Submitter: Jenkins
Branch:master

commit 8be1ec5e706b07b47f13b8c97c70327b25b09552
Author: Rob Cresswell 
Date:   Thu Mar 2 14:18:17 2017 +

Add the 'fade' class to Python modals, for animation

Change-Id: I0547df31529925d9957e704aee167b6b414588c1
Closes-Bug: 1669450


** Changed in: horizon
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1669450

Title:
  Python modals are not animated like angular modals

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The Python modals aren't animated like the Angular modals; this is
  just due to a missing 'fade' class, and is a minor fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1669450/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674557] [NEW] eventlet 0.20.x breaks functional tests due to missing select.poll()

[Ihar Hrachyshka]

Public bug reported:

eventlet was bumped from 0.19.x to 0.20.1 in gate, and it broke
functional job:

http://logs.openstack.org/78/385178/18/check/gate-neutron-dsvm-
functional-ubuntu-xenial/184b97c/testr_results.html.gz

Traceback (most recent call last):
  File "neutron/tests/base.py", line 116, in func
return f(self, *args, **kwargs)
  File "neutron/tests/functional/agent/l3/test_legacy_router.py", line 155, in 
test_conntrack_disassociate_fip_legacy_router
self._test_conntrack_disassociate_fip(ha=False)
  File "neutron/tests/functional/agent/l3/framework.py", line 159, in 
_test_conntrack_disassociate_fip
self.assertTrue(netcat.test_connectivity())
  File "neutron/tests/common/net_helpers.py", line 505, in test_connectivity
message = self.server_process.read_stdout(READ_TIMEOUT).strip()
  File "neutron/tests/common/net_helpers.py", line 287, in read_stdout
return self._read_stream(self.stdout, timeout)
  File "neutron/tests/common/net_helpers.py", line 292, in _read_stream
poller = select.poll()
AttributeError: 'module' object has no attribute 'poll'

That's because as per release notes for 0.20.0, select.poll was removed:

http://eventlet.net/doc/changelog.html#id2

** Affects: neutron
 Importance: Critical
 Status: Confirmed


** Tags: functional-tests gate-failure

** Changed in: neutron
   Importance: Undecided => Critical

** Changed in: neutron
   Status: New => Confirmed

** Tags added: functional-tests gate-failure

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1674557

Title:
  eventlet 0.20.x breaks functional tests due to missing select.poll()

Status in neutron:
  Confirmed

Bug description:
  eventlet was bumped from 0.19.x to 0.20.1 in gate, and it broke
  functional job:

  http://logs.openstack.org/78/385178/18/check/gate-neutron-dsvm-
  functional-ubuntu-xenial/184b97c/testr_results.html.gz

  Traceback (most recent call last):
File "neutron/tests/base.py", line 116, in func
  return f(self, *args, **kwargs)
File "neutron/tests/functional/agent/l3/test_legacy_router.py", line 155, 
in test_conntrack_disassociate_fip_legacy_router
  self._test_conntrack_disassociate_fip(ha=False)
File "neutron/tests/functional/agent/l3/framework.py", line 159, in 
_test_conntrack_disassociate_fip
  self.assertTrue(netcat.test_connectivity())
File "neutron/tests/common/net_helpers.py", line 505, in test_connectivity
  message = self.server_process.read_stdout(READ_TIMEOUT).strip()
File "neutron/tests/common/net_helpers.py", line 287, in read_stdout
  return self._read_stream(self.stdout, timeout)
File "neutron/tests/common/net_helpers.py", line 292, in _read_stream
  poller = select.poll()
  AttributeError: 'module' object has no attribute 'poll'

  That's because as per release notes for 0.20.0, select.poll was
  removed:

  http://eventlet.net/doc/changelog.html#id2

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1674557/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1669696] Re: Some select widgets are not themable

[OpenStack Infra]

Reviewed:  https://review.openstack.org/440978
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=00173dc3c8a81a18807084c07e0e16bed0ecfd0a
Submitter: Jenkins
Branch:master

commit 00173dc3c8a81a18807084c07e0e16bed0ecfd0a
Author: Kenji Ishii 
Date:   Fri Mar 3 17:15:29 2017 +0900

Use ThemableSelectWidget for themable

Some places are not using ThemableSelectWidget, so
these select ui is not themable. This patch fix it.

Change-Id: I303a9cf8c6f8f651edf68973a2f5e16a8b04b26d
Closes-bug: #1669696


** Changed in: horizon
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1669696

Title:
  Some select widgets are not themable

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  We have ThemableSelectWidget class and this is for the themable widget for 
Select.
  Some places don't use this class.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1669696/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1651658] Re: In drawer, 'priority' attribute should be handled conversely against rows

[OpenStack Infra]

Reviewed:  https://review.openstack.org/413462
Committed: 
https://git.openstack.org/cgit/openstack/horizon/commit/?id=d33939cb982ede5973f8b0cebbd5c5f55e61cd0c
Submitter: Jenkins
Branch:master

commit d33939cb982ede5973f8b0cebbd5c5f55e61cd0c
Author: Shu Muto 
Date:   Wed Dec 21 16:33:36 2016 +0900

In drawer, handle 'priority' attribute conversely against row

'priority' attribute has be handled in drawer [1][2], but the behavior
is same as in rows. The behavior is that the items which have lower
priority are hidden from both of row and drawer when wid$

Drawer is used for the supplements against the row, so it should be
handled conversely.
It means that items appear in drawer when they are hidden from row.

This patch fixes it.

[1] https://bugs.launchpad.net/horizon/+bug/1648332
[2] https://review.openstack.org/#/c/397132/

Change-Id: Ia0487a1d95ba16d764546cdb374fe786a0f0f648
Closes-Bug: #1651658


** Changed in: horizon
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1651658

Title:
  In drawer, 'priority' attribute should be handled conversely against
  rows

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  'priority' attribute has be handled in drawer [1][2], but the behavior is 
same as in rows.
  The behavior is that the items which have lower priority are hidden from both 
of row and drawer when widow width is narrower.

  Drawer is used for the supplements against the row, so it should be handled 
conversely.
  It means that items appear in drawer when they are hidden from row.

  [1] https://bugs.launchpad.net/horizon/+bug/1648332
  [2] https://review.openstack.org/#/c/397132/

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1651658/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674546] [NEW] Remove log translations

[yfzhao]

Public bug reported:


Log messages are no longer being translated. This removes all use of
the _LE, _LI, and _LW translation markers to simplify logging and to
avoid confusion with new contributions.

See:
http://lists.openstack.org/pipermail/openstack-i18n/2016-November/002574.html
http://lists.openstack.org/pipermail/openstack-dev/2017-March/113365.html

** Affects: glance
 Importance: Undecided
 Assignee: yfzhao (yfzhao)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => yfzhao (yfzhao)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1674546

Title:
   Remove log translations

Status in Glance:
  New

Bug description:
  
  Log messages are no longer being translated. This removes all use of
  the _LE, _LI, and _LW translation markers to simplify logging and to
  avoid confusion with new contributions.

  See:
  http://lists.openstack.org/pipermail/openstack-i18n/2016-November/002574.html
  http://lists.openstack.org/pipermail/openstack-dev/2017-March/113365.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1674546/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1592000] Re: [RFE] Admin customized default security-group

[Launchpad Bug Tracker]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1592000

Title:
  [RFE] Admin customized default security-group

Status in neutron:
  Expired

Bug description:
  Allow the admin to decide which rules should be added (by default) to
  the tenant default security-group once created.

  At the moment, each tenant default security-group is created with specific 
set of rules: allow all egress and allow ingress from default sg.
  However, this is not the desired behavior for all deployments, as some would 
want to practice a “zero trust” model where all traffic is blocked unless 
explicitly decided otherwise, or on the other hand, allow all inbound+outbound 
traffic.
  It’s worth nothing that at some use cases the default behavior can be 
expressed with very specific sets of rules, which only the admin has the 
knowledge to define (e.g- allow connection to active directory endpoints), in 
such cases the impact on usability is even worse, as it requires the admin to 
create rules on every tenant default security-group.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1592000/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1592627] Re: [RFE] Lack of support for SR-IOV bond.

[Launchpad Bug Tracker]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1592627

Title:
  [RFE] Lack of support for SR-IOV bond.

Status in neutron:
  Expired

Bug description:
  Now sriov don't have the function of bond. In NFV, we need to add a
  bond port using sriov. One option is to use two sriov port using as a
  bond port. Another option is just one port and add option of port
  create. Such as "--bond" to add two vf in a port when we use "neutron
  port-create". I prefer the second way，because it is easy to use, or
  there are other way to do this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1592627/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1462082] Re: Delete Objects should have check box to select all

[Launchpad Bug Tracker]

[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]

** Changed in: horizon
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1462082

Title:
  Delete Objects should have check box to select all

Status in OpenStack Dashboard (Horizon):
  Expired

Bug description:
  It's not possible to delete a Container that contains objects (I wish
  this was possible) - So instead I need to drill down to all objects
  and from the bottom up and delete them.  There is no way to select all
  objects when attempting delete the objects in a panel.  Need a box
  that allows for selecting all objects for deletion.  See attached
  screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1462082/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1605343] Re: [rfe] update CIDR for subnet

[Launchpad Bug Tracker]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1605343

Title:
  [rfe] update CIDR for subnet

Status in neutron:
  Expired

Bug description:
  Use case to solve: as an operator I want to expand or shrink Public
  network without re-allocating all Floating IPs.

  Currently, updating subnet CIDR is blocked by validation from API
  side. By the way, PD code is already updating CIDRs so far.

  Generic approach is:

    1. Accept CIDR and optionally allocation pools and gateway_ip.
    2. If new allocation pool is not provided, and old pool is not fit into
   CIDR, then fail. Same for GW.
    3. Re-allocate IP if they're out of new allocation pool.

  Here is a proposed patch https://review.openstack.org/#/c/345594/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1605343/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1656242] Re: nova live snapshot of rbd instance fails on xen hypervisor

[Launchpad Bug Tracker]

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1656242

Title:
  nova live snapshot of rbd instance fails on xen hypervisor

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Description:
  We use a Mitaka environment with one control and three compute nodes (all 
running on openSUSE Leap 42.1), the compute nodes are xen hypervisors, our 
storage backend is ceph (for nova, glance and cinder).

  When we try to snapshot a running instance, it's always a cold
  snapshot, nova-compute reports:

  2017-01-12 12:55:51.919 [instance: 14b75237-7619-481f-9636-792b64d1be17] 
Beginning cold snapshot process
  2017-01-12 12:59:27.085 [instance: 14b75237-7619-481f-9636-792b64d1be17] 
Snapshot image upload complete

  On rbd level the live snapshot process works as expected, without any
  downtime of the instance, we use it for our backup strategy for
  example.

  With some additional log statements in /usr/lib/python2.7/site-
  packages/nova/virt/libvirt/driver.py I found that nova always passes
  hard coded hypervisor-driver "qemu" into the function
  _host.has_min_version(), it always returns "false" so that
  "live_snapshot" is disabled. Replacing host.HV_DRIVER_QEMU with
  host.HV_DRIVER_XEN results in a working live snapshot:

  ---cut here---
  compute1:~ # diff -u 
/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py 
/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py.mod
  --- /usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py
2017-01-13 09:33:23.257525708 +0100
  +++ /usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py.mod
2017-01-13 09:33:46.349105366 +0100
  @@ -1649,9 +1649,14 @@
   #   redundant because LVM supports only cold snapshots.
   #   It is necessary in case this situation changes in the
   #   future.
  +if CONF.libvirt.virt_type == 'xen':
  +hv_driver = host.HV_DRIVER_XEN
  +else:
  +hv_driver = host.HV_DRIVER_QEMU
  +
   if (self._host.has_min_version(MIN_LIBVIRT_LIVESNAPSHOT_VERSION,
  MIN_QEMU_LIVESNAPSHOT_VERSION,
  -   host.HV_DRIVER_QEMU)
  +   hv_driver)
and source_type not in ('lvm')
and not CONF.ephemeral_storage_encryption.enabled
and not CONF.workarounds.disable_libvirt_livesnapshot):
  ---cut here---

  nova-compute reports:

  2017-01-12 17:20:22.760 [instance: 14b75237-7619-481f-9636-792b64d1be17] 
instance snapshotting
  2017-01-12 17:20:24.049 [instance: 14b75237-7619-481f-9636-792b64d1be17] 
Beginning live snapshot process
  2017-01-12 17:24:38.997 [instance: 14b75237-7619-481f-9636-792b64d1be17] 
Snapshot image upload complete

  The versions we use:

  compute1:~ # nova --version
  3.3.0

  compute1:~ # ceph --version
  ceph version 0.94.7-84-g8e6f430 (8e6f430683e4d8293e31fd4eb6cb09be96960cfa)

  compute1:~ # libvirtd --version
  libvirtd (libvirt) 2.5.0

  compute1:~ # qemu-img --version
  qemu-img version 2.7.0((SUSE Linux)), Copyright (c) 2003-2016 Fabrice Bellard 
and the QEMU Project developers

  compute1:~ # rpm -qa | grep xen
  xen-4.7.0_12-461.1.x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1656242/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1657655] Re: Dashboard|出错啦！遇到异常情况，请刷新。如需帮助请联系管理员。

[Launchpad Bug Tracker]

[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]

** Changed in: horizon
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1657655

Title:
  Dashboard|出错啦！遇到异常情况，请刷新。如需帮助请联系管理员。

Status in OpenStack Dashboard (Horizon):
  Expired

Bug description:
  Documents:
  http://docs.openstack.org/mitaka/zh_CN/
  While I do with above URl
  At the part of Dashboard
  http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/horizon-verify.html
  I can't login in ..

  登录后提示：出错啦！遇到异常情况，请刷新。如需帮助请联系管理员。

  [Thu Jan 19 14:51:17.321188 2017] [:error] [pid 15466] Login successful for 
user "admin".
  [Thu Jan 19 14:51:21.938370 2017] [:error] [pid 15466] Internal Server Error: 
/dashboard/auth/login/
  [Thu Jan 19 14:51:21.938397 2017] [:error] [pid 15466] Traceback (most recent 
call last):
  [Thu Jan 19 14:51:21.938401 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in 
get_response
  [Thu Jan 19 14:51:21.938404 2017] [:error] [pid 15466] response = 
wrapped_callback(request, *callback_args, **callback_kwargs)
  [Thu Jan 19 14:51:21.938407 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/django/views/decorators/debug.py", line 76, 
in sensitive_post_parameters_wrapper
  [Thu Jan 19 14:51:21.938410 2017] [:error] [pid 15466] return 
view(request, *args, **kwargs)
  [Thu Jan 19 14:51:21.938412 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 110, in 
_wrapped_view
  [Thu Jan 19 14:51:21.938415 2017] [:error] [pid 15466] response = 
view_func(request, *args, **kwargs)
  [Thu Jan 19 14:51:21.938417 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/django/views/decorators/cache.py", line 57, 
in _wrapped_view_func
  [Thu Jan 19 14:51:21.938420 2017] [:error] [pid 15466] response = 
view_func(request, *args, **kwargs)
  [Thu Jan 19 14:51:21.938422 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/openstack_auth/views.py", line 103, in login
  [Thu Jan 19 14:51:21.938441 2017] [:error] [pid 15466] **kwargs)
  [Thu Jan 19 14:51:21.938445 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/django/views/decorators/debug.py", line 76, 
in sensitive_post_parameters_wrapper
  [Thu Jan 19 14:51:21.938447 2017] [:error] [pid 15466] return 
view(request, *args, **kwargs)
  [Thu Jan 19 14:51:21.938450 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 110, in 
_wrapped_view
  [Thu Jan 19 14:51:21.938452 2017] [:error] [pid 15466] response = 
view_func(request, *args, **kwargs)
  [Thu Jan 19 14:51:21.938455 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/django/views/decorators/cache.py", line 57, 
in _wrapped_view_func
  [Thu Jan 19 14:51:21.938457 2017] [:error] [pid 15466] response = 
view_func(request, *args, **kwargs)
  [Thu Jan 19 14:51:21.938460 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/django/contrib/auth/views.py", line 51, in 
login
  [Thu Jan 19 14:51:21.938462 2017] [:error] [pid 15466] 
auth_login(request, form.get_user())
  [Thu Jan 19 14:51:21.938464 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/django/contrib/auth/__init__.py", line 110, 
in login
  [Thu Jan 19 14:51:21.938467 2017] [:error] [pid 15466] 
request.session.cycle_key()
  [Thu Jan 19 14:51:21.938470 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/django/contrib/sessions/backends/base.py", 
line 285, in cycle_key
  [Thu Jan 19 14:51:21.938472 2017] [:error] [pid 15466] self.create()
  [Thu Jan 19 14:51:21.938474 2017] [:error] [pid 15466]   File 
"/usr/lib/python2.7/site-packages/django/contrib/sessions/backends/cache.py", 
line 48, in create
  [Thu Jan 19 14:51:21.938477 2017] [:error] [pid 15466] "Unable to create 
a new session key. "
  [Thu Jan 19 14:51:21.938479 2017] [:error] [pid 15466] RuntimeError: Unable 
to create a new session key. It is likely that the cache is unavailable.
  [root@controller httpd]#

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1657655/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1665318] Re: Fwaas(bind a firewall to a legacy router that without qrouter namespace):iptables rules do not tabke effect after the qrouter namespace created.

[wujun]

** Changed in: neutron
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1665318

Title:
  Fwaas(bind a firewall to a legacy router that without qrouter
  namespace):iptables rules do not tabke effect  after the qrouter
  namespace created.

Status in neutron:
  Invalid

Bug description:
  environment: Mitaka

  1.create a legacy router (do not add interface and set gateway), so there is 
no qrouter namespace
  2.bind a firewall to the router
  3.add interface or set gateway for the router, qrouter namespace is created 
now

  The problem is there no firewall rule in the qrouter namespace.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1665318/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1635358] Re: os-volume_attachments APIs requiring os-volumes permissions

[OpenStack Infra]

Reviewed:  https://review.openstack.org/389314
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=4aa55f3edf453b3baba4efef4cca054f490f2d69
Submitter: Jenkins
Branch:master

commit 4aa55f3edf453b3baba4efef4cca054f490f2d69
Author: Matthew Edmonds 
Date:   Thu Oct 20 14:26:35 2016 -0400

fix os-volume_attachments policy checks

The os-volume_attachments APIs have their own policy settings defined,
yet were also checking the policy settings defined for the os-volumes
APIs. This should never have been the case, but especially not now
that the os-volumes APIs are deprecated and don't even work anymore
with newer microversions. This change removes the os-volumes policy
checks for os-volume_attachment API requests. The code will continue
to make os-volumes policy checks for os-volumes APIs, and
os-volume_attachment policy checks for os-volume_attachment APIs.

Removed the _items method, which was only being called from one place,
to resolve comments that policy checks should always happen immediately
upon entering the API methods.

Change-Id: I35aaedf5c4c49cb568fa06c2974f9a35aa2ffcc5
Closes-Bug: #1635358
UpgradeImpact


** Changed in: nova
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1635358

Title:
  os-volume_attachments APIs requiring os-volumes permissions

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  The os-volume_attachments APIs (see http://developer.openstack.org
  /api-ref/compute/#servers-with-volume-attachments-servers-os-volume-
  attachments) have their own policy settings defined, yet are also
  checking the policy settings which are defined for the os-volumes APIs
  (see http://developer.openstack.org/api-ref/compute/#volume-extension-
  os-volumes-os-snapshots-deprecated). This should never have been the
  case, but especially not now that the os-volumes APIs have been
  deprecated and have even stopped working with newer microversions.

  seen in newton

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1635358/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1670642] Re: get_model method missing for Ploop image

[Matt Riedemann]

** Also affects: nova/ocata
   Importance: Undecided
   Status: New

** Changed in: nova/ocata
   Status: New => In Progress

** Tags added: libvirt parallels

** Changed in: nova
   Importance: Undecided => Medium

** Changed in: nova/ocata
   Importance: Undecided => Medium

** Changed in: nova/ocata
 Assignee: (unassigned) => Lee Yarwood (lyarwood)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1670642

Title:
  get_model method missing for Ploop image

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) ocata series:
  In Progress

Bug description:
  This results in failures in inject_data from nova/virt/disk/api.py
  even if no real data is injected:

  2017-03-03 15:11:55.707 48683 ERROR nova.virt.libvirt.driver 
[req-f6f3df11-35b0-44c2-a1c4-52548504a1b5 fd33deabe809466a8dcd517bdf882e6b 
e4046b10f1074f06bd5d474ddfce09bc - - -] [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] Error injecting data into image 
082f0243-cd99-4312-a27a-86b8cd3688d2 ()
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager 
[req-f6f3df11-35b0-44c2-a1c4-52548504a1b5 fd33deabe809466a8dcd517bdf882e6b 
e4046b10f1074f06bd5d474ddfce09bc - - -] [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] Instance failed to spawn
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] Traceback (most recent call last):
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2078, in 
_build_resources
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] yield resources
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1920, in 
_build_and_run_instance
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] block_device_info=block_device_info)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2624, in 
spawn
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] admin_pass=admin_password)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3028, in 
_create_image
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] fallback_from_host)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3137, in 
_create_and_inject_local_root
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] files)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2977, in 
_inject_data
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] instance=instance)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] self.force_reraise()
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] six.reraise(self.type_, self.value, 
self.tb)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2968, in 
_inject_data
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] 
disk_api.inject_data(injection_image.get_model(self._conn),
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/imagebackend.py", line 395, 
in get_model
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 

[Yahoo-eng-team] [Bug 1674517] [NEW] pecan missing custom tenant_id policy project_id matching

[Kevin Benton]

Public bug reported:

The pecan code is missing these two chunks of code to support filtering
project_id based on tenant_id policies:

https://github.com/openstack/neutron/blob/cd947ac4d05a5301fb3bf704b0dd1ca39fd7e541/neutron/api/v2/base.py#L173-L179
https://github.com/openstack/neutron/blob/cd947ac4d05a5301fb3bf704b0dd1ca39fd7e541/neutron/api/v2/base.py#L193-L197


They need to be added in here:

https://github.com/openstack/neutron/blob/cd947ac4d05a5301fb3bf704b0dd1ca39fd7e541/neutron/pecan_wsgi/hooks/policy_enforcement.py#L225

** Affects: neutron
 Importance: Medium
 Status: Confirmed


** Tags: api low-hanging-fruit

** Tags added: api

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1674517

Title:
  pecan missing custom tenant_id policy project_id matching

Status in neutron:
  Confirmed

Bug description:
  The pecan code is missing these two chunks of code to support
  filtering project_id based on tenant_id policies:

  
https://github.com/openstack/neutron/blob/cd947ac4d05a5301fb3bf704b0dd1ca39fd7e541/neutron/api/v2/base.py#L173-L179
  
https://github.com/openstack/neutron/blob/cd947ac4d05a5301fb3bf704b0dd1ca39fd7e541/neutron/api/v2/base.py#L193-L197

  
  They need to be added in here:

  
https://github.com/openstack/neutron/blob/cd947ac4d05a5301fb3bf704b0dd1ca39fd7e541/neutron/pecan_wsgi/hooks/policy_enforcement.py#L225

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1674517/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1668908] Re: available_local_vlans miss 4094

[OpenStack Infra]

Reviewed:  https://review.openstack.org/440609
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=ae8e6095f9c15f9d1012427c0b098c98fdc154fa
Submitter: Jenkins
Branch:master

commit ae8e6095f9c15f9d1012427c0b098c98fdc154fa
Author: rtmdk 
Date:   Thu Mar 2 22:21:47 2017 -0700

add 4094 to fix the range of available local vlans

in fact the range of available local vlan is 1-4094,
but when initialization of the local vlan in ovs_neutron_agent,
self.available_local_vlans is set([1,2,3...4093]),omit 4094
This causes a problem that ovs-agent will not use 4094 as local vlan

modify moves.range(p_const.MIN_VLAN_TAG, p_const.MAX_VLAN_TAG+1)

Closes-Bug: #1668908
Change-Id: Ic25929cad89ab2e31fdf5b70875b84491dfc52ed


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1668908

Title:
  available_local_vlans miss 4094

Status in neutron:
  Fix Released

Bug description:
  p_const.MIN_VLAN_TAG=1
  p_const.MAX_VLAN_TAG=4094

  
  self.available_local_vlans = 
set(moves.range(p_const.MIN_VLAN_TAG,p_const.MAX_VLAN_TAG))

  
  the value of self.available_local_vlans is ([1,2.4093]),omit 4094
  when ovs-agent set the local vlan，4094 is valid

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1668908/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674486] [NEW] sync_instances in os-cells undocumented

[Sujitha]

Public bug reported:

sync_instances action in os-cells API is not documented in
https://developer.openstack.org/api-ref/compute/.

** Affects: nova
 Importance: Undecided
 Assignee: Sujitha (sujitha-neti)
 Status: New


** Tags: api-ref

** Summary changed:

- sync_instances
+ sync_instances in os-cells undocumented

** Tags added: api-ref

** Changed in: nova
 Assignee: (unassigned) => Sujitha (sujitha-neti)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1674486

Title:
  sync_instances in os-cells undocumented

Status in OpenStack Compute (nova):
  New

Bug description:
  sync_instances action in os-cells API is not documented in
  https://developer.openstack.org/api-ref/compute/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1674486/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1633669] Re: Pecan: Tempest API tests fail for RoutersSearchCriteriaTest

[Anindita Das]

** Changed in: neutron
   Status: In Progress => Invalid

** Changed in: neutron
 Assignee: Anindita Das (anindita-das) => (unassigned)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1633669

Title:
  Pecan: Tempest API tests fail for RoutersSearchCriteriaTest

Status in neutron:
  Invalid

Bug description:
  
neutron.tests.tempest.api.test_routers.RoutersSearchCriteriaTest.test_list_pagination_with_href_links

  Traceback (most recent call last):
File "/opt/stack/new/neutron/neutron/tests/tempest/api/test_routers.py", 
line 295, in test_list_pagination_with_href_links
  self._test_list_pagination_with_href_links()
File "/opt/stack/new/neutron/neutron/tests/tempest/api/base.py", line 503, 
in inner
  return f(self, *args, **kwargs)
File "/opt/stack/new/neutron/neutron/tests/tempest/api/base.py", line 494, 
in inner
  return f(self, *args, **kwargs)
File "/opt/stack/new/neutron/neutron/tests/tempest/api/base.py", line 681, 
in _test_list_pagination_with_href_links
  self._test_list_pagination_iteratively(self._list_all_with_hrefs)
File "/opt/stack/new/neutron/neutron/tests/tempest/api/base.py", line 610, 
in _test_list_pagination_iteratively
  len(expected_resources), sort_args
File "/opt/stack/new/neutron/neutron/tests/tempest/api/base.py", line 653, 
in _list_all_with_hrefs
  self.assertEqual(1, len(resources_))
File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 
411, in assertEqual
  self.assertThat(observed, matcher, message)
File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 
498, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: 1 != 0

  
  
neutron.tests.tempest.api.test_routers.RoutersSearchCriteriaTest.test_list_pagination_with_marker

  Traceback (most recent call last):
File "/opt/stack/new/neutron/neutron/tests/tempest/api/test_routers.py", 
line 291, in test_list_pagination_with_marker
  self._test_list_pagination_with_marker()
File "/opt/stack/new/neutron/neutron/tests/tempest/api/base.py", line 503, 
in inner
  return f(self, *args, **kwargs)
File "/opt/stack/new/neutron/neutron/tests/tempest/api/base.py", line 494, 
in inner
  return f(self, *args, **kwargs)
File "/opt/stack/new/neutron/neutron/tests/tempest/api/base.py", line 635, 
in _test_list_pagination_with_marker
  self._test_list_pagination_iteratively(self._list_all_with_marker)
File "/opt/stack/new/neutron/neutron/tests/tempest/api/base.py", line 615, 
in _test_list_pagination_iteratively
  self.assertSameOrder(expected_resources, resources)
File "/opt/stack/new/neutron/neutron/tests/tempest/api/base.py", line 533, 
in assertSameOrder
  self.assertEqual(expected[self.field], res[self.field])
File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 
411, in assertEqual
  self.assertThat(observed, matcher, message)
File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 
498, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: u'test10' != u'test1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1633669/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1580327] Re: [RFE] Neutron Feature Classification

[OpenStack Infra]

Reviewed:  https://review.openstack.org/318192
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=c0130c57e5138a8906fad7cab9cf820b88064d72
Submitter: Jenkins
Branch:master

commit c0130c57e5138a8906fad7cab9cf820b88064d72
Author: Ankur Gupta 
Date:   Wed May 18 10:14:19 2016 -0500

Neutron Feature Classification

The feature classification matrix will provide information about
plugins and the features they support.
Acts as a launching point for users to read about the intent
of the matrix before reviewing the matrix to find features and plugins
that meet their needs.

Will implement a page where users can view Neutron features
and plugins and their status.
Similar to Nova's implementation here:
http://docs.openstack.org/developer/nova/feature_classification.html
http://docs.openstack.org/developer/nova/support-matrix.html

Co-Authored-By: Darek Smigiel 

Closes-Bug: #1580327

Change-Id: I67f4dc67883623decdbf136c598eb9e2d0bc24c4


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1580327

Title:
  [RFE] Neutron Feature Classification

Status in neutron:
  Fix Released

Bug description:
  Based off of the OpenStack User Story:
  https://review.openstack.org/#/c/291298/

  From the User Story: Problem Definition
  --
  Operators and Users lack centralized visibility into the status of the
  completeness, stability and documentation of features. They also lack 
knowledge
  of the effects of configuration decisions on these features and their
  classification. This prevents Operators from making optimal decisions when
  configuring their clouds and leaves their users unsure of the maturity and
  stability of features they might choose to use in their applications and
  workloads.

  Will implement a page where users can view Neutron features and plugins and 
their status.
  Similar to Nova's implementation here:
  http://docs.openstack.org/developer/nova/feature_classification.html
  http://docs.openstack.org/developer/nova/support-matrix.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1580327/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1664463] Re: should not allow delete cell_v2 cell0

[OpenStack Infra]

Reviewed:  https://review.openstack.org/433476
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=17b9f83778fbc5e902d938c4ee5ed19beda8a9d4
Submitter: Jenkins
Branch:master

commit 17b9f83778fbc5e902d938c4ee5ed19beda8a9d4
Author: jichenjc 
Date:   Mon Jan 23 23:31:24 2017 +0800

Prevent delete cell0 in nova-manage command

not allow to delete cell0 in nova-manage command
as it's used by nova

Change-Id: I64ddba522c34e46ac8f642af4b26a926015ab330
Closes-Bug: 1664463


** Changed in: nova
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1664463

Title:
  should not allow delete cell_v2 cell0

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  
  latest nova

  commit fb8ca9df80d9c63fcdec58e66f0403340db2c525

  result: delete_cell command can delete cell_v2 cell0 
  expect: the delete cell0 should fail

  after cell delete

  stack@ubuntu1604:~$ nova-manage cell_v2 list_cells
  /usr/local/lib/python2.7/dist-packages/pymysql/cursors.py:166: Warning: 
(3090, u"Changing sql mode 'NO_AUTO_CREATE_USER' is deprecated. It will be 
removed in a future release.")
result = self._query(query)
  +--+--+
  | Name | UUID |
  +--+--+
  | None | 85980b20-6ca3-451f-a873-af4a5ba3809f |
  +--+--+

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1664463/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674449] [NEW] NoneType logging warning with "Received unexpected event network-vif-unplugged" message

[Matt Riedemann]

Public bug reported:

http://logs.openstack.org/90/417590/9/check/gate-tempest-dsvm-neutron-
full-ubuntu-
xenial/c831c5d/logs/screen-n-cpu.txt.gz?level=TRACE#_2017-03-20_17_10_19_178

2017-03-20 17:10:19.178 6155 WARNING nova.compute.manager 
[req-cc7e154f-3cfa-46bd-8af5-d7b4a0871836 service nova] [instance: 
dae92389-8afc-4666-b290-788e62749524] Received unexpected event 
network-vif-unplugged-8ed92137-a81a-4afd-a391-854848cd2916 for instance
Traceback (most recent call last):
  File "/usr/lib/python2.7/logging/__init__.py", line 861, in emit
msg = self.format(record)
  File "/usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py", line 100, 
in format
return logging.StreamHandler.format(self, record)
  File "/usr/lib/python2.7/logging/__init__.py", line 734, in format
return fmt.format(record)
  File "/usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py", line 
273, in format
for arg in record.args:
TypeError: 'NoneType' object is not iterable
Logged from file processutils.py, line 385

Introduced here:

https://review.openstack.org/#/c/381888/1/nova/compute/manager.py@6641

** Affects: nova
 Importance: Medium
 Status: Triaged

** Affects: nova/ocata
 Importance: Medium
 Status: Confirmed


** Tags: ocata-backport-potential

** Also affects: nova/ocata
   Importance: Undecided
   Status: New

** Changed in: nova/ocata
   Status: New => Confirmed

** Changed in: nova/ocata
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1674449

Title:
  NoneType logging warning with "Received unexpected event network-vif-
  unplugged" message

Status in OpenStack Compute (nova):
  Triaged
Status in OpenStack Compute (nova) ocata series:
  Confirmed

Bug description:
  http://logs.openstack.org/90/417590/9/check/gate-tempest-dsvm-neutron-
  full-ubuntu-
  xenial/c831c5d/logs/screen-n-cpu.txt.gz?level=TRACE#_2017-03-20_17_10_19_178

  2017-03-20 17:10:19.178 6155 WARNING nova.compute.manager 
[req-cc7e154f-3cfa-46bd-8af5-d7b4a0871836 service nova] [instance: 
dae92389-8afc-4666-b290-788e62749524] Received unexpected event 
network-vif-unplugged-8ed92137-a81a-4afd-a391-854848cd2916 for instance
  Traceback (most recent call last):
File "/usr/lib/python2.7/logging/__init__.py", line 861, in emit
  msg = self.format(record)
File "/usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py", line 
100, in format
  return logging.StreamHandler.format(self, record)
File "/usr/lib/python2.7/logging/__init__.py", line 734, in format
  return fmt.format(record)
File "/usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py", line 
273, in format
  for arg in record.args:
  TypeError: 'NoneType' object is not iterable
  Logged from file processutils.py, line 385

  Introduced here:

  https://review.openstack.org/#/c/381888/1/nova/compute/manager.py@6641

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1674449/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674443] [NEW] gate-grenade-dsvm-neutron-linuxbridge-multinode fails on smoke test sometimes

[Manjeet Singh Bhatia]

Public bug reported:

failure rate for gate-grenade-dsvm-neutron-linuxbridge-multinode is
increasing, from logs It looks like it fails mostly on executing smoke
tests, there could be range of reasons for it failing, corrupted data
plane, timeout for instance build etc. one of my observation is it fails
when it runs of rax-node cloud. one other thing I've noticed it runs
smoke tests with concurrency=4.

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: gate-failure upgrades

** Tags added: gate-failure

** Tags added: upgrades

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1674443

Title:
  gate-grenade-dsvm-neutron-linuxbridge-multinode fails on smoke test
  sometimes

Status in neutron:
  New

Bug description:
  failure rate for gate-grenade-dsvm-neutron-linuxbridge-multinode is
  increasing, from logs It looks like it fails mostly on executing smoke
  tests, there could be range of reasons for it failing, corrupted data
  plane, timeout for instance build etc. one of my observation is it
  fails when it runs of rax-node cloud. one other thing I've noticed it
  runs smoke tests with concurrency=4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1674443/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1673910] Re: libvirt racing with linux bridge agent

[OpenStack Infra]

Reviewed:  https://review.openstack.org/447173
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=ce3f96f324b21f8ef3b3a4c02adc678411163a84
Submitter: Jenkins
Branch:master

commit ce3f96f324b21f8ef3b3a4c02adc678411163a84
Author: Kevin Benton 
Date:   Sat Mar 18 01:06:54 2017 +

Revert "Stop skipping compute owner in Linux Bridge loop"

This reverts commit 1feb19c83ff61a3782ce862d71b8d04e21d7aa00.
Better fix in I23c5faaeab69aede1fd038a36f4a0b8f928498ce but that
make take time due to dependency on a nova patch.

Change-Id: Iaa4d85f63cb8e058d09858636ce1434352e39bed
Closes-Bug: #1673910


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1673910

Title:
  libvirt racing with linux bridge agent

Status in neutron:
  Fix Released

Bug description:
  We're getting the following error in the gate on linux bridge jobs:

  2017-03-16 15:13:15.984 5903 ERROR oslo_messaging.rpc.server
  libvirtError: Unable to add bridge brq776c3f9c-e6 port tapc5c67a59-f3:
  Device or resource busy

  
  This is caused by the merge of I2a23d0cbc4c4d0db6e9f48d91ca03b5007f91a84 
which causes the LB agent to no longer skip compute ports. Even though os-vif 
has protection from races, it appears that libvirt itself is not robust to the 
tap being added to the bridge by another process.


  1. http://logs.openstack.org/06/445706/5/gate/gate-tempest-dsvm-
  neutron-linuxbridge-ubuntu-
  xenial/a1314ac/logs/screen-n-cpu.txt.gz?level=TRACE

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1673910/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674434] [NEW] RouterL3AgentBindingDbObjTestCase may fail with NeutronDbObjectDuplicateEntry

[Ihar Hrachyshka]

Public bug reported:

http://logs.openstack.org/08/360908/51/gate/gate-neutron-
python35/8473cfb/testr_results.html.gz

Traceback (most recent call last):
  File "/home/jenkins/workspace/gate-neutron-python35/neutron/tests/base.py", 
line 116, in func
return f(self, *args, **kwargs)
  File 
"/home/jenkins/workspace/gate-neutron-python35/neutron/tests/unit/objects/test_base.py",
 line 1640, in test_count_validate_filters_false
self._make_object(fields).create()
  File "/home/jenkins/workspace/gate-neutron-python35/neutron/objects/base.py", 
line 212, in decorator
res = func(self, *args, **kwargs)
  File "/home/jenkins/workspace/gate-neutron-python35/neutron/objects/base.py", 
line 592, in create
object_class=self.__class__, db_exception=db_exc)
neutron.objects.exceptions.NeutronDbObjectDuplicateEntry: Failed to create a 
duplicate RouterL3AgentBinding: for attribute(s) ['router_id', 'binding_index'] 
with value(s) None

This is triggered by https://review.openstack.org/#/c/360908/

** Affects: neutron
 Importance: Medium
 Assignee: Ihar Hrachyshka (ihar-hrachyshka)
 Status: In Progress


** Tags: gate-failure unittest

** Tags added: gate-failure unittest

** Changed in: neutron
 Assignee: (unassigned) => Ihar Hrachyshka (ihar-hrachyshka)

** Changed in: neutron
   Status: New => In Progress

** Changed in: neutron
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1674434

Title:
  RouterL3AgentBindingDbObjTestCase may fail with
  NeutronDbObjectDuplicateEntry

Status in neutron:
  In Progress

Bug description:
  http://logs.openstack.org/08/360908/51/gate/gate-neutron-
  python35/8473cfb/testr_results.html.gz

  Traceback (most recent call last):
File "/home/jenkins/workspace/gate-neutron-python35/neutron/tests/base.py", 
line 116, in func
  return f(self, *args, **kwargs)
File 
"/home/jenkins/workspace/gate-neutron-python35/neutron/tests/unit/objects/test_base.py",
 line 1640, in test_count_validate_filters_false
  self._make_object(fields).create()
File 
"/home/jenkins/workspace/gate-neutron-python35/neutron/objects/base.py", line 
212, in decorator
  res = func(self, *args, **kwargs)
File 
"/home/jenkins/workspace/gate-neutron-python35/neutron/objects/base.py", line 
592, in create
  object_class=self.__class__, db_exception=db_exc)
  neutron.objects.exceptions.NeutronDbObjectDuplicateEntry: Failed to create a 
duplicate RouterL3AgentBinding: for attribute(s) ['router_id', 'binding_index'] 
with value(s) None

  This is triggered by https://review.openstack.org/#/c/360908/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1674434/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674415] [NEW] keystone exception messages are not translating when locale is set

[prashkre]

Public bug reported:

When user invokes identity API's on an environment with locale(other
than default locale en_US) being set, keystone.exception messages are
not getting translated in case of any error messages from identity API.

For example: we are requesting to get list of projects without authtoken
and Accept-Language: de.

curl -g -i --insecure -X GET https://<>:5000/v3/projects? -H 
"User-Agent: python-keystoneclient" -H "Accept: application/json" -H 
"Accept-Language: de"
HTTP/1.1 401 Unauthorized
Date: Mon, 20 Mar 2017 14:31:54 GMT
Server: Apache
Vary: X-Auth-Token
x-openstack-request-id: req-63b4b8ae-e8fc-4a6d-9744-cc9bc268c6c2
WWW-Authenticate: Keystone uri="https://<>:5000"
Content-Length: 114
Content-Type: application/json

Actual Result:
{"error": {"message": "The request you have made requires authentication.", 
"code": 401, "title": "Unauthorized"}}


Expected Result:
{"error": {"message": "Die von Ihnen gestellte Anfrage erfoderdert eine 
Authentifizierung.", "code": 401, "title": "Unauthorized"}}

** Affects: keystone
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1674415

Title:
  keystone exception messages are not translating when locale is set

Status in OpenStack Identity (keystone):
  New

Bug description:
  When user invokes identity API's on an environment with locale(other
  than default locale en_US) being set, keystone.exception messages are
  not getting translated in case of any error messages from identity
  API.

  For example: we are requesting to get list of projects without
  authtoken and Accept-Language: de.

  curl -g -i --insecure -X GET https://<>:5000/v3/projects? -H 
"User-Agent: python-keystoneclient" -H "Accept: application/json" -H 
"Accept-Language: de"
  HTTP/1.1 401 Unauthorized
  Date: Mon, 20 Mar 2017 14:31:54 GMT
  Server: Apache
  Vary: X-Auth-Token
  x-openstack-request-id: req-63b4b8ae-e8fc-4a6d-9744-cc9bc268c6c2
  WWW-Authenticate: Keystone uri="https://<>:5000"
  Content-Length: 114
  Content-Type: application/json

  Actual Result:
  {"error": {"message": "The request you have made requires authentication.", 
"code": 401, "title": "Unauthorized"}}

  
  Expected Result:
  {"error": {"message": "Die von Ihnen gestellte Anfrage erfoderdert eine 
Authentifizierung.", "code": 401, "title": "Unauthorized"}}

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1674415/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1669847] Re: sample config default values show details of infra worker instead of intended default values

[OpenStack Infra]

Reviewed:  https://review.openstack.org/441227
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=67bf3b83f6e945ecd38c7ac11c26367052500f8b
Submitter: Jenkins
Branch:master

commit 67bf3b83f6e945ecd38c7ac11c26367052500f8b
Author: Maciej Szankin 
Date:   Fri Mar 3 10:51:56 2017 -0600

conf: fix default values reporting infra worker

Default values set for console_host and
xenserver.console_public_hostname are reporting the details of the
infra worker or some python code,, thus making it unclear what the
real default value should be.

Change-Id: Iba7bf16ba30958d9c4008cc2fbf77cd9f64cf5a3
Closes-Bug: 1669847
Implements: blueprint centralize-config-options-pike


** Changed in: nova
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1669847

Title:
  sample config default values show details of infra worker instead of
  intended default values

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Following the discovery in [1], few more places were found where the
  config options default instead of the intended value reports details
  of infra worker.

  Affected options are:

  * console_host, nova/conf/compute.py
  * xenserver.console_public_hostname, nova/conf/xenserver.py

  [1] https://bugs.launchpad.net/nova/+bug/1669746

  For context:

  #
  # Console proxy host to be used to connect to instances on this host. It is 
the
  # publicly visible name for the console host.
  #
  # Possible values:
  #
  # * Current hostname (default) or any string representing hostname.
  #  (string value)
  #console_host = socket.gethostname()

  #
  # Publicly visible name for this console host.
  #
  # Possible values:
  #
  # * A string representing a valid hostname
  #  (string value)
  # Deprecated group/name - [DEFAULT]/console_public_hostname
  #console_public_hostname = ubuntu-xenial-osic-cloud1-s3700-7551763

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1669847/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674392] [NEW] placement api requires content-type on put and post even when no body

[Chris Dent]

Public bug reported:

The placement API a guarding condition which checks the request method.
If it is PUT, POST or PATCH the presence of a content-type header is
required.

This is too strict (but happened to work fine for the api at the time).
It is reasonable and okay to make a PUT or POST without a body, and thus
without a content-type, and now we want to do such things within the
placement API (with putting custom traits and resource classes).

The fix is to only raise the 400 when content-length is set and non-
zero. In that case a missing content-type is a bug, irrespective of
method.

** Affects: nova
 Importance: Undecided
 Assignee: Chris Dent (cdent)
 Status: In Progress


** Tags: placement

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1674392

Title:
  placement api requires content-type on put and post even when no body

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  The placement API a guarding condition which checks the request
  method. If it is PUT, POST or PATCH the presence of a content-type
  header is required.

  This is too strict (but happened to work fine for the api at the
  time). It is reasonable and okay to make a PUT or POST without a body,
  and thus without a content-type, and now we want to do such things
  within the placement API (with putting custom traits and resource
  classes).

  The fix is to only raise the 400 when content-length is set and non-
  zero. In that case a missing content-type is a bug, irrespective of
  method.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1674392/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1665698] Re: /etc/qemu-ifup not allowed by apparmor

[James Page]

Marking Cloud Archive task as Invalid (as the Newton UCA does not have
any libvirt/qemu packages).

** Also affects: nova
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1665698

Title:
  /etc/qemu-ifup not allowed by apparmor

Status in Ubuntu Cloud Archive:
  Invalid
Status in OpenStack Compute (nova):
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Yakkety:
  Triaged

Bug description:
  I have VMs failing to start with 2017-02-17 15:38:44.458 264015 ERROR
  nova.compute.manager [instance: 0c97ab16-2d30-43fa-b0e4-a064a842b5ed]
  libvirtError: internal error: process exited while connecting to
  monitor: 2017-02-17T15:38:43.907222Z qemu-system-x86_64: -netdev
  tap,ifname=tapf34ef99e-18,id=hostnet0,vhost=on,vhostfd=28: network
  script /etc/qemu-ifup failed with status 256

  Log excerpt:
  http://cdn.pasteraw.com/b3tw4cjefomfi3e9k09hvodrfun85z

  Seems to be that /etc/qemu-ifup is being blocked by apparmor:
  type=AVC msg=audit(1487347189.015:28536): apparmor="DENIED" operation="exec" 
profile="libvirt-4a03fea7-e966-48e4-80ac-aa138db67243" name="/etc/qemu-ifup" 
pid=285438 comm="qemu-system-x86" requested_mask="x" denied_mask="x" fsuid=0 
ouid=0
  type=PATH msg=audit(1487347189.015:28536): item=0 name="/etc/qemu-ifup" 
inode=66403 dev=08:01 mode=0100755 ouid=0 ogid=0 rdev=00:00 nametype=NORMAL

  root@ubuntu-trusty-5773:/etc/apparmor.d/abstractions# cat 
/etc/apparmor.d/libvirt/libvirt-4a03fea7-e966-48e4-80ac-aa138db67243
  #
  # This profile is for the domain whose UUID matches this file.
  #

  #include 

  profile libvirt-4a03fea7-e966-48e4-80ac-aa138db67243 {
#include 
#include 

  }
  root@ubuntu-trusty-5773:/etc/apparmor.d/abstractions# cat 
/etc/apparmor.d/libvirt/libvirt-4a03fea7-e966-48e4-80ac-aa138db67243.files
  # DO NOT EDIT THIS FILE DIRECTLY. IT IS MANAGED BY LIBVIRT.
"/var/log/libvirt/**/instance-0008.log" w,
"/var/lib/libvirt/qemu/domain-instance-0008/monitor.sock" rw,
"/var/run/libvirt/**/instance-0008.pid" rwk,
"/run/libvirt/**/instance-0008.pid" rwk,
"/var/run/libvirt/**/*.tunnelmigrate.dest.instance-0008" rw,
"/run/libvirt/**/*.tunnelmigrate.dest.instance-0008" rw,
"/var/lib/nova/instances/4a03fea7-e966-48e4-80ac-aa138db67243/console.log" 
rw,
"/var/lib/nova/instances/4a03fea7-e966-48e4-80ac-aa138db67243/console.log" 
rw,
# for qemu guest agent channel
owner "/var/lib/libvirt/qemu/channel/target/domain-instance-0008/**" rw,
/dev/vhost-net rw,

  root@ubuntu-trusty-5773:/etc/apparmor.d/abstractions# dpkg -S libvirt-qemu
  libvirt-bin: /etc/apparmor.d/abstractions/libvirt-qemu

  root@ubuntu-trusty-5773:/etc/apparmor.d/abstractions# dpkg -l libvirt-bin
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version   
Architecture  Description
  
+++-=-=-=-===
  ii  libvirt-bin   1.3.1-1ubuntu10.6~cloud0  amd64 
programs for the libvirt library

  
  Seeing identical behavior on Xenial
  ubuntu@ubuntu-xenial-5165:~$ dpkg -l libvirt-bin
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version   
Architecture  Description
  
+++-=-=-=-===
  ii  libvirt-bin   1.3.1-1ubuntu10.8 amd64 
programs for the libvirt library

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1665698/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674349] [NEW] [RFE] Introduce a new rule with service user role in Neutron policy

[Pushkar Umaranikar]

Public bug reported:

When other services like Nova talks to the Neutron REST API, it uses an
admin token, in some scenarios like setting the port binding on a port.
In these cases, the admin token is used to ensure only Nova has access
to the binding API, not the end user.

With the introduction of service token, we can use service token instead of 
admin token to perform metadata API services related operations which
currently uses admin token.

In Ocata, Nova started sending a service token along with the user token, so 
Neutron already knows it is Nova sending a request on behalf of the user.
https://review.openstack.org/#/c/410394/

We can make use new role added by keystoneauth.

"service_roles": "service:nova"

The above role can be used in policy to define level of access for an
action when service token is used along with user context. This allows to 
perform any actions for which we have added service role in policy 
configurations.

For example, if we want to perform "binding port to host id" operation
with service token authentication, we will pass service token along with
auth token to communicate with Neutron. In this case, Neutron policy
should also allow performing this operation with "service_roles".

Spec in Nova:
https://review.openstack.org/#/c/439890/

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: rfe

** Tags added: rfe

** Description changed:

  When other services like Nova talks to the Neutron REST API, it uses an admin 
token, in some scenarios like setting the port binding on a port. In these 
cases, the admin token is
  used to ensure only Nova has access to the binding API, not the end user.
  
  With the introduction of service token, we can use service token instead of
  admin token to perform metadata API services related operations which
  currently uses admin token.
  
  In Ocata, Nova started sending a service token along with the user token, so 
Neutron already
  knows it is Nova sending a request on behalf of the user.
  https://review.openstack.org/#/c/410394/
  
  We can make use new role added by keystoneauth.
  
  "service_roles": "service:nova"
  
  The above role can be used in policy to define level of access for an
  action when service token is used along with user context. This allows to 
perform any actions for which we have added service role in policy 
configurations.
  
- For example, if we want to perform "binding port to host id" operation with
- service token authentication, we will pass service token along with auth token
- to communicate with Neutron. In this case, Neutron policy should also allow
- performing this operation with "service_roles".
+ For example, if we want to perform "binding port to host id" operation
+ with service token authentication, we will pass service token along with
+ auth token to communicate with Neutron. In this case, Neutron policy
+ should also allow performing this operation with "service_roles".
  
  Spec in Nova:
  https://review.openstack.org/#/c/439890/

** Description changed:

- When other services like Nova talks to the Neutron REST API, it uses an admin 
token, in some scenarios like setting the port binding on a port. In these 
cases, the admin token is
- used to ensure only Nova has access to the binding API, not the end user.
+ When other services like Nova talks to the Neutron REST API, it uses an
+ admin token, in some scenarios like setting the port binding on a port.
+ In these cases, the admin token is used to ensure only Nova has access
+ to the binding API, not the end user.
  
- With the introduction of service token, we can use service token instead of
- admin token to perform metadata API services related operations which
+ With the introduction of service token, we can use service token instead of 
admin token to perform metadata API services related operations which
  currently uses admin token.
  
- In Ocata, Nova started sending a service token along with the user token, so 
Neutron already
- knows it is Nova sending a request on behalf of the user.
+ In Ocata, Nova started sending a service token along with the user token, so 
Neutron already knows it is Nova sending a request on behalf of the user.
  https://review.openstack.org/#/c/410394/
  
  We can make use new role added by keystoneauth.
  
  "service_roles": "service:nova"
  
  The above role can be used in policy to define level of access for an
  action when service token is used along with user context. This allows to 
perform any actions for which we have added service role in policy 
configurations.
  
  For example, if we want to perform "binding port to host id" operation
  with service token authentication, we will pass service token along with
  auth token to communicate with Neutron. In this case, Neutron policy
  should also allow performing this operation with "service_roles".
  
  Spec in Nova:
  https://review.openstack.org/#/c/439890/

-- 
You received this bug notification because you 

[Yahoo-eng-team] [Bug 1424728] Re: Remove old rpc alias(es) from code

[OpenStack Infra]

Reviewed:  https://review.openstack.org/447288
Committed: 
https://git.openstack.org/cgit/openstack/sahara/commit/?id=c5b3f826516d16f8f01105f804cd8f2bd9de51cc
Submitter: Jenkins
Branch:master

commit c5b3f826516d16f8f01105f804cd8f2bd9de51cc
Author: ChangBo Guo(gcb) 
Date:   Sun Mar 19 20:47:33 2017 +0800

Remove old oslo.messaging transport aliases

Those are remnants from the oslo-incubator times. Also, oslo.messaging
deprecated [1] transport aliases since 5.2.0+ that is the minimal
version supported for stable/newton. The patch that bumped the minimal
version for Sahara landed 3 months+ ago, so we can proceed ripping
those aliases from the code base.

[1] I314cefa5fb1803fa7e21e3e34300e5ced31bba89

Closes-Bug: #1424728

Change-Id: I02fbe5f4f9f3bda80f4fc1ea94f852e1969ce1aa


** Changed in: sahara
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1424728

Title:
  Remove old rpc alias(es) from code

Status in Cinder:
  In Progress
Status in Designate:
  In Progress
Status in grenade:
  New
Status in Ironic:
  Fix Released
Status in Magnum:
  In Progress
Status in Manila:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo.messaging:
  Confirmed
Status in Sahara:
  Fix Released
Status in OpenStack Search (Searchlight):
  New
Status in watcher:
  New

Bug description:
  We have several TRANSPORT_ALIASES entries from way back (Essex, Havana)
  http://git.openstack.org/cgit/openstack/nova/tree/nova/rpc.py#n48

  We need a way to warn end users that they need to fix their nova.conf
  So these can be removed in a later release (full cycle?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1424728/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1670642] Re: get_model method missing for Ploop image

[OpenStack Infra]

Reviewed:  https://review.openstack.org/441989
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=d629d4e42c04756444a79e9ac15f3f2192c47b52
Submitter: Jenkins
Branch:master

commit d629d4e42c04756444a79e9ac15f3f2192c47b52
Author: Evgeny Antyshev 
Date:   Mon Mar 6 14:27:06 2017 +

get_model method missing for Ploop image

Image.get_model is called in partition injection code,
and now inject partition attempt fails unconditionally.
This patch makes use of disk/api.py inject_data failure tolerance:
it doesn't fail unless injected data is mandatory.

Closes-Bug: 1670642
Change-Id: I6c68693be818219f78d6fcda019b867066396b29


** Changed in: nova
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1670642

Title:
  get_model method missing for Ploop image

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  This results in failures in inject_data from nova/virt/disk/api.py
  even if no real data is injected:

  2017-03-03 15:11:55.707 48683 ERROR nova.virt.libvirt.driver 
[req-f6f3df11-35b0-44c2-a1c4-52548504a1b5 fd33deabe809466a8dcd517bdf882e6b 
e4046b10f1074f06bd5d474ddfce09bc - - -] [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] Error injecting data into image 
082f0243-cd99-4312-a27a-86b8cd3688d2 ()
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager 
[req-f6f3df11-35b0-44c2-a1c4-52548504a1b5 fd33deabe809466a8dcd517bdf882e6b 
e4046b10f1074f06bd5d474ddfce09bc - - -] [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] Instance failed to spawn
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] Traceback (most recent call last):
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2078, in 
_build_resources
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] yield resources
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1920, in 
_build_and_run_instance
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] block_device_info=block_device_info)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2624, in 
spawn
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] admin_pass=admin_password)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3028, in 
_create_image
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] fallback_from_host)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3137, in 
_create_and_inject_local_root
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] files)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2977, in 
_inject_data
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] instance=instance)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] self.force_reraise()
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] six.reraise(self.type_, self.value, 
self.tb)
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5]   File 
"/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2968, in 
_inject_data
  2017-03-03 15:11:55.708 48683 ERROR nova.compute.manager [instance: 
99aaeae0-e611-424e-bbd6-8d83ef37caf5] 

[Yahoo-eng-team] [Bug 1664117] Re: Error message should not include SQL command

[OpenStack Infra]

Reviewed:  https://review.openstack.org/436773
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=d88a2f00e184475258eebe4f6a2bff8a6b9e341f
Submitter: Jenkins
Branch:master

commit d88a2f00e184475258eebe4f6a2bff8a6b9e341f
Author: liyingjun 
Date:   Wed Feb 22 11:20:12 2017 +0800

Error message should not include SQL command

There is SQL command included in the http response for conflicting
resource provider. We should remove SQL related errors from the
error message.

Change-Id: I47726919f9a2d2a767564909f454c334e42ffbe0
Closes-bug: 1664117


** Changed in: nova
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1664117

Title:
  Error message should not include SQL command

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Description
  ===
  When i create one resource provider with existed one's name,
  returned error message includes SQL command.

  Steps to reproduce
  ==
  * Create one resource provider with name 'RP_test'
  * Create another resource provider with name 'RP_test'

  Expected result
  ===
"detail": "There was a conflict when trying to complete your 
request.\n\n Conflicting resource provider RP_test already exists.",

  I think message above is detailed enough.

  Actual result
  =
"detail": "There was a conflict when trying to complete your 
request.\n\n Conflicting resource provider already exists: 
(pymysql.err.IntegrityError) (1062, u\"Duplicate entry 'RP_test' for key 
'uniq_resource_providers0name'\") [SQL: u'INSERT INTO resource_providers 
(created_at, updated_at, uuid, name, generation, can_host) VALUES 
(%(created_at)s, %(updated_at)s, %(uuid)s, %(name)s, %(generation)s, 
%(can_host)s)'] [parameters: {'uuid': 'cfafc096-4b15-4dc1-bb44-2bad0cd6d9e5', 
'generation': 0, 'created_at': datetime.datetime(2017, 2, 13, 5, 27, 41, 
686138), 'updated_at': None, 'can_host': 0, 'name': u'RP_test'}]  ",

  Environment
  ===
  1. nova version
  [root@controller nova]# git log
  commit 50d402821be7476eb58ccd791c50d8ed801e85eb
  Author: Matt Riedemann 
  Date: Wed Feb 8 10:23:14 2017 -0500

  Consider startup scenario in _get_compute_nodes_in_db

  2. Which hypervisor did you use?
  devstack + libvirt + kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1664117/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1669433] Re: nova-status needs to check that placement 1.4 is available for pike

[OpenStack Infra]

Reviewed:  https://review.openstack.org/441881
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=a17851ab0ab1296e587c582523e9421a06e20597
Submitter: Jenkins
Branch:master

commit a17851ab0ab1296e587c582523e9421a06e20597
Author: Roman Podoliaka 
Date:   Mon Mar 6 12:45:51 2017 +0200

nova-status: require placement >= 1.4

Since Ia1a0066dc30025c02553584a077365b28d8ff80e FilterScheduler will
no longer fall back to not using placement API. We need to require
version 1.4 to prevent NoValidHost errors.

Closes-Bug: #1669433

Change-Id: Icb2f558ed1f4e83f21e0317a206b07c25134


** Changed in: nova
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1669433

Title:
  nova-status needs to check that placement 1.4 is available for pike

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  In Ocata, nova-compute wouldn't start if placement wasn't available,
  but it didn't check the version so placement from newton will still
  work with ocata computes. Also, the filter scheduler will fallback to
  not using placement if the computes aren't all new enough yet, but
  even once the computes are upgraded if placement is not the latest and
  microversion 1.4 isn't available, then the filter scheduler will not
  find any resource providers and it will result in a NoValidHost error.

  For Pike, the fallback code for the older computes has been removed
  from the filter scheduler:

  https://review.openstack.org/#/c/436180/

  So we're always calling placement from the filter scheduler. However,
  we don't enforce a minimum version of placement and we need 1.4 for
  the filter scheduler to work. We should add a check to the "nova-
  status upgrade check" command to enforce that placement is running
  with at least the 1.4 microversion (ocata) before upgrading to Pike.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1669433/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1661501] Re: Unlocalized string "Warning!" is found in Register Image page under Data Processing

[Akihiro Motoki]

This string comes from not horizon but sahara-dashboard. Move to sahara-
dashboard (corresponding launchpad project is  sahara).

** Project changed: horizon => sahara

** Changed in: sahara
   Status: Incomplete => New

** Tags added: dashboard i18n

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1661501

Title:
  Unlocalized string "Warning!" is found in Register Image page under
  Data Processing

Status in Sahara:
  New

Bug description:
  The string "Warning!" is unlocalized. 
  I confirmed it in Japanese and Simplified Chinese.

  I can locate the same string in Zanata but that seems to be used in
  the Developer tab according to the pot file at:
  http://tarballs.openstack.org/translation-
  source/horizon/master/openstack_dashboard/locale/djangojs.pot

  #: openstack_dashboard/contrib/developer/static/dashboard/
  developer/theme-preview/theme-preview.html:995
  msgid "Warning!"
  msgstr ""

  In Zanata, I cannot even find the translated strings used in the same
  text box.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sahara/+bug/1661501/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1424728] Re: Remove old rpc alias(es) from code

[Thomas Herve]

** No longer affects: heat

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1424728

Title:
  Remove old rpc alias(es) from code

Status in Cinder:
  In Progress
Status in Designate:
  In Progress
Status in grenade:
  New
Status in Ironic:
  Fix Released
Status in Magnum:
  In Progress
Status in Manila:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo.messaging:
  Confirmed
Status in Sahara:
  In Progress
Status in OpenStack Search (Searchlight):
  New
Status in watcher:
  New

Bug description:
  We have several TRANSPORT_ALIASES entries from way back (Essex, Havana)
  http://git.openstack.org/cgit/openstack/nova/tree/nova/rpc.py#n48

  We need a way to warn end users that they need to fix their nova.conf
  So these can be removed in a later release (full cycle?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1424728/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674300] [NEW] Cannot spin an instance because the NUMATopology Filter Returned 0 Hosts

[Kundan Debnath]

Public bug reported:

Description
===
I am unable to launch an instance which requests for 16vCPUs dedicated (CPU 
Pinning) and 232 GB of RAM. The request fails all the time with "Filter 
NUMATopologyFilter returned 0 hosts". The blade server has 28 vCPUs available 
and 240 GB of RAM available. 

Paste #603395 - Has the error and exception that I see in nova-all.log.

The blade server where I am trying to create this instance has the below
configuration-

root@RTPCLABQPS1H-3-1:~# numactl --hardware
available: 2 nodes (0-1)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 20 21 22 23 24 25 26 27 28 29
node 0 size: 193386 MB
node 0 free: 186836 MB
node 1 cpus: 10 11 12 13 14 15 16 17 18 19 30 31 32 33 34 35 36 37 38 39
node 1 size: 193533 MB
node 1 free: 191822 MB
node distances:
node   0   1
  0:  10  20
  1:  20  10
root@RTPCLABQPS1H-3-1:~#


Steps to reproduce
==
1. Try to create instance using nova, web or heat - with 16 vCPUs and 232 GB RAM
2. I receive an error that 0 Hosts are returned by NUMATOPOLOGY Filter
~ nova --debug boot - complete log at 
http://paste.openstack.org/show/603398/


Expected result
===
The instance should be created without any issue because the blade server has 
28 vCPUs available and 240 GB RAM.


Actual result
=
The instance creation failed with- NUMATopology Filter Returned 0 Hosts


Environment
===
1. Openstack KILO
root@RTPCLABQPS1H-CC-A:/var/log/nova# dpkg -l | grep nova
ii  nova-api1:2015.1.1-1~u14.04+mos19695   
all  OpenStack Compute - compute API frontend
ii  nova-cert   1:2015.1.1-1~u14.04+mos19695   
all  OpenStack Compute - certificate manager
ii  nova-common 1:2015.1.1-1~u14.04+mos19695   
all  OpenStack Compute - common files
ii  nova-conductor  1:2015.1.1-1~u14.04+mos19695   
all  OpenStack Compute - conductor service
ii  nova-consoleauth1:2015.1.1-1~u14.04+mos19695   
all  OpenStack Compute - Console Authenticator
ii  nova-consoleproxy   1:2015.1.1-1~u14.04+mos19695   
all  OpenStack Compute - NoVNC proxy
ii  nova-objectstore1:2015.1.1-1~u14.04+mos19695   
all  OpenStack Compute - object store
ii  nova-scheduler  1:2015.1.1-1~u14.04+mos19695   
all  OpenStack Compute - virtual machine scheduler
ii  python-nova 1:2015.1.1-1~u14.04+mos19695   
all  OpenStack Compute - libraries
ii  python-novaclient   1:2.23.0-1~u14.04+mos1247  
all  client library for OpenStack Compute API

2. Libvirt + KVM Version 
root@RTPCLABQPS1H-3-1:~# kvm --version
QEMU emulator version 2.4.0 (Debian 1:2.4+dfsg-ubuntu3), Copyright (c) 
2003-2008 Fabrice Bellard

3. Networking Type - Neutron

4.

** Affects: nova
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1674300

Title:
  Cannot spin an instance because the NUMATopology Filter Returned 0
  Hosts

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===
  I am unable to launch an instance which requests for 16vCPUs dedicated (CPU 
Pinning) and 232 GB of RAM. The request fails all the time with "Filter 
NUMATopologyFilter returned 0 hosts". The blade server has 28 vCPUs available 
and 240 GB of RAM available. 

  Paste #603395 - Has the error and exception that I see in nova-
  all.log.

  The blade server where I am trying to create this instance has the
  below configuration-

  root@RTPCLABQPS1H-3-1:~# numactl --hardware
  available: 2 nodes (0-1)
  node 0 cpus: 0 1 2 3 4 5 6 7 8 9 20 21 22 23 24 25 26 27 28 29
  node 0 size: 193386 MB
  node 0 free: 186836 MB
  node 1 cpus: 10 11 12 13 14 15 16 17 18 19 30 31 32 33 34 35 36 37 38 39
  node 1 size: 193533 MB
  node 1 free: 191822 MB
  node distances:
  node   0   1
0:  10  20
1:  20  10
  root@RTPCLABQPS1H-3-1:~#

  
  Steps to reproduce
  ==
  1. Try to create instance using nova, web or heat - with 16 vCPUs and 232 GB 
RAM
  2. I receive an error that 0 Hosts are returned by NUMATOPOLOGY Filter
  ~ nova --debug boot - complete log at 
http://paste.openstack.org/show/603398/

  
  Expected result
  ===
  The instance should be created without any issue because the blade server has 
28 vCPUs available and 240 GB RAM.

  
  Actual result
  =
  The instance creation failed with- NUMATopology Filter Returned 0 Hosts

  
  Environment
  ===
  1. Openstack KILO
  root@RTPCLABQPS1H-CC-A:/var/log/nova# dpkg -l | grep nova
  ii  nova-api1:2015.1.1-1~u14.04+mos19695  
 all  

[Yahoo-eng-team] [Bug 1673334] Re: min_ttl variable is not being honoured when adding records

[Akihiro Motoki]

designate-dashboard is implemented as a horizon plugin, so it should be
moved to a project-specific launchpad page.

** Project changed: horizon => designate-dashboard

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1673334

Title:
  min_ttl variable is not being honoured when adding records

Status in Designate Dashboard:
  New

Bug description:
  Currently using Designate version 2.0.0-1 (el7) with Mitaka.

  Designate is not honouring min_ttl variable when records are created.

  An example from our setup:

  $ grep min_ttl /etc/designate/designate.conf
  min_ttl = 300

  $ designate record-create --name test.matt-ttl-test.com. --ttl 100 --type A 
--data 101.0.101.10 c1dada84-7500-4a4d-b2ea-f415b75cf61c
  +-+--+
  | Field   | Value|
  +-+--+
  | description | None |
  | type| A|
  | created_at  | 2017-03-16T05:46:56.00   |
  | updated_at  | None |
  | domain_id   | c1dada84-7500-4a4d-b2ea-f415b75cf61c |
  | priority| None |
  | ttl | 100  |
  | data| 101.0.101.10 |
  | id  | 2a55e1d6-51b2-402e-b943-917a0ff23a90 |
  | name| test.matt-ttl-test.com.  |
  +-+--+

  Also, specifying a value which is not in range as specified within
  domain.json (ie. 1 to 2147483647) will fail, however if you don't
  specify a '-ttl', it'll add with a null value:

  $ designate record-create --name testa.matt-ttl-test.com. --type A --data 
101.0.101.10 c1dada84-
  +-+--+
  | Field   | Value|
  +-+--+
  | description | None |
  | type| A|
  | created_at  | 2017-03-16T05:49:00.00   |
  | updated_at  | None |
  | domain_id   | c1dada84-7500-4a4d-b2ea-f415b75cf61c |
  | priority| None |
  | ttl | None |
  | data| 101.0.101.10 |
  | id  | 71003363-02b4-40b1-87e9-dd88d6326c44 |
  | name| testa.matt-ttl-test.com. |
  +-+--+

  This is also the same case with adding records via Horizon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/designate-dashboard/+bug/1673334/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1424728] Re: Remove old rpc alias(es) from code

[OpenStack Infra]

Reviewed:  https://review.openstack.org/447295
Committed: 
https://git.openstack.org/cgit/openstack/ironic/commit/?id=330ba8c502880a16db4d2673ab36358f559711ec
Submitter: Jenkins
Branch:master

commit 330ba8c502880a16db4d2673ab36358f559711ec
Author: ChangBo Guo(gcb) 
Date:   Sun Mar 19 21:16:53 2017 +0800

Remove old oslo.messaging transport aliases

Those are remnants from the oslo-incubator times. Also, oslo.messaging
deprecated [1] transport aliases since 5.2.0+ that is the minimal
version supported for stable/newton. The patch that bumped the minimal
version for Ironic landed 3 months+ ago, so we can proceed ripping
those aliases from the code base.

[1] I314cefa5fb1803fa7e21e3e34300e5ced31bba89

Change-Id: I42dcc4b64f0b8e667abad68f7a5ed1ba004ec329
Closes-Bug: #1424728


** Changed in: ironic
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1424728

Title:
  Remove old rpc alias(es) from code

Status in Cinder:
  In Progress
Status in Designate:
  In Progress
Status in grenade:
  New
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in Magnum:
  In Progress
Status in Manila:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo.messaging:
  Confirmed
Status in Sahara:
  In Progress
Status in OpenStack Search (Searchlight):
  New
Status in watcher:
  New

Bug description:
  We have several TRANSPORT_ALIASES entries from way back (Essex, Havana)
  http://git.openstack.org/cgit/openstack/nova/tree/nova/rpc.py#n48

  We need a way to warn end users that they need to fix their nova.conf
  So these can be removed in a later release (full cycle?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1424728/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1424728] Re: Remove old rpc alias(es) from code

[OpenStack Infra]

Reviewed:  https://review.openstack.org/447293
Committed: 
https://git.openstack.org/cgit/openstack/manila/commit/?id=201f99f778510f6397bd6f341f8e88d4fcf829b2
Submitter: Jenkins
Branch:master

commit 201f99f778510f6397bd6f341f8e88d4fcf829b2
Author: ChangBo Guo(gcb) 
Date:   Sun Mar 19 21:14:00 2017 +0800

Remove old oslo.messaging transport aliases

Those are remnants from the oslo-incubator times. Also, oslo.messaging
deprecated [1] transport aliases since 5.2.0+ that is the minimal
version supported for stable/newton. The patch that bumped the minimal
version for Manila landed 3 months+ ago, so we can proceed ripping
those aliases from the code base.

[1] I314cefa5fb1803fa7e21e3e34300e5ced31bba89

Change-Id: Iea406d784bcef5c4c50e11a49cd967d0143d1d62
Closes-Bug: #1424728


** Changed in: manila
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1424728

Title:
  Remove old rpc alias(es) from code

Status in Cinder:
  In Progress
Status in Designate:
  In Progress
Status in grenade:
  New
Status in heat:
  Fix Released
Status in Ironic:
  In Progress
Status in Magnum:
  In Progress
Status in Manila:
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo.messaging:
  Confirmed
Status in Sahara:
  In Progress
Status in OpenStack Search (Searchlight):
  New
Status in watcher:
  New

Bug description:
  We have several TRANSPORT_ALIASES entries from way back (Essex, Havana)
  http://git.openstack.org/cgit/openstack/nova/tree/nova/rpc.py#n48

  We need a way to warn end users that they need to fix their nova.conf
  So these can be removed in a later release (full cycle?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1424728/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674259] [NEW] code comments incorrectness

[Zhou Jianming]

Public bug reported:

I am running OpenStack Mitaka on CentOS7.1 with VMware vSphere 5.5 Enterprise 
Plus.
In function get_datastore() of nova/virt/vmwareapi/ds_utils.py file, the 
following code comments:
  ..
  datastore_ret = session._call_method(vutil,
   "get_object_property",
   object,
   "datastore")
  # If there are no hosts in the cluster then an empty string is returned.
  if not datastore_ret:
  raise exception.DatastoreNotFound()

  ..

According to context, I think  this comments are incorrectness: 
   1)  We get datastore objects, not hosts object.
   2)  If there are no datastores in the cluster then raise exception, not 
return an empty string.

** Affects: nova
 Importance: Undecided
 Assignee: Zhou Jianming (zhoujm-cri)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Zhou Jianming (zhoujm-cri)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1674259

Title:
  code comments incorrectness

Status in OpenStack Compute (nova):
  New

Bug description:
  I am running OpenStack Mitaka on CentOS7.1 with VMware vSphere 5.5 Enterprise 
Plus.
  In function get_datastore() of nova/virt/vmwareapi/ds_utils.py file, the 
following code comments:
..
datastore_ret = session._call_method(vutil,
 "get_object_property",
 object,
 "datastore")
# If there are no hosts in the cluster then an empty string is returned.
if not datastore_ret:
raise exception.DatastoreNotFound()

..

  According to context, I think  this comments are incorrectness: 
 1)  We get datastore objects, not hosts object.
 2)  If there are no datastores in the cluster then raise exception, not 
return an empty string.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1674259/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674257] [NEW] we should not log unimplemented error in _get_host_metrics method

[Tao Li]

Public bug reported:

When nova used ironic driver， there was an exception which was always
logged in nova compute log fie periodically. The
update_available_resource method calls the  _get_host_metrics method to
cause this problem. In ironic driver , the get_host_cpu_stats method is
not implemented. so we should not log the exception message to eliminate
misunderstanding. The cycle logged message is as follows.

2017-03-20 14:14:43.669 10933 INFO nova.compute.resource_tracker 
[req-c4decc3b-f8b4-49c4-afba-40b6c70e86be - - - - -] Final resource view: 
name=20ba28a6-a00d-46e8-983e-c6ef4140cc21 phys_ram=0MB used_ram=0MB 
phys_disk=0GB used_disk=0GB total_vcpus=0 used_vcpus=0 pci_stats=[]
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
[req-c4decc3b-f8b4-49c4-afba-40b6c70e86be - - - - -] Not all properties needed 
are implemented in the compute driver
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
Traceback (most recent call last):
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver   
File 
"/usr/lib/python2.7/site-packages/nova/compute/monitors/cpu/virt_driver.py", 
line 59, in _update_data
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
stats = self.driver.get_host_cpu_stats()
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver   
File "/usr/lib/python2.7/site-packages/nova/virt/driver.py", line 1224, in 
get_host_cpu_stats
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
raise NotImplementedError()
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
NotImplementedError
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 


So, I want to ignore the unimplemented excepion in the '_update_data'  method 
in virt_driver.py.

** Affects: nova
 Importance: Undecided
 Assignee: Tao Li (eric-litao)
 Status: New

** Project changed: ltsp => nova

** Changed in: nova
 Assignee: (unassigned) => Tao Li (eric-litao)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1674257

Title:
  we should not log  unimplemented error in _get_host_metrics method

Status in OpenStack Compute (nova):
  New

Bug description:
  When nova used ironic driver， there was an exception which was always
  logged in nova compute log fie periodically. The
  update_available_resource method calls the  _get_host_metrics method
  to cause this problem. In ironic driver , the get_host_cpu_stats
  method is not implemented. so we should not log the exception message
  to eliminate misunderstanding. The cycle logged message is as follows.

  2017-03-20 14:14:43.669 10933 INFO nova.compute.resource_tracker 
[req-c4decc3b-f8b4-49c4-afba-40b6c70e86be - - - - -] Final resource view: 
name=20ba28a6-a00d-46e8-983e-c6ef4140cc21 phys_ram=0MB used_ram=0MB 
phys_disk=0GB used_disk=0GB total_vcpus=0 used_vcpus=0 pci_stats=[]
  2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
[req-c4decc3b-f8b4-49c4-afba-40b6c70e86be - - - - -] Not all properties needed 
are implemented in the compute driver
  2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
Traceback (most recent call last):
  2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver   
File 
"/usr/lib/python2.7/site-packages/nova/compute/monitors/cpu/virt_driver.py", 
line 59, in _update_data
  2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
stats = self.driver.get_host_cpu_stats()
  2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver   
File "/usr/lib/python2.7/site-packages/nova/virt/driver.py", line 1224, in 
get_host_cpu_stats
  2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
raise NotImplementedError()
  2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
NotImplementedError
  2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 

  
  So, I want to ignore the unimplemented excepion in the '_update_data'  method 
in virt_driver.py.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1674257/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674257] [NEW] we should not log unimplemented error in _get_host_metrics method

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When nova used ironic driver， there was an exception which was always
logged in nova compute log fie periodically. The
update_available_resource method calls the  _get_host_metrics method to
cause this problem. In ironic driver , the get_host_cpu_stats method is
not implemented. so we should not log the exception message to eliminate
misunderstanding. The cycle logged message is as follows.

2017-03-20 14:14:43.669 10933 INFO nova.compute.resource_tracker 
[req-c4decc3b-f8b4-49c4-afba-40b6c70e86be - - - - -] Final resource view: 
name=20ba28a6-a00d-46e8-983e-c6ef4140cc21 phys_ram=0MB used_ram=0MB 
phys_disk=0GB used_disk=0GB total_vcpus=0 used_vcpus=0 pci_stats=[]
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
[req-c4decc3b-f8b4-49c4-afba-40b6c70e86be - - - - -] Not all properties needed 
are implemented in the compute driver
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
Traceback (most recent call last):
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver   
File 
"/usr/lib/python2.7/site-packages/nova/compute/monitors/cpu/virt_driver.py", 
line 59, in _update_data
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
stats = self.driver.get_host_cpu_stats()
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver   
File "/usr/lib/python2.7/site-packages/nova/virt/driver.py", line 1224, in 
get_host_cpu_stats
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
raise NotImplementedError()
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 
NotImplementedError
2017-03-20 14:14:43.670 10933 ERROR nova.compute.monitors.cpu.virt_driver 


So, I want to ignore the unimplemented excepion in the '_update_data'  method 
in virt_driver.py.

** Affects: nova
 Importance: Undecided
 Status: New

-- 
we should not log  unimplemented error in _get_host_metrics method
https://bugs.launchpad.net/bugs/1674257
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to OpenStack Compute (nova).

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1674246] [NEW] Image filtering does not work for "protected" property

[Mateusz Kowalski]

Public bug reported:

When trying to filter images by "Protected: yes", it always shows result
of the filter "Protected: no", making it impossible to show only images
which are protected.

** Affects: horizon
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1674246

Title:
  Image filtering does not work for "protected" property

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When trying to filter images by "Protected: yes", it always shows
  result of the filter "Protected: no", making it impossible to show
  only images which are protected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1674246/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp