[Yahoo-eng-team] [Bug 1312002] [NEW] nova cell-show fails in devstack development environment
Public bug reported:
I am using devstack development environment with n-cell enabled in localrc.
When I call API to list all cells a cell with name "child" is explored.
Again when I try to "cell-show" this cell "child" call is failed with an error
response 500.
following is the operations followed -
Setting in /etc/nova/nova.conf
[cells]
name = region
cell_type = api
enable = True
When API call to get cells -
REQUEST -
curl -i
'http://10.0.9.40:8774/v2/dcab4e3fc2734bad97c43d46bb77d076/os-cells' -X GET -H
"X-Auth-Project-Id: demo" -H "User-Agent: python-novaclient" -H "Accept:
application/json" -H "X-Auth-Token:"
RESPONSE -
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 111
X-Compute-Request-Id: req-e83c337a-a7d9-47e5-a472-72cd41126f21
Date: Thu, 24 Apr 2014 04:12:34 GMT
{"cells": [{"username": "guest", "rpc_host": "10.0.9.40", "type":
"child", "name": "child", "rpc_port": 5672}]}
During particular cell show (using cell name as "child")-
REQUEST -
curl -i
'http://10.0.9.40:8774/v2/dcab4e3fc2734bad97c43d46bb77d076/os-cells/child' -X
GET -H "X-Auth-Project-Id: demo" -H "User-Agent: python-novaclient" -H "Accept:
application/json" -H "X-Auth-Token: "
RESPONSE -
HTTP/1.1 500 Internal Server Error
Content-Length: 128
Content-Type: application/json; charset=UTF-8
X-Compute-Request-Id: req-ba2503bd-3948-4cce-8ee6-543aa597497b
Date: Thu, 24 Apr 2014 04:10:33 GMT
{"computeFault": {"message": "The server has either erred or is
incapable of performing the requested operation.", "code": 500}}
Note: when using cell name as "api" or "region" 404 is returned.
nova-api logs during show call is traced as below -
2014-04-24 11:15:20.219 DEBUG keystoneclient.middleware.auth_token [-]
Authenticating user token from (pid=705) __call__
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py:603
2014-04-24 11:15:20.220 DEBUG keystoneclient.middleware.auth_token [-]
Removing headers from request environment:
X-Identity-Status,X-Domain-Id,X-Domain-Name,X-Project-Id,X-Project-Name,X-Project-Domain-Id,X-Project-Domain-Name,X-User-Id,X-User-Name,X-User-Domain-Id,X-User-Domain-Name,X-Roles,X-Service-Catalog,X-User,X-Tenant-Id,X-Tenant-Name,X-Tenant,X-Role
from (pid=705) _remove_auth_headers
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py:662
2014-04-24 11:15:20.232 DEBUG keystoneclient.middleware.auth_token [-]
Storing token in cache from (pid=705) _cache_put
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py:1121
2014-04-24 11:15:20.233 DEBUG keystoneclient.middleware.auth_token [-]
Received request from user: 6cf0c59310fb4b189fc157b19d0e1026 with project_id :
2c3857a83f454b7cb073891ef47acd11 and roles: heat_stack_owner,admin from
(pid=705) _build_user_headers
/opt/stack/python-keystoneclient/keystoneclient/middleware/auth_token.py:910
2014-04-24 11:15:20.238 DEBUG routes.middleware
[req-3ddd31fe-cd31-4c81-b960-81c753566b4a admin demo] Matched GET
/2c3857a83f454b7cb073891ef47acd11/os-cells/child from (pid=705) __call__
/usr/lib/python2.7/dist-packages/routes/middleware.py:100
2014-04-24 11:15:20.239 DEBUG routes.middleware
[req-3ddd31fe-cd31-4c81-b960-81c753566b4a admin demo] Route path:
'/{project_id}/os-cells/:(id)', defaults: {'action': u'show', 'controller':
} from (pid=705) __call__
/usr/lib/python2.7/dist-packages/routes/middleware.py:102
2014-04-24 11:15:20.239 DEBUG routes.middleware
[req-3ddd31fe-cd31-4c81-b960-81c753566b4a admin demo] Match dict: {'action':
u'show', 'controller': ,
'project_id': u'2c3857a83f454b7cb073891ef47acd11', 'id': u'child'} from
(pid=705) __call__ /usr/lib/python2.7/dist-packages/routes/middleware.py:103
2014-04-24 11:15:20.240 DEBUG nova.api.openstack.wsgi
[req-3ddd31fe-cd31-4c81-b960-81c753566b4a admin demo] Calling method '>' (Content-type='None', Accept='appl
[Yahoo-eng-team] [Bug 1311971] [NEW] database exception causes UnboundLocalError in linuxbridge-agent
Public bug reported: When database exception raises in update_port_status, the linuxbridge- agent doesn't deal with them very well that causes accessing not-existed local variables. 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent Traceback (most recent call last): 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent File "/usr/lib/python2.6/site-packages/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py", line 997, in daemon_loop 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent sync = self.process_network_devices(device_info) 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent File "/usr/lib/python2.6/site-packages/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py", line 894, in process_network_devices 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent resync_b = self.treat_devices_removed(device_info['removed']) 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent File "/usr/lib/python2.6/site-packages/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py", line 963, in treat_devices_removed 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent if details['exists']: 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent UnboundLocalError: local variable 'details' referenced before assignment 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent 2014-04-22 20:35:53.437 494 DEBUG neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent [req-ffc712fc-80af-4837-a068-6e1a076e4ebc None] Loop iteration exceeded interval (2 vs. 51.2715768814)! daemon_loop /usr/lib/python2.6/site-packages/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py:1011 2014-04-22 20:35:53.438 494 INFO neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent [req-ffc712fc-80af-4837-a068-6e1a076e4ebc None] Agent out of sync with plugin! ** Affects: neutron Importance: Undecided Assignee: Li Ma (nick-ma-z) Status: New ** Changed in: neutron Assignee: (unassigned) => Li Ma (nick-ma-z) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1311971 Title: database exception causes UnboundLocalError in linuxbridge-agent Status in OpenStack Neutron (virtual network service): New Bug description: When database exception raises in update_port_status, the linuxbridge- agent doesn't deal with them very well that causes accessing not- existed local variables. 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent Traceback (most recent call last): 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent File "/usr/lib/python2.6/site-packages/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py", line 997, in daemon_loop 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent sync = self.process_network_devices(device_info) 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent File "/usr/lib/python2.6/site-packages/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py", line 894, in process_network_devices 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent resync_b = self.treat_devices_removed(device_info['removed']) 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent File "/usr/lib/python2.6/site-packages/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py", line 963, in treat_devices_removed 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent if details['exists']: 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent UnboundLocalError: local variable 'details' referenced before assignment 2014-04-22 20:35:53.436 494 TRACE neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent 2014-04-22 20:35:53.437 494 DEBUG neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent [req-ffc712fc-80af-4837-a068-6e1a076e4ebc None] Loop iteration exceeded interval (2 vs. 51.2715768814)! daemon_loop /usr/lib/python2.6/site-packages/neutron/plugins/linuxbridge/agent/linuxbridge_neutron_agent.py:1011 2014-04-22 20:35:53.438 494 INFO neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent [req-ffc712fc-80af-4837-a068-6e1a076e4ebc None] Agent out of sync with plugin! To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+
[Yahoo-eng-team] [Bug 1311970] [NEW] Concurrent delete-update raises database lock in linuxbridge-agent
Public bug reported:
I concurrently deleted more than 100 instances and then linuxbridge-
agent threw exception as below:
2014-04-22 20:35:53.435 494 DEBUG
neutron.plugins.linuxbridge.agent.linuxbridge_neutron_agent [req-
ffc712fc-80af-4837-a068-6e1a076e4ebc None] port_removed failed for
tap2552f6fa-0a: Remote error: OperationalError (OperationalError) (1205,
'Lock wait timeout exceeded; try restarting transaction') 'UPDATE ports
SET status=%s WHERE ports.id = %s' ('DOWN', '2552f6fa-
0a43-4193-b018-2c971fe4b0d7')
[u'Traceback (most recent call last):\n', u'
File
"/usr/lib/python2.6/site-packages/neutron/openstack/common/rpc/impl_zmq.py",
line 314, in _get_response\ndata.get(\'namespace\'), **data[\'args\'])\n',
u'
File "/usr/lib/python2.6/site-packages/neutron/common/rpc.py", line 45, in
dispatch\nneutron_ctxt, version, method, namespace, **kwargs)\n', u'
File
"/usr/lib/python2.6/site-packages/neutron/openstack/common/rpc/dispatcher.py",
line 172, in dispatch\nresult = getattr(proxyobj, method)(ctxt,
**kwargs)\n', u' File
"/usr/lib/python2.6/site-packages/neutron/plugins/ml2/rpc.py", line 178, in
update_device_down\nq_const.PORT_STATUS_DOWN)\n', u'
File "/usr/lib/python2.6/site-packages/neutron/plugins/ml2/plugin.py", line
747, in update_port_status\noriginal_port[\'network_id\'])\n', u'
File "/usr/lib/python2.6/site-packages/neutron/plugins/ml2/plugin.py", line
410, in get_network\nresult = super(Ml2Plugin, self).get_network(context,
id, None)\n', u'
File "/usr/lib/python2.6/site-packages/neutron/db/db_base_plugin_v2.py", line
971, in get_network\nnetwork = self._get_network(context, id)\n', u'
File "/usr/lib/python2.6/site-packages/neutron/db/db_base_plugin_v2.py", line
245, in _get_network\nnetwork = self._get_by_id(context, models_v2.Network,
id)\n', u'
File "/usr/lib/python2.6/site-packages/neutron/db/db_base_plugin_v2.py", line
144, in _get_by_id\nreturn query.filter(model.id == id).one()\n', u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/orm/query.py",
line 2184, in one\nret = list(self)\n', u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/orm/query.py",
line 2226, in __iter__\nself.session._autoflush()\n', u' File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/orm/session.py",
line 1012, in _autoflush\nself.flush()\n', u'
File
"/usr/lib/python2.6/site-packages/neutron/openstack/common/db/sqlalchemy/session.py",
line 597, in _wrap\nreturn f(*args, **kwargs)\n', u'
File
"/usr/lib/python2.6/site-packages/neutron/openstack/common/db/sqlalchemy/session.py",
line 836, in flush\nreturn super(Session, self).flush(*args, **kwargs)\n',
u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/orm/session.py",
line 1583, in flush\nself._flush(objects)\n', u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/orm/session.py",
line 1654, in _flush\nflush_context.execute()\n', u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/orm/unitofwork.py",
line 331, in execute\nrec.execute(self)\n', u' File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/orm/unitofwork.py",
line 475, in execute\nuow\n', u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/orm/persistence.py",
line 59, in save_obj\nmapper, table, update)\n', u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/orm/persistence.py",
line 485, in _emit_update_statements\nexecute(statement, params)\n', u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py",
line 1449, in execute\nparams)\n', u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py",
line 1584, in _execute_clauseelement\ncompiled_sql, distilled_params\n', u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py",
line 1698, in _execute_context\ncontext)\n', u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/base.py",
line 1691, in _execute_context\ncontext)\n', u'
File
"/usr/lib64/python2.6/site-packages/SQLAlchemy-0.7.8-py2.6-linux-x86_64.egg/sqlalchemy/engine/default.py",
line 331, in do_execute\ncursor.execute(statement, parameters)\n', u'
File "/usr/lib64/python2.6/site-packages/MySQLdb/cursors.py", line 173, in
execute\nself.errorhandler(self, exc, value)\n', u'
File "/usr/lib64/python2.6/site-packages/MySQLdb/connections.py", line 36, in
defaulterrorhandler\nraise errorclass, errorvalue\n', u"OperationalError:
(OperationalError) (1205, 'Lock wait
[Yahoo-eng-team] [Bug 1311968] [NEW] Show admin/project instance details in a modal
Public bug reported: Today, when we click on the instances we can redirected to the instance details page. Doing so causes us to lose track of where we were previously. This requires us to navigate back to the instances page, and if paginated, requires us to page. It would be nice to have this information show up inside of a dialog instead. Implements: https://blueprints.launchpad.net/horizon/+spec/instance-detail-modal ** Affects: horizon Importance: Undecided Status: New ** Tags: detail instance modal ** Attachment added: "bp-instance-detail-modal.png" https://bugs.launchpad.net/bugs/1311968/+attachment/4094949/+files/bp-instance-detail-modal.png ** Description changed: Today, when we click on the instances we can redirected to the instance details page. Doing so causes us to lose track of where we were previously. This requires us to navigate back to the instances page, and if paginated, requires us to page. - It would be nice to have this information show up inside of a dialog - instead. + It would be nice to have this information show up inside of a dialog instead. + Implements: https://blueprints.launchpad.net/horizon/+spec/instance-detail-modal -- 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/1311968 Title: Show admin/project instance details in a modal Status in OpenStack Dashboard (Horizon): New Bug description: Today, when we click on the instances we can redirected to the instance details page. Doing so causes us to lose track of where we were previously. This requires us to navigate back to the instances page, and if paginated, requires us to page. It would be nice to have this information show up inside of a dialog instead. Implements: https://blueprints.launchpad.net/horizon/+spec/instance-detail-modal To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1311968/+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 1311960] [NEW] Handle session timeout in the VMware store
Public bug reported: The current implementation can potentially lead to a timeout when the invoke_api is not triggered (for example PUT/GET: direct HTTP access to the datastore). We need to recreate the session responses and retry when getting 401 HTTP responses. ** Affects: glance Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: glance Assignee: (unassigned) => Arnaud Legendre (arnaudleg) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1311960 Title: Handle session timeout in the VMware store Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: The current implementation can potentially lead to a timeout when the invoke_api is not triggered (for example PUT/GET: direct HTTP access to the datastore). We need to recreate the session responses and retry when getting 401 HTTP responses. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1311960/+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 1311943] [NEW] ibm: plugin should set secret=Tur on cfg.stropt('password
Public bug reported:
ibm: plugin should set secret=Tur on cfg.stropt('password
** Affects: neutron
Importance: Undecided
Status: New
** Tags: icehouse-backport-potential
** Tags added: icehouse-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1311943
Title:
ibm: plugin should set secret=Tur on cfg.stropt('password
Status in OpenStack Neutron (virtual network service):
New
Bug description:
ibm: plugin should set secret=Tur on cfg.stropt('password
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1311943/+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 1311904] [NEW] iptables manager doesn't decrement rule_index upon duplicate chain
Public bug reported: The iptables manager can fail to load iptables rules if a chain to be created already exists. The solution seems to be to decrement rule_index. This seems to cause vif plugging to fail. ** Affects: neutron Importance: Undecided Assignee: Aaron Knister (aaron-knister) Status: New ** Changed in: neutron Assignee: (unassigned) => Aaron Knister (aaron-knister) ** Description changed: The iptables manager can fail to load iptables rules if a chain to be created already exists. The solution seems to be to decrement - rule_index. + rule_index. This seems to cause vif plugging to fail. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1311904 Title: iptables manager doesn't decrement rule_index upon duplicate chain Status in OpenStack Neutron (virtual network service): New Bug description: The iptables manager can fail to load iptables rules if a chain to be created already exists. The solution seems to be to decrement rule_index. This seems to cause vif plugging to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1311904/+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 1311843] [NEW] fail to install openvswitch
Public bug reported: While using ubuntu 14.04 with the latest updates uname -a Linux compute1 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I tried to install openvswitch apt-get install neutron-common neutron-plugin-ml2 neutron-plugin- openvswitch-agent openvswitch-datapath-dkms which resulted in the following error while using dkms: configure: error: Linux kernel in /lib/modules/3.13.0-24-generic/build is version 3.13.9, but version newer than 3.12.x is not supported ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1311843/+attachment/4094637/+files/make.log ** Project changed: neutron => openvswitch (Ubuntu) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1311843 Title: fail to install openvswitch Status in “openvswitch” package in Ubuntu: New Bug description: While using ubuntu 14.04 with the latest updates uname -a Linux compute1 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I tried to install openvswitch apt-get install neutron-common neutron-plugin-ml2 neutron-plugin- openvswitch-agent openvswitch-datapath-dkms which resulted in the following error while using dkms: configure: error: Linux kernel in /lib/modules/3.13.0-24-generic/build is version 3.13.9, but version newer than 3.12.x is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1311843/+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 1311731] Re: Deploys fail with "NetworkRequiresSubnet" Exception when deployed with networks without subnets
Before this patch was added the instance would go into error state. The subnet is required for security groups. ** Changed in: nova Status: New => Invalid -- 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/1311731 Title: Deploys fail with "NetworkRequiresSubnet" Exception when deployed with networks without subnets Status in OpenStack Compute (Nova): Invalid Bug description: Deploys fail with "Network requires a subnet in order to boot instances on." when done with networks which don't have an associated subnet. It seems that this error was introduced after the following code was integrated: https://review.openstack.org/gitweb?p=openstack%2Fnova.git;a=commitdiff;h=45e2398f0c01c327db46ce92fb9dda886455db9d This review mentions that the subnet check will be subsequently removed but the issue is still present in the latest icehouse builds. The issue can be easily simulated by attempting a deploy without associating a subnet with it. Note: port_security_enabled is also not used as a part of the network used. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1311731/+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 1311820] [NEW] Neutron subnet create tooltip has invalid html tags
Public bug reported: In the Subnet Detail dialog (Neutron networks), when you hover the cursor over 'Allocation Pools' and 'Host Routes' text boxes, the help text contains '<' and '>' tags, instead of the standard <> chars. This kind of rendering should be left for the widget, and not be embedded in the text itself. ** 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/1311820 Title: Neutron subnet create tooltip has invalid html tags Status in OpenStack Dashboard (Horizon): New Bug description: In the Subnet Detail dialog (Neutron networks), when you hover the cursor over 'Allocation Pools' and 'Host Routes' text boxes, the help text contains '<' and '>' tags, instead of the standard <> chars. This kind of rendering should be left for the widget, and not be embedded in the text itself. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1311820/+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 1311814] [NEW] Add documentation for backend config in VMware
Public bug reported: There is no documentation describing how to configure backend datastores for Glance in VMware vCenter. ** Affects: glance Importance: Undecided Assignee: Andy Dugas (adugas) Status: New ** Changed in: glance Assignee: (unassigned) => Andy Dugas (adugas) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1311814 Title: Add documentation for backend config in VMware Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: There is no documentation describing how to configure backend datastores for Glance in VMware vCenter. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1311814/+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 1311804] [NEW] ip netns list starts without root_helper
Public bug reported:
In ip_lib in IpNetnsComand losted root_helper.
Without it L3 agent can't create interfaces inside network namespace:
2014-04-23 16:15:44.760 28240 DEBUG neutron.agent.linux.utils
[req-d0f812f6-d987-45f5-9cff-11f1fa52fed6 None] Running command: ['ip', '-o',
'netns', 'list'] create_process /
usr/lib/python2.6/site-packages/neutron/agent/linux/utils.py:48
2014-04-23 16:15:44.781 28240 DEBUG neutron.agent.linux.utils
[req-d0f812f6-d987-45f5-9cff-11f1fa52fed6 None]
Command: ['ip', '-o', 'netns', 'list']
Exit code: 0
Stdout: ''
Stderr: '' execute
/usr/lib/python2.6/site-packages/neutron/agent/linux/utils.py:74
2014-04-23 16:15:44.782 28240 DEBUG neutron.agent.linux.utils
[req-d0f812f6-d987-45f5-9cff-11f1fa52fed6 None] Running command: ['sudo',
'neutron-rootwrap', '/etc/neutron/roo
twrap.conf', 'ip', 'netns', 'add',
'qrouter-b582586e-70e3-4a38-8b19-039f30ce87a9'] create_process
/usr/lib/python2.6/site-packages/neutron/agent/linux/utils.py:48
2014-04-23 16:15:44.864 28240 DEBUG neutron.agent.linux.utils
[req-d0f812f6-d987-45f5-9cff-11f1fa52fed6 None]
Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip',
'netns', 'add', 'qrouter-b582586e-70e3-4a38-8b19-039f30ce87a9']
Exit code: 255
Stdout: ''
Stderr: 'Could not create
/var/run/netns/qrouter-b582586e-70e3-4a38-8b19-039f30ce87a9: File exists\n'
execute /usr/lib/python2.6/site-packages/neutron/agent/linux/utils.py:7
4
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/eventlet/greenpool.py", line 80, in
_spawn_n_impl
func(*args, **kwargs)
File "/usr/lib/python2.6/site-packages/neutron/agent/l3_agent.py", line 438,
in process_router
p['ip_cidr'], p['mac_address'])
File "/usr/lib/python2.6/site-packages/neutron/agent/l3_agent.py", line 707,
in internal_network_added
prefix=INTERNAL_DEV_PREFIX)
File "/usr/lib/python2.6/site-packages/neutron/agent/linux/interface.py",
line 195, in plug
namespace_obj = ip.ensure_namespace(namespace)
File "/usr/lib/python2.6/site-packages/neutron/agent/linux/ip_lib.py", line
136, in ensure_namespace
ip = self.netns.add(name)
File "/usr/lib/python2.6/site-packages/neutron/agent/linux/ip_lib.py", line
446, in add
self._as_root('add', name, use_root_namespace=True)
File "/usr/lib/python2.6/site-packages/neutron/agent/linux/ip_lib.py", line
217, in _as_root
kwargs.get('use_root_namespace', False))
File "/usr/lib/python2.6/site-packages/neutron/agent/linux/ip_lib.py", line
70, in _as_root
namespace)
File "/usr/lib/python2.6/site-packages/neutron/agent/linux/ip_lib.py", line
81, in _execute
root_helper=root_helper)
File "/usr/lib/python2.6/site-packages/neutron/agent/linux/utils.py", line
76, in execute
raise RuntimeError(m)
RuntimeError:
Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip',
'netns', 'add', 'qrouter-b582586e-70e3-4a38-8b19-039f30ce87a9']
Exit code: 255
** 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/1311804
Title:
ip netns list starts without root_helper
Status in OpenStack Neutron (virtual network service):
New
Bug description:
In ip_lib in IpNetnsComand losted root_helper.
Without it L3 agent can't create interfaces inside network namespace:
2014-04-23 16:15:44.760 28240 DEBUG neutron.agent.linux.utils
[req-d0f812f6-d987-45f5-9cff-11f1fa52fed6 None] Running command: ['ip', '-o',
'netns', 'list'] create_process /
usr/lib/python2.6/site-packages/neutron/agent/linux/utils.py:48
2014-04-23 16:15:44.781 28240 DEBUG neutron.agent.linux.utils
[req-d0f812f6-d987-45f5-9cff-11f1fa52fed6 None]
Command: ['ip', '-o', 'netns', 'list']
Exit code: 0
Stdout: ''
Stderr: '' execute
/usr/lib/python2.6/site-packages/neutron/agent/linux/utils.py:74
2014-04-23 16:15:44.782 28240 DEBUG neutron.agent.linux.utils
[req-d0f812f6-d987-45f5-9cff-11f1fa52fed6 None] Running command: ['sudo',
'neutron-rootwrap', '/etc/neutron/roo
twrap.conf', 'ip', 'netns', 'add',
'qrouter-b582586e-70e3-4a38-8b19-039f30ce87a9'] create_process
/usr/lib/python2.6/site-packages/neutron/agent/linux/utils.py:48
2014-04-23 16:15:44.864 28240 DEBUG neutron.agent.linux.utils
[req-d0f812f6-d987-45f5-9cff-11f1fa52fed6 None]
Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip',
'netns', 'add', 'qrouter-b582586e-70e3-4a38-8b19-039f30ce87a9']
Exit code: 255
Stdout: ''
Stderr: 'Could not create
/var/run/netns/qrouter-b582586e-70e3-4a38-8b19-039f30ce87a9: File exists\n'
execute /usr/lib/python2.6/site-packages/neutron/agent/linux/utils.py:7
4
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/eventlet/greenpool.py", line 80, in
_spawn_n_impl
func(*args, **kwargs)
File "/usr/lib/python2.6/site-packages/neutron/agent/l3_agent.py", line
43
[Yahoo-eng-team] [Bug 1297998] Re: VMWare: spawn refactor - _power_on_vm
** Changed in: nova Status: New => Invalid -- 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/1297998 Title: VMWare: spawn refactor - _power_on_vm Status in OpenStack Compute (Nova): Invalid Bug description: refactor this method and add unit tests as part of the spawn refactor effort To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1297998/+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 1311793] [NEW] wrap_instance_event() swallows return codes
Public bug reported: In compute/manager.py the function wrap_instance_event() just calls function(). This means that if it's used to decorate a function that returns a value, then the caller will never see the return code. ** Affects: nova Importance: Undecided Assignee: Chris Friesen (cbf123) Status: New ** Changed in: nova Assignee: (unassigned) => Chris Friesen (cbf123) -- 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/1311793 Title: wrap_instance_event() swallows return codes Status in OpenStack Compute (Nova): New Bug description: In compute/manager.py the function wrap_instance_event() just calls function(). This means that if it's used to decorate a function that returns a value, then the caller will never see the return code. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1311793/+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 1311789] [NEW] Filter does not work when table name has space
Public bug reported: Problem Description: When the DataTable name (as defined in the 'name' field of the Meta class in tables.py) has a space, filters defined on that table using FilterActions wont work. Cause: -table name is used as the table id in the html -the elements_to_search parameter for quicksearch plugin uses the following: table# tbody tr For example: if the table name specified in the Meta class of tables.py is 'foo bar', then the elements_to_search parameter for the quicksearch plugin will be: table#foo bar tbody tr. ** Affects: horizon Importance: Undecided Assignee: mariam john (mariamj) Status: New ** Changed in: horizon Assignee: (unassigned) => mariam john (mariamj) -- 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/1311789 Title: Filter does not work when table name has space Status in OpenStack Dashboard (Horizon): New Bug description: Problem Description: When the DataTable name (as defined in the 'name' field of the Meta class in tables.py) has a space, filters defined on that table using FilterActions wont work. Cause: -table name is used as the table id in the html -the elements_to_search parameter for quicksearch plugin uses the following: table# tbody tr For example: if the table name specified in the Meta class of tables.py is 'foo bar', then the elements_to_search parameter for the quicksearch plugin will be: table#foo bar tbody tr. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1311789/+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 1311778] [NEW] Unit tests fail with MessagingTimeout errors
Public bug reported: There is an issue that is causing unit tests to fail with the following error: MessagingTimeout: No reply on topic conductor MessagingTimeout: No reply on topic scheduler 2014-04-23 13:45:52.017 | Traceback (most recent call last): 2014-04-23 13:45:52.017 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply 2014-04-23 13:45:52.017 | incoming.message)) 2014-04-23 13:45:52.017 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 176, in _dispatch 2014-04-23 13:45:52.017 | return self._do_dispatch(endpoint, method, ctxt, args) 2014-04-23 13:45:52.017 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 122, in _do_dispatch 2014-04-23 13:45:52.017 | result = getattr(endpoint, method)(ctxt, **new_args) 2014-04-23 13:45:52.018 | File "nova/conductor/manager.py", line 798, in build_instances 2014-04-23 13:45:52.018 | legacy_bdm_in_spec=legacy_bdm) 2014-04-23 13:51:50.628 | File "nlibvir: error : internal error could not initialize domain event timer 2014-04-23 13:54:57.953 | ova/scheduler/rpcapi.py", line 120, in run_instance 2014-04-23 13:54:57.953 | cctxt.cast(ctxt, 'run_instance', **msg_kwargs) 2014-04-23 13:54:57.953 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/oslo/messaging/rpc/client.py", line 150, in call 2014-04-23 13:54:57.953 | wait_for_reply=True, timeout=timeout) 2014-04-23 13:54:57.953 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/oslo/messaging/transport.py", line 90, in _send 2014-04-23 13:54:57.953 | timeout=timeout) 2014-04-23 13:54:57.954 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/oslo/messaging/_drivers/impl_fake.py", line 166, in send 2014-04-23 13:54:57.954 | return self._send(target, ctxt, message, wait_for_reply, timeout) 2014-04-23 13:54:57.954 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/oslo/messaging/_drivers/impl_fake.py", line 161, in _send 2014-04-23 13:54:57.954 | 'No reply on topic %s' % target.topic) 2014-04-23 13:54:57.954 | MessagingTimeout: No reply on topic scheduler 2014-04-23 13:45:52.008 | Traceback (most recent call last): 2014-04-23 13:45:52.008 | File "nova/api/openstack/__init__.py", line 125, in __call__ 2014-04-23 13:45:52.008 | return req.get_response(self.application) 2014-04-23 13:45:52.009 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/webob/request.py", line 1320, in send 2014-04-23 13:45:52.009 | application, catch_exc_info=False) 2014-04-23 13:45:52.009 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/webob/request.py", line 1284, in call_application 2014-04-23 13:45:52.009 | app_iter = application(self.environ, start_response) 2014-04-23 13:45:52.009 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py", line 144, in __call__ 2014-04-23 13:45:52.009 | return resp(environ, start_response) 2014-04-23 13:45:52.009 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py", line 144, in __call__ 2014-04-23 13:45:52.010 | return resp(environ, start_response) 2014-04-23 13:45:52.010 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py", line 144, in __call__ 2014-04-23 13:45:52.010 | return resp(environ, start_response) 2014-04-23 13:45:52.010 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py", line 144, in __call__ 2014-04-23 13:45:52.010 | return resp(environ, start_response) 2014-04-23 13:45:52.010 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/routes/middleware.py", line 131, in __call__ 2014-04-23 13:45:52.010 | response = self.app(environ, start_response) 2014-04-23 13:45:52.011 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py", line 144, in __call__ 2014-04-23 13:45:52.011 | return resp(environ, start_response) 2014-04-23 13:45:52.011 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py", line 130, in __call__ 2014-04-23 13:45:52.011 | resp = self.call_func(req, *args, **self.kwargs) 2014-04-23 13:45:52.011 | File "/home/jenkins/workspace/gate-nova-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py", line 195, in call_func 2014-04-23 13:45:52.011 | return self.func(req, *args, **kwargs) 2014-04-23 13
[Yahoo-eng-team] [Bug 1311758] [NEW] OpenDaylight ML2 Mechanism Driver does not handle authentication errors
Public bug reported: This behaviour was noticed when troubleshooting a misconfiguration. Authentication with ODL was failing and the exception was being ignored. In the "sync_resources" method of the ODL Mechanism Driver, HTTPError exceptions with a status code of 404 are handled but the exception is not re-raised if the status code is not 404. It is preferable to re-raise this exception. In addition it would be helpful if the "obtain_auth_cookies" should throw a more specific exception than HTTPError when authentication with the ODL controller fails. ** Affects: neutron Importance: Undecided Assignee: Dave Tucker (davetucker) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Dave Tucker (davetucker) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1311758 Title: OpenDaylight ML2 Mechanism Driver does not handle authentication errors Status in OpenStack Neutron (virtual network service): In Progress Bug description: This behaviour was noticed when troubleshooting a misconfiguration. Authentication with ODL was failing and the exception was being ignored. In the "sync_resources" method of the ODL Mechanism Driver, HTTPError exceptions with a status code of 404 are handled but the exception is not re-raised if the status code is not 404. It is preferable to re-raise this exception. In addition it would be helpful if the "obtain_auth_cookies" should throw a more specific exception than HTTPError when authentication with the ODL controller fails. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1311758/+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 1306699] Re: utils.find_resource return resource not depends on query
Problem original opened as openstack client issue, but seems to be a
problem with keystone. I've updated the description.
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: python-openstackclient
Status: In Progress => Invalid
** Description changed:
+ When I have one group, the query /groups?display_name=bogus returns:
+
+ {u'groups': [{u'id': u'6ce42989b4ae41f89323813812ca6208', u'name':
+ u'asdf', u'domain_id': u'default', u'links': {u'self':
+ u'http://172.20.1.112:5000/v3/groups/6ce42989b4ae41f89323813812ca6208'},
+ u'description': u''}], u'links': {u'self':
+ u'http://172.20.1.112:5000/v3/groups', u'next': None, u'previous':
+ None}}
+
+ Even though the query did not match the query string.
+
I have defined only one resource of keystone (one user and one group), then I
try command which call method utils.find_resource.
This resource would be returned by utils.find_resource not depends on what
was specified as name or id.
Examples:
(.venv)stack@eu:/opt/stack/python-openstackclient$ openstack user list --role
--os-identity-api-version 3 non_existing_user
| 54fbed994dc84616b2118e4fe6b77d8f | Member |
(.venv)stack@eu:/opt/stack/python-openstackclient$ openstack user list
--role --os-identity-api-version 3 admin
| 54fbed994dc84616b2118e4fe6b77d8f | Member |
openstack group list --role --os-identity-api-version 3 --domain admin
group_not_exist
| 54fbed994dc84616b2118e4fe6b77d8f | Member | Default | t_dr |
So, utils.find_resource tries to find user/group with incorrect names
but doesn't fail in case when only one resource of such type is
specified. But it should raise an exception that it can't find resource
with specified name or ID.
I tried this also with nova and cinder commands, it works correct with
this services.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1306699
Title:
utils.find_resource return resource not depends on query
Status in OpenStack Identity (Keystone):
New
Status in OpenStack Command Line Client:
Invalid
Bug description:
When I have one group, the query /groups?display_name=bogus returns:
{u'groups': [{u'id': u'6ce42989b4ae41f89323813812ca6208', u'name':
u'asdf', u'domain_id': u'default', u'links': {u'self':
u'http://172.20.1.112:5000/v3/groups/6ce42989b4ae41f89323813812ca6208'},
u'description': u''}], u'links': {u'self':
u'http://172.20.1.112:5000/v3/groups', u'next': None, u'previous':
None}}
Even though the query did not match the query string.
I have defined only one resource of keystone (one user and one group), then I
try command which call method utils.find_resource.
This resource would be returned by utils.find_resource not depends on what
was specified as name or id.
Examples:
(.venv)stack@eu:/opt/stack/python-openstackclient$ openstack user list --role
--os-identity-api-version 3 non_existing_user
| 54fbed994dc84616b2118e4fe6b77d8f | Member |
(.venv)stack@eu:/opt/stack/python-openstackclient$ openstack user list
--role --os-identity-api-version 3 admin
| 54fbed994dc84616b2118e4fe6b77d8f | Member |
openstack group list --role --os-identity-api-version 3 --domain admin
group_not_exist
| 54fbed994dc84616b2118e4fe6b77d8f | Member | Default | t_dr |
So, utils.find_resource tries to find user/group with incorrect names
but doesn't fail in case when only one resource of such type is
specified. But it should raise an exception that it can't find
resource with specified name or ID.
I tried this also with nova and cinder commands, it works correct with
this services.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1306699/+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 1311731] [NEW] Deploys fail with "NetworkRequiresSubnet" Exception when deployed with networks without subnets
Public bug reported: Deploys fail with "Network requires a subnet in order to boot instances on." when done with networks which don't have an associated subnet. It seems that this error was introduced after the following code was integrated: https://review.openstack.org/gitweb?p=openstack%2Fnova.git;a=commitdiff;h=45e2398f0c01c327db46ce92fb9dda886455db9d This review mentions that the subnet check will be subsequently removed but the issue is still present in the latest icehouse builds. The issue can be easily simulated by attempting a deploy without associating a subnet with it. Note: port_security_enabled is also not used as a part of the network used. ** 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/1311731 Title: Deploys fail with "NetworkRequiresSubnet" Exception when deployed with networks without subnets Status in OpenStack Compute (Nova): New Bug description: Deploys fail with "Network requires a subnet in order to boot instances on." when done with networks which don't have an associated subnet. It seems that this error was introduced after the following code was integrated: https://review.openstack.org/gitweb?p=openstack%2Fnova.git;a=commitdiff;h=45e2398f0c01c327db46ce92fb9dda886455db9d This review mentions that the subnet check will be subsequently removed but the issue is still present in the latest icehouse builds. The issue can be easily simulated by attempting a deploy without associating a subnet with it. Note: port_security_enabled is also not used as a part of the network used. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1311731/+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 1311715] Re: Inconsistent capitization in UpdateFlavorAccess list titles.
Not sure how Ubuntu got added. Sorry about that. Removed it now. ** No longer affects: ubuntu -- 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/1311715 Title: Inconsistent capitization in UpdateFlavorAccess list titles. Status in OpenStack Dashboard (Horizon): Triaged Bug description: On the flavor access tab of the edit flavor workflow, you can select the projects that have access to the flavor. Currently, the left list is "All Projects" and the right list is "Selected projects". The "p" should be capitalized in Selected projects. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1311715/+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 1311715] Re: Inconsistent capitization in UpdateFlavorAccess list titles.
Hm, it seems to me this is a valid Horizon bug, not Ubuntu's? ** Also 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/1311715 Title: Inconsistent capitization in UpdateFlavorAccess list titles. Status in OpenStack Dashboard (Horizon): Triaged Status in Ubuntu: Confirmed Bug description: On the flavor access tab of the edit flavor workflow, you can select the projects that have access to the flavor. Currently, the left list is "All Projects" and the right list is "Selected projects". The "p" should be capitalized in Selected projects. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1311715/+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 1311715] [NEW] Inconsistent capitization in UpdateFlavorAccess list titles.
Public bug reported: On the flavor access tab of the edit flavor workflow, you can select the projects that have access to the flavor. Currently, the left list is "All Projects" and the right list is "Selected projects". The "p" should be capitalized in Selected projects. ** Affects: ubuntu Importance: Undecided Assignee: Travis Tripp (travis-tripp) Status: Confirmed ** Tags: low-hanging-fruit ** Changed in: horizon Assignee: (unassigned) => Travis Tripp (travis-tripp) ** Tags added: low-hanging-fruit -- 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/1311715 Title: Inconsistent capitization in UpdateFlavorAccess list titles. Status in Ubuntu: Confirmed Bug description: On the flavor access tab of the edit flavor workflow, you can select the projects that have access to the flavor. Currently, the left list is "All Projects" and the right list is "Selected projects". The "p" should be capitalized in Selected projects. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1311715/+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 1311715] Re: Inconsistent capitization in UpdateFlavorAccess list titles.
** Project changed: horizon => ubuntu ** Changed in: ubuntu Status: New => Confirmed -- 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/1311715 Title: Inconsistent capitization in UpdateFlavorAccess list titles. Status in Ubuntu: Confirmed Bug description: On the flavor access tab of the edit flavor workflow, you can select the projects that have access to the flavor. Currently, the left list is "All Projects" and the right list is "Selected projects". The "p" should be capitalized in Selected projects. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1311715/+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 1311693] [NEW] add docs to configuration federated identity
Public bug reported: currently, there are no docs to help users in configuring keystone to use federated identity, let's create first draft and publish to keystone/docs ** Affects: keystone Importance: Low Assignee: Steve Martinelli (stevemar) Status: New ** Changed in: keystone Milestone: None => juno-1 ** Changed in: keystone Assignee: (unassigned) => Steve Martinelli (stevemar) ** Changed in: keystone Importance: Undecided => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1311693 Title: add docs to configuration federated identity Status in OpenStack Identity (Keystone): New Bug description: currently, there are no docs to help users in configuring keystone to use federated identity, let's create first draft and publish to keystone/docs To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1311693/+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 1311681] [NEW] test_list_security_groups_list_all_tenants_filter fails with nova-net "Security group 34 not found"
Public bug reported:
http://logs.openstack.org/63/84363/2/check/check-grenade-
dsvm/0e4dcac/console.html
Looks like this only fails in grenade jobs with nova-network:
2014-04-23 08:39:17.718 | Traceback (most recent call last):
2014-04-23 08:39:17.718 | File
"tempest/api/compute/admin/test_security_groups.py", line 76, in
test_list_security_groups_list_all_tenants_filter
2014-04-23 08:39:17.718 | resp, fetched_list =
self.adm_client.list_security_groups(params=param)
2014-04-23 08:39:17.718 | File
"tempest/services/compute/xml/security_groups_client.py", line 51, in
list_security_groups
2014-04-23 08:39:17.718 | resp, body = self.get(url)
2014-04-23 08:39:17.718 | File "tempest/common/rest_client.py", line 204, in
get
2014-04-23 08:39:17.718 | return self.request('GET', url, extra_headers,
headers)
2014-04-23 08:39:17.718 | File "tempest/common/rest_client.py", line 452, in
request
2014-04-23 08:39:17.719 | resp, resp_body)
2014-04-23 08:39:17.719 | File "tempest/common/rest_client.py", line 496, in
_error_checker
2014-04-23 08:39:17.719 | raise exceptions.NotFound(resp_body)
2014-04-23 08:39:17.719 | NotFound: Object not found
2014-04-23 08:39:17.719 | Details: http://docs.openstack.org/compute/api/v1.1";>Security group 34
not found.
message:"Security group 34 not found" AND tags:screen-n-api.txt
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiU2VjdXJpdHkgZ3JvdXAgMzQgbm90IGZvdW5kXCIgQU5EIHRhZ3M6c2NyZWVuLW4tYXBpLnR4dCIsImZpZWxkcyI6WyJ0YWdzIl0sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTM5ODI2MTE3ODE3OCwibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ==
This doesn't always result in a failure when it shows up in the logs.
** 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/1311681
Title:
test_list_security_groups_list_all_tenants_filter fails with nova-net
"Security group 34 not found"
Status in OpenStack Compute (Nova):
New
Bug description:
http://logs.openstack.org/63/84363/2/check/check-grenade-
dsvm/0e4dcac/console.html
Looks like this only fails in grenade jobs with nova-network:
2014-04-23 08:39:17.718 | Traceback (most recent call last):
2014-04-23 08:39:17.718 | File
"tempest/api/compute/admin/test_security_groups.py", line 76, in
test_list_security_groups_list_all_tenants_filter
2014-04-23 08:39:17.718 | resp, fetched_list =
self.adm_client.list_security_groups(params=param)
2014-04-23 08:39:17.718 | File
"tempest/services/compute/xml/security_groups_client.py", line 51, in
list_security_groups
2014-04-23 08:39:17.718 | resp, body = self.get(url)
2014-04-23 08:39:17.718 | File "tempest/common/rest_client.py", line 204,
in get
2014-04-23 08:39:17.718 | return self.request('GET', url, extra_headers,
headers)
2014-04-23 08:39:17.718 | File "tempest/common/rest_client.py", line 452,
in request
2014-04-23 08:39:17.719 | resp, resp_body)
2014-04-23 08:39:17.719 | File "tempest/common/rest_client.py", line 496,
in _error_checker
2014-04-23 08:39:17.719 | raise exceptions.NotFound(resp_body)
2014-04-23 08:39:17.719 | NotFound: Object not found
2014-04-23 08:39:17.719 | Details: http://docs.openstack.org/compute/api/v1.1";>Security group 34
not found.
message:"Security group 34 not found" AND tags:screen-n-api.txt
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiU2VjdXJpdHkgZ3JvdXAgMzQgbm90IGZvdW5kXCIgQU5EIHRhZ3M6c2NyZWVuLW4tYXBpLnR4dCIsImZpZWxkcyI6WyJ0YWdzIl0sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTM5ODI2MTE3ODE3OCwibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ==
This doesn't always result in a failure when it shows up in the logs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1311681/+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 1311573] Re: Error for Keystone V3 extension "OS-SIMPLE-CERT" for XML interface
There's neither an XML interface nor a JSON interface to this call.
The only supported content type on this call is "application/x-pem-
file". The content of of the error->message attribute in your example
response should be the entire response body itself, regardless of
whether the client demands an application/xml response or not.
The XML translation layer is also deprecated as of Icehouse, due to the
high cost of maintenance and a lack of interest in the community to
support it (hence the Won't Fix).
** Changed in: keystone
Importance: Undecided => Low
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1311573
Title:
Error for Keystone V3 extension "OS-SIMPLE-CERT" for XML interface
Status in OpenStack Identity (Keystone):
Won't Fix
Bug description:
I tried to execute keystone V3 API "OS-SIMPLE-CERT/certificates" for
xml interface using curl request.
The response of the curl request doesnt contain a status code and an
error message is observed.
-Below is the curl command used:
curl -i -X GET http://127.0.0.1:35357/v3/OS-SIMPLE-CERT/certificates
-H "Content-Type: application/xml" -H "Accept: application/xml" -H
"User-Agent: python-keystoneclient"
-H "X-Auth-Token: "
-Below is the response:
Output:
HTTP/1.1 None None
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 4384
Date: Thu, 17 Apr 2014 07:06:07 GMT
{"error": {"message": "Certificate:\n Data:\n Version:
3 (0x2)\n Serial Number: 1 (0x1)\n
Signature Algorithm: sha1WithRSAEncryption\n
Issuer: C=US, ST=Unset, L=Unset, O=Unset, CN=www.example.com\n
Validity\n Not Before: Apr 17 06:58:08 2014 GMT\n
Not After : Apr 14 06:58:08 2024 GMT\n Subject: C=US,
ST=Unset, O=Unset, CN=www.example.com\n Subject Public Key Info:\n
Public Key Algorithm: rsaEncryption\n Public-Key: (2048 bit)\n
Modulus:\n 00:db:f2:8d:33:10:a3:b7:5a:c9:6e:58:a1:c9:2b:\n
89:f2:d2:2d:88:a7:73:a4:da:48:3e:2b:57:2e:99:\n
51:a8:73:26:5c:a0:54:32:1f:ad:35:8a:5a:65:2b:\n
22:13:18:9f:66:ac:09:0b:31:60:21:80:2f:af:5e:\n
03:7e:e0:66:8d:9d:b8:2e:87:82:ca:74:ee:b5:92:\n
4c:d8:f5:c9:33:c1:de:fe:29:c7:2e:ac:7d:10:8e:\n
57:27:27:36:b2:70:d5:d5:e0:be:7f:b6:68:af:e5:\n
a8:17:94:25:3e:80:69:c8:ad:72:c9:ce:b5:3a:d9:\n
71:f3:fd:45:50:2e:8f:c2:43:65:34:98:03:ee:14:\n
60:82:30:f7:14:85:2d:cb:5c:d4:92:55:e6:81:1e:\n
9f:93:df:3e:dc:3b:ad:0d:54:84:e1:48:20:73:42:\n
63:c0:54:4e:7b:e3:f3:70:97:f2:d6:ac:2e:33:c8:\n
4f:d1:9d:ef:a5:36:c5:d0:0b:19:d2:5f:3f:08:88:\n
f5:bf:44:57:88:c2:23:87:b6:42:7e:0d:3d:6b:b2:\n
a9:a1:56:5d:8a:20:c2:5d:b2:7f:01:ee:1f:5a:ee:\n
b7:ff:38:02:e6:bf:a8:ad:cc:3a:bd:18:6c:1b:b9:\n
c1:eb:d4:50:58:4a:49:fd:52:64:4b:a9:92:80:7b:\n
9d:95\n Exponent: 65537 (0x10001)\n
X509v3 extensions:\n X509v3 Basic Constraints: \n
CA:FALSE\n X509v3 Subject Key Identifier: \n
75:B4:09:04:09:5A:50:70:F6:15:E7:1F:D0:ED:26:7E:2A:7D:AF:7B\n
X509v3 Authority Key Identifier: \n
keyid:62:CC:B7:5A:72:BB:A0:7D:47:03:62:6B:6E:05:B0:FB:E6:1A:88:EE\n\n
Signature Algorithm: sha1WithRSAEncryption\n
4a:20:15:6d:70:09:6f:a6:7d:e7:8c:6a:26:77:e3:57:33:34:\n
b9:53:06:da:4e:76:3e:83:7c:79:c1:cf:aa:36:d9:05:c5:2f:\n
1f:81:44:ec:19:40:25:91:1f:cb:99:51:93:93:f1:6c:61:32:\n
0d:9e:a9:ce:e9:a7:30:43:a8:a8:7b:96:35:ea:e3:59:f9:df:\n
f1:f8:48:e0:7b:36:eb:c4:ae:c7:1d:13:aa:be:9a:79:c5:ba:\n
89:5d:bb:3c:4f:ea:73:c4:1f:96:e1:c8:19:f4:1e:06:50:cb:\n
75:dd:ed:95:d6:02:1d:08:2b:73:82:24:68:7a:c6:91:f8:06:\n
58:f5:f9:ff:6c:7b:40:8a:0c:f9:11:e9:a2:d7:46:bb:f8:74:\n
78:29:46:aa:c2:86:10:7c:48:7f:90:57:82:85:a2:f5:53:25:\n
97:c5:4a:83:10:db:22:d8:9a:c4:7c:a3:bc:3d:9d:f0:d0:9f:\n
fd:d5:4c:e4:74:3b:74:9c:73:f1:74:0b:b9:1a:31:a5:17:b1:\n
4b:fa:94:ee:f0:f4:34:0f:40:56:b7:6a:69:96:b7:8a:83:5e:\n
11:00:22:06:c1:3b:82:25:cd:1b:4b:88:0d:34:f8:af:2d:7b:\n
27:4d:74:ea:ee:6a:25:dc:1d:64:a1:5d:75:1f:4c:8f:f5:76:\n
6d:af:cd:06\n
-BEGIN CERTIFICATE-\n
MIIDZjCCAk6gAwIBAgIBATANBgkqhkiG9w0BAQUFADBXMQswCQYDVQQGEwJVUzEO\n
MAwGA1UECAwFVW5zZXQxDjAMBgNVBAcMBVVuc2V0MQ4wDAYDVQQKDAVVbnNldDEY\n
MBYGA1UEAwwPd3d3LmV4YW1wbGUuY29tMB4XDTE0MDQxNzA2NTgwOFoXDTI0MDQx\n
NDA2NTgwOFowRzELMAkGA1UEBhMCVVMxDjAMBgNVBAgMBVVuc2V0MQ4wDAYDVQQK\n
DAVVbnNldDEYMBYGA1UEAwwPd3d3LmV4YW1wbG
[Yahoo-eng-team] [Bug 1309297] Re: oslo removal of use_tpool conf option
** Changed in: nova Status: New => Fix Committed ** Changed in: nova Assignee: (unassigned) => Victor Sergeyev (vsergeyev) ** Changed in: oslo Status: New => Invalid ** Tags added: icehouse-backport-potential -- 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/1309297 Title: oslo removal of use_tpool conf option Status in OpenStack Compute (Nova): Fix Committed Status in Oslo - a Library of Common OpenStack Code: Invalid Bug description: Details here on the Mailing list: http://markmail.org/message/wwhd4qwrbynkzeax Here are the Oslo and Nova reviews: https://review.openstack.org/#/c/60031/ https://review.openstack.org/#/c/59760/ The Oslo review made it, but Nova did not make it in time. So we lost a config option in the shuffle. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1309297/+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 1311613] [NEW] missing virtio-scsi controller after evacuate
Public bug reported: When boot a instance from a volume create from an image with "hw_scsi_mode=virito-scsi" property, instance will use virtio-scsi controller instead of lsi controller. However, after evacuating, the new instance will not have the virtio- scsi controller. The reason is that the correct "image_meta" is not passing to the libvirt driver. ** Affects: nova Importance: Undecided Assignee: Trump.Zhang (zhangleiqiang) Status: New ** Tags: evacuate virtio-scsi ** Changed in: nova Assignee: (unassigned) => Trump.Zhang (zhangleiqiang) -- 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/1311613 Title: missing virtio-scsi controller after evacuate Status in OpenStack Compute (Nova): New Bug description: When boot a instance from a volume create from an image with "hw_scsi_mode=virito-scsi" property, instance will use virtio-scsi controller instead of lsi controller. However, after evacuating, the new instance will not have the virtio- scsi controller. The reason is that the correct "image_meta" is not passing to the libvirt driver. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1311613/+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 1311589] [NEW] DB2 upgrade failure for 50d5ba354c23_ml2_binding_vif_details
Public bug reported:
When upgrading Neutron with DB2, the following error will be seen at
step 50d5ba354c23_ml2_binding_vif_details
sqlalchemy.exc.ProgrammingError: (ProgrammingError)
ibm_db_dbi::ProgrammingError: Statement Execute Failed: [IBM][CLI
Driver][DB2/LINUXPPC64] SQL0401N The data types of the operands for the
operation "=" are not compatible or comparable. SQLSTATE=42818
SQLCODE=-401 'UPDATE ml2_port_bindings SET vif_details =
\'{"port_filter": true}\' WHERE cap_port_filter = true' ()
The reason is DB2 doesn't support Boolean type but uses small int
** Affects: neutron
Importance: Undecided
Assignee: Xu Han Peng (xuhanp)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Xu Han Peng (xuhanp)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1311589
Title:
DB2 upgrade failure for 50d5ba354c23_ml2_binding_vif_details
Status in OpenStack Neutron (virtual network service):
New
Bug description:
When upgrading Neutron with DB2, the following error will be seen at
step 50d5ba354c23_ml2_binding_vif_details
sqlalchemy.exc.ProgrammingError: (ProgrammingError)
ibm_db_dbi::ProgrammingError: Statement Execute Failed: [IBM][CLI
Driver][DB2/LINUXPPC64] SQL0401N The data types of the operands for
the operation "=" are not compatible or comparable. SQLSTATE=42818
SQLCODE=-401 'UPDATE ml2_port_bindings SET vif_details =
\'{"port_filter": true}\' WHERE cap_port_filter = true' ()
The reason is DB2 doesn't support Boolean type but uses small int
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1311589/+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 1311582] [NEW] resource usage for storage components shows no results
Public bug reported:
when I try to view storage resources in horizon's "resource usage" tab we get
no data available message.
looking at horizon log I see that we are getting an error but can't find
anything in ceilometer to suggest why we fail to show the info.
HTTP/0.9 200
Error response
Error response
Error code 400.
Message: Bad request syntax ('GET /v2/meters/image.update
/statistics?q.field=project_id&q.field=timestamp&q.field=timestamp&q.op=eq&q.op=ge&q.op=le&q.type=&q.type=&q.type=&q.value=18b1ac6dfd3f4235a420d136662c7062&q.value=2014-04-16+10%3A10%3A11.121506&q.value=2014-04-23+10%3A10%3A11.121522&period=1512
HTTP/1.1').
Error code explanation: 400 = Bad request syntax or unsupported method.
2014-04-23 10:10:11,267 2351 DEBUG ceilometerclient.common.http
HTTP/0.9 200
Error response
Error response
Error code 400.
Message: Bad request syntax ('GET /v2/meters/image.update
/statistics?q.field=project_id&q.field=timestamp&q.field=timestamp&q.op=eq&q.op=ge&q.op=le&q.type=&q.type=&q.type=&q.value=c3178ebef2c24d1b9a045bd67483a83c&q.value=2014-04-16+10%3A10%3A11.121506&q.value=2014-04-23+10%3A10%3A11.121522&period=1512
HTTP/1.1').
Error code explanation: 400 = Bad request syntax or unsupported method.
** 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/1311582
Title:
resource usage for storage components shows no results
Status in OpenStack Dashboard (Horizon):
New
Bug description:
when I try to view storage resources in horizon's "resource usage" tab we get
no data available message.
looking at horizon log I see that we are getting an error but can't find
anything in ceilometer to suggest why we fail to show the info.
HTTP/0.9 200
Error response
Error response
Error code 400.
Message: Bad request syntax ('GET /v2/meters/image.update
/statistics?q.field=project_id&q.field=timestamp&q.field=timestamp&q.op=eq&q.op=ge&q.op=le&q.type=&q.type=&q.type=&q.value=18b1ac6dfd3f4235a420d136662c7062&q.value=2014-04-16+10%3A10%3A11.121506&q.value=2014-04-23+10%3A10%3A11.121522&period=1512
HTTP/1.1').
Error code explanation: 400 = Bad request syntax or unsupported method.
2014-04-23 10:10:11,267 2351 DEBUG ceilometerclient.common.http
HTTP/0.9 200
Error response
Error response
Error code 400.
Message: Bad request syntax ('GET /v2/meters/image.update
/statistics?q.field=project_id&q.field=timestamp&q.field=timestamp&q.op=eq&q.op=ge&q.op=le&q.type=&q.type=&q.type=&q.value=c3178ebef2c24d1b9a045bd67483a83c&q.value=2014-04-16+10%3A10%3A11.121506&q.value=2014-04-23+10%3A10%3A11.121522&period=1512
HTTP/1.1').
Error code explanation: 400 = Bad request syntax or unsupported method.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1311582/+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 1311573] [NEW] Error for Keystone V3 extension "OS-SIMPLE-CERT" for XML interface
Public bug reported:
I tried to execute keystone V3 API "OS-SIMPLE-CERT/certificates" for xml
interface using curl request.
The response of the curl request doesnt contain a status code and an
error message is observed.
-Below is the curl command used:
curl -i -X GET http://127.0.0.1:35357/v3/OS-SIMPLE-CERT/certificates
-H "Content-Type: application/xml" -H "Accept: application/xml" -H
"User-Agent: python-keystoneclient"
-H "X-Auth-Token: "
-Below is the response:
Output:
HTTP/1.1 None None
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 4384
Date: Thu, 17 Apr 2014 07:06:07 GMT
{"error": {"message": "Certificate:\n Data:\n Version:
3 (0x2)\n Serial Number: 1 (0x1)\n
Signature Algorithm: sha1WithRSAEncryption\n
Issuer: C=US, ST=Unset, L=Unset, O=Unset, CN=www.example.com\n
Validity\n Not Before: Apr 17 06:58:08 2014 GMT\n
Not After : Apr 14 06:58:08 2024 GMT\n Subject: C=US,
ST=Unset, O=Unset, CN=www.example.com\n Subject Public Key Info:\n
Public Key Algorithm: rsaEncryption\n Public-Key: (2048 bit)\n
Modulus:\n 00:db:f2:8d:33:10:a3:b7:5a:c9:6e:58:a1:c9:2b:\n
89:f2:d2:2d:88:a7:73:a4:da:48:3e:2b:57:2e:99:\n
51:a8:73:26:5c:a0:54:32:1f:ad:35:8a:5a:65:2b:\n
22:13:18:9f:66:ac:09:0b:31:60:21:80:2f:af:5e:\n
03:7e:e0:66:8d:9d:b8:2e:87:82:ca:74:ee:b5:92:\n
4c:d8:f5:c9:33:c1:de:fe:29:c7:2e:ac:7d:10:8e:\n
57:27:27:36:b2:70:d5:d5:e0:be:7f:b6:68:af:e5:\n
a8:17:94:25:3e:80:69:c8:ad:72:c9:ce:b5:3a:d9:\n
71:f3:fd:45:50:2e:8f:c2:43:65:34:98:03:ee:14:\n
60:82:30:f7:14:85:2d:cb:5c:d4:92:55:e6:81:1e:\n
9f:93:df:3e:dc:3b:ad:0d:54:84:e1:48:20:73:42:\n
63:c0:54:4e:7b:e3:f3:70:97:f2:d6:ac:2e:33:c8:\n
4f:d1:9d:ef:a5:36:c5:d0:0b:19:d2:5f:3f:08:88:\n
f5:bf:44:57:88:c2:23:87:b6:42:7e:0d:3d:6b:b2:\n
a9:a1:56:5d:8a:20:c2:5d:b2:7f:01:ee:1f:5a:ee:\n
b7:ff:38:02:e6:bf:a8:ad:cc:3a:bd:18:6c:1b:b9:\n
c1:eb:d4:50:58:4a:49:fd:52:64:4b:a9:92:80:7b:\n
9d:95\n Exponent: 65537 (0x10001)\n
X509v3 extensions:\n X509v3 Basic Constraints: \n
CA:FALSE\n X509v3 Subject Key Identifier: \n
75:B4:09:04:09:5A:50:70:F6:15:E7:1F:D0:ED:26:7E:2A:7D:AF:7B\n
X509v3 Authority Key Identifier: \n
keyid:62:CC:B7:5A:72:BB:A0:7D:47:03:62:6B:6E:05:B0:FB:E6:1A:88:EE\n\n
Signature Algorithm: sha1WithRSAEncryption\n
4a:20:15:6d:70:09:6f:a6:7d:e7:8c:6a:26:77:e3:57:33:34:\n
b9:53:06:da:4e:76:3e:83:7c:79:c1:cf:aa:36:d9:05:c5:2f:\n
1f:81:44:ec:19:40:25:91:1f:cb:99:51:93:93:f1:6c:61:32:\n
0d:9e:a9:ce:e9:a7:30:43:a8:a8:7b:96:35:ea:e3:59:f9:df:\n
f1:f8:48:e0:7b:36:eb:c4:ae:c7:1d:13:aa:be:9a:79:c5:ba:\n
89:5d:bb:3c:4f:ea:73:c4:1f:96:e1:c8:19:f4:1e:06:50:cb:\n
75:dd:ed:95:d6:02:1d:08:2b:73:82:24:68:7a:c6:91:f8:06:\n
58:f5:f9:ff:6c:7b:40:8a:0c:f9:11:e9:a2:d7:46:bb:f8:74:\n
78:29:46:aa:c2:86:10:7c:48:7f:90:57:82:85:a2:f5:53:25:\n
97:c5:4a:83:10:db:22:d8:9a:c4:7c:a3:bc:3d:9d:f0:d0:9f:\n
fd:d5:4c:e4:74:3b:74:9c:73:f1:74:0b:b9:1a:31:a5:17:b1:\n
4b:fa:94:ee:f0:f4:34:0f:40:56:b7:6a:69:96:b7:8a:83:5e:\n
11:00:22:06:c1:3b:82:25:cd:1b:4b:88:0d:34:f8:af:2d:7b:\n
27:4d:74:ea:ee:6a:25:dc:1d:64:a1:5d:75:1f:4c:8f:f5:76:\n
6d:af:cd:06\n
-BEGIN CERTIFICATE-\n
MIIDZjCCAk6gAwIBAgIBATANBgkqhkiG9w0BAQUFADBXMQswCQYDVQQGEwJVUzEO\n
MAwGA1UECAwFVW5zZXQxDjAMBgNVBAcMBVVuc2V0MQ4wDAYDVQQKDAVVbnNldDEY\n
MBYGA1UEAwwPd3d3LmV4YW1wbGUuY29tMB4XDTE0MDQxNzA2NTgwOFoXDTI0MDQx\n
NDA2NTgwOFowRzELMAkGA1UEBhMCVVMxDjAMBgNVBAgMBVVuc2V0MQ4wDAYDVQQK\n
DAVVbnNldDEYMBYGA1UEAwwPd3d3LmV4YW1wbGUuY29tMIIBIjANBgkqhkiG9w0B\n
AQEFAAOCAQ8AMIIBCgKCAQEA2/KNMxCjt1rJblihySuJ8tItiKdzpNpIPitXLplR\n
qHMmXKBUMh+tNYpaZSsiExifZqwJCzFgIYAvr14DfuBmjZ24LoeCynTutZJM2PXJ\n
M8He/inHLqx9EI5XJyc2snDV1eC+f7Zor+WoF5QlPoBpyK1yyc61Otlx8/1FUC6P\n
wkNlNJgD7hRggjD3FIUty1zUklXmgR6fk98+3DutDVSE4Uggc0JjwFROe+PzcJfy\n
1qwuM8hP0Z3vpTbF0AsZ0l8/CIj1v0RXiMIjh7ZCfg09a7KpoVZdiiDCXbJ/Ae4f\n
Wu63/zgC5r+orcw6vRhsG7nB69RQWEpJ/VJkS6mSgHudlQIDAQABo00wSzAJBgNV\n
HRMEAjAAMB0GA1UdDgQWBBR1tAkECVpQcPYV5x/Q7SZ+Kn2vezAfBgNVHSMEGDAW\n
gBRizLdacrugfUcDYmtuBbD75hqI7jANBgkqhkiG9w0BAQUFAAOCAQEASiAVbXAJ\n
b6Z954xqJnfjVzM0uVMG2k52PoN8ecHPqjbZBcUvH4FE7BlAJZEfy5lRk5PxbGEy\n
DZ6pzumnMEOoqHuWNerjWfnf8fhI4Hs268Suxx0Tqr6aecW6iV27PE/qc8QfluHI\n
GfQeBlDLdd3tldYCHQgrc4IkaHrGkfgGWPX5/2x7QIoM+RHpotdGu/h0eClGqsKG\n
EHxIf5BXgoWi9VMll8VKgxDbItiaxHyjvD2d8NCf/dVM5HQ7dJxz8XQLuRoxpRex\n
S/qU7vD0NA9AVrdqaZa3ioNeEQAiBsE7giXNG0uIDTT4ry17J0106u5qJdwdZKFd\n
dR9Mj/V2ba/NBg=
[Yahoo-eng-team] [Bug 1311561] [NEW] editing a flavor changes it's ID
Public bug reported: try to edit a flavor in Horizon(in CLI we can only edit extra_spec field for a flavor, so in CLI "nova flavor-key " doesn't reproduce the bug). So open edit flavor dialog for any of them, change VCPUs or anything else, push "save" button => ID of the flavor will also change. m1.tiny had id=1, after the change it becomes the uuid and every next edit will change the ID field value... # nova flavor-list +--+---+---+--+---+--+---+-+---+ | ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | +--+---+---+--+---+--+---+-+---+ | 036c428f-3562-4a29-a690-56ed79c57742 | test2 | 50| 60 | 0 | | 4 | 1.0 | True | | 4| m1.large | 8192 | 80 | 0 | | 4 | 1.0 | True | | 5| m1.xlarge | 16384 | 160 | 0 | | 8 | 1.0 | True | | b16fc3d9-7dbf-494d-af06-53bf04b28494 | m1.tiny | 2048 | 10 | 0 | | 1 | 1.0 | True | | e0c68f91-c016-47be-871d-09a23c369115 | m1.medium | 4096 | 40 | 0 | 1024 | 2 | 1.0 | True | +--+---+---+--+---+--+---+-+---+ ** 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/1311561 Title: editing a flavor changes it's ID Status in OpenStack Dashboard (Horizon): New Bug description: try to edit a flavor in Horizon(in CLI we can only edit extra_spec field for a flavor, so in CLI "nova flavor-key " doesn't reproduce the bug). So open edit flavor dialog for any of them, change VCPUs or anything else, push "save" button => ID of the flavor will also change. m1.tiny had id=1, after the change it becomes the uuid and every next edit will change the ID field value... # nova flavor-list +--+---+---+--+---+--+---+-+---+ | ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | +--+---+---+--+---+--+---+-+---+ | 036c428f-3562-4a29-a690-56ed79c57742 | test2 | 50| 60 | 0 | | 4 | 1.0 | True | | 4| m1.large | 8192 | 80 | 0 | | 4 | 1.0 | True | | 5| m1.xlarge | 16384 | 160 | 0 | | 8 | 1.0 | True | | b16fc3d9-7dbf-494d-af06-53bf04b28494 | m1.tiny | 2048 | 10 | 0 | | 1 | 1.0 | True | | e0c68f91-c016-47be-871d-09a23c369115 | m1.medium | 4096 | 40 | 0 | 1024 | 2 | 1.0 | True | +--+---+---+--+---+--+---+-+---+ To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1311561/+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 1311500] [NEW] Nova 'os-security-group-default-rules' API does not work with neutron
Public bug reported: Nova APIs 'os-security-group-default-rules' does not work if 'conf->security_group_api' is 'neutron'. I wrote the test cases for above Nova APIs (https://review.openstack.org/#/c/87924) and it fails in gate neutron tests. I further investigated this issue and found that in 'nova/api/openstack/compute/contrib/security_group_default_rules.py', 'security_group_api' is set according to 'conf->security_group_api' (https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/contrib/security_group_default_rules.py#L107). If 'conf->security_group_api' is 'nova' then, 'NativeNovaSecurityGroupAPI(NativeSecurityGroupExceptions, compute_api.SecurityGroupAPI)' is being used in this API and no issue here. It works fine. If 'conf->security_group_api' is 'neutron' then, 'NativeNeutronSecurityGroupAPI(NativeSecurityGroupExceptions, neutron_driver.SecurityGroupAPI)' is being used in this API and 'neutron_driver.SecurityGroupAPI' (https://github.com/openstack/nova/blob/master/nova/network/security_group/neutron_driver.py#L48) does not have any of the function which are being called from this API class. So gives AttributeError (http://logs.openstack.org/24/87924/2/check/check-tempest-dsvm-neutron- full/7951abf/logs/screen-n-api.txt.gz). Traceback - . . 2014-04-21 00:44:22.430 10186 TRACE nova.api.openstack File "/opt/stack/new/nova/nova/api/openstack/compute/contrib/security_group_default_rules.py", line 130, in create 2014-04-21 00:44:22.430 10186 TRACE nova.api.openstack if self.security_group_api.default_rule_exists(context, values): 2014-04-21 00:44:22.430 10186 TRACE nova.api.openstack AttributeError: 'NativeNeutronSecurityGroupAPI' object has no attribute 'default_rule_exists' I think this API is only for Nova-network. If so then this API should always use the nova network security group driver (https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/contrib/security_groups.py#L669). ** Affects: nova Importance: Undecided Assignee: Ghanshyam (ghanshyammann) Status: New ** Tags: api network ** Changed in: nova Assignee: (unassigned) => Ghanshyam (ghanshyammann) -- 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/1311500 Title: Nova 'os-security-group-default-rules' API does not work with neutron Status in OpenStack Compute (Nova): New Bug description: Nova APIs 'os-security-group-default-rules' does not work if 'conf->security_group_api' is 'neutron'. I wrote the test cases for above Nova APIs (https://review.openstack.org/#/c/87924) and it fails in gate neutron tests. I further investigated this issue and found that in 'nova/api/openstack/compute/contrib/security_group_default_rules.py', 'security_group_api' is set according to 'conf->security_group_api' (https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/contrib/security_group_default_rules.py#L107). If 'conf->security_group_api' is 'nova' then, 'NativeNovaSecurityGroupAPI(NativeSecurityGroupExceptions, compute_api.SecurityGroupAPI)' is being used in this API and no issue here. It works fine. If 'conf->security_group_api' is 'neutron' then, 'NativeNeutronSecurityGroupAPI(NativeSecurityGroupExceptions, neutron_driver.SecurityGroupAPI)' is being used in this API and 'neutron_driver.SecurityGroupAPI' (https://github.com/openstack/nova/blob/master/nova/network/security_group/neutron_driver.py#L48) does not have any of the function which are being called from this API class. So gives AttributeError (http://logs.openstack.org/24/87924/2/check/check-tempest-dsvm- neutron-full/7951abf/logs/screen-n-api.txt.gz). Traceback - . . 2014-04-21 00:44:22.430 10186 TRACE nova.api.openstack File "/opt/stack/new/nova/nova/api/openstack/compute/contrib/security_group_default_rules.py", line 130, in create 2014-04-21 00:44:22.430 10186 TRACE nova.api.openstack if self.security_group_api.default_rule_exists(context, values): 2014-04-21 00:44:22.430 10186 TRACE nova.api.openstack AttributeError: 'NativeNeutronSecurityGroupAPI' object has no attribute 'default_rule_exists' I think this API is only for Nova-network. If so then this API should always use the nova network security group driver (https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/contrib/security_groups.py#L669). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1311500/+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
