[Yahoo-eng-team] [Bug 1520775] [NEW] Update the gateway of external net won't affect router
Public bug reported: I found this one when build up a test env. Steps to reproduce: 1) I create a set of external network, internal network and router. The external network has gateway ip in its subnet. 2) connect the external, internal network and router, by using router-gateway-set, router-interface-add. 3) Then I realize my physical network doesn't have a gateway. So I update the subnet of external network with --no-gateway. 4) I can't see the default route be deleted in router namespace, even if I restart l3-agent. Then I try another way: a) The same as 1), except that the subnet of external network don't have gateway ip when creation. b) The same as 2) c) I update the subnet of external network with --gateway-ip AA:BB:CC:DD . d) I can't see the default route be added to router namespace, until I restart l3-agent. I try it in legacy router and DVR, they both have this problem, and I believe HA router will have this problem. ** Affects: neutron Importance: Undecided Assignee: Hong Hui Xiao (xiaohhui) Status: New ** Changed in: neutron Assignee: (unassigned) => Hong Hui Xiao (xiaohhui) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1520775 Title: Update the gateway of external net won't affect router Status in neutron: New Bug description: I found this one when build up a test env. Steps to reproduce: 1) I create a set of external network, internal network and router. The external network has gateway ip in its subnet. 2) connect the external, internal network and router, by using router-gateway-set, router-interface-add. 3) Then I realize my physical network doesn't have a gateway. So I update the subnet of external network with --no-gateway. 4) I can't see the default route be deleted in router namespace, even if I restart l3-agent. Then I try another way: a) The same as 1), except that the subnet of external network don't have gateway ip when creation. b) The same as 2) c) I update the subnet of external network with --gateway-ip AA:BB:CC:DD . d) I can't see the default route be added to router namespace, until I restart l3-agent. I try it in legacy router and DVR, they both have this problem, and I believe HA router will have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1520775/+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 1520737] Re: User creation is allowed with empty password
*** This bug is a duplicate of bug 1391116 *** https://bugs.launchpad.net/bugs/1391116 ** This bug has been marked a duplicate of bug 1391116 password prompts should check for empty string -- 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/1520737 Title: User creation is allowed with empty password Status in OpenStack Identity (keystone): New Bug description: While creating user using keystone command with password option, it does not check if user entered any character for password or not. steps: $ keystone user-create --name testing --pass New Password: Repeat New Password: +--+--+ | Property | Value | +--+--+ | email | | | enabled | True | |id| 47aa13b9c9354f42be3d92a882f39667 | | name | testing | | username | testing | +--+--+ In 'New Password' press enter without typing any character and same for 'Repeat New Password' then execute any command using the this user credentials and it will prompt for password, but password is empty so you can not execute any command. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1520737/+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 1520850] [NEW] testcase fail due to value is not match
You have been subscribed to a public bug: The testcase fail occasionally, since the value got from DB or cache is not always match with the sequence of when the value is created. File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 'db0c40558d7e4125a3f68b3b8bfb9720' != u'526844a9f6f747ffaa422ce48795fbc5' ** Affects: keystone Importance: Undecided Status: Invalid -- testcase fail due to value is not match https://bugs.launchpad.net/bugs/1520850 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). -- 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 1520850] [NEW] testcase fail due to value is not match
Public bug reported: The testcase fail occasionally, since the value got from DB or cache is not always match with the sequence of when the value is created. File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 'db0c40558d7e4125a3f68b3b8bfb9720' != u'526844a9f6f747ffaa422ce48795fbc5' ** Affects: keystone Importance: Undecided Status: New ** Changed in: python-openstackclient Status: New => Invalid ** Project changed: python-openstackclient => keystone ** Changed in: keystone Status: Invalid => New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1520850 Title: testcase fail due to value is not match Status in OpenStack Identity (keystone): New Bug description: The testcase fail occasionally, since the value got from DB or cache is not always match with the sequence of when the value is created. File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 435, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 'db0c40558d7e4125a3f68b3b8bfb9720' != u'526844a9f6f747ffaa422ce48795fbc5' To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1520850/+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 1193972] Re: To set mac address needs the link is down
[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/1193972 Title: To set mac address needs the link is down Status in neutron: Expired Bug description: `Command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ip', 'link', 'set', 'tap12968d5 a-ba', 'address', 'fa:16:3e:3f:c2:0c'] Exit code: 2 Stdout: '' Stderr: 'RTNETLINK answers: Device or resource busy\n'` The workaround above can be done within the code as: --- /usr/lib/python2.6/site-packages/quantum/agent/linux/interface.py +++ /usr/lib/python2.6/site-packages/quantum/agent/linux/interface.py @@ -174,7 +174,9 @@ internal=internal) ns_dev = ip.device(device_name) + ns_dev.link.set_down() ns_dev.link.set_address(mac_address) + ns_dev.link.set_up() if self.conf.network_device_mtu: ns_dev.link.set_mtu(self.conf.network_device_mtu) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1193972/+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 1369751] Re: Cannot enable both syslog and regular log for neutron-ns-metadata-proxy
[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/1369751
Title:
Cannot enable both syslog and regular log for neutron-ns-metadata-
proxy
Status in neutron:
Expired
Bug description:
The current implementation of neutron won't allow to enable both
syslog and regular log for neutron-ns-metadata-proxy.
In current implemention, that's how neutron/agent/dhcp_agent.py
sprawns the neutron-ns-metadata-proxy process.
def callback(pid_file):
metadata_proxy_socket = cfg.CONF.metadata_proxy_socket
proxy_cmd = ['neutron-ns-metadata-proxy',
'--pid_file=%s' % pid_file,
'--metadata_proxy_socket=%s' % metadata_proxy_socket,
neutron_lookup_param,
'--state_path=%s' % self.conf.state_path,
'--metadata_port=%d' % dhcp.METADATA_PORT]
proxy_cmd.extend(config.get_log_args(
cfg.CONF, 'neutron-ns-metadata-proxy-%s.log' % network.id))
return proxy_cmd
However, for the config.get_log_args() in
neutron/agent/common/config.py
def get_log_args(conf, log_file_name):
cmd_args = []
if conf.debug:
cmd_args.append('--debug')
if conf.verbose:
cmd_args.append('--verbose')
if (conf.log_dir or conf.log_file):
cmd_args.append('--log-file=%s' % log_file_name)
log_dir = None
if conf.log_dir and conf.log_file:
log_dir = os.path.dirname(
os.path.join(conf.log_dir, conf.log_file))
elif conf.log_dir:
log_dir = conf.log_dir
elif conf.log_file:
log_dir = os.path.dirname(conf.log_file)
if log_dir:
cmd_args.append('--log-dir=%s' % log_dir)
else:
if conf.use_syslog:
cmd_args.append('--use-syslog')
if conf.syslog_log_facility:
cmd_args.append(
'--syslog-log-facility=%s' % conf.syslog_log_facility)
return cmd_args
It only allows one of the options.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1369751/+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 1042045] Re: L3: make l3-agent handle changes to router port
[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/1042045 Title: L3: make l3-agent handle changes to router port Status in neutron: Expired Bug description: currently, the tenant could choose to change the mac address, or even the IP address of a port that is being used as a router port. however, the l3-agent will not detect this change or update its behavior without a restart. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1042045/+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 1244820] Re: Moving a router between l3 agents works but reports an error
[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/1244820
Title:
Moving a router between l3 agents works but reports an error
Status in neutron:
Expired
Bug description:
Using Havana on precise moving a router between l3 agents works but
reports an error:
$ quantum l3-agent-list-hosting-router f0fb41d3-f820-489d-b1de-7b00c665ebc8
+--+-++---+
| id | host| admin_state_up | alive |
+--+-++---+
| f9910cc4-2a4d-4a6b-9d12-5a8235c5108f | antaeus | True | :-) |
+--+-++---+
$ quantum l3-agent-router-remove f9910cc4-2a4d-4a6b-9d12-5a8235c5108f
f0fb41d3-f820-489d-b1de-7b00c665ebc8
Removed Router f0fb41d3-f820-489d-b1de-7b00c665ebc8 to L3 agent
$ quantum l3-agent-list-hosting-router f0fb41d3-f820-489d-b1de-
7b00c665ebc8
$ quantum l3-agent-router-add 2c53a9cd-4aba-409e-830b-1f76cc0d8bb7
f0fb41d3-f820-489d-b1de-7b00c665ebc8
409-{u'NeutronError': {u'message': u'The router
f0fb41d3-f820-489d-b1de-7b00c665ebc8 has been already hosted by the L3 Agent
2c53a9cd-4aba-409e-830b-1f76cc0d8bb7.', u'type': u'RouterHostedByL3Agent',
u'detail': u''}}
$ quantum l3-agent-list-hosting-router f0fb41d3-f820-489d-b1de-7b00c665ebc8
+--+---++---+
| id | host | admin_state_up | alive |
+--+---++---+
| 2c53a9cd-4aba-409e-830b-1f76cc0d8bb7 | dabih | True | :-) |
+--+---++---+
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1244820/+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 1349239] Re: ovs vlan tag is not reconfigured after system reboot.
[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/1349239
Title:
ovs vlan tag is not reconfigured after system reboot.
Status in neutron:
Expired
Bug description:
After install system, interfaces are configured with VLAN tag 1.
[root@cnode37-m ~(keystone_admin)]# ovs-vsctl show
aa5f627f-0180-4971-b423-33268cbcb070
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Port "qg-2132c88c-dd"
Interface "qg-2132c88c-dd"
type: internal
Bridge br-tun
Port br-tun
Interface br-tun
type: internal
Bridge br-int
Port "tap90fd0463-7a"
tag: 1
Interface "tap90fd0463-7a"
type: internal
Port br-int
Interface br-int
type: internal
Port "qr-c5c0a71f-30"
tag: 1
Interface "qr-c5c0a71f-30"
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
ovs_version: "1.11.0"
But after rebooting the system, neutron does not properly reconfigure
vlan tags.
[root@cnode37-m ~(keystone_admin)]# ovs-vsctl show
aa5f627f-0180-4971-b423-33268cbcb070
Bridge br-tun
Port br-tun
Interface br-tun
type: internal
Bridge br-ex
Port "qg-2132c88c-dd"
Interface "qg-2132c88c-dd"
type: internal
Port br-ex
Interface br-ex
type: internal
Bridge br-int
Port "qr-c5c0a71f-30"
Interface "qr-c5c0a71f-30"
type: internal
Port br-int
Interface br-int
type: internal
Port "tap90fd0463-7a"
Interface "tap90fd0463-7a"
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
ovs_version: "1.11.0"
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1349239/+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 1261194] Re: The wsgi server should support tcp_keepalive
[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/1261194 Title: The wsgi server should support tcp_keepalive Status in neutron: Expired Bug description: This will be useful in deployments with a load balancer To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1261194/+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 1198799] Re: Neutron add_router_interface Error, SELECT FOR UPDATE/SHARE cannot be applied to the nullable side of an outer join
[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/1198799 Title: Neutron add_router_interface Error, SELECT FOR UPDATE/SHARE cannot be applied to the nullable side of an outer join Status in neutron: Expired Bug description: 2013-07-08 12:30:46.514 23374 ERROR quantum.api.v2.resource [-] add_router_interface failed 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource Traceback (most recent call last): 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/home/trystack/quantum/quantum/api/v2/resource.py", line 82, in resource 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource result = method(request=request, **args) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/home/trystack/quantum/quantum/api/v2/base.py", line 184, in _handle_action 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource return getattr(self._plugin, name)(*arg_list, **kwargs) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/home/trystack/quantum/quantum/db/l3_db.py", line 382, in add_router_interface 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource 'name': ''}}) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/home/trystack/quantum/quantum/plugins/openvswitch/ovs_quantum_plugin.py", line 522, in create_port 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource port = super(OVSQuantumPluginV2, self).create_port(context, port) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/home/trystack/quantum/quantum/db/db_base_plugin_v2.py", line 1344, in create_port 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource ips = self._allocate_ips_for_port(context, network, port) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/home/trystack/quantum/quantum/db/db_base_plugin_v2.py", line 723, in _allocate_ips_for_port 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource ips = self._allocate_fixed_ips(context, network, configured_ips) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/home/trystack/quantum/quantum/db/db_base_plugin_v2.py", line 658, in _allocate_fixed_ips 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource context, fixed['subnet_id'], fixed['ip_address']) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/home/trystack/quantum/quantum/db/db_base_plugin_v2.py", line 511, in _allocate_specific_ip 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource for (range, pool) in results: 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2227, in __iter__ 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource return self._execute_and_instances(context) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2242, in _execute_and_instances 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource result = conn.execute(querycontext.statement, self._params) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1449, in execute 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource params) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1584, in _execute_clauseelement 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource compiled_sql, distilled_params 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1698, in _execute_context 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource context) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1691, in _execute_context 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource context) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 331, in do_execute 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource cursor.execute(statement, parameters) 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource NotSupportedError: (NotSupportedError) SELECT FOR UPDATE/SHARE cannot be applied to the nullable side of an outer join 2013-07-08 12:30:46.514 23374 TRACE quantum.api.v2.resource 'SELECT ipavailabilityranges.allocation_pool_id AS
[Yahoo-eng-team] [Bug 1136064] Re: quantum server consumes all of sqlalchemy sessions
[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/1136064
Title:
quantum server consumes all of sqlalchemy sessions
Status in neutron:
Expired
Bug description:
2013-03-01 01:19:44.356 17363 DEBUG quantum.openstack.common.rpc.amqp [-]
unpacked context: {'user_id': None, 'roles': [u'admin'], 'tenant_id': None,
'is_admin': True, 'timestamp': u'2013-02-28 17:19:35.268564', 'project_id':
None, 'read_deleted': u'no'} _safe_log
/mnt/data/git/quantum/quantum/openstack/common/rpc/common.py:254
2013-03-01 01:19:44.450 17363 DEBUG quantum.db.dhcp_rpc_base [-] Network list
requested from HostC get_active_networks
/mnt/data/git/quantum/quantum/db/dhcp_rpc_base.py:35
2013-03-01 01:19:44.454 17363 DEBUG quantum.scheduler.dhcp_agent_scheduler
[-] No non-hosted networks auto_schedule_networks
/mnt/data/git/quantum/quantum/scheduler/dhcp_agent_scheduler.py:101
2013-03-01 01:19:44.491 17363 DEBUG quantum.plugins.openvswitch.ovs_db_v2 [-]
get_port_with_securitygroups()
called:port_id=ce9af4bb-970c-4869-81fd-1dd70d754cba get_port_from_device
/mnt/data/git/quantum/quantum/plugins/openvswitch/ovs_db_v2.py:309
2013-03-01 01:20:14.914 17363 ERROR quantum.openstack.common.rpc.amqp [-]
Exception during message handling
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
Traceback (most recent call last):
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/mnt/data/git/quantum/quantum/openstack/common/rpc/amqp.py", line 429, in
_process_data
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
rval = self.proxy.dispatch(ctxt, version, method, **args)
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/mnt/data/git/quantum/quantum/common/rpc.py", line 43, in dispatch
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
quantum_ctxt, version, method, **kwargs)
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/mnt/data/git/quantum/quantum/openstack/common/rpc/dispatcher.py", line 133,
in dispatch
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
return getattr(proxyobj, method)(ctxt, **kwargs)
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/mnt/data/git/quantum/quantum/db/agents_db.py", line 167, in report_state
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
plugin.create_or_update_agent(context, agent_state)
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/mnt/data/git/quantum/quantum/db/agents_db.py", line 145, in
create_or_update_agent
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
context, agent['agent_type'], agent['host'])
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/mnt/data/git/quantum/quantum/db/agents_db.py", line 121, in
_get_agent_by_type_and_host
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
Agent.host == host).one()
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2184, in
one
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp ret
= list(self)
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2227, in
__iter__
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
return self._execute_and_instances(context)
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2240, in
_execute_and_instances
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
close_with_result=True)
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2231, in
_connection_from_session
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
**kw)
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 777,
in connection
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
close_with_result=close_with_result)
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 781,
in _connection_for_bind
2013-03-01 01:20:14.914 17363 TRACE quantum.openstack.common.rpc.amqp
return
[Yahoo-eng-team] [Bug 1161426] Re: netns_cleanup: stale ovs port ramains with use_ovs_veth=True
[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/1161426 Title: netns_cleanup: stale ovs port ramains with use_ovs_veth=True Status in neutron: Expired Bug description: After netns_cleanup is used, stale ovs port remains https://review.openstack.org/#/c/21496/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1161426/+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
