[Yahoo-eng-team] [Bug 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread zhurong 
** Also affects: murano
   Importance: Undecided
   Status: New

** Changed in: murano
 Assignee: (unassigned) => zhurong (zhu-rong)

** Also affects: python-muranoclient
   Importance: Undecided
   Status: New

** Changed in: python-muranoclient
 Assignee: (unassigned) => zhurong (zhu-rong)

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

Title:
  Change LOG.warn to LOG.warning

Status in OpenStack Dashboard (Horizon):
  In Progress
Status in Murano:
  In Progress
Status in python-muranoclient:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1530742/+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 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread zhurong 
** Also affects: senlin
   Importance: Undecided
   Status: New

** Changed in: senlin
 Assignee: (unassigned) => zhurong (zhu-rong)

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

Title:
  Change LOG.warn to LOG.warning

Status in OpenStack Dashboard (Horizon):
  In Progress
Status in Murano:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1530742/+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 1530729] [NEW] Create button in "Create Subnet" dialog on "Subnet Details" tab is disabled when "Disable Gateway" is selected

2016-01-03 Thread Liam Haworth 
Public bug reported:

When creating a subnet via the "Create Subnet" dialog, if the check box
"Disable Gateway" is check and the user click on the "Subnet Details"
tag in the dialog the create button is disabled an displayed as "Next
>>".

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

Title:
  Create button in "Create Subnet" dialog on "Subnet Details" tab is
  disabled when "Disable Gateway" is selected

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When creating a subnet via the "Create Subnet" dialog, if the check
  box "Disable Gateway" is check and the user click on the "Subnet
  Details" tag in the dialog the create button is disabled an displayed
  as "Next >>".

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1530729/+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 1526369] Re: nova.tests.unit.virt.xenapi.test_vmops.BootableTestCase.test_set_bootable is racy on py34

2016-01-03 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/257950
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=14295be0edba4070a604d93b4e9acb91d5ed39d2
Submitter: Jenkins
Branch:master

commit 14295be0edba4070a604d93b4e9acb91d5ed39d2
Author: Matt Riedemann 
Date:   Thu Dec 31 08:12:54 2015 -0800

xen: block BootableTestCase from py34 testing

The tests use mox which isn't stable with py34 testing, there are
race failures with the assertions. This test fails in unexpected
ways in unrelated changes so we need to blacklist it from py34
testing.

Change-Id: Ieb972f4705254af4b014d79a39bd6d78ad0b6376
Closes-Bug: #1526369


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

Title:
  nova.tests.unit.virt.xenapi.test_vmops.BootableTestCase.test_set_bootable
  is racy on py34

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  
http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22mox3.mox.UnexpectedMethodCallError:%20Unexpected%20method%20call%20function.__call__(%3Cnova.virt.xenapi.client.session.XenAPISession%5C%22%20AND%20tags:%5C%22console%5C%22%20AND%20build_name:%5C
  %22gate-nova-python34%5C%22

  ft1.7942: 
nova.tests.unit.virt.xenapi.test_vmops.BootableTestCase.test_set_bootable_StringException:
 Empty attachments:
stdout

  pythonlogging:'': {{{2015-12-15 13:33:23,562 WARNING 
[oslo_reports.guru_meditation_report] Guru mediation now registers SIGUSR1 and 
SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be 
registered in a future release, so please use SIGUSR2 to generate reports.}}}
  stderr: {{{
  
/home/jenkins/workspace/gate-nova-python34/.tox/py34/lib/python3.4/site-packages/pkg_resources/__init__.py:213:
 RuntimeWarning: You have iterated over the result of 
pkg_resources.parse_version. This is a legacy behavior which is inconsistent 
with the new version class introduced in setuptools 8.0. In most cases, 
conversion to a tuple is unnecessary. For comparison of versions, sort the 
Version instances directly. If you have another use case requiring the tuple, 
please file a bug with the setuptools project describing that need.
stacklevel=1,
  }}}

  Traceback (most recent call last):
File 
"/home/jenkins/workspace/gate-nova-python34/.tox/py34/lib/python3.4/site-packages/mox3/mox.py",
 line 1153, in _PopNextMethod
  return self._call_queue.popleft()
  IndexError: pop from an empty deque

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/home/jenkins/workspace/gate-nova-python34/nova/tests/unit/virt/xenapi/test_vmops.py",
 line 1044, in test_set_bootable
  self.vmops.set_bootable(self.instance, True)
File 
"/home/jenkins/workspace/gate-nova-python34/nova/virt/xenapi/vmops.py", line 
1621, in set_bootable
  vm_ref = self._get_vm_opaque_ref(instance)
File 
"/home/jenkins/workspace/gate-nova-python34/nova/virt/xenapi/vmops.py", line 
824, in _get_vm_opaque_ref
  vm_ref = vm_utils.lookup(self._session, instance['name'], check_rescue)
File 
"/home/jenkins/workspace/gate-nova-python34/.tox/py34/lib/python3.4/site-packages/mox3/mox.py",
 line 814, in __call__
  return mock_method(*params, **named_params)
File 
"/home/jenkins/workspace/gate-nova-python34/.tox/py34/lib/python3.4/site-packages/mox3/mox.py",
 line 1113, in __call__
  expected_method = self._VerifyMethodCall()
File 
"/home/jenkins/workspace/gate-nova-python34/.tox/py34/lib/python3.4/site-packages/mox3/mox.py",
 line 1169, in _VerifyMethodCall
  expected = self._PopNextMethod()
File 
"/home/jenkins/workspace/gate-nova-python34/.tox/py34/lib/python3.4/site-packages/mox3/mox.py",
 line 1155, in _PopNextMethod
  raise UnexpectedMethodCallError(self, None)
  mox3.mox.UnexpectedMethodCallError: Unexpected method call 
function.__call__(, 'test', False) -> None

  7 hits in 7 days, check and gate, py34 only, this is just mox3 being
  racy on py34.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1526369/+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 1530742] [NEW] Change LOG.warn to LOG.warning

2016-01-03 Thread zhurong 
Public bug reported:

Python 3 deprecated the logger.warn method, see:
https://docs.python.org/3/library/logging.html#logging.warning
so we prefer to use warning to avoid DeprecationWarning.

** Affects: horizon
 Importance: Undecided
 Assignee: zhurong (zhu-rong)
 Status: In Progress

** Affects: murano
 Importance: Undecided
 Assignee: zhurong (zhu-rong)
 Status: New

** Affects: python-muranoclient
 Importance: Undecided
 Assignee: zhurong (zhu-rong)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) => zhurong (zhu-rong)

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

Title:
  Change LOG.warn to LOG.warning

Status in OpenStack Dashboard (Horizon):
  In Progress
Status in Murano:
  New
Status in python-muranoclient:
  New

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1530742/+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 1482633] Re: requests to SSL wrapped sockets hang while reading using py3

2016-01-03 Thread Davanum Srinivas (DIMS) 
** 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 neutron.
https://bugs.launchpad.net/bugs/1482633

Title:
  requests to SSL wrapped sockets hang while reading using py3

Status in Manila:
  New
Status in neutron:
  Invalid
Status in OpenStack Compute (nova):
  New
Status in oslo.service:
  New

Bug description:
  If we run unit tests using py3 then we get following errors:

  ==
  FAIL: manila.tests.test_wsgi.TestWSGIServer.test_app_using_ssl
  tags: worker-0
  --
  Empty attachments:
pythonlogging:''
stdout

  stderr: {{{
  Traceback (most recent call last):
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/hubs/hub.py",
 line 457, in fire_timers
  timer()
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/hubs/timer.py",
 line 58, in __call__
  cb(*args, **kw)
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/greenthread.py",
 line 214, in main
  result = function(*args, **kwargs)
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/wsgi.py",
 line 823, in server
  client_socket = sock.accept()
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/green/ssl.py",
 line 333, in accept
  suppress_ragged_eofs=self.suppress_ragged_eofs)
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/green/ssl.py",
 line 88, in __init__
  self.do_handshake()
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/green/ssl.py",
 line 241, in do_handshake
  super(GreenSSLSocket, self).do_handshake)
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/green/ssl.py",
 line 106, in _call_trampolining
  return func(*a, **kw)
File "/usr/lib/python3.4/ssl.py", line 805, in do_handshake
  self._sslobj.do_handshake()
  ssl.SSLWantReadError: The operation did not complete (read) (_ssl.c:598)
  }}}

  Traceback (most recent call last):
File 
"/home/vponomaryov/Documents/python/projects/manila/manila/tests/test_wsgi.py", 
line 181, in test_app_using_ssl
  'https://127.0.0.1:%d/' % server.port)
File "/usr/lib/python3.4/urllib/request.py", line 153, in urlopen
  return opener.open(url, data, timeout)
File "/usr/lib/python3.4/urllib/request.py", line 455, in open
  response = self._open(req, data)
File "/usr/lib/python3.4/urllib/request.py", line 473, in _open
  '_open', req)
File "/usr/lib/python3.4/urllib/request.py", line 433, in _call_chain
  result = func(*args)
File "/usr/lib/python3.4/urllib/request.py", line 1273, in https_open
  context=self._context, check_hostname=self._check_hostname)
File "/usr/lib/python3.4/urllib/request.py", line 1232, in do_open
  h.request(req.get_method(), req.selector, req.data, headers)
File "/usr/lib/python3.4/http/client.py", line 1065, in request
  self._send_request(method, url, body, headers)
File "/usr/lib/python3.4/http/client.py", line 1103, in _send_request
  self.endheaders(body)
File "/usr/lib/python3.4/http/client.py", line 1061, in endheaders
  self._send_output(message_body)
File "/usr/lib/python3.4/http/client.py", line 906, in _send_output
  self.send(msg)
File "/usr/lib/python3.4/http/client.py", line 841, in send
  self.connect()
File "/usr/lib/python3.4/http/client.py", line 1205, in connect
  server_hostname=server_hostname)
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/green/ssl.py",
 line 362, in _green_sslcontext_wrap_socket
  return GreenSSLSocket(sock, *a, _context=self, **kw)
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/green/ssl.py",
 line 88, in __init__
  self.do_handshake()
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/green/ssl.py",
 line 241, in do_handshake
  super(GreenSSLSocket, self).do_handshake)
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/green/ssl.py",
 line 116, in _call_trampolining
  timeout_exc=timeout_exc('timed out'))
File 
"/home/vponomaryov/Documents/python/projects/manila/.tox/py34/lib/python3.4/site-packages/eventlet/hubs/__init__.py",
 line 162, in trampoline
  return hub.switch()
File

[Yahoo-eng-team] [Bug 1471966] Re: Invalid json types cause stacktrace

2016-01-03 Thread 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/1471966

Title:
  Invalid json types cause stacktrace

Status in neutron:
  Expired

Bug description:
  Incorrect json input cause error instead of being invalidated
  properly:

  Type error in dns_nameservers raise keyerror:

  ERROR neutron.api.v2.resource [req-be58f6e1-db2f-4b2e-9620-afb49bdd4552 demo 
d1da3f8632e3413b915eda78899806d7] create failed
  Traceback (most recent call last):
    File "/opt/stack/neutron/neutron/api/v2/resource.py", line 87, in resource
  result = method(request=request, **args)
    File "/opt/stack/neutron/neutron/api/v2/base.py", line 379, in create
  allow_bulk=self._allow_bulk)
    File "/opt/stack/neutron/neutron/api/v2/base.py", line 637, in 
prepare_request_body
  attr_vals['validate'][rule])
    File "/opt/stack/neutron/neutron/api/v2/attributes.py", line 275, in 
_validate_nameservers
  msg = _validate_ip_or_hostname(host)
    File "/opt/stack/neutron/neutron/api/v2/attributes.py", line 257, in 
_validate_ip_or_hostname
  name_err = _validate_hostname(host)
    File "/opt/stack/neutron/neutron/api/v2/attributes.py", line 370, in 
_validate_hostname
  trimmed = data if data[-1] != '.' else data[:-1]
  TRACE neutron.api.v2.resource KeyError: -1
  TRACE neutron.api.v2.resource·

  Steps to reproduce:
  token=$(keystone token-get | grep ' id ' | awk '{ print $4}')
  curl -H "X-Auth-Token:${token}"  -H 'Content-Type:application/json' -X POST 
http://localhost:9696//v2.0/subnets.json \
   -d '{"subnet": {"dns_nameservers": [{}], "cidr": "192.168.0.1/24", 
"network_id": "----", "ip_version": "4"}}'; echo

  Various sql errors with security-group params:

  Trace:
  ERROR neutron.api.v2.resource [req-0f32e171-029c-465a-872e-d3533fc191c7 demo 
4a2f46b3469240589af5db1ffd3e56e7] create failed
  TRACE neutron.api.v2.resource Traceback (most recent call last):
  TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron/neutron/api/v2/resource.py", line 87, in resource
  TRACE neutron.api.v2.resource result = method(request=request, **args)
  TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron/neutron/api/v2/base.py", line 448, in create
  TRACE neutron.api.v2.resource obj = obj_creator(request.context, **kwargs)
  TRACE neutron.api.v2.resource   File 
"/opt/stack/neutron/neutron/db/securitygroups_db.py", line 137, in 
create_security_group
  TRACE neutron.api.v2.resource context.session.add(egress_rule)
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 447, in 
__exit__
  TRACE neutron.api.v2.resource self.rollback()
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py", line 58, in 
__exit__
  TRACE neutron.api.v2.resource compat.reraise(exc_type, exc_value, exc_tb)
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 444, in 
__exit__
  TRACE neutron.api.v2.resource self.commit()
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 354, in 
commit
  TRACE neutron.api.v2.resource self._prepare_impl()
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 334, in 
_prepare_impl
  TRACE neutron.api.v2.resource self.session.flush()
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1818, in 
flush
  TRACE neutron.api.v2.resource self._flush(objects)
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1936, in 
_flush
  TRACE neutron.api.v2.resource 
transaction.rollback(_capture_exception=True)
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py", line 58, in 
__exit__
  TRACE neutron.api.v2.resource compat.reraise(exc_type, exc_value, exc_tb)
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1900, in 
_flush
  TRACE neutron.api.v2.resource flush_context.execute()
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 372, in 
execute
  TRACE neutron.api.v2.resource rec.execute(self)
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 525, in 
execute
  TRACE neutron.api.v2.resource uow
  TRACE neutron.api.v2.resource   File 
"/usr/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 64, in 
save_obj
  TRACE neutron.api.v2.resource table, insert)
  TRACE

[Yahoo-eng-team] [Bug 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread zhangguoqing 
** Also affects: gnocchi
   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/1530742

Title:
  Change LOG.warn to LOG.warning

Status in Evoque:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in Murano:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evoque/+bug/1530742/+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 1513048] Re: the container can not be pinged via name space, after 860 tenants/networks/container created

2016-01-03 Thread 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/1513048

Title:
  the container can not be pinged via name space, after 860
  tenants/networks/container created

Status in neutron:
  Expired

Bug description:
  [Summary]
  the container can not be pinged via name space, after 860 
tenants/networks/container created

  [Topo]
  1 controller, 2 network nodes, 6 compute nodes, all in ubuntu 14.04
  (openstack version is 2015.1.2, linux kernel version is 3.19.0-31)
  root@ah:~# uname -a
  Linux ah.container13 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 
10:21:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
  root@ah:~# 
  root@ah:~# dpkg -l | grep neutron
  ii  neutron-common  1:2015.1.2-0ubuntu1~cloud0
all  Neutron is a virtual network service for Openstack - common
  ii  neutron-plugin-ml2  1:2015.1.2-0ubuntu1~cloud0
all  Neutron is a virtual network service for Openstack - ML2 plugin
  ii  neutron-server  1:2015.1.2-0ubuntu1~cloud0
all  Neutron is a virtual network service for Openstack - server
  ii  python-neutron  1:2015.1.2-0ubuntu1~cloud0
all  Neutron is a virtual network service for Openstack - Python 

  library
  ii  python-neutron-fwaas2015.1.2-0ubuntu2~cloud0  
all  Firewall-as-a-Service driver for OpenStack Neutron
  ii  python-neutronclient1:2.3.11-0ubuntu1.2~cloud0
all  client - Neutron is a virtual network service for Openstack
  root@ah:~#

  [Description and expect result]
  the container should be pinged via name space

  [Reproduceable or not]
  reproducible intermittently when large number of tenant/network/instance 
configed

  [Recreate Steps]
  1)use script to create: 860 tenants, 1 network/router in each tenant, 1 
cirros container in each network, all containers are associate to FIP

  2)create one more tenant, 1 network/contaier in the tenant, the
  container can be in Active state, but can not be pinged via name space
  ISSUE

  
  [Configration]
  config files on controller/network/compute are attached

  [logs]
  instance can be in Active state:
  oot@ah:~# nova --os-tenant-id 73731bbaf2db48f89a067604e3556e05 list
  
+--+-+++-++
  | ID   | Name| Status 
| Task State | Power State | Networks   
|
  
+--+-+++-++
  | d5ba18d5-aaf9-4ed6-9a2b-71d2b2f10bae | mexico_test_new_2_1_net1_vm | ACTIVE 
| -  | Running | mexico_test_new_2_1_net1=10.10.32.3, 172.168.6.211 
|
  
+--+-+++-++
  root@ah:~# keystone tenant-list | grep test_new_2_1
  | 73731bbaf2db48f89a067604e3556e05 | mexico_test_new_2_1 |   True  |
  root@ah:~# neutron net-list | grep exico_test_new_2_1_net1
  | a935642d-b56c-4a87-83c5-755f01bf0814 | mexico_test_new_2_1_net1 | 
bed0330f-e0ea-4bcc-bc75-96766dad32a7 10.10.32.0/24  |
  root@ah:~#

  on network node:
  root@ah:~# ip netns | grep a935642d-b56c-4a87-83c5-755f01bf0814
  qdhcp-a935642d-b56c-4a87-83c5-755f01bf0814
  root@ah:~# ip netns exec qdhcp-a935642d-b56c-4a87-83c5-755f01bf0814 ping 
10.10.32.3
  PING 10.10.32.3 (10.10.32.3) 56(84) bytes of data.
  From 10.10.32.2 icmp_seq=1 Destination Host Unreachable
  From 10.10.32.2 icmp_seq=2 Destination Host Unreachable
  From 10.10.32.2 icmp_seq=3 Destination Host Unreachable
  From 10.10.32.2 icmp_seq=4 Destination Host Unreachable>>>ISSUE

  [Root cause anlyze or debug inf]
  high load on controller and network node

  [Attachment]
  log files on controller/network/compute are attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1513048/+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 1483618] Re: modify subnet twice, then a port is created

2016-01-03 Thread 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/1483618

Title:
  modify subnet twice,then a port is created

Status in neutron:
  Expired

Bug description:
  1. I create net net1 in dashboard
  2. then  create a subnet subnet1 without enable gateway and dhcp.
  3. I modify subnet to enable gateway and dhcp, then no port was created
  4. I do it again without modify anything,  a port was created.

  a port should be created when I first modify subnet,
  acturely a port  is created with same  operating twice.
  I think it is a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1483618/+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 1465922] Re: Password visible in clear text in keystone.log when user created and keystone debug logging is enabled

2016-01-03 Thread Stanislaw Pitucha 
For Bandit I'm marking "Won't fix":
Offending code is:

LOG.debug('RBAC: Authorizing %(action)s(%(kwargs)s)', {
'action': action,
'kwargs': ', '.join(['%s=%s' % (k, kwargs[k]) for k in kwargs])})

There's no indication of what the kwargs are, so without a runtime
integration (tainting) or symbolic execution this is not realistic to
pick up. At the call sites the kwargs are not a literal dict, but rather
values from up the call chain, so not easy to analyse.

It would be great to pick this up, but it's way out of reach for the
engine currently or in reasonable future.

** Changed in: bandit
   Status: New => Won't Fix

** Changed in: bandit
   Importance: Undecided => Wishlist

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

Title:
  Password visible in clear text in keystone.log when user created and
  keystone debug logging is enabled

Status in Bandit:
  Won't Fix
Status in OpenStack Identity (keystone):
  Fix Released
Status in OpenStack Identity (keystone) juno series:
  Fix Released
Status in OpenStack Identity (keystone) kilo series:
  Fix Released
Status in OpenStack Security Advisory:
  Won't Fix

Bug description:
  grep CLEARTEXTPASSWORD keystone.log

  2015-06-16 06:44:39.770 20986 DEBUG keystone.common.controller [-]
  RBAC: Authorizing identity:create_user(user={u'domain_id': u'default',
  u'password': u'CLEARTEXTPASSWORD', u'enabled': True,
  u'default_project_id': u'0175b43419064ae38c4b74006baaeb8d', u'name':
  u'DermotJ'}) _build_policy_check_credentials /usr/lib/python2.7/site-
  packages/keystone/common/controller.py:57

  Issue code:
  
https://github.com/openstack/keystone/blob/master/keystone/common/controller.py#L57

  LOG.debug('RBAC: Authorizing %(action)s(%(kwargs)s)', {
  'action': action,
  'kwargs': ', '.join(['%s=%s' % (k, kwargs[k]) for k in kwargs])})

  Shadow the values of sensitive fields like 'password' by some
  meaningless garbled text like "X" is one way to fix.

  Well, in addition to this, I think we should never pass the 'password'
  with its original value along the code and save it in any persistence,
  instead we should convert it to a strong hash value as early as
  possible. With the help of a good hash system, we never have to need
  the original value of the password, right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/bandit/+bug/1465922/+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 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread zhangguoqing 
** Also affects: python-evoqueclient
   Importance: Undecided
   Status: New

** Changed in: mistral
 Assignee: (unassigned) => zhangguoqing (474751729-o)

** Changed in: python-evoqueclient
 Assignee: (unassigned) => zhangguoqing (474751729-o)

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

Title:
  Change LOG.warn to LOG.warning

Status in Evoque:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  New
Status in Mistral:
  New
Status in Murano:
  In Progress
Status in python-evoqueclient:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evoque/+bug/1530742/+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 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread zhangguoqing 
** Also affects: tempest
   Importance: Undecided
   Status: New

** Changed in: tempest
 Assignee: (unassigned) => zhangguoqing (474751729-o)

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

Title:
  Change LOG.warn to LOG.warning

Status in Evoque:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  In Progress
Status in Mistral:
  New
Status in Murano:
  In Progress
Status in oslo.messaging:
  In Progress
Status in oslo.middleware:
  New
Status in python-evoqueclient:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  In Progress
Status in tempest:
  New

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evoque/+bug/1530742/+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 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread Wanlong Gao 
*** This bug is a duplicate of bug 1508442 ***
https://bugs.launchpad.net/bugs/1508442

** This bug has been marked a duplicate of bug 1508442
   LOG.warn is deprecated

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

Title:
  Change LOG.warn to LOG.warning

Status in Evoque:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  In Progress
Status in Mistral:
  New
Status in Murano:
  In Progress
Status in oslo.messaging:
  In Progress
Status in oslo.middleware:
  New
Status in python-evoqueclient:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  In Progress
Status in tempest:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evoque/+bug/1530742/+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 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread zhangguoqing 
** Also affects: evoque
   Importance: Undecided
   Status: New

** Changed in: evoque
 Assignee: (unassigned) => zhangguoqing (474751729-o)

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

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

Title:
  Change LOG.warn to LOG.warning

Status in Evoque:
  In Progress
Status in Gnocchi:
  New
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in Murano:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evoque/+bug/1530742/+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 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread zhangguoqing 
** Also affects: keystoneauth
   Importance: Undecided
   Status: New

** Changed in: keystoneauth
 Assignee: (unassigned) => zhangguoqing (474751729-o)

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

Title:
  Change LOG.warn to LOG.warning

Status in Evoque:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  In Progress
Status in Mistral:
  New
Status in Murano:
  In Progress
Status in python-evoqueclient:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evoque/+bug/1530742/+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 1530762] [NEW] Lbaas: shouldn't return the fields "http_method/url_path/expected_codes" when healthmonitor type is TCP or ICMP

2016-01-03 Thread tianqing 
Public bug reported:

The attributes http_method,url_path,expected_codes ars invalid to a
TCP/PING type healthmonitor.

:~# neutron lbaas-healthmonitor-show e308f4e3-7c4e-4dce-abe5-f7a9177f6e18
+++
| Field  | Value  |
+++
| admin_state_up | True   |
| delay  | 1  |
| expected_codes | 200|
| http_method| GET|
| id | e308f4e3-7c4e-4dce-abe5-f7a9177f6e18   |
| max_retries| 1  |
| pools  | {"id": "663a41ff-ffdb-41a8-860a-655cc3fdeca5"} |
| tenant_id  | bdab536c9b344a6d927b5235dd2b7056   |
| timeout| 1  |
| type   | TCP|
| url_path   | /  |
+++

** Affects: neutron
 Importance: Undecided
 Status: New

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

Title:
  Lbaas: shouldn't return  the fields
  "http_method/url_path/expected_codes" when healthmonitor type is TCP
  or ICMP

Status in neutron:
  New

Bug description:
  The attributes http_method,url_path,expected_codes ars invalid to a
  TCP/PING type healthmonitor.

  :~# neutron lbaas-healthmonitor-show e308f4e3-7c4e-4dce-abe5-f7a9177f6e18
  +++
  | Field  | Value  |
  +++
  | admin_state_up | True   |
  | delay  | 1  |
  | expected_codes | 200|
  | http_method| GET|
  | id | e308f4e3-7c4e-4dce-abe5-f7a9177f6e18   |
  | max_retries| 1  |
  | pools  | {"id": "663a41ff-ffdb-41a8-860a-655cc3fdeca5"} |
  | tenant_id  | bdab536c9b344a6d927b5235dd2b7056   |
  | timeout| 1  |
  | type   | TCP|
  | url_path   | /  |
  +++

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1530762/+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 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread zhangguoqing 
** Also affects: python-heatclient
   Importance: Undecided
   Status: New

** Changed in: python-heatclient
 Assignee: (unassigned) => zhangguoqing (474751729-o)

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

Title:
  Change LOG.warn to LOG.warning

Status in Evoque:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  In Progress
Status in Mistral:
  New
Status in Murano:
  In Progress
Status in python-evoqueclient:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evoque/+bug/1530742/+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 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread OpenStack Infra 
*** This bug is a duplicate of bug 1508442 ***
https://bugs.launchpad.net/bugs/1508442

Reviewed:  https://review.openstack.org/263090
Committed: 
https://git.openstack.org/cgit/openstack/senlin/commit/?id=b3cde506957c3fe6496beffd68e7f9a5c981e40b
Submitter: Jenkins
Branch:master

commit b3cde506957c3fe6496beffd68e7f9a5c981e40b
Author: zhurong 
Date:   Tue Dec 22 09:40:07 2015 +0800

Change LOG.warn to LOG.warning

Python 3 deprecated the logger.warn method, see:
https://docs.python.org/3/library/logging.html#logging.warning
so we prefer to use warning to avoid DeprecationWarning.

Change-Id: Ic7496d4dc765586e1bc79c3202b80c43faf0
Closes-Bug: #1530742


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

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

Title:
  Change LOG.warn to LOG.warning

Status in Evoque:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  In Progress
Status in Mistral:
  New
Status in Murano:
  In Progress
Status in oslo.messaging:
  In Progress
Status in oslo.middleware:
  New
Status in python-evoqueclient:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  Fix Released
Status in tempest:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evoque/+bug/1530742/+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 1480042] Re: L3 agent notify error after HA router deletion

2016-01-03 Thread 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/1480042

Title:
  L3 agent notify error after HA router deletion

Status in neutron:
  Expired

Bug description:
  $ uname -a
  Linux compute02 3.10.0-229.el7.x86_64 #1 SMP Fri Mar 6 11:36:42 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  $ neutron-server --version
  neutron-server 2015.1.0

  Reproduce the bug:
  1. Two network node running l3, dhcp, metadata
  2. ml2 ovs + gre
  3. enable neutron l3 ha
  4. create ha router
  5. set router gateway
  6. add router interface to a subnet
  7. create an instance
  8. set a floating IP to the instance
  9. unset and release the floating IP
  10. unset the router gateway and the interface to a subnet
  11. delete the router

  
  Assert that the master vRouter is running in host A,
  the second network node host B which is the stand-by vrrp qrouter-ns, it will 
get errors:

  l3-agent.log

  2015-07-31 12:10:01.886 7017 ERROR neutron.agent.linux.utils [-]
  Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 
'netns', 'exec', 'qrouter-0678efdd-e6e7-4f4e-be5c-ac975929d2c1', 
'iptables-save', '-c']
  Exit code: 1
  Stdin:
  Stdout:
  Stderr: Cannot open network namespace 
"qrouter-0678efdd-e6e7-4f4e-be5c-ac975929d2c1": No such file or directory

  2015-07-31 12:10:01.887 7017 DEBUG oslo_concurrency.lockutils [-] Releasing 
file lock 
"/var/lib/neutron/lock/neutron-iptables-qrouter-0678efdd-e6e7-4f4e-be5c-ac975929d2c1"
 after holding it for 0.074s release 
/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:227
  2015-07-31 12:10:01.887 7017 DEBUG oslo_concurrency.lockutils [-] Releasing 
semaphore "iptables-qrouter-0678efdd-e6e7-4f4e-be5c-ac975929d2c1" lock 
/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:404
  2015-07-31 12:10:01.887 7017 DEBUG neutron.agent.linux.iptables_manager [-] 
Semaphore / lock released 
"iptables-qrouter-0678efdd-e6e7-4f4e-be5c-ac975929d2c1" _apply 
/usr/lib/python2.7/site-packages/neutron/agent/linux/iptables_manager.py:419
  2015-07-31 12:10:01.888 7017 ERROR neutron.callbacks.manager [-] Error during 
notification for neutron.agent.metadata.driver.before_router_removed router, 
before_delete
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager Traceback (most 
recent call last):
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/callbacks/manager.py", line 143, in 
_notify_loop
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager 
callback(resource, event, trigger, **kwargs)
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/agent/metadata/driver.py", line 171, 
in before_router_removed
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager 
router.iptables_manager.apply()
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/agent/linux/iptables_manager.py", 
line 407, in apply
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager self._apply()
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/agent/linux/iptables_manager.py", 
line 417, in _apply
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager return 
self._apply_synchronized()
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/agent/linux/iptables_manager.py", 
line 437, in _apply_synchronized
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager all_tables = 
self.execute(args, run_as_root=True)
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager   File 
"/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py", line 137, in 
execute
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager raise 
RuntimeError(m)
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager RuntimeError:
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager Command: 
['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 
'exec', 'qrouter-0678efdd-e6e7-4f4e-be5c-ac975929d2c1', 'iptables-save', '-c']
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager Exit code: 1
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager Stdin:
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager Stdout:
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager Stderr: Cannot 
open network namespace "qrouter-0678efdd-e6e7-4f4e-be5c-ac975929d2c1": No such 
file or directory
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager
  2015-07-31 12:10:01.888 7017 TRACE neutron.callbacks.manager
  2015-07-31

[Yahoo-eng-team] [Bug 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread zhangguoqing 
** Also affects: oslo.messaging
   Importance: Undecided
   Status: New

** Changed in: oslo.messaging
 Assignee: (unassigned) => zhangguoqing (474751729-o)

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

Title:
  Change LOG.warn to LOG.warning

Status in Evoque:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  In Progress
Status in Mistral:
  New
Status in Murano:
  In Progress
Status in oslo.messaging:
  In Progress
Status in oslo.middleware:
  New
Status in python-evoqueclient:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evoque/+bug/1530742/+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 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread zhangguoqing 
** Also affects: mistral
   Importance: Undecided
   Status: New

** Also 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 Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1530742

Title:
  Change LOG.warn to LOG.warning

Status in Evoque:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  New
Status in Mistral:
  New
Status in Murano:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evoque/+bug/1530742/+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 1530742] Re: Change LOG.warn to LOG.warning

2016-01-03 Thread zhangguoqing 
** Also affects: oslo.middleware
   Importance: Undecided
   Status: New

** Changed in: oslo.middleware
 Assignee: (unassigned) => zhangguoqing (474751729-o)

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

Title:
  Change LOG.warn to LOG.warning

Status in Evoque:
  In Progress
Status in Gnocchi:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  In Progress
Status in Mistral:
  New
Status in Murano:
  In Progress
Status in oslo.messaging:
  In Progress
Status in oslo.middleware:
  New
Status in python-evoqueclient:
  In Progress
Status in python-heatclient:
  In Progress
Status in python-muranoclient:
  In Progress
Status in senlin:
  In Progress

Bug description:
  Python 3 deprecated the logger.warn method, see:
  https://docs.python.org/3/library/logging.html#logging.warning
  so we prefer to use warning to avoid DeprecationWarning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evoque/+bug/1530742/+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 1427731] Re: Port is not deleted after instance removal (DVR)

2016-01-03 Thread Abdul Rehman 
Hi Itzik,

This has been fixed in Liberty release 12.0.0 on 2015-10-15.  Please re-
verify.

Thanks.


** Changed in: neutron
   Status: New => 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/1427731

Title:
  Port is not deleted after instance removal (DVR)

Status in neutron:
  Fix Released

Bug description:
  Having a DVR created by 'admin' with 1 port connected to a tenant private 
network and 1 connected to an external network.
  After removing an instance connected to the private network the port of the 
instance is not deleted.

  Error in Neutron Log
  =
  2015-03-04 10:35:22.914 4360 INFO neutron.api.v2.resource 
[req-c9645d8e-b76b-481e-8ace-6ca54859c15c None] delete failed (client error): 
Router 23cca51f-df26-4a29-b454-c7ae8204b479 could not be found

  
  Version
  ==
  openstack-neutron-2014.2.2-1.el7ost.noarch
  python-neutron-2014.2.2-1.el7ost.noarch
  openstack-neutron-ml2-2014.2.2-1.el7ost.noarch

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1427731/+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 1517839] Re: Make CONF.set_override with paramter enforce_type=True by default

2016-01-03 Thread LiuNanke 
** Also affects: keystone
   Importance: Undecided
   Status: New

** Changed in: keystone
 Assignee: (unassigned) => LiuNanke (nanke-liu)

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

Title:
  Make CONF.set_override with paramter enforce_type=True by default

Status in OpenStack Identity (keystone):
  New
Status in oslo.config:
  New
Status in Rally:
  In Progress

Bug description:
  1. Problems :
 oslo_config provides method CONF.set_override[1] , developers usually use 
it to change config option's value in tests. That's convenient .
 By default  parameter enforce_type=False,  it doesn't check any type or 
value of override. If set enforce_type=True , will check parameter
 override's type and value.  In production code(running time code),  
oslo_config  always checks  config option's value.
 In short, we test and run code in different ways. so there's  gap:  config 
option with wrong type or invalid value can pass tests when
 parameter enforce_type = False in consuming projects.  that means some 
invalid or wrong tests are in our code base.
 There is nova POC result when I enable "enforce_type=true" [2],  and I 
must fix them in [3]

 [1] 
https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py#L2173
 [2] 
http://logs.openstack.org/16/242416/1/check/gate-nova-python27/97b5eff/testr_results.html.gz
 [3]  https://review.openstack.org/#/c/242416/  
https://review.openstack.org/#/c/242717/  
https://review.openstack.org/#/c/243061/

  2. Proposal 
 1) Make  method CONF.set_override with  enforce_type=True  in consuming 
projects. and  fix violations when  enforce_type=True in each project.

2) Make  method CONF.set_override with  enforce_type=True by default
  in oslo_config

 Hope some one from consuming projects can help make
  enforce_type=True in consuming projects and fix violations,

 You can find more details and comments  in
  https://etherpad.openstack.org/p/enforce_type_true_by_default

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1517839/+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 1530647] [NEW] dhcp: Default to using local DNS resolution

2016-01-03 Thread OpenStack Infra 
Public bug reported:

https://review.openstack.org/192712
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

commit 0de1d8d4ca8f7bb51c3e39259d0e0f48039ba5d0
Author: Kyle Mestery 
Date:   Wed Jun 17 14:46:47 2015 +

dhcp: Default to using local DNS resolution

It's pointless to not include default DNS resolution for Neutron.
This adds a new config option (dnsmasq_local_resolv) which defaults
to 'True' and will allow for DNS name resolution to work out of
the box. The caveat is that if the 'dnsmasq_dns_servers' is set it
will override the 'dnsmasq_local_resolv' setting, thus allowing
operators to explicitly set their own DNS servers.

DocImpact: Default to using local DNS resolution with the DHCP agent.

Change-Id: I17a884f467d307432a06f67a9dd93ed2fa6081a3
Closes-Bug: #1466117
Signed-off-by: Kyle Mestery 

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: neutron

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

Title:
  dhcp: Default to using local DNS resolution

Status in neutron:
  New

Bug description:
  https://review.openstack.org/192712
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 0de1d8d4ca8f7bb51c3e39259d0e0f48039ba5d0
  Author: Kyle Mestery 
  Date:   Wed Jun 17 14:46:47 2015 +

  dhcp: Default to using local DNS resolution
  
  It's pointless to not include default DNS resolution for Neutron.
  This adds a new config option (dnsmasq_local_resolv) which defaults
  to 'True' and will allow for DNS name resolution to work out of
  the box. The caveat is that if the 'dnsmasq_dns_servers' is set it
  will override the 'dnsmasq_local_resolv' setting, thus allowing
  operators to explicitly set their own DNS servers.
  
  DocImpact: Default to using local DNS resolution with the DHCP agent.
  
  Change-Id: I17a884f467d307432a06f67a9dd93ed2fa6081a3
  Closes-Bug: #1466117
  Signed-off-by: Kyle Mestery 

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1530647/+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 1466117] Re: Add default DNS servers to Neutron's DNS configuration

2016-01-03 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/192712
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=0de1d8d4ca8f7bb51c3e39259d0e0f48039ba5d0
Submitter: Jenkins
Branch:master

commit 0de1d8d4ca8f7bb51c3e39259d0e0f48039ba5d0
Author: Kyle Mestery 
Date:   Wed Jun 17 14:46:47 2015 +

dhcp: Default to using local DNS resolution

It's pointless to not include default DNS resolution for Neutron.
This adds a new config option (dnsmasq_local_resolv) which defaults
to 'True' and will allow for DNS name resolution to work out of
the box. The caveat is that if the 'dnsmasq_dns_servers' is set it
will override the 'dnsmasq_local_resolv' setting, thus allowing
operators to explicitly set their own DNS servers.

DocImpact: Default to using local DNS resolution with the DHCP agent.

Change-Id: I17a884f467d307432a06f67a9dd93ed2fa6081a3
Closes-Bug: #1466117
Signed-off-by: Kyle Mestery 


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

Title:
  Add default DNS servers to Neutron's DNS configuration

Status in neutron:
  Fix Released

Bug description:
  When Neutron is used to manage networking, the default dhcp agent
  configuration does not include dns servers that would allow dnsmasq to
  resolve external hosts.  This change adds the google dns servers to
  the dhcp agent configuration to ensure that external resolution is
  possible by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1466117/+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 1530650] [NEW] Neutron: Unable to create ICMP customer rules when type/code is 0

2016-01-03 Thread Gary Kotton 
Public bug reported:

The horizon checks for ICMP codes and types are invalid. This should be
between 0 and 255

** Affects: horizon
 Importance: Undecided
 Assignee: Gary Kotton (garyk)
 Status: In Progress

** Changed in: horizon
 Assignee: (unassigned) => Gary Kotton (garyk)

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

Title:
  Neutron: Unable to create ICMP customer rules when type/code is 0

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  The horizon checks for ICMP codes and types are invalid. This should
  be between 0 and 255

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1530650/+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 1489059] Re: "db type could not be determined" running py34

2016-01-03 Thread LiuNanke 
** No longer affects: horizon

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

Title:
  "db type could not be determined" running py34

Status in Aodh:
  Fix Released
Status in Barbican:
  Fix Released
Status in cloudkitty:
  Fix Committed
Status in Glance:
  Fix Committed
Status in glance_store:
  Fix Committed
Status in hacking:
  Fix Released
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-lib:
  Fix Committed
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Committed
Status in Manila:
  Fix Released
Status in Murano:
  Fix Committed
Status in networking-midonet:
  Fix Released
Status in networking-ofagent:
  New
Status in neutron:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-keystoneclient:
  Fix Committed
Status in python-muranoclient:
  Fix Released
Status in python-solumclient:
  In Progress
Status in Rally:
  In Progress
Status in Sahara:
  Fix Released
Status in senlin:
  Fix Released
Status in tap-as-a-service:
  New
Status in tempest:
  Fix Released
Status in zaqar:
  In Progress

Bug description:
  When running tox for the first time, the py34 execution fails with an
  error saying "db type could not be determined".

  This issue is know to be caused when the run of py27 preceeds py34 and
  can be solved erasing the .testrepository and running "tox -e py34"
  first of all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1489059/+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 1525819] Re: nova image-list returns 500 error

2016-01-03 Thread Elhay Efrat 
** Changed in: nova
   Status: Incomplete => Invalid

** Changed in: nova
 Assignee: (unassigned) => Elhay Efrat (elhayefrat)

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

Title:
  nova image-list returns 500 error

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  I am installing liberty release on centos7 with one controller and one
  compute node. nova service-list and nova endpoints work fine. But,
  nova image-list returns the following error.

  ERROR(ClientException) : Unexpected API Error. Please report this at 
http://bugs.launchpad.net/nova and attach the Nova API log if possible.
   (HTTP 500) (Request-ID: 
...)

  glance image-list works fine. 
  Pls, help me out.

  the nova-api.log is following.

  2015-12-14 16:29:56.071 9986 INFO nova.osapi_compute.wsgi.server 
[req-496b5df0-e28f-486b-8386-96f704433daf 504f2af1b9044a3e97bc69e80daf5809 
8de4c51458804564b79932efa364524b - - -] 192.168.219.11 "GET /v2/ HTTP/1.1" 
status: 200 len: 572 time: 0.0285130
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions 
[req-e65f8242-8d2c-43f1-af66-362f3161b655 504f2af1b9044a3e97bc69e80daf5809 
8de4c51458804564b79932efa364524b - - -] Unexpected exception in API method
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, 
in wrapped
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/api/openstack/compute/images.py", line 
145, in detail
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions 
**page_params)
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/image/api.py", line 68, in get_all
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions return 
session.detail(context, **kwargs)
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/nova/image/glance.py", line 284, in detail
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions for 
image in images:
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/glanceclient/v1/images.py", line 254, in list
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions for 
image in paginate(params, return_request_id):
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/glanceclient/v1/images.py", line 238, in 
paginate
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions images, 
resp = self._list(url, "images")
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/glanceclient/v1/images.py", line 63, in _list
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions resp, 
body = self.client.get(url)
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/glanceclient/common/http.py", line 280, in get
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions return 
self._request('GET', url, **kwargs)
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/glanceclient/common/http.py", line 272, in 
_request
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions resp, 
body_iter = self._handle_response(resp)
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File 
"/usr/lib/python2.7/site-packages/glanceclient/common/http.py", line 93, in 
_handle_response
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions raise 
exc.from_response(resp, resp.content)
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions 
HTTPInternalServerError: 500 Internal Server Error: The server has either erred 
or is incapable of performing the requested operation. (HTTP 500)
  2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions 
  2015-12-14 16:30:01.685 9986 INFO nova.api.openstack.wsgi 
[req-e65f8242-8d2c-43f1-af66-362f3161b655 504f2af1b9044a3e97bc69e80daf5809 
8de4c51458804564b79932efa364524b - - -] HTTP exception thrown: Unexpected API 
Error. Please report this at http://bugs.launchpad.net/nova/ and attach the 
Nova API log if possible.
  
  2015-12-14 16:30:01.687 9986 INFO nova.osapi_compute.wsgi.server 
[req-e65f8242-8d2c-43f1-af66-362f3161b655 504f2af1b9044a3e97bc69e80daf5809 
8de4c51458804564b79932efa364524b - - -] 192.168.219.11 "GET 
/v2/8de4c51458804564b79932efa364524b/images/detail