[Yahoo-eng-team] [Bug 1398417] [NEW] Redundant methods in DB heal script after alembic 0.7.1
Public bug reported: Methods add_fk and remove_fk were needed in the heal script as they weren't provided by alembic. Now that we have them in alembic 0.7.1 they can be removed from the heal script. ** Affects: neutron Importance: Undecided Status: New ** Tags: db ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1398417 Title: Redundant methods in DB heal script after alembic 0.7.1 Status in OpenStack Neutron (virtual network service): New Bug description: Methods add_fk and remove_fk were needed in the heal script as they weren't provided by alembic. Now that we have them in alembic 0.7.1 they can be removed from the heal script. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1398417/+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 1398422] [NEW] Hard-coded alembic methods in DB heal script is inflexible
Public bug reported: See http://lists.openstack.org/pipermail/openstack- dev/2014-December/051897.html Also see review comments in https://review.openstack.org/137989 ** Affects: neutron Importance: Undecided Assignee: Ann Kamyshnikova (akamyshnikova) Status: New ** Tags: db ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1398422 Title: Hard-coded alembic methods in DB heal script is inflexible Status in OpenStack Neutron (virtual network service): New Bug description: See http://lists.openstack.org/pipermail/openstack- dev/2014-December/051897.html Also see review comments in https://review.openstack.org/137989 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1398422/+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 1404093] [NEW] Use of *OpportunisticTestCase causes functional tests to skip on db error
Public bug reported: Tests using oslo.db.sqlalchemy.test_base.DbFixture will skip if the database cannot be provisioned. In the neutron functional job we do not want to skip tests. The tests should fail if the environment is not set up correctly for the tests. After https://review.openstack.org/126175 is merged we should see to it that the migrations tests do not skip. ** Affects: neutron Importance: Undecided Status: New ** Description changed: Tests using oslo.db.sqlalchemy.test_base.DbFixture will skip if the database cannot be provisioned. In the neutron functional job we do not want to skip tests. The tests should fail if the environment is not set up correctly for the tests. + + After https://review.openstack.org/126175 is merged we should see to it + that the migrations tests do not skip. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1404093 Title: Use of *OpportunisticTestCase causes functional tests to skip on db error Status in OpenStack Neutron (virtual network service): New Bug description: Tests using oslo.db.sqlalchemy.test_base.DbFixture will skip if the database cannot be provisioned. In the neutron functional job we do not want to skip tests. The tests should fail if the environment is not set up correctly for the tests. After https://review.openstack.org/126175 is merged we should see to it that the migrations tests do not skip. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1404093/+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 1416713] Re: Decompose the NCS ML2 driver
** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1416713 Title: Decompose the NCS ML2 driver Status in Cisco Vendor Code for OpenStack Neutron: New Status in OpenStack Neutron (virtual network service): New Bug description: Decompose the NCS mechanism driver in Neutron. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1416713/+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 1426473] [NEW] Improve notification robustness related to ipv6 auto-addressing
Public bug reported: This is related to gate bug: https://bugs.launchpad.net/neutron/+bug/1426397 Although tempest will need to allow for a delay in the assignment of ipv6 auto-addresses to guests, on the neutron side we should do all we can to make sure that everything has been set up to allow the address assignment to be completed by the protocol, before notifying (nova) of completion. Some things to verify: - radvd running in router namespace - radvd configured correctly for interface - router port added for guest's network - [more things to be added here] ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Tags: ipv6 ** Tags added: ipv6 ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Description changed: This is related to gate bug: https://bugs.launchpad.net/neutron/+bug/1426397 Although tempest will need to allow for a delay in the assignment of ipv6 auto-addresses to guests, on the neutron side we should do all we can to make sure that everything has been set up to allow the address assignment to be completed by the protocol, before notifying (nova) of completion. Some things to verify: - - radvd running in router namespace - - radvd configured correctly for interface - - [more things to be added here] + - radvd running in router namespace + - radvd configured correctly for interface + - router port added for guest's network + - [more things to be added here] -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1426473 Title: Improve notification robustness related to ipv6 auto-addressing Status in OpenStack Neutron (virtual network service): New Bug description: This is related to gate bug: https://bugs.launchpad.net/neutron/+bug/1426397 Although tempest will need to allow for a delay in the assignment of ipv6 auto-addresses to guests, on the neutron side we should do all we can to make sure that everything has been set up to allow the address assignment to be completed by the protocol, before notifying (nova) of completion. Some things to verify: - radvd running in router namespace - radvd configured correctly for interface - router port added for guest's network - [more things to be added here] To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1426473/+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 1426397] Re: tempest.scenario.test_network_v6.TestGettingAddress.test_slaac_from_os intermittently fails with MismatchError
** Also affects: tempest Importance: Undecided Status: New ** Changed in: tempest Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1426397 Title: tempest.scenario.test_network_v6.TestGettingAddress.test_slaac_from_os intermittently fails with MismatchError Status in OpenStack Neutron (virtual network service): New Status in Tempest: New Bug description: http://logs.openstack.org/63/155863/1/gate/gate-tempest-dsvm-neutron- full/7d13276/console.html#_2015-02-26_20_24_10_382 2015-02-26 20:24:10.382 | tempest.scenario.test_network_v6.TestGettingAddress.test_slaac_from_os[compute,network] 2015-02-26 20:24:10.382 | --- 2015-02-26 20:24:10.382 | 2015-02-26 20:24:10.382 | Captured traceback: 2015-02-26 20:24:10.383 | ~~~ 2015-02-26 20:24:10.383 | Traceback (most recent call last): 2015-02-26 20:24:10.383 | File "tempest/test.py", line 109, in wrapper 2015-02-26 20:24:10.383 | return f(self, *func_args, **func_kwargs) 2015-02-26 20:24:10.383 | File "tempest/scenario/test_network_v6.py", line 147, in test_slaac_from_os 2015-02-26 20:24:10.383 | self._prepare_and_test(address6_mode='slaac') 2015-02-26 20:24:10.383 | File "tempest/scenario/test_network_v6.py", line 128, in _prepare_and_test 2015-02-26 20:24:10.383 | self.assertIn(srv2['accessIPv6'], result) 2015-02-26 20:24:10.383 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/testtools/testcase.py", line 354, in assertIn 2015-02-26 20:24:10.383 | self.assertThat(haystack, Contains(needle), message) 2015-02-26 20:24:10.383 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/testtools/testcase.py", line 433, in assertThat 2015-02-26 20:24:10.384 | raise mismatch_error 2015-02-26 20:24:10.384 | MismatchError: u'2003::f816:3eff:fec2:f2a4' not in '1: lo: mtu 16436 qdisc noqueue \nlink/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\ninet 127.0.0.1/8 scope host lo\n inet6 ::1/128 scope host \n valid_lft forever preferred_lft forever\n2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000\n link/ether fa:16:3e:c2:f2:a4 brd ff:ff:ff:ff:ff:ff\ninet 10.100.0.4/28 brd 10.100.0.15 scope global eth0\ninet6 fe80::f816:3eff:fec2:f2a4/64 scope link \n valid_lft forever preferred_lft forever\n' 2015-02-26 20:24:10.384 | Traceback (most recent call last): 2015-02-26 20:24:10.384 | _StringException: Empty attachments: 2015-02-26 20:24:10.384 | stderr 2015-02-26 20:24:10.384 | stdout Looks like this started around 2/25: http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiTWlzbWF0Y2hFcnJvclwiIEFORCBtZXNzYWdlOlwiOjpcIiBBTkQgbWVzc2FnZTpcIm5vdCBpblwiIEFORCBtZXNzYWdlOlwiaW5ldDZcIiBBTkQgbWVzc2FnZTpcInNjb3BlIGxpbmtcIiBBTkQgbWVzc2FnZTpcInZhbGlkX2xmdCBmb3JldmVyIHByZWZlcnJlZF9sZnQgZm9yZXZlclwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDI1MDQ4MDgyOTk3fQ== To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1426397/+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 1204456] Re: neutron ml2 plugin test failures
Works without the -N option:
$ ./run_tests.sh neutron.tests.unit.ml2.test_agent_scheduler
Also works with tox (version 1.6.1):
$ tox -e py27 -- neutron.tests.unit.ml2.test_agent_scheduler
The above two methods use a virtualenv to run the tests in. The -N
option to run_tests.sh tells it to not use a virtualenv and run the unit
tests in the system environment. If the system environment does not
satisfy the test-requirements correctly or has some settings that
interfere, then the tests may not work.
The recommended way of running unit tests is in a virtualenv. If someone
wants to run tests in their system environment it is up to them to
adjust their environment appropriately.
** 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/1204456
Title:
neutron ml2 plugin test failures
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
./run_tests.sh -N neutron.tests.unit.ml2.test_agent_scheduler
Running ` python setup.py testr --slowest --testr-args='--subunit
neutron.tests.unit.ml2.test_agent_scheduler'`
running testr
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 ${PYTHON:-python} -m
subunit.run discover -t ./ neutron/tests/unit --list
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 ${PYTHON:-python} -m
subunit.run discover -t ./ neutron/tests/unit --load-list /tmp/tmpYUaXvW
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 ${PYTHON:-python} -m
subunit.run discover -t ./ neutron/tests/unit --load-list /tmp/tmp1h3tWw
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 ${PYTHON:-python} -m
subunit.run discover -t ./ neutron/tests/unit --load-list /tmp/tmpsYVCGc
running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 ${PYTHON:-python} -m
subunit.run discover -t ./ neutron/tests/unit --load-list /tmp/tmpZS9P2j
process-returncode
process-returncode ... FAIL
process-returncode
process-returncode ... FAIL
process-returncode
process-returncode ... FAIL
process-returncode
process-returncode ... FAIL
math domain error
Slowest Tests
neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_auto_schedule_with_disabled
neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_auto_schedule_with_disabled
... FAIL
neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_scheduler_with_hosted_network
neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_scheduler_with_hosted_network
... FAIL
neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_auto_schedule_with_hosted
neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_auto_schedule_with_hosted
... FAIL
neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_add_to_dhcp_agent
neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_add_to_dhcp_agent
... FAIL
==
FAIL: process-returncode
process-returncode
--
testtools.testresult.real._StringException: Binary content:
traceback (test/plain; charset="utf8")
==
FAIL: process-returncode
process-returncode
--
testtools.testresult.real._StringException: Binary content:
traceback (test/plain; charset="utf8")
==
FAIL: process-returncode
process-returncode
--
testtools.testresult.real._StringException: Binary content:
traceback (test/plain; charset="utf8")
==
FAIL: process-returncode
process-returncode
--
testtools.testresult.real._StringException: Binary content:
traceback (test/plain; charset="utf8")
==
FAIL:
neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_auto_schedule_with_disabled
neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_auto_schedule_with_disabled
--
testtools.testresult.real._StringException
==
FAIL:
neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_scheduler_with_hosted_network
neutron.tests.unit.ml2.test_agent_scheduler.
[Yahoo-eng-team] [Bug 1334922] [NEW] agent functional tests reference incorrect MAX_LEN constant
Public bug reported: File "neutron/neutron/tests/functional/agent/linux/base.py", line 59, in create_resource name = self.get_rand_name(n_const.DEV_NAME_MAX_LEN, name_prefix) AttributeError: 'module' object has no attribute 'DEV_NAME_MAX_LEN' ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1334922 Title: agent functional tests reference incorrect MAX_LEN constant Status in OpenStack Neutron (virtual network service): New Bug description: File "neutron/neutron/tests/functional/agent/linux/base.py", line 59, in create_resource name = self.get_rand_name(n_const.DEV_NAME_MAX_LEN, name_prefix) AttributeError: 'module' object has no attribute 'DEV_NAME_MAX_LEN' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1334922/+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 1341144] [NEW] Wrong server_default value for multicast_ip_index in cisco_network_profiles table
Public bug reported: Change https://review.openstack.org/105411 introduced the following incorrect server_default value: multicast_ip_index = sa.Column(sa.Integer, default=0, server_default=sql.false()) in neutron/plugins/cisco/db/n1kv_models_v2.py for table cisco_network_profiles. ** 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/1341144 Title: Wrong server_default value for multicast_ip_index in cisco_network_profiles table Status in OpenStack Neutron (virtual network service): New Bug description: Change https://review.openstack.org/105411 introduced the following incorrect server_default value: multicast_ip_index = sa.Column(sa.Integer, default=0, server_default=sql.false()) in neutron/plugins/cisco/db/n1kv_models_v2.py for table cisco_network_profiles. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1341144/+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 1342756] [NEW] cisco_ml2_apic_contracts table needs to set nullable=False on tenant_id column
Public bug reported: In DB migrations the following is detected: INFO [alembic.autogenerate.compare] Detected NULL on column 'cisco_ml2_apic_contracts.tenant_id' ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Tags: cisco db ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Tags added: cisco db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1342756 Title: cisco_ml2_apic_contracts table needs to set nullable=False on tenant_id column Status in OpenStack Neutron (virtual network service): New Bug description: In DB migrations the following is detected: INFO [alembic.autogenerate.compare] Detected NULL on column 'cisco_ml2_apic_contracts.tenant_id' To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1342756/+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 1345341] [NEW] radvd needs functional tests
Public bug reported: See the review comments for https://review.openstack.org/102648 ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1345341 Title: radvd needs functional tests Status in OpenStack Neutron (virtual network service): New Bug description: See the review comments for https://review.openstack.org/102648 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1345341/+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 1346444] [NEW] DB migrations need unit tests
Public bug reported: Now that the DB healing https://review.openstack.org/96438 is merged, the DB migrations need unit tests. ** Affects: neutron Importance: Medium Assignee: Ann Kamyshnikova (akamyshnikova) Status: In Progress ** Tags: db ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1346444 Title: DB migrations need unit tests Status in OpenStack Neutron (virtual network service): In Progress Bug description: Now that the DB healing https://review.openstack.org/96438 is merged, the DB migrations need unit tests. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1346444/+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 1346638] [NEW] neutron-db-manage --autogenerate needs update after DB healing
Public bug reported: Now that the DB is healed, neutron-db-manage revision --autogenerate needs to be updated. The template should do unconditional upgrade/downgrade. The env.py should include all models from head to compare against the schema. ** Affects: neutron Importance: Undecided Status: New ** Tags: db ** Tags added: db ** Description changed: - Now that the DB is healed, neutrion-db-manage revision --autogenerate needs to be updated. + Now that the DB is healed, neutron-db-manage revision --autogenerate needs to be updated. The template should do unconditional upgrade/downgrade. The env.py should include all models from head to compare against the schema. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1346638 Title: neutron-db-manage --autogenerate needs update after DB healing Status in OpenStack Neutron (virtual network service): New Bug description: Now that the DB is healed, neutron-db-manage revision --autogenerate needs to be updated. The template should do unconditional upgrade/downgrade. The env.py should include all models from head to compare against the schema. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1346638/+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 1346658] [NEW] All DB model classes should be consolidated into one directory
Public bug reported: We have discussed moving all models out of their current diverse locations to one directory, like maybe neutron/db/models/*.py The idea is to move just the model classes (not the entire modules that they currently reside in) here. Then head.py would be able to from neutron.db.models import * # noqa and this would have much less baggage than importing all the current modules. The convention of putting all models in one directory will be quite easy to follow and maintain. ** Affects: neutron Importance: Undecided Status: New ** Tags: db ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1346658 Title: All DB model classes should be consolidated into one directory Status in OpenStack Neutron (virtual network service): New Bug description: We have discussed moving all models out of their current diverse locations to one directory, like maybe neutron/db/models/*.py The idea is to move just the model classes (not the entire modules that they currently reside in) here. Then head.py would be able to from neutron.db.models import * # noqa and this would have much less baggage than importing all the current modules. The convention of putting all models in one directory will be quite easy to follow and maintain. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1346658/+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 1277217] Re: Cisco plugin should use common network type consts
** Changed in: neutron Status: Confirmed => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1277217 Title: Cisco plugin should use common network type consts Status in OpenStack Neutron (virtual network service): Opinion Bug description: The Cisco plugin was not covered by 4cdccd69a45aec19d547c10f29f61359b69ad6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1277217/+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 1347361] [NEW] There should be a naming convention for neutron DB tables
Public bug reported: Now that the database is healed and all tables are present, the names of tables are haphazard and there is no convention for avoiding naming conflicts or having sensible grouping. A naming convention may look something like: __ Existing tables should be renamed to follow the convention. A README file explaining the convention should be created in the directory with the models. ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1347361 Title: There should be a naming convention for neutron DB tables Status in OpenStack Neutron (virtual network service): New Bug description: Now that the database is healed and all tables are present, the names of tables are haphazard and there is no convention for avoiding naming conflicts or having sensible grouping. A naming convention may look something like: __ Existing tables should be renamed to follow the convention. A README file explaining the convention should be created in the directory with the models. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1347361/+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 1350387] [NEW] Remove the Cisco Nexus monolithic plugin from the code tree
Public bug reported: The Open vSwitch and Linuxbridge plugins are being removed from the Neutron tree in Juno. See https://bugs.launchpad.net/neutron/+bug/1323729 The Cisco Nexus monolithic plugin does not work without the Open vSwitch plugin, so it also needs to be removed from the tree. The Cisco monolithic plugin contains code for both the Nexus hardware switches and the N1KV virtual switch. The N1KV code will remain in the tree (it does not depend on the OVS plugin). Note: the Cisco Nexus is now supported in Neutron via the Nexus mechanism driver in the ML2 plugin. ** Affects: devstack Importance: Undecided Status: New ** Affects: neutron Importance: Medium Assignee: Henry Gessau (gessau) Status: New ** Tags: cisco ** Tags added: cisco ** Also affects: devstack 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/1350387 Title: Remove the Cisco Nexus monolithic plugin from the code tree Status in devstack - openstack dev environments: New Status in OpenStack Neutron (virtual network service): New Bug description: The Open vSwitch and Linuxbridge plugins are being removed from the Neutron tree in Juno. See https://bugs.launchpad.net/neutron/+bug/1323729 The Cisco Nexus monolithic plugin does not work without the Open vSwitch plugin, so it also needs to be removed from the tree. The Cisco monolithic plugin contains code for both the Nexus hardware switches and the N1KV virtual switch. The N1KV code will remain in the tree (it does not depend on the OVS plugin). Note: the Cisco Nexus is now supported in Neutron via the Nexus mechanism driver in the ML2 plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1350387/+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 1350942] [NEW] Use oslo.db create_engine instead of SQLAlchemy
Public bug reported: oslo.db may set additional options to engines that we may be interested in. This will also ease the switch to mysql-connector if that gets approved. ** Affects: neutron Importance: Wishlist Assignee: Ihar Hrachyshka (ihar-hrachyshka) Status: In Progress ** Tags: db ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1350942 Title: Use oslo.db create_engine instead of SQLAlchemy Status in OpenStack Neutron (virtual network service): In Progress Bug description: oslo.db may set additional options to engines that we may be interested in. This will also ease the switch to mysql-connector if that gets approved. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1350942/+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 1351466] Re: can't copy '.../cisco_cfg_agent.ini': doesn't exist
** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1351466 Title: can't copy '.../cisco_cfg_agent.ini': doesn't exist Status in OpenStack Neutron (virtual network service): In Progress Status in tripleo - openstack on openstack: Triaged Bug description: Started roughly 1800 UTC this evening 2014-08-01 19:36:06.878 | error: can't copy 'etc/neutron/plugins/cisco/cisco_cfg_agent.ini': doesn't exist or not a regular file http://logs.openstack.org/70/111370/1/check-tripleo/check-tripleo- ironic-undercloud-precise-nonha/3bc75ae/console.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1351466/+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 1362171] [NEW] Reuse process management classes from dnsmasq for radvd
Public bug reported: When reviewing/discussing the change to add functional tests for radvd[1] it was requested that radvd should be managed similar to the dnsmasq process. We should reuse the classes already existing for dnsmasq. Extract common functionality to allow them to work for both radvd and dnsmasq. This will allow some common functional testing too. [1] https://review.openstack.org/109889 ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1362171 Title: Reuse process management classes from dnsmasq for radvd Status in OpenStack Neutron (virtual network service): New Bug description: When reviewing/discussing the change to add functional tests for radvd[1] it was requested that radvd should be managed similar to the dnsmasq process. We should reuse the classes already existing for dnsmasq. Extract common functionality to allow them to work for both radvd and dnsmasq. This will allow some common functional testing too. [1] https://review.openstack.org/109889 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1362171/+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 1363332] [NEW] Database migration downgrade to havana fails
Public bug reported:
The first migration script after havana (e197124d4b9) has a bad
downgrade.
INFO [alembic.migration] Running downgrade e197124d4b9 -> havana, add unique
constraint to members
Traceback (most recent call last):
File "/home/henry/Dev/neutron/.tox/py27/bin/neutron-db-manage", line 10, in
sys.exit(main())
File "/home/henry/Dev/neutron/neutron/db/migration/cli.py", line 175, in main
CONF.command.func(config, CONF.command.name)
File "/home/henry/Dev/neutron/neutron/db/migration/cli.py", line 85, in
do_upgrade_downgrade
do_alembic_command(config, cmd, revision, sql=CONF.command.sql)
File "/home/henry/Dev/neutron/neutron/db/migration/cli.py", line 63, in
do_alembic_command
getattr(alembic_command, cmd)(config, *args, **kwargs)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/alembic/command.py",
line 151, in downgrade
script.run_env()
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/alembic/script.py",
line 203, in run_env
util.load_python_file(self.dir, 'env.py')
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/alembic/util.py",
line 215, in load_python_file
module = load_module_py(module_id, path)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/alembic/compat.py",
line 58, in load_module_py
mod = imp.load_source(module_id, path, fp)
File
"/home/henry/Dev/neutron/neutron/db/migration/alembic_migrations/env.py", line
120, in
run_migrations_online()
File
"/home/henry/Dev/neutron/neutron/db/migration/alembic_migrations/env.py", line
108, in run_migrations_online
options=build_options())
File "", line 7, in run_migrations
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/alembic/environment.py",
line 689, in run_migrations
self.get_context().run_migrations(**kw)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/alembic/migration.py",
line 263, in run_migrations
change(**kw)
File
"/home/henry/Dev/neutron/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py",
line 62, in downgrade
type_='unique'
File "", line 7, in drop_constraint
File "", line 1, in
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/alembic/util.py",
line 332, in go
return fn(*arg, **kw)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/alembic/operations.py",
line 841, in drop_constraint
self.impl.drop_constraint(const)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/alembic/ddl/impl.py",
line 138, in drop_constraint
self._exec(schema.DropConstraint(const))
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/alembic/ddl/impl.py",
line 76, in _exec
conn.execute(construct, *multiparams, **params)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 729, in execute
return meth(self, multiparams, params)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/sql/ddl.py",
line 69, in _execute_on_connection
return connection._execute_ddl(self, multiparams, params)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 783, in _execute_ddl
compiled
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 958, in _execute_context
context)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 1156, in _handle_dbapi_exception
util.raise_from_cause(newraise, exc_info)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/util/compat.py",
line 199, in raise_from_cause
reraise(type(exception), exception, tb=exc_tb)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 951, in _execute_context
context)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py",
line 436, in do_execute
cursor.execute(statement, parameters)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/MySQLdb/cursors.py",
line 205, in execute
self.errorhandler(self, exc, value)
File
"/home/henry/Dev/neutron/.tox/py27/local/lib/python2.7/site-packages/MySQLdb/connections.py",
line 36, in defaulterrorhandler
raise errorclass, errorvalue
sqlalchemy.exc.OperationalError: (Operatio
[Yahoo-eng-team] [Bug 1261298] Re: The [database] section in neutron.conf should have a comment that it goes in the core plugin .ini file
Moving from devstack to neutron (low priority) ** Summary changed: - The 'connection' param in neutron.conf is in the default value always + The [database] section in neutron.conf should have a comment that it goes in the core plugin .ini file ** Project changed: devstack => neutron ** Changed in: neutron Assignee: Kiyohiro Adachi (adachi) => (unassigned) ** Changed in: neutron Status: In Progress => 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/1261298 Title: The [database] section in neutron.conf should have a comment that it goes in the core plugin .ini file Status in OpenStack Neutron (virtual network service): New Bug description: No one sets the 'connection' param at the '[database]' section in neutron.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1261298/+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 1268711] [NEW] Unlock the psutil version requirement or use an alternative to psutil
Public bug reported: psutil is currently version locked at psutil>=0.6.1,<1.0 These versions are not in PyPI, which is not liked by the new pip. For further information see the comments in https://review.openstack.org/65209 ** 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/1268711 Title: Unlock the psutil version requirement or use an alternative to psutil Status in OpenStack Neutron (virtual network service): New Bug description: psutil is currently version locked at psutil>=0.6.1,<1.0 These versions are not in PyPI, which is not liked by the new pip. For further information see the comments in https://review.openstack.org/65209 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1268711/+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 1275789] [NEW] KeyError 'svc_type' in unit tests
Public bug reported:
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwic3ZjX3R5cGVcIiBBTkQgZmlsZW5hbWU6XCJjb25zb2xlLmh0bWxcIiIsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50Iiwib2Zmc2V0IjowLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiIsInN0YW1wIjoxMzkxNDI5ODM4MjY5fQ==
2014-02-03 08:44:47.763 | FAIL:
neutron.tests.unit.test_provider_configuration.ParseServiceProviderConfigurationTestCase.test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.763 | tags: worker-3
2014-02-03 08:44:47.763 |
--
2014-02-03 08:44:47.763 | Empty attachments:
2014-02-03 08:44:47.764 | stderr
2014-02-03 08:44:47.764 | stdout
2014-02-03 08:44:47.764 |
2014-02-03 08:44:47.765 | pythonlogging:'': {{{2014-02-03 08:44:28,162ERROR
[neutron.services.provider_configuration] Service type 'svc_type' is not
allowed, allowed types: ['CORE', 'DUMMY', 'LOADBALANCER', 'FIREWALL', 'VPN',
'METERING', 'L3_ROUTER_NAT']}}}
2014-02-03 08:44:47.765 |
2014-02-03 08:44:47.765 | Traceback (most recent call last):
2014-02-03 08:44:47.766 | File
"neutron/tests/unit/test_provider_configuration.py", line 87, in
test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.766 | self.assertRaises(q_exc.Invalid,
provconf.parse_service_provider_opt)
2014-02-03 08:44:47.766 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 393, in assertRaises
2014-02-03 08:44:47.766 | self.assertThat(our_callable, matcher)
2014-02-03 08:44:47.767 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 404, in assertThat
2014-02-03 08:44:47.767 | mismatch_error = self._matchHelper(matchee,
matcher, message, verbose)
2014-02-03 08:44:47.767 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 454, in _matchHelper
2014-02-03 08:44:47.768 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.768 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py",
line 108, in match
2014-02-03 08:44:47.768 | mismatch = self.exception_matcher.match(exc_info)
2014-02-03 08:44:47.769 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_higherorder.py",
line 62, in match
2014-02-03 08:44:47.769 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.769 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 385, in match
2014-02-03 08:44:47.770 | reraise(*matchee)
2014-02-03 08:44:47.771 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py",
line 101, in match
2014-02-03 08:44:47.771 | result = matchee()
2014-02-03 08:44:47.771 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 902, in __call__
2014-02-03 08:44:47.772 | return self._callable_object(*self._args,
**self._kwargs)
2014-02-03 08:44:47.772 | File "neutron/services/provider_configuration.py",
line 74, in parse_service_provider_opt
2014-02-03 08:44:47.774 | raise n_exc.Invalid(msg)
2014-02-03 08:44:47.774 | File "neutron/common/exceptions.py", line 198, in
__init__
2014-02-03 08:44:47.774 | super(Invalid, self).__init__()
2014-02-03 08:44:47.774 | File "neutron/common/exceptions.py", line 34, in
__init__
2014-02-03 08:44:47.775 | super(NeutronException,
self).__init__(self.message % kwargs)
2014-02-03 08:44:47.775 | File "neutron/openstack/common/gettextutils.py",
line 199, in __mod__
2014-02-03 08:44:47.775 | params=self._sanitize_mod_params(other),
2014-02-03 08:44:47.776 | File "neutron/openstack/common/gettextutils.py",
line 215, in _sanitize_mod_params
2014-02-03 08:44:47.776 | params = self._trim_dictionary_parameters(other)
2014-02-03 08:44:47.776 | File "neutron/openstack/common/gettextutils.py",
line 239, in _trim_dictionary_parameters
2014-02-03 08:44:47.777 | params[key] = self._copy_param(dict_param[key])
2014-02-03 08:44:47.777 | KeyError: 'svc_type'
** Affects: neutron
Importance: Undecided
Assignee: Henry Gessau (gessau)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Henry Gessau (gessau)
--
You received this bug notification because you are a member of
[Yahoo-eng-team] [Bug 1275789] Re: KeyError 'svc_type' in unit tests
OK I agree the KeyError part is a duplicate of bug #1270212.
But I really meant to file this bug against:
ERROR [neutron.services.provider_configuration] Service type 'svc_type' is not
allowed, allowed types: ['CORE', 'DUMMY', 'LOADBALANCER', 'FIREWALL', 'VPN',
'METERING', 'L3_ROUTER_NAT']
** Summary changed:
- KeyError 'svc_type' in unit tests
+ "ERROR [neutron.services.provider_configuration] Service type 'svc_type' is
not allowed" in unit tests
** This bug is no longer a duplicate of bug 1270212
regression: multiple calls to Message.__mod__ trigger exceptions
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1275789
Title:
"ERROR [neutron.services.provider_configuration] Service type
'svc_type' is not allowed" in unit tests
Status in OpenStack Neutron (virtual network service):
New
Bug description:
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwic3ZjX3R5cGVcIiBBTkQgZmlsZW5hbWU6XCJjb25zb2xlLmh0bWxcIiIsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50Iiwib2Zmc2V0IjowLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiIsInN0YW1wIjoxMzkxNDI5ODM4MjY5fQ==
2014-02-03 08:44:47.763 | FAIL:
neutron.tests.unit.test_provider_configuration.ParseServiceProviderConfigurationTestCase.test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.763 | tags: worker-3
2014-02-03 08:44:47.763 |
--
2014-02-03 08:44:47.763 | Empty attachments:
2014-02-03 08:44:47.764 | stderr
2014-02-03 08:44:47.764 | stdout
2014-02-03 08:44:47.764 |
2014-02-03 08:44:47.765 | pythonlogging:'': {{{2014-02-03 08:44:28,162
ERROR [neutron.services.provider_configuration] Service type 'svc_type' is not
allowed, allowed types: ['CORE', 'DUMMY', 'LOADBALANCER', 'FIREWALL', 'VPN',
'METERING', 'L3_ROUTER_NAT']}}}
2014-02-03 08:44:47.765 |
2014-02-03 08:44:47.765 | Traceback (most recent call last):
2014-02-03 08:44:47.766 | File
"neutron/tests/unit/test_provider_configuration.py", line 87, in
test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.766 | self.assertRaises(q_exc.Invalid,
provconf.parse_service_provider_opt)
2014-02-03 08:44:47.766 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 393, in assertRaises
2014-02-03 08:44:47.766 | self.assertThat(our_callable, matcher)
2014-02-03 08:44:47.767 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 404, in assertThat
2014-02-03 08:44:47.767 | mismatch_error = self._matchHelper(matchee,
matcher, message, verbose)
2014-02-03 08:44:47.767 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 454, in _matchHelper
2014-02-03 08:44:47.768 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.768 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py",
line 108, in match
2014-02-03 08:44:47.768 | mismatch =
self.exception_matcher.match(exc_info)
2014-02-03 08:44:47.769 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_higherorder.py",
line 62, in match
2014-02-03 08:44:47.769 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.769 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 385, in match
2014-02-03 08:44:47.770 | reraise(*matchee)
2014-02-03 08:44:47.771 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py",
line 101, in match
2014-02-03 08:44:47.771 | result = matchee()
2014-02-03 08:44:47.771 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 902, in __call__
2014-02-03 08:44:47.772 | return self._callable_object(*self._args,
**self._kwargs)
2014-02-03 08:44:47.772 | File
"neutron/services/provider_configuration.py", line 74, in
parse_service_provider_opt
2014-02-03 08:44:47.774 | raise n_exc.Invalid(msg)
2014-02-03 08:44:47.774 | File "neutron/common/exceptions.py", line 198, in
__init__
2014-02-03 08:44:47.774 | super(Invalid, self).__init__()
2014-02-03 08:44:47.774 | File "neutron/common/exceptions.py", line 34, in
__init__
2014-02-03 08:44:47.775 | super(NeutronException,
self).__init__(self.message % kwargs)
2014-02-03 08:44:47.775 | File "neutron/openstack/common/gettextutils.py",
line 199, in __mod__
2014-02-03 08:44:47.775 | param
[Yahoo-eng-team] [Bug 1275789] Re: "ERROR [neutron.services.provider_configuration] Service type 'svc_type' is not allowed" in unit tests
*** This bug is a duplicate of bug 1270212 ***
https://bugs.launchpad.net/bugs/1270212
Nope. You are right Amir. It seems that ERROR is a fallout of Bug
#1270212.
** This bug has been marked a duplicate of bug 1270212
regression: multiple calls to Message.__mod__ trigger exceptions
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1275789
Title:
"ERROR [neutron.services.provider_configuration] Service type
'svc_type' is not allowed" in unit tests
Status in OpenStack Neutron (virtual network service):
New
Bug description:
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwic3ZjX3R5cGVcIiBBTkQgZmlsZW5hbWU6XCJjb25zb2xlLmh0bWxcIiIsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50Iiwib2Zmc2V0IjowLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6IiIsInN0YW1wIjoxMzkxNDI5ODM4MjY5fQ==
2014-02-03 08:44:47.763 | FAIL:
neutron.tests.unit.test_provider_configuration.ParseServiceProviderConfigurationTestCase.test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.763 | tags: worker-3
2014-02-03 08:44:47.763 |
--
2014-02-03 08:44:47.763 | Empty attachments:
2014-02-03 08:44:47.764 | stderr
2014-02-03 08:44:47.764 | stdout
2014-02-03 08:44:47.764 |
2014-02-03 08:44:47.765 | pythonlogging:'': {{{2014-02-03 08:44:28,162
ERROR [neutron.services.provider_configuration] Service type 'svc_type' is not
allowed, allowed types: ['CORE', 'DUMMY', 'LOADBALANCER', 'FIREWALL', 'VPN',
'METERING', 'L3_ROUTER_NAT']}}}
2014-02-03 08:44:47.765 |
2014-02-03 08:44:47.765 | Traceback (most recent call last):
2014-02-03 08:44:47.766 | File
"neutron/tests/unit/test_provider_configuration.py", line 87, in
test_parse_service_provider_opt_not_allowed_raises
2014-02-03 08:44:47.766 | self.assertRaises(q_exc.Invalid,
provconf.parse_service_provider_opt)
2014-02-03 08:44:47.766 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 393, in assertRaises
2014-02-03 08:44:47.766 | self.assertThat(our_callable, matcher)
2014-02-03 08:44:47.767 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 404, in assertThat
2014-02-03 08:44:47.767 | mismatch_error = self._matchHelper(matchee,
matcher, message, verbose)
2014-02-03 08:44:47.767 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 454, in _matchHelper
2014-02-03 08:44:47.768 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.768 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py",
line 108, in match
2014-02-03 08:44:47.768 | mismatch =
self.exception_matcher.match(exc_info)
2014-02-03 08:44:47.769 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_higherorder.py",
line 62, in match
2014-02-03 08:44:47.769 | mismatch = matcher.match(matchee)
2014-02-03 08:44:47.769 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 385, in match
2014-02-03 08:44:47.770 | reraise(*matchee)
2014-02-03 08:44:47.771 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/matchers/_exception.py",
line 101, in match
2014-02-03 08:44:47.771 | result = matchee()
2014-02-03 08:44:47.771 | File
"/home/jenkins/workspace/gate-neutron-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 902, in __call__
2014-02-03 08:44:47.772 | return self._callable_object(*self._args,
**self._kwargs)
2014-02-03 08:44:47.772 | File
"neutron/services/provider_configuration.py", line 74, in
parse_service_provider_opt
2014-02-03 08:44:47.774 | raise n_exc.Invalid(msg)
2014-02-03 08:44:47.774 | File "neutron/common/exceptions.py", line 198, in
__init__
2014-02-03 08:44:47.774 | super(Invalid, self).__init__()
2014-02-03 08:44:47.774 | File "neutron/common/exceptions.py", line 34, in
__init__
2014-02-03 08:44:47.775 | super(NeutronException,
self).__init__(self.message % kwargs)
2014-02-03 08:44:47.775 | File "neutron/openstack/common/gettextutils.py",
line 199, in __mod__
2014-02-03 08:44:47.775 | params=self._sanitize_mod_params(other),
2014-02-03 08:44:47.776 | File "neutron/openstack/common/gettextutils.py",
line 215, in _sanitize_mod_params
2014-02-03 08:44:47.776 | params = self._trim_dictionary_parameters(other)
2014-02-03 08:44:47.776 | File "neutron/openstack/co
[Yahoo-eng-team] [Bug 1277217] [NEW] Cisco plugins should use common network type consts
Public bug reported: Cisco plugin and ML2 mech driver were not covered by 4cdccd69a45aec19d547c10f29f61359b69ad6c1 ** Affects: neutron Importance: Undecided Status: In Progress ** Tags: cisco ** Changed in: neutron Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1277217 Title: Cisco plugins should use common network type consts Status in OpenStack Neutron (virtual network service): In Progress Bug description: Cisco plugin and ML2 mech driver were not covered by 4cdccd69a45aec19d547c10f29f61359b69ad6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1277217/+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 1277222] [NEW] Reorganize code tree for multiple cisco ML2 mech drivers
Public bug reported: Currently there is one ML2 driver for cisco nexus in neutron/plugins/ml2/drivers/cisco It needs to go down a level so other cisco drivers can live alongside it: neutron/plugins/ml2/drivers/cisco/apic neutron/plugins/ml2/drivers/cisco/nexus neutron/plugins/ml2/drivers/cisco/ucs neutron/plugins/ml2/drivers/cisco/... ** Affects: neutron Importance: Undecided Status: In Progress ** Tags: cisco ** Changed in: neutron Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1277222 Title: Reorganize code tree for multiple cisco ML2 mech drivers Status in OpenStack Neutron (virtual network service): In Progress Bug description: Currently there is one ML2 driver for cisco nexus in neutron/plugins/ml2/drivers/cisco It needs to go down a level so other cisco drivers can live alongside it: neutron/plugins/ml2/drivers/cisco/apic neutron/plugins/ml2/drivers/cisco/nexus neutron/plugins/ml2/drivers/cisco/ucs neutron/plugins/ml2/drivers/cisco/... To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1277222/+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 1280100] Re: StringIO.StringIO is incompatible for python 3
Neutron client does not use StringIO. (It does use cStringIO, but a separate bug should be opened for that.) ** Changed in: python-neutronclient Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1280100 Title: StringIO.StringIO is incompatible for python 3 Status in OpenStack Telemetry (Ceilometer): New Status in Cinder: New Status in config: New Status in Gantt: New Status in OpenStack Image Registry and Delivery Service (Glance): New Status in Orchestration API (Heat): New Status in Heat CloudFormation Clients: New Status in Heat API Instance Tools: New Status in OpenStack Dashboard (Horizon): New Status in Ironic (Bare Metal Provisioning): New Status in OpenStack Message Queuing Service (Marconi): New Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): New Status in Oslo - a Library of Common OpenStack Code: New Status in Python client library for Glance: New Status in Python client library for Neutron: Invalid Status in OpenStack Command Line Client: Invalid Status in Python client library for Tuskar: New Status in OpenStack Data Processing (Savanna): New Status in Storyboard database creator: New Status in Tempest: New Status in Trove - Database as a Service: New Status in Tuskar: Triaged Status in Tuskar UI: Triaged Status in Zuul: A project gating system: New Bug description: Import StringIO StringIO.StringIO() should be : Import six six.StringIO() six.StringIO is an alias for StringIO.StringIO in Python 2 and io.StringIO in Python3. For Python3 compatible. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1280100/+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 1470598] [NEW] Move LibraryAPIBreakage wiki to devref
Public bug reported: The following wiki is intended to keep track of neutron changes that may affect external plugins and drivers. https://wiki.openstack.org/wiki/Neutron/LibraryAPIBreakage However it is not easily discoverable unless you know that it exists and what to search for. The information should be kept in a living document in the devref area of the neutron code tree. ** Affects: neutron Importance: Medium Status: Triaged ** Tags: documentation low-hanging-fruit ** Changed in: neutron Status: New => Triaged ** Changed in: neutron Importance: Undecided => Medium ** Tags added: documentation low-hanging-fruit -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1470598 Title: Move LibraryAPIBreakage wiki to devref Status in OpenStack Neutron (virtual network service): Triaged Bug description: The following wiki is intended to keep track of neutron changes that may affect external plugins and drivers. https://wiki.openstack.org/wiki/Neutron/LibraryAPIBreakage However it is not easily discoverable unless you know that it exists and what to search for. The information should be kept in a living document in the devref area of the neutron code tree. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1470598/+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 1470622] [NEW] Devref documentation for client command extension support
Public bug reported: The only documentation for client extensibility is the commit message in https://review.openstack.org/148318 The information should be in an official devref document. ** Affects: neutron Importance: Medium Status: Triaged ** Affects: python-neutronclient Importance: Medium Status: Triaged ** Tags: documentation low-hanging-fruit ** Tags added: documentation low-hanging-fruit ** Also affects: python-neutronclient Importance: Undecided Status: New ** Changed in: neutron Status: New => Triaged ** Changed in: python-neutronclient Status: New => Triaged ** Changed in: neutron Importance: Undecided => Medium ** Changed in: python-neutronclient Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1470622 Title: Devref documentation for client command extension support Status in OpenStack Neutron (virtual network service): Triaged Status in Python client library for Neutron: Triaged Bug description: The only documentation for client extensibility is the commit message in https://review.openstack.org/148318 The information should be in an official devref document. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1470622/+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 1470625] [NEW] Mechanism to register and run all external alembic migrations automatically
Public bug reported: For alembic migration branches that are out-of-tree, we need a mechanism whereby the external code can register its branches when it is installed, and then neutron will provide automation of running all installed external migration branches when neutron-db-manage is used for upgrading. ** Affects: neutron Importance: High Assignee: Henry Gessau (gessau) Status: Triaged ** Tags: db ** Changed in: python-neutronclient Status: New => Triaged ** Changed in: python-neutronclient Importance: Undecided => High ** Changed in: python-neutronclient Assignee: (unassigned) => Henry Gessau (gessau) ** Also affects: neutron Importance: Undecided Status: New ** No longer affects: python-neutronclient ** Changed in: neutron Status: New => Triaged ** Changed in: neutron Importance: Undecided => High ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1470625 Title: Mechanism to register and run all external alembic migrations automatically Status in OpenStack Neutron (virtual network service): Triaged Bug description: For alembic migration branches that are out-of-tree, we need a mechanism whereby the external code can register its branches when it is installed, and then neutron will provide automation of running all installed external migration branches when neutron-db-manage is used for upgrading. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1470625/+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 1470678] [NEW] Provide a template DB migration/model sync test for third-party maintainers
Public bug reported: See the "DB Model/Migration Testing" section in https://review.openstack.org/187267 ** Affects: neutron Importance: Medium Assignee: Ann Kamyshnikova (akamyshnikova) Status: Triaged ** Tags: db ** Changed in: neutron Status: New => Triaged ** Changed in: neutron Importance: Undecided => Medium ** Changed in: neutron Assignee: (unassigned) => Ann Kamyshnikova (akamyshnikova) ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1470678 Title: Provide a template DB migration/model sync test for third-party maintainers Status in OpenStack Neutron (virtual network service): Triaged Bug description: See the "DB Model/Migration Testing" section in https://review.openstack.org/187267 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1470678/+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 1471333] [NEW] neutron-db-manage autogenerate support for external repos
Public bug reported: Neutron third-party external repos (and also the *aaS repos) have their own independent alembic branches. Then autogenerate command of neutron- db-manage shall support these external branches. Documentation shall be provided on how to use it. ** Affects: neutron Importance: Medium Assignee: Henry Gessau (gessau) Status: Triaged ** Tags: db ** Changed in: neutron Status: New => Triaged ** Changed in: neutron Importance: Undecided => Medium ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1471333 Title: neutron-db-manage autogenerate support for external repos Status in OpenStack Neutron (virtual network service): Triaged Bug description: Neutron third-party external repos (and also the *aaS repos) have their own independent alembic branches. Then autogenerate command of neutron-db-manage shall support these external branches. Documentation shall be provided on how to use it. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1471333/+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 1470625] Re: Mechanism to register and run all external alembic migrations automatically
This is a mini-RFE since we are adding a new mechanism using entry- points to register external alembic branches at install time. ** Tags added: rfe ** Also affects: networking-l2gw Importance: Undecided Status: New ** Also affects: networking-cisco Importance: Undecided Status: New ** Changed in: networking-cisco Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: networking-l2gw Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1470625 Title: Mechanism to register and run all external alembic migrations automatically Status in networking-cisco: New Status in networking-l2gw: New Status in neutron: In Progress Bug description: For alembic migration branches that are out-of-tree, we need a mechanism whereby the external code can register its branches when it is installed, and then neutron will provide automation of running all installed external migration branches when neutron-db-manage is used for upgrading. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1470625/+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 1479123] Re: N1Kv ML2 mech driver and DB models decomposition
** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Assignee: (unassigned) => Saksham Varma (sakvarma) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1479123 Title: N1Kv ML2 mech driver and DB models decomposition Status in networking-cisco: In Progress Status in neutron: In Progress Bug description: As part of the second phase of core-vendor decomposition, N1Kv mech driver and DB models need to be moved from neutron's shim layer to the networking-cisco repo. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1479123/+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 1475297] Re: Unbind segment not working correctly
** Changed in: neutron Importance: Undecided => Critical ** Changed in: neutron Importance: Critical => High ** Also affects: networking-cisco Importance: Undecided Status: New ** Changed in: networking-cisco Status: New => In Progress ** Changed in: networking-cisco Importance: Undecided => Critical ** Changed in: networking-cisco Assignee: (unassigned) => Sam Betts (sambetts) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1475297 Title: Unbind segment not working correctly Status in networking-cisco: In Progress Status in neutron: In Progress Bug description: A recent commit https://review.openstack.org/#/c/196908/21 changed the order of some of the calls in update_port and its causing a failure of segment unbind in the Cisco nexus driver. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1475297/+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 1482236] Re: Support replay retry in Liberty so it works with multiprocesses
** Also affects: networking-cisco Importance: Undecided Status: New ** Changed in: networking-cisco Assignee: (unassigned) => Carol Bouchard (caboucha) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1482236 Title: Support replay retry in Liberty so it works with multiprocesses Status in networking-cisco: New Status in neutron: New Bug description: For the short-term, the retry capability was backed out or liberty and kilo since it will require data base changes to support multiprocesses(ref: 1469839). Due to planned movement on vendor data bases this capability will only be implemented in new releases. This capability allows the user to configure in the cisco vendor ml2 ini file the number of replay attempts which can be performed. These attempts include any point of replay failure of which there are two points. The first failure point is attempt to contact the Nexus Switch. The second failure is when the switch was contacted but the ML2 Nexus Driver encountered errors trying to configure the switch during replay. When the sum of these errors is reaches the max configured attempt, the ML2 Driver will stop attempting to contact the switch. However, Once a new transaction is encountered, the stats kept for these two points of failure will be reset and Replay attempts will start over. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1482236/+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 1484160] [NEW] Final decomposition of ML2 Cisco NCS driver
Public bug reported: Fully decompose the ncs driver from neutron. ** Affects: networking-cisco Importance: High Assignee: Henry Gessau (gessau) Status: New ** Affects: neutron Importance: High Assignee: Henry Gessau (gessau) Status: New ** Tags: cisco ** Tags added: cisco ** Also affects: networking-cisco Importance: Undecided Status: New ** Changed in: networking-cisco Importance: Undecided => High ** Changed in: neutron Importance: Undecided => High ** Changed in: networking-cisco Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: neutron Milestone: None => liberty-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1484160 Title: Final decomposition of ML2 Cisco NCS driver Status in networking-cisco: New Status in neutron: New Bug description: Fully decompose the ncs driver from neutron. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1484160/+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 1484165] [NEW] Final decomposition of ML2 Cisco UCSM driver
Public bug reported: Fully decompose the ML2 Cisco ucsm driver to the vendor repo ** Affects: networking-cisco Importance: High Assignee: Sandhya Dasu (sadasu) Status: Triaged ** Affects: neutron Importance: High Assignee: Sandhya Dasu (sadasu) Status: Triaged ** Tags: cisco ** Tags added: cisco ** Also affects: networking-cisco Importance: Undecided Status: New ** Changed in: networking-cisco Status: New => Triaged ** Changed in: neutron Status: New => Triaged ** Changed in: networking-cisco Importance: Undecided => High ** Changed in: neutron Importance: Undecided => High ** Changed in: networking-cisco Assignee: (unassigned) => Sandhya Dasu (sadasu) ** Changed in: neutron Assignee: (unassigned) => Sandhya Dasu (sadasu) ** Changed in: neutron Milestone: None => liberty-3 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1484165 Title: Final decomposition of ML2 Cisco UCSM driver Status in networking-cisco: Triaged Status in neutron: Triaged Bug description: Fully decompose the ML2 Cisco ucsm driver to the vendor repo To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1484165/+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 1484344] [NEW] Decompose Cisco l3 and cfg_agent service plugins
Public bug reported: Files in plugins/cisco related to the l3 service and cfg_agent need to be decomposed to the vendor repo. ** Affects: networking-cisco Importance: High Status: Triaged ** Affects: neutron Importance: High Status: Triaged ** Tags: cisco ** Tags added: cisco ** Also affects: networking-cisco Importance: Undecided Status: New ** Changed in: networking-cisco Importance: Undecided => High ** Changed in: neutron Importance: Undecided => High ** Changed in: networking-cisco Status: New => Triaged ** Changed in: neutron Status: New => Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1484344 Title: Decompose Cisco l3 and cfg_agent service plugins Status in networking-cisco: Triaged Status in neutron: Triaged Bug description: Files in plugins/cisco related to the l3 service and cfg_agent need to be decomposed to the vendor repo. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1484344/+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 1470625] Re: Mechanism to register and run all external neutron alembic migrations automatically
** Summary changed: - Mechanism to register and run all external alembic migrations automatically + Mechanism to register and run all external neutron alembic migrations automatically ** Also affects: devstack Importance: Undecided Status: New ** Changed in: devstack Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: networking-cisco Importance: Undecided => High ** Changed in: neutron Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1470625 Title: Mechanism to register and run all external neutron alembic migrations automatically Status in devstack: New Status in networking-cisco: New Status in networking-l2gw: In Progress Status in neutron: Fix Committed Bug description: For alembic migration branches that are out-of-tree, we need a mechanism whereby the external code can register its branches when it is installed, and then neutron will provide automation of running all installed external migration branches when neutron-db-manage is used for upgrading. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1470625/+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 1484745] Re: DB migration juno-> kilo fails: Can't create table nsxv_internal_networks
** Changed in: neutron
Status: Incomplete => 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/1484745
Title:
DB migration juno-> kilo fails: Can't create table
nsxv_internal_networks
Status in neutron:
Invalid
Bug description:
Get the following error when upgrading my juno DB to kilo
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file
/etc/neutron/plugins/ml2/ml2_conf.ini upgrade kilo
INFO [alembic.migration] Context impl MySQLImpl.
INFO [alembic.migration] Will assume non-transactional DDL.
INFO [alembic.migration] Context impl MySQLImpl.
INFO [alembic.migration] Will assume non-transactional DDL.
INFO [alembic.migration] Running upgrade 38495dc99731 -> 4dbe243cd84d, nsxv
Traceback (most recent call last):
File "/usr/bin/neutron-db-manage", line 10, in
sys.exit(main())
File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line
238, in main
CONF.command.func(config, CONF.command.name)
File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line
106, in do_upgrade
do_alembic_command(config, cmd, revision, sql=CONF.command.sql)
File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line
72, in do_alembic_command
getattr(alembic_command, cmd)(config, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/alembic/command.py", line 165, in
upgrade
script.run_env()
File "/usr/lib/python2.7/dist-packages/alembic/script.py", line 382, in
run_env
util.load_python_file(self.dir, 'env.py')
File "/usr/lib/python2.7/dist-packages/alembic/util.py", line 241, in
load_python_file
module = load_module_py(module_id, path)
File "/usr/lib/python2.7/dist-packages/alembic/compat.py", line 79, in
load_module_py
mod = imp.load_source(module_id, path, fp)
File
"/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py",
line 109, in
run_migrations_online()
File
"/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py",
line 100, in run_migrations_online
context.run_migrations()
File "", line 7, in run_migrations
File "/usr/lib/python2.7/dist-packages/alembic/environment.py", line 742,
in run_migrations
self.get_context().run_migrations(**kw)
File "/usr/lib/python2.7/dist-packages/alembic/migration.py", line 305, in
run_migrations
step.migration_fn(**kw)
File
"/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/versions/4dbe243cd84d_nsxv.py",
line 65, in upgrade
sa.PrimaryKeyConstraint('network_purpose'))
File "", line 7, in create_table
File "/usr/lib/python2.7/dist-packages/alembic/operations.py", line 936, in
create_table
self.impl.create_table(table)
File "/usr/lib/python2.7/dist-packages/alembic/ddl/impl.py", line 182, in
create_table
self._exec(schema.CreateTable(table))
File "/usr/lib/python2.7/dist-packages/alembic/ddl/impl.py", line 106, in
_exec
return conn.execute(construct, *multiparams, **params)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line
729, in execute
return meth(self, multiparams, params)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/sql/ddl.py", line 69, in
_execute_on_connection
return connection._execute_ddl(self, multiparams, params)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line
783, in _execute_ddl
compiled
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line
958, in _execute_context
context)
File
"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/compat/handle_error.py",
line 261, in _handle_dbapi_exception
e, statement, parameters, cursor, context)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line
1155, in _handle_dbapi_exception
util.raise_from_cause(newraise, exc_info)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/util/compat.py", line
199, in raise_from_cause
reraise(type(exception), exception, tb=exc_tb)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line
951, in _execute_context
context)
File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line
436, in do_execute
cursor.execute(statement, parameters)
File "/usr/lib/python2.7/dist-packages/MySQLdb/cursors.py", line 174, in
execute
self.errorhandler(self, exc, value)
File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 36, in
defaulterrorhandler
raise errorclass, errorvalue
sqlalchemy.exc.OperationalError: (OperationalError) (1005, "Can't create
table 'neutron_rctest.nsxv_internal_networks' (errno: 150)") "\nCREATE TABLE
nsxv_internal_networks (\n\tnetwork_purpose ENUM('inter_edge_net') NOT NULL,
\n\tnetwork_
[Yahoo-eng-team] [Bug 1497830] [NEW] Neutron subprojects cannot depend on alembic revisions from other neutron subprojects
Public bug reported: If networking-foo depends on networking-bar, then a requirement may arise for an alembic revision in networking-foo to depend on an alembic revision in networking-bar. Currently this cannot be accommodated because each subproject has its own alembic environment. To solve this issue we need to switch to one alembic environment (neutron's) for all neutron subprojects. ** Affects: neutron Importance: High Assignee: Henry Gessau (gessau) Status: New ** Tags: db ** Tags added: db ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: neutron Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1497830 Title: Neutron subprojects cannot depend on alembic revisions from other neutron subprojects Status in neutron: New Bug description: If networking-foo depends on networking-bar, then a requirement may arise for an alembic revision in networking-foo to depend on an alembic revision in networking-bar. Currently this cannot be accommodated because each subproject has its own alembic environment. To solve this issue we need to switch to one alembic environment (neutron's) for all neutron subprojects. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1497830/+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 1430994] [NEW] Some strings split across lines are missing a space
Public bug reported:
For example,
msg = (_("Validation of dictionary's keys failed."
"Expected keys: %(expected_keys)s "
** Affects: neutron
Importance: Undecided
Assignee: Brian Bowen (brbowen)
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/1430994
Title:
Some strings split across lines are missing a space
Status in OpenStack Neutron (virtual network service):
New
Bug description:
For example,
msg = (_("Validation of dictionary's keys failed."
"Expected keys: %(expected_keys)s "
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1430994/+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 1431627] [NEW] Entrypoint should not refer to vendor library
Public bug reported: [entry_points] console_scripts = neutron-cisco-cfg-agent = networking_cisco.plugins.cisco.cfg_agent.cfg_agent:main ** Affects: neutron Importance: Undecided Status: New ** Tags: cisco ** Tags added: cisco -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1431627 Title: Entrypoint should not refer to vendor library Status in OpenStack Neutron (virtual network service): New Bug description: [entry_points] console_scripts = neutron-cisco-cfg-agent = networking_cisco.plugins.cisco.cfg_agent.cfg_agent:main To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1431627/+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 1434103] [NEW] SQL schema downgrades are no longer supported
Public bug reported: Approved cross-project spec: https://review.openstack.org/152337 ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: In Progress ** Tags: db ** Tags added: db -- 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 OpenStack Neutron (virtual network service): In Progress Bug description: Approved cross-project spec: https://review.openstack.org/152337 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+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 1437124] [NEW] API test_update_agent_description modifies agent assumed unchanged by test_list_agent
Public bug reported:
API test_update_agent_description modifies the description of the agent
identified by self.agent['id']. If that test case is run before
test_list_agent, then the latter will fail because it compares with the
original description:
2015-03-18 14:47:53.271 | 2015-03-18 14:47:53.237 |
2015-03-18 14:47:53.273 | 2015-03-18 14:47:53.239 | Captured traceback:
2015-03-18 14:47:53.275 | 2015-03-18 14:47:53.240 | ~~~
2015-03-18 14:47:53.275 | 2015-03-18 14:47:53.242 | Traceback (most recent
call last):
2015-03-18 14:47:53.277 | 2015-03-18 14:47:53.243 | File
"neutron/tests/tempest/api/network/admin/test_agent_management.py", line 43, in
test_list_agent
2015-03-18 14:47:53.302 | 2015-03-18 14:47:53.244 |
self.assertIn(self.agent, agents)
2015-03-18 14:47:53.303 | 2015-03-18 14:47:53.246 | File
"/opt/stack/new/neutron/.tox/api/local/lib/python2.7/site-packages/testtools/testcase.py",
line 356, in assertIn
2015-03-18 14:47:53.304 | 2015-03-18 14:47:53.251 |
self.assertThat(haystack, Contains(needle), message)
2015-03-18 14:47:53.304 | 2015-03-18 14:47:53.254 | File
"/opt/stack/new/neutron/.tox/api/local/lib/python2.7/site-packages/testtools/testcase.py",
line 435, in assertThat
2015-03-18 14:47:53.305 | 2015-03-18 14:47:53.255 | raise mismatch_error
2015-03-18 14:47:53.306 | 2015-03-18 14:47:53.257 |
testtools.matchers._impl.MismatchError: {u'alive': True, u'started_at':
u'2015-03-18 14:43:45', u'admin_state_up': True, u'binary':
u'neutron-dhcp-agent', u'host':
u'devstack-trusty-rax-ord-1343601.slave.openstack.org', u'created_at':
u'2015-03-18 14:43:45', u'description': u'description for update agent.',
u'topic': u'dhcp_agent', u'agent_type': u'DHCP agent', u'id':
u'25ea8e00-36e8-4408-9b00-d60e8b3a9b39'} not in [{u'alive': True,
u'started_at': u'2015-03-18 14:43:45', u'admin_state_up': True, u'binary':
u'neutron-dhcp-agent', u'host':
u'devstack-trusty-rax-ord-1343601.slave.openstack.org', u'created_at':
u'2015-03-18 14:43:45', u'description': u'', u'topic': u'dhcp_agent',
u'agent_type': u'DHCP agent', u'id': u'25ea8e00-36e8-4408-9b00-d60e8b3a9b39'},
{u'alive': True, u'started_at': u'2015-03-18 14:43:45', u'admin_state_up':
True, u'binary': u'neutron-lbaas-agent', u'host':
u'devstack-trusty-rax-ord-1343601.slave.openstack.org
', u'created_at': u'2015-03-18 14:43:45', u'description': None, u'topic':
u'n-lbaas_agent', u'agent_type': u'Loadbalancer agent', u'id':
u'667de509-9eb8-4350-9f42-9a8511b85e06'}, {u'alive': True, u'started_at':
u'2015-03-18 14:43:45', u'admin_state_up': True, u'binary':
u'neutron-openvswitch-agent', u'host':
u'devstack-trusty-rax-ord-1343601.slave.openstack.org', u'created_at':
u'2015-03-18 14:43:45', u'description': None, u'topic': u'N/A', u'agent_type':
u'Open vSwitch agent', u'id': u'68006b4f-4950-46d6-b660-ddbe23c9b30c'},
{u'alive': True, u'started_at': u'2015-03-18 14:43:45', u'admin_state_up':
True, u'binary': u'neutron-metering-agent', u'host':
u'devstack-trusty-rax-ord-1343601.slave.openstack.org', u'created_at':
u'2015-03-18 14:43:45', u'description': None, u'topic': u'metering_agent',
u'agent_type': u'Metering agent', u'id':
u'8f0f8c3a-b8fe-41c8-ad3a-191e26dd71a4'}, {u'alive': True, u'started_at':
u'2015-03-18 14:43:45', u'admin_state_up': True, u'binary': u'neutron-l3-age
nt', u'host': u'devstack-trusty-rax-ord-1343601.slave.openstack.org',
u'created_at': u'2015-03-18 14:43:45', u'description': None, u'topic':
u'l3_agent', u'agent_type': u'L3 agent', u'id':
u'f1ed957b-68ed-4669-9c85-84cac8095561'}, {u'alive': True, u'started_at':
u'2015-03-18 14:43:45', u'admin_state_up': True, u'binary':
u'neutron-metadata-agent', u'host':
u'devstack-trusty-rax-ord-1343601.slave.openstack.org', u'created_at':
[Yahoo-eng-team] [Bug 1437745] [NEW] ML2 flat_networks config defaults to '*' instead of '', needs deprecation
Public bug reported:
Problem #1: The description and help for the flat_networks config do not
explain what the default value is.
etc/neutron/plugins/ml2/ml2_conf.ini
# (ListOpt) List of physical_network names with which flat networks
# can be created. Use * to allow flat networks with arbitrary
# physical_network names.
#
# flat_networks =
# Example:flat_networks = physnet1,physnet2
# Example:flat_networks = *
neutron/plugins/ml2/drivers/type_flat.py
flat_opts = [
cfg.ListOpt('flat_networks',
default=[],
help=_("List of physical_network names with which flat "
"networks can be created. Use * to allow flat "
"networks with arbitrary physical_network names."))
]
Problem #2:
The code that verifies the config and validates the provider segment for
a flat network ends up treating [] the same as ['*']. This means that
the default is actually ['*']. This leads to bugs like bug 1424548.
An attempt to fix it was made in https://review.openstack.org/160842 but
had to be reverted due to bug 1437116.
Solution:
Deprecate the unintended default of ['*'] and make the new default []
which was the original intent.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: ml2
** Tags added: ml2
** Description changed:
- See bug 1437116, https://launchpad.net/bugs/1437116
-
Problem #1: The description and help for the flat_networks config do not
explain what the default value is.
etc/neutron/plugins/ml2/ml2_conf.ini
- # (ListOpt) List of physical_network names with which flat networks
- # can be created. Use * to allow flat networks with arbitrary
- # physical_network names.
- #
- # flat_networks =
- # Example:flat_networks = physnet1,physnet2
- # Example:flat_networks = *
+ # (ListOpt) List of physical_network names with which flat networks
+ # can be created. Use * to allow flat networks with arbitrary
+ # physical_network names.
+ #
+ # flat_networks =
+ # Example:flat_networks = physnet1,physnet2
+ # Example:flat_networks = *
neutron/plugins/ml2/drivers/type_flat.py
- flat_opts = [
- cfg.ListOpt('flat_networks',
- default=[],
- help=_("List of physical_network names with which flat "
-"networks can be created. Use * to allow flat "
-"networks with arbitrary physical_network names."))
-]
+ flat_opts = [
+ cfg.ListOpt('flat_networks',
+ default=[],
+ help=_("List of physical_network names with which flat "
+ "networks can be created. Use * to allow flat "
+ "networks with arbitrary physical_network names."))
+ ]
Problem #2:
The code that verifies the config and validates the provider segment for
a flat network ends up treating [] the same as ['*']. This means that
- the default is actually ['*']. This leads to bugs like
- https://bugs.launchpad.net/neutron/+bug/1424548.
+ the default is actually ['*']. This leads to bugs like bug 1424548.
An attempt to fix it was made in https://review.openstack.org/160842 but
had to be reverted due to bug 1437116.
Solution:
Deprecate the unintended default of ['*'] and make the new default []
which was the original intent.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1437745
Title:
ML2 flat_networks config defaults to '*' instead of '', needs
deprecation
Status in OpenStack Neutron (virtual network service):
New
Bug description:
Problem #1: The description and help for the flat_networks config do
not explain what the default value is.
etc/neutron/plugins/ml2/ml2_conf.ini
# (ListOpt) List of physical_network names with which flat networks
# can be created. Use * to allow flat networks with arbitrary
# physical_network names.
#
# flat_networks =
# Example:flat_networks = physnet1,physnet2
# Example:flat_networks = *
neutron/plugins/ml2/drivers/type_flat.py
flat_opts = [
cfg.ListOpt('flat_networks',
default=[],
help=_("List of physical_network names with which flat "
"networks can be created. Use * to allow flat "
"networks with arbitrary physical_network names."))
]
Problem #2:
The code that verifies the config and validates the provider segment
for a flat network ends up treating [] the same as ['*']. This means
that the default is actually ['*']. This leads to bugs like bug
1424548.
An attempt to fix it was made in https://review.openstack.org/160842
but had to be reverted due to bug 1437116.
Solution:
Deprecate the unintended default of ['*'] and make the new default []
w
[Yahoo-eng-team] [Bug 1438463] [NEW] Some unit tests cannot be run independently
Public bug reported: See the comment here: https://review.openstack.org/#/c/163758/10/neutron/tests/unit/test_dhcp_agent.py The following test cases fail when run independently: neutron.tests.unit.db.test_agent_db.TestAgentsDbGetAgents.test_get_agents(Get all agents) neutron.tests.unit.db.test_agent_db.TestAgentsDbGetAgents.test_get_agents(Get alive agents (True)) neutron.tests.unit.db.test_agent_db.TestAgentsDbGetAgents.test_get_agents(Get down agents (False)) neutron.tests.unit.db.test_agent_db.TestAgentsDbGetAgents.test_get_agents(Get alive agents (true)) neutron.tests.unit.db.test_agent_db.TestAgentsDbGetAgents.test_get_agents(Get down agents (false)) neutron.tests.unit.db.test_agent_db.TestAgentsDbGetAgents.test_get_agents(Get agents invalid alive filter) neutron.tests.unit.ml2.drivers.arista.test_arista_mechanism_driver.AristaDriverTestCase.test_create_network_postcommit neutron.tests.unit.ml2.drivers.arista.test_arista_mechanism_driver.AristaDriverTestCase.test_create_network_precommit neutron.tests.unit.ml2.drivers.arista.test_arista_mechanism_driver.AristaDriverTestCase.test_create_port_postcommit neutron.tests.unit.ml2.drivers.arista.test_arista_mechanism_driver.AristaDriverTestCase.test_create_port_precommit neutron.tests.unit.ml2.drivers.arista.test_arista_mechanism_driver.AristaDriverTestCase.test_delete_network_postcommit neutron.tests.unit.ml2.drivers.arista.test_arista_mechanism_driver.AristaDriverTestCase.test_delete_network_precommit neutron.tests.unit.ml2.drivers.arista.test_arista_mechanism_driver.AristaDriverTestCase.test_delete_port_postcommit neutron.tests.unit.ml2.drivers.arista.test_arista_mechanism_driver.AristaDriverTestCase.test_delete_port_precommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_create_external_network_postcommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_create_network_postcommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_create_port_nobound_postcommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_create_port_postcommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_create_subnet_nogw_postcommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_create_subnet_postcommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_delete_external_network_postcommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_delete_network_postcommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_initialize neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_update_gw_port_postcommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_update_port_nobound_postcommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_mechanism_driver.TestCiscoApicMechDriver.test_update_port_postcommit neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_topology_agent.TestCiscoApicTopologyAgent.test_check_for_new_peers_no_peers neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_topology_agent.TestCiscoApicTopologyAgent.test_check_for_new_peers_with_peers neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_topology_agent.TestCiscoApicTopologyAgent.test_get_peers neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_topology_agent.TestCiscoApicTopologyAgent.test_init_host_device_exists neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_topology_agent.TestCiscoApicTopologyAgent.test_init_host_device_not_exist neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_topology_agent.TestCiscoApicTopologyService.test_init_host neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_topology_agent.TestCiscoApicTopologyService.test_update_link_add_nopeers neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_topology_agent.TestCiscoApicTopologyService.test_update_link_add_with_peers_diff neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_topology_agent.TestCiscoApicTopologyService.test_update_link_add_with_peers_eq neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_topology_agent.TestCiscoApicTopologyService.test_update_link_rem_no_peers neutron.tests.unit.ml2.drivers.cisco.apic.test_cisco_apic_topology_agent.TestCiscoApicTopologyService.test_update_link_rem_with_peers neutron.tests.unit.ml2.test_rpcapi.RpcCallbacksTestCase.test_get_device_details_caching neutron.tests.unit.ml2.test_rpcapi.RpcCallbacksTestCase.test_get_device_details_port_context_without_bounded_segment neutron.tests.unit.ml2.test_rpcapi.RpcCallbacksTestCase.test_get_device_
[Yahoo-eng-team] [Bug 1440834] Re: Unit test tree does not match the structure of the code tree
** Also affects: networking-cisco Importance: Undecided Status: New ** Changed in: networking-cisco Importance: Undecided => Critical ** Changed in: networking-cisco Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1440834 Title: Unit test tree does not match the structure of the code tree Status in Cisco Vendor Code for OpenStack Neutron: New Status in OpenStack Neutron (virtual network service): In Progress Bug description: The structure of the unit test tree does not currently correspond to the structure of the code under test. This makes it difficult for a developer to find the unit tests for a given module and complicates non-mechanical evaluation of coverage. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1440834/+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 1441790] [NEW] Simplify and modernize model_query()
Public bug reported: >From zzzeek on IRC, 2015-04-08: this thing: https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/plugin.py#L486 this is in a few places. the model_query() for neutron is broken up into these three awkward phases, and seveal of these pliugins put an unnecessary and expensive OUTER JOIN on all queries this should be an INNER JOIN and only when the filter_hook is actually in use now its hard for me to change this b.c. everyone will be like, it works great and nobody uses that thing so who cares but i really want to fix up how we build queries to be cleaner, using newer techniques there’s a quick cahnge we can make right there that will probably corect the outerjoin, we can do query.join() right in the _ml2_port_result_filter_hook for now ** Affects: neutron Importance: Undecided Status: New ** Tags: db ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1441790 Title: Simplify and modernize model_query() Status in OpenStack Neutron (virtual network service): New Bug description: From zzzeek on IRC, 2015-04-08: this thing: https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/plugin.py#L486 this is in a few places. the model_query() for neutron is broken up into these three awkward phases, and seveal of these pliugins put an unnecessary and expensive OUTER JOIN on all queries this should be an INNER JOIN and only when the filter_hook is actually in use now its hard for me to change this b.c. everyone will be like, it works great and nobody uses that thing so who cares but i really want to fix up how we build queries to be cleaner, using newer techniques there’s a quick cahnge we can make right there that will probably corect the outerjoin, we can do query.join() right in the _ml2_port_result_filter_hook for now To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1441790/+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 1377997] Re: All combinations of IPv6 subnet modes need to be tested
** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1377997 Title: All combinations of IPv6 subnet modes need to be tested Status in OpenStack Neutron (virtual network service): Fix Released Bug description: On subnets, the attributes ipv6_ra_mode ipv6_address_mode can have values slaac dhcpv6_stateless dhcpv6_statefull None or not be specified. All combinations of the above need to be tested, for both create_subnet and update_subnet. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1377997/+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 1458682] [NEW] neutron-db-manage autogenerate does not produce a clean upgrade
Public bug reported: neutron-db-manage --autogenerate create commands to drop all the tables without models in the neutron tree. All the FWaaS, LBaaS and VPNaaS tables have models in separate repos. This means that people who just want to add/change some tables will get a lot of unwanted commands in their autogenerated migration script. ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Tags: db ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1458682 Title: neutron-db-manage autogenerate does not produce a clean upgrade Status in OpenStack Neutron (virtual network service): New Bug description: neutron-db-manage --autogenerate create commands to drop all the tables without models in the neutron tree. All the FWaaS, LBaaS and VPNaaS tables have models in separate repos. This means that people who just want to add/change some tables will get a lot of unwanted commands in their autogenerated migration script. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1458682/+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 1404093] Re: Provide option for *OpportunisticTestCase to fail instead of skip on db error
** Also 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/1404093 Title: Provide option for *OpportunisticTestCase to fail instead of skip on db error Status in OpenStack Neutron (virtual network service): Confirmed Status in Oslo Database library: Confirmed Bug description: Tests using oslo.db.sqlalchemy.test_base.DbFixture will skip if the database cannot be provisioned. In the neutron functional job we do not want to skip tests. The tests should fail if the environment is not set up correctly for the tests. After https://review.openstack.org/126175 is merged we should see to it that the migrations tests do not skip. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1404093/+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 1423295] Re: Extend interfaces driver to support N1kV interface type
** Also affects: networking-cisco Importance: Undecided Status: New ** Changed in: networking-cisco Assignee: (unassigned) => Sourabh Patwardhan (sopatwar) ** No longer affects: neutron ** Changed in: networking-cisco Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1423295 Title: Extend interfaces driver to support N1kV interface type Status in Cisco Vendor Code for OpenStack Neutron: In Progress Bug description: Extend the interfaces driver to support the N1kV interface type which is currently unsupported. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1423295/+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 1465678] Re: Table cisco_ml2_apic_contracts has wrong router_id field length: 64 vs 36 in routers.id
** Also affects: networking-cisco Importance: Undecided Status: New ** Tags added: cisco ** Changed in: networking-cisco Status: New => Confirmed ** Changed in: neutron Importance: Undecided => Low ** Changed in: networking-cisco Importance: Undecided => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1465678 Title: Table cisco_ml2_apic_contracts has wrong router_id field length: 64 vs 36 in routers.id Status in Cisco Vendor Code for OpenStack Neutron: Confirmed Status in OpenStack Neutron (virtual network service): In Progress Bug description: Some database engines require foreign keys to be of the same size as referenced fields. cisco_ml2_apic_contracts.router_id is a foreign key to routers.id - the former is varchar(64) while the latter is varchar(36). Database migration scripts fail while running new OpenStack installations (tested with MySQL Cluster/NDB). This bug is very similar to https://bugs.launchpad.net/neutron/+bug/1463806 - the same type of changes should be applied to fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1465678/+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 1466704] [NEW] Frozen (external) DB tables not prevented from alteration
Public bug reported: Database models are being split out of neutron. The FW/LB/VPNaaS models have already been split. Once a model is split out of neutron, it may no longer be altered by any neutron alembic migration. We need to add a test case to the DB migration tests that checks that no external tables are altered after they are split. The names of external tables are recorded in neutron/db/migration/alembic_migrations/external.py We will need to add the revision when the split occurred for each table or group of tables. ** Affects: neutron Importance: Undecided Status: Confirmed ** Tags: db low-hanging-fruit ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1466704 Title: Frozen (external) DB tables not prevented from alteration Status in OpenStack Neutron (virtual network service): Confirmed Bug description: Database models are being split out of neutron. The FW/LB/VPNaaS models have already been split. Once a model is split out of neutron, it may no longer be altered by any neutron alembic migration. We need to add a test case to the DB migration tests that checks that no external tables are altered after they are split. The names of external tables are recorded in neutron/db/migration/alembic_migrations/external.py We will need to add the revision when the split occurred for each table or group of tables. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1466704/+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 1291144] [NEW] Calling cfg.CONF.reset not necessary in individual unit tests
Public bug reported: oslo.config.cfg.CONF.reset is added to cleanup in BaseTestCase.setUp(). No need for individual test classes to do it. ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1291144 Title: Calling cfg.CONF.reset not necessary in individual unit tests Status in OpenStack Neutron (virtual network service): New Bug description: oslo.config.cfg.CONF.reset is added to cleanup in BaseTestCase.setUp(). No need for individual test classes to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1291144/+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 1291174] [NEW] Calling patch.stop not needed in individual test cases
Public bug reported: https://bugs.launchpad.net/neutron/+bug/1290550 adds mock.patch.stopall to BaseTestCase. https://bugs.launchpad.net/neutron/+bug/1291130 removes stopall from individual test cases. We can now go one step further, and remove individual patch stops from cleanups. ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: neutron Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1291174 Title: Calling patch.stop not needed in individual test cases Status in OpenStack Neutron (virtual network service): In Progress Bug description: https://bugs.launchpad.net/neutron/+bug/1290550 adds mock.patch.stopall to BaseTestCase. https://bugs.launchpad.net/neutron/+bug/1291130 removes stopall from individual test cases. We can now go one step further, and remove individual patch stops from cleanups. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1291174/+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 1291174] Re: Calling patch.stop not needed in individual test cases
Even though addCleanup(mock.patch.stopall) is in the base test class, I find that removing some of the existing individual stops causes test failures during tox full suite runs. Abandoning this change since major refactoring of neutron unit tests is planned. ** Changed in: neutron Status: In Progress => New ** Changed in: neutron Status: New => Invalid ** Changed in: neutron Assignee: Henry Gessau (gessau) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1291174 Title: Calling patch.stop not needed in individual test cases Status in OpenStack Neutron (virtual network service): Invalid Bug description: https://bugs.launchpad.net/neutron/+bug/1290550 adds mock.patch.stopall to BaseTestCase. https://bugs.launchpad.net/neutron/+bug/1291130 removes stopall from individual test cases. We can now go one step further, and remove individual patch stops from cleanups. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1291174/+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 1300322] Re: TestSecurityGroupsBasicOps IndexError
Neutron port list can return some ports without fixed ips. This is not
an error in neutron. The tempest test needs to account for ports without
fixed ips.
** Also affects: tempest
Importance: Undecided
Status: New
** Changed in: tempest
Assignee: (unassigned) => Henry Gessau (gessau)
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1300322
Title:
TestSecurityGroupsBasicOps IndexError
Status in OpenStack Neutron (virtual network service):
Invalid
Status in Tempest:
New
Bug description:
Seen in the neutron full job:
Console log:
2014-03-29 19:09:49.985 | Traceback (most recent call last):
2014-03-29 19:09:49.985 | File
"tempest/scenario/test_security_groups_basic_ops.py", line 167, in setUp
2014-03-29 19:09:49.985 | self._verify_mac_addr(self.primary_tenant)
2014-03-29 19:09:49.985 | File
"tempest/scenario/test_security_groups_basic_ops.py", line 429, in
_verify_mac_addr
2014-03-29 19:09:49.985 | port['mac_address'].lower()) for port in
port_list
2014-03-29 19:09:49.985 | IndexError: list index out of range
Neutron log reports 2 error, problem in the communication with nova:
2014-03-28 01:38:20.922 31361 ERROR neutron.notifiers.nova [-] Failed to
notify nova on events: [{'status': 'completed', 'tag':
u'd15f3fdd-31fb-48da-9563-17796df7b6aa', 'name': 'network-vif-plugged',
'server_uuid': u'devstack-precise-check-rax-iad-3242364.slave.openstack.org'}]
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova Traceback (most
recent call last):
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova File
"/opt/stack/new/neutron/neutron/notifiers/nova.py", line 186, in send_events
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova batched_events)
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova File
"/opt/stack/new/python-novaclient/novaclient/v1_1/contrib/server_external_events.py",
line 39, in create
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova
return_raw=True)
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova File
"/opt/stack/new/python-novaclient/novaclient/base.py", line 152, in _create
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova _resp, body =
self.api.client.post(url, body=body)
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova File
"/opt/stack/new/python-novaclient/novaclient/client.py", line 287, in post
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova return
self._cs_request(url, 'POST', **kwargs)
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova File
"/opt/stack/new/python-novaclient/novaclient/client.py", line 261, in
_cs_request
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova **kwargs)
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova File
"/opt/stack/new/python-novaclient/novaclient/client.py", line 243, in
_time_request
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova resp, body =
self.request(url, method, **kwargs)
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova File
"/opt/stack/new/python-novaclient/novaclient/client.py", line 237, in request
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova raise
exceptions.from_response(resp, body, url, method)
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova NotFound: No
instances found for any event (HTTP 404) (Request-ID:
req-904163b3-3b79-4b6f-8dc7-e53ed7520212)
2014-03-28 01:38:20.922 31361 TRACE neutron.notifiers.nova
And problems querying the DB:
2014-03-28 01:59:10.584 31361 ERROR neutron.openstack.common.rpc.amqp
[req-6f6479c4-4893-4c8e-8a06-da6c70c572e8 None] Exception during message
handling
2014-03-28 01:59:10.584 31361 TRACE neutron.openstack.common.rpc.amqp
Traceback (most recent call last):
2014-03-28 01:59:10.584 31361 TRACE neutron.openstack.common.rpc.amqp File
"/opt/stack/new/neutron/neutron/openstack/common/rpc/amqp.py", line 462, in
_process_data
2014-03-28 01:59:10.584 31361 TRACE neutron.openstack.common.rpc.amqp
**args)
2014-03-28 01:59:10.584 31361 TRACE neutron.openstack.common.rpc.amqp File
"/opt/stack/new/neutron/neutron/common/rpc.py", line 45, in dispatch
2014-03-28 01:59:10.584 31361 TRACE neutron.openstack.common.rpc.amqp
neutron_ctxt, version, method, namespace, **kwargs)
2014-03-28 01:59:10.584 31361 TRACE neutron.openstack.common.rpc.amqp File
"/opt/stack/new/neutron/neutron/openstack/common/rpc/dispatcher.py", line 172,
in dispatch
2014-03-28 01:59:10.584 31361 TRACE neutron.open
[Yahoo-eng-team] [Bug 1302304] [NEW] tox pep8 warns /bin/bash not installed in testenv
Public bug reported: $ tox -e pep8 pep8 develop-inst-nodeps: /home/henry/Dev/neutron pep8 runtests: commands[0] | flake8 pep8 runtests: commands[1] | neutron-db-manage check_migration pep8 runtests: commands[2] | bash -c find neutron -type f -regex '.*\.pot?' -print0|xargs -0 -n 1 msgfmt --check-format -o /dev/null WARNING:test command found but not installed in testenv cmd: /bin/bash env: /home/henry/Dev/neutron/.tox/pep8 Maybe forgot to specify a dependency? This is due to the tox.ini changes in https://review.openstack.org/84234 ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Description changed: $ tox -e pep8 pep8 develop-inst-nodeps: /home/henry/Dev/neutron pep8 runtests: commands[0] | flake8 pep8 runtests: commands[1] | neutron-db-manage check_migration pep8 runtests: commands[2] | bash -c find neutron -type f -regex '.*\.pot?' -print0|xargs -0 -n 1 msgfmt --check-format -o /dev/null WARNING:test command found but not installed in testenv - cmd: /bin/bash - env: /home/henry/Dev/neutron/.tox/pep8 + cmd: /bin/bash + env: /home/henry/Dev/neutron/.tox/pep8 Maybe forgot to specify a dependency? - This is dues to the tox changes in https://review.openstack.org/84234 + This is due to the tox.ini changes in https://review.openstack.org/84234 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1302304 Title: tox pep8 warns /bin/bash not installed in testenv Status in OpenStack Neutron (virtual network service): In Progress Bug description: $ tox -e pep8 pep8 develop-inst-nodeps: /home/henry/Dev/neutron pep8 runtests: commands[0] | flake8 pep8 runtests: commands[1] | neutron-db-manage check_migration pep8 runtests: commands[2] | bash -c find neutron -type f -regex '.*\.pot?' -print0|xargs -0 -n 1 msgfmt --check-format -o /dev/null WARNING:test command found but not installed in testenv cmd: /bin/bash env: /home/henry/Dev/neutron/.tox/pep8 Maybe forgot to specify a dependency? This is due to the tox.ini changes in https://review.openstack.org/84234 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1302304/+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 1303179] [NEW] Missing comma in nsx router mappings migration
Public bug reported: Found during review https://review.openstack.org/40296 There is a comma missing in the migration_for_plugins list https://github.com/openstack/neutron/blob/master/neutron/db/migration/alembic_migrations/versions/4ca36cfc898c_nsx_router_mappings.py#L30 ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: In Progress ** Tags: db nicira ** Tags added: db nicira ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1303179 Title: Missing comma in nsx router mappings migration Status in OpenStack Neutron (virtual network service): In Progress Bug description: Found during review https://review.openstack.org/40296 There is a comma missing in the migration_for_plugins list https://github.com/openstack/neutron/blob/master/neutron/db/migration/alembic_migrations/versions/4ca36cfc898c_nsx_router_mappings.py#L30 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1303179/+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 1304741] [NEW] folsom_initial migration has wrong type for brocadenetworks.id
Public bug reported:
brocadenetworks table model is defined as:
class BrocadeNetwork(model_base.BASEV2, models_v2.HasId)
where models_v2.HasId is sa.String(36)
But in the folsom_initial migration we have:
def upgrade_brocade():
op.create_table(
'brocadenetworks',
sa.Column('id', sa.Integer(), autoincrement=False, nullable=False),
** Affects: neutron
Importance: Undecided
Assignee: Henry Gessau (gessau)
Status: New
** Tags: brocade db
** Tags added: brocade db
** Changed in: neutron
Assignee: (unassigned) => Henry Gessau (gessau)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1304741
Title:
folsom_initial migration has wrong type for brocadenetworks.id
Status in OpenStack Neutron (virtual network service):
New
Bug description:
brocadenetworks table model is defined as:
class BrocadeNetwork(model_base.BASEV2, models_v2.HasId)
where models_v2.HasId is sa.String(36)
But in the folsom_initial migration we have:
def upgrade_brocade():
op.create_table(
'brocadenetworks',
sa.Column('id', sa.Integer(), autoincrement=False, nullable=False),
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1304741/+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 1305377] [NEW] Correct flake8 E711 and E712 violations
Public bug reported:
Enable flake8 checking for
E711 comparison to False should be 'if cond is False:' or 'if not cond:'
E712 comparison to True should be 'if cond is True:' or 'if cond:'
** Affects: neutron
Importance: Undecided
Assignee: Henry Gessau (gessau)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Henry Gessau (gessau)
** Summary changed:
- Correct pep8 E711 and E712 violations
+ Correct flake8 E711 and E712 violations
** Description changed:
- Enable PEP8 checking for
+ Enable flake8 checking for
E711/E712 comparison to False should be 'if cond is False:' or 'if not cond:'
** Description changed:
Enable flake8 checking for
- E711/E712 comparison to False should be 'if cond is False:' or 'if not cond:'
+ E711 comparison to False should be 'if cond is False:' or 'if not cond:'
+ E712 comparison to True should be 'if cond is True:' or 'if cond:'
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1305377
Title:
Correct flake8 E711 and E712 violations
Status in OpenStack Neutron (virtual network service):
New
Bug description:
Enable flake8 checking for
E711 comparison to False should be 'if cond is False:' or 'if not cond:'
E712 comparison to True should be 'if cond is True:' or 'if cond:'
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1305377/+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 1313812] [NEW] test_l3_agent unit tests cannot be run individually
Public bug reported: When trying to run the test_l3_agent unit tests individually the following test case fails: == ERROR: neutron.tests.unit.test_l3_agent.TestL3AgentEventHandler.test_spawn_metadata_proxy -- _StringException: Empty attachments: pythonlogging:'' pythonlogging:'neutron.api.extensions' Traceback (most recent call last): File "/home/henry/Dev/neutron/neutron/tests/unit/test_l3_agent.py", line 1203, in setUp 'interface_driver', 'neutron.agent.linux.interface.NullDriver' File "/usr/local/lib/python2.7/dist-packages/oslo/config/cfg.py", line 1547, in __inner result = f(self, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/oslo/config/cfg.py", line 1797, in set_override opt_info = self._get_opt_info(name, group) File "/usr/local/lib/python2.7/dist-packages/oslo/config/cfg.py", line 2106, in _get_opt_info raise NoSuchOptError(opt_name, group) NoSuchOptError: no such option: interface_driver ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Tags: unittest ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1313812 Title: test_l3_agent unit tests cannot be run individually Status in OpenStack Neutron (virtual network service): New Bug description: When trying to run the test_l3_agent unit tests individually the following test case fails: == ERROR: neutron.tests.unit.test_l3_agent.TestL3AgentEventHandler.test_spawn_metadata_proxy -- _StringException: Empty attachments: pythonlogging:'' pythonlogging:'neutron.api.extensions' Traceback (most recent call last): File "/home/henry/Dev/neutron/neutron/tests/unit/test_l3_agent.py", line 1203, in setUp 'interface_driver', 'neutron.agent.linux.interface.NullDriver' File "/usr/local/lib/python2.7/dist-packages/oslo/config/cfg.py", line 1547, in __inner result = f(self, *args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/oslo/config/cfg.py", line 1797, in set_override opt_info = self._get_opt_info(name, group) File "/usr/local/lib/python2.7/dist-packages/oslo/config/cfg.py", line 2106, in _get_opt_info raise NoSuchOptError(opt_name, group) NoSuchOptError: no such option: interface_driver To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1313812/+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 1499033] [NEW] Add Liberty release milestone
Public bug reported: We do this for every release ** Affects: neutron Importance: Medium Assignee: Henry Gessau (gessau) Status: New ** Tags: db ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: neutron Importance: Undecided => Medium ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1499033 Title: Add Liberty release milestone Status in neutron: New Bug description: We do this for every release To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1499033/+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 1501380] [NEW] Evolution of options and features in neutron-db-manage
Public bug reported: Neutron's DB schema and alembic revisions management is evolving. In the process, we have deprecated and dropped features and options. This RFE will be used to track evolutionary updates: - Better help and documentation - Better formatting and and more useful output from commands - Additional commands and options for more insight - New features - etc. This RFE will also be used to track the deprecations and removals: - Branchless migrations - split_branches option - core_plugin option - service option - quota_driver option? - etc. ** Affects: neutron Importance: Undecided Status: New ** Tags: db rfe ** Tags added: db rfe -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1501380 Title: Evolution of options and features in neutron-db-manage Status in neutron: New Bug description: Neutron's DB schema and alembic revisions management is evolving. In the process, we have deprecated and dropped features and options. This RFE will be used to track evolutionary updates: - Better help and documentation - Better formatting and and more useful output from commands - Additional commands and options for more insight - New features - etc. This RFE will also be used to track the deprecations and removals: - Branchless migrations - split_branches option - core_plugin option - service option - quota_driver option? - etc. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1501380/+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 1197570] Re: Update instructions for database migration with additional steps that may be needed
I will close it with a doc update soon. ** Changed in: neutron Status: Invalid => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1197570 Title: Update instructions for database migration with additional steps that may be needed Status in neutron: In Progress Bug description: These instructions https://wiki.openstack.org/wiki/Neutron/DatabaseMigration (and the README referred to therein) do not mention that backend- specific methods will be generated in the migration script, and that the developer must replace them with sa.* abstract methods. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1197570/+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 1504670] [NEW] Remove embrane plugin
Public bug reported: The embrane plugin shall be removed after EOL. ** 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/1504670 Title: Remove embrane plugin Status in neutron: New Bug description: The embrane plugin shall be removed after EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1504670/+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 1388230] Re: Checks for DB models and migrations sync not working
No.
** Changed in: neutron
Status: Incomplete => 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/1388230
Title:
Checks for DB models and migrations sync not working
Status in neutron:
Invalid
Bug description:
I noticed a couple of issues, which might be related.
1. "db-manage revision --autogenerate" on master with no code changes
generates:
def upgrade():
op.drop_index('idx_autoinc_vr_id',
table_name='ha_router_vrid_allocations')
2. With the following change to the IPAllocation() model, the revision is not
detected. Also, the unit tests for model/migration sync do not give an error.
diff --git a/neutron/db/models_v2.py b/neutron/db/models_v2.py
--- a/neutron/db/models_v2.py
+++ b/neutron/db/models_v2.py
@@ -98,8 +98,8 @@ class IPAllocation(model_base.BASEV2):
port_id = sa.Column(sa.String(36), sa.ForeignKey('ports.id',
ondelete="CASCADE"),
-nullable=True)
-ip_address = sa.Column(sa.String(64), nullable=False, primary_key=True)
+nullable=True, primary_key=True)
+ip_address = sa.Column(sa.String(64), nullable=False)
subnet_id = sa.Column(sa.String(36), sa.ForeignKey('subnets.id',
ondelete="CASCADE"),
nullable=False, primary_key=True)
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1388230/+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 1484344] Re: Decompose Cisco l3 and cfg_agent service plugins
Fixed by https://review.openstack.org/217910 ** Changed in: networking-cisco Status: Triaged => Fix Committed ** Changed in: neutron Status: Triaged => Fix Released ** Changed in: networking-cisco Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1484344 Title: Decompose Cisco l3 and cfg_agent service plugins Status in networking-cisco: Fix Committed Status in neutron: Fix Released Bug description: Files in plugins/cisco related to the l3 service and cfg_agent need to be decomposed to the vendor repo. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1484344/+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 1363064] Re: Cannot set only one of IPv6 attributes while second is None
Now invalid because updating of ipv6 mode attributes has been disabled.
** Changed in: neutron
Status: In Progress => 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/1363064
Title:
Cannot set only one of IPv6 attributes while second is None
Status in neutron:
Invalid
Bug description:
When trying to update ipv6 subnet's (created with default None
attributes) ra_mode or address_mode operation is not permited
(although it should be) :
neutron subnet-create --ip-version 6 Test fe80:::/40
+---+---+
| Field | Value
|
+---+---+
| allocation_pools | {"start": "fe80:::2", "end":
"fe80::ff:::::fffe"} |
| cidr | fe80:::/40
|
| dns_nameservers |
|
| enable_dhcp | True
|
| gateway_ip| fe80:::1
|
| host_routes |
|
| id| 720d4f22-ee49-40c9-a865-cb31defcf6bd
|
| ip_version| 6
|
| ipv6_address_mode |
|
| ipv6_ra_mode |
|
| name |
|
| network_id| 124826a4-77ed-4682-8e39-d9090689cb85
|
| tenant_id | d2b47b4677fb4e30ad1961fb7d51ffdc
|
+---+---+
neutron subnet-update 720d4f22-ee49-40c9-a865-cb31defcf6bd
--ipv6_address_mode slaac
Invalid input for operation: ipv6_ra_mode set to 'None' with
ipv6_address_mode set to 'slaac' is not valid. If both attributes are set, they
must be the same value.
neutron subnet-update 720d4f22-ee49-40c9-a865-cb31defcf6bd --ipv6_ra_mode
slaac
Invalid input for operation: ipv6_ra_mode set to 'slaac' with
ipv6_address_mode set to 'None' is not valid. If both attributes are set, they
must be the same value.
Clearly as message states leaving one attribute not set should be allowed
(also I've found spec where attributes combinations are disccused)
http://specs.openstack.org/openstack/neutron-specs/specs/juno/ipv6-radvd-ra.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1363064/+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 1465678] Re: Table cisco_ml2_apic_contracts has wrong router_id field length: 64 vs 36 in routers.id
** Changed in: neutron Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1465678 Title: Table cisco_ml2_apic_contracts has wrong router_id field length: 64 vs 36 in routers.id Status in networking-cisco: Fix Committed Status in neutron: Fix Released Bug description: Some database engines require foreign keys to be of the same size as referenced fields. cisco_ml2_apic_contracts.router_id is a foreign key to routers.id - the former is varchar(64) while the latter is varchar(36). Database migration scripts fail while running new OpenStack installations (tested with MySQL Cluster/NDB). This bug is very similar to https://bugs.launchpad.net/neutron/+bug/1463806 - the same type of changes should be applied to fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1465678/+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 1471333] Re: neutron-db-manage autogenerate support for external repos
neutron-db-manage revision --autogenerate works for sub-projects. There are some remaining issues tracked by Bug #1497830 and Bug #1458682. ** Changed in: neutron Milestone: mitaka-1 => None ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1471333 Title: neutron-db-manage autogenerate support for external repos Status in neutron: Fix Released Bug description: Neutron third-party external repos (and also the *aaS repos) have their own independent alembic branches. Then autogenerate command of neutron-db-manage shall support these external branches. Documentation shall be provided on how to use it. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1471333/+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 1347361] Re: There should be a naming convention for neutron DB tables
The recommended naming of tables for sub-projects is documented. The risk of conflicting names is low enough that it is not worth the effort to implement checks across sub-projects. Marking as Won't-Fix. This can be revisited if it becomes a problem. ** Changed in: neutron Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1347361 Title: There should be a naming convention for neutron DB tables Status in neutron: Won't Fix Bug description: Now that the database is healed and all tables are present, the names of tables are haphazard and there is no convention for avoiding naming conflicts or having sensible grouping. A naming convention may look something like: __ Existing tables should be renamed to follow the convention. A README file explaining the convention should be created in the directory with the models. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1347361/+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 1504670] Re: Remove embrane plugin
** Changed in: neutron Milestone: mitaka-1 => None ** Changed in: neutron Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1504670 Title: Remove embrane plugin Status in neutron: Fix Released Bug description: The embrane plugin shall be removed after EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1504670/+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 1504670] Re: Remove embrane plugin
Oops, not released yet. ** Changed in: neutron Status: Fix Released => Fix Committed ** Changed in: neutron Milestone: None => mitaka-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1504670 Title: Remove embrane plugin Status in neutron: Fix Committed Bug description: The embrane plugin shall be removed after EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1504670/+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 1514823] [NEW] Opendaylight driver shim still present in neutron tree
Public bug reported: The opendaylight ML2 mechanism driver should be completely removed from the neutron tree. All opendaylight driver code and artifacts should be contained in the networking-odl sub-project. ** Affects: networking-odl Importance: Undecided Assignee: Henry Gessau (gessau) Status: In Progress ** Affects: neutron Importance: Medium Assignee: Henry Gessau (gessau) Status: New ** Changed in: neutron Importance: Undecided => Medium ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: neutron Milestone: None => mitaka-1 ** Also affects: networking-odl Importance: Undecided Status: New ** Changed in: networking-odl Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1514823 Title: Opendaylight driver shim still present in neutron tree Status in networking-odl: In Progress Status in neutron: New Bug description: The opendaylight ML2 mechanism driver should be completely removed from the neutron tree. All opendaylight driver code and artifacts should be contained in the networking-odl sub-project. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-odl/+bug/1514823/+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 1396671] Re: Cannot Migrate OpenStack (Juno) Neutron's database
sqlite is not a supported backend. If you have this problem with mysql then please file a new bug with logs showing what went wrong. ** Tags added: db ** 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/1396671 Title: Cannot Migrate OpenStack (Juno) Neutron's database Status in neutron: Invalid Bug description: I am following the Openstack documentation (http://docs.openstack.org/juno/install-guide/install/apt/content/) for installing Openstack on Ubuntu 14.04. At page 59, there is an instruction to finalize the installation of Neutron on the controller node with the following command; # su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno" neutron However, I get the following error; # su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \ --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade juno" neutron INFO [alembic.migration] Context impl SQLiteImpl. INFO [alembic.migration] Will assume non-transactional DDL. INFO [alembic.migration] Running upgrade havana -> e197124d4b9, add unique constraint to members Traceback (most recent call last): File "/usr/bin/neutron-db-manage", line 10, in sys.exit(main()) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 173, in main CONF.command.func(config, CONF.command.name) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 83, in do_upgrade_downgrade do_alembic_command(config, cmd, revision, sql=CONF.command.sql) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py", line 61, in do_alembic_command getattr(alembic_command, cmd)(config, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/alembic/command.py", line 125, in upgrade script.run_env() File "/usr/lib/python2.7/dist-packages/alembic/script.py", line 203, in run_env util.load_python_file(self.dir, 'env.py') File "/usr/lib/python2.7/dist-packages/alembic/util.py", line 212, in load_python_file module = load_module_py(module_id, path) File "/usr/lib/python2.7/dist-packages/alembic/compat.py", line 58, in load_module_py mod = imp.load_source(module_id, path, fp) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py", line 108, in run_migrations_online() File "/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py", line 100, in run_migrations_online context.run_migrations() File "", line 7, in run_migrations File "/usr/lib/python2.7/dist-packages/alembic/environment.py", line 688, in run_migrations self.get_context().run_migrations(**kw) File "/usr/lib/python2.7/dist-packages/alembic/migration.py", line 258, in run_migrations change(**kw) File "/usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/versions/e197124d4b9_add_unique_constrain.py", line 42, in upgrade local_cols=['pool_id', 'address', 'protocol_port'] File "", line 7, in create_unique_constraint File "/usr/lib/python2.7/dist-packages/alembic/operations.py", line 621, in create_unique_constraint schema=schema, **kw) File "/usr/lib/python2.7/dist-packages/alembic/ddl/sqlite.py", line 21, in add_constraint "No support for ALTER of constraints in SQLite dialect") NotImplementedError: No support for ALTER of constraints in SQLite dialect I am pretty sure that I followed all the steps in the right order. I hope I have not raised a false alarm. Cheers, Simon. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1396671/+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 1518637] [NEW] Brocade vendor code still present in neutron tree
Public bug reported: The Brocade plugins and ML2 mechanism drivers should be completely removed from the neutron tree. All Brocade code and artifacts should be contained in the networking-brocade sub-project. See http://docs.openstack.org/developer/neutron/devref/contribute.html ** Affects: networking-brocade Importance: Undecided Status: New ** Affects: neutron Importance: Medium Assignee: Henry Gessau (gessau) Status: New ** Changed in: neutron Importance: Undecided => Medium ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: neutron Milestone: None => mitaka-2 ** Also affects: networking-brocade 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/1518637 Title: Brocade vendor code still present in neutron tree Status in networking-brocade: New Status in neutron: New Bug description: The Brocade plugins and ML2 mechanism drivers should be completely removed from the neutron tree. All Brocade code and artifacts should be contained in the networking-brocade sub-project. See http://docs.openstack.org/developer/neutron/devref/contribute.html To manage notifications about this bug go to: https://bugs.launchpad.net/networking-brocade/+bug/1518637/+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 1518643] [NEW] Nuage vendor code still present in neutron tree
Public bug reported: The Nuage plugins and ML2 mechanism drivers should be completely removed from the neutron tree. See http://docs.openstack.org/developer/neutron/devref/contribute.html ** Affects: neutron Importance: Medium Assignee: Henry Gessau (gessau) Status: New ** Project changed: networking-odl => neutron ** Changed in: neutron Importance: Undecided => Medium ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: neutron Milestone: None => mitaka-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1518643 Title: Nuage vendor code still present in neutron tree Status in neutron: New Bug description: The Nuage plugins and ML2 mechanism drivers should be completely removed from the neutron tree. See http://docs.openstack.org/developer/neutron/devref/contribute.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1518643/+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 1519078] [NEW] Freescale vendor code still present in neutron tree
Public bug reported: The Freescale service plugin and ML2 mechanism driver should be completely removed from the neutron tree. All Freescale code and artifacts should be contained in an external freescale repository. See http://docs.openstack.org/developer/neutron/devref/contribute.html ** Affects: neutron Importance: Medium Status: New ** Changed in: neutron Importance: Undecided => Medium ** Changed in: neutron Milestone: None => mitaka-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1519078 Title: Freescale vendor code still present in neutron tree Status in neutron: New Bug description: The Freescale service plugin and ML2 mechanism driver should be completely removed from the neutron tree. All Freescale code and artifacts should be contained in an external freescale repository. See http://docs.openstack.org/developer/neutron/devref/contribute.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1519078/+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 1519171] [NEW] model-migration check fails to detect integer-biginteger mismatch
Public bug reported: See https://review.openstack.org/#/c/222079/15/neutron/db/migration/alembic_migrations/versions/mitaka/expand/32e5974ada25_add_neutron_resources_table.py Kevin had Integer in the model and BigInteger in the migration. This should be detected by _TestModelsMigrations(). ** Affects: neutron Importance: Medium Status: New ** Tags: db functional-tests ** Changed in: neutron Importance: Undecided => Medium ** Tags added: db ** Tags added: functional-tests -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1519171 Title: model-migration check fails to detect integer-biginteger mismatch Status in neutron: New Bug description: See https://review.openstack.org/#/c/222079/15/neutron/db/migration/alembic_migrations/versions/mitaka/expand/32e5974ada25_add_neutron_resources_table.py Kevin had Integer in the model and BigInteger in the migration. This should be detected by _TestModelsMigrations(). To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1519171/+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 1520054] [NEW] HyperV third-party code still present in neutron tree
Public bug reported: The HyperV ML2 mechanism driver and agent should be completely removed from the neutron tree. All HyperV code and artifacts should be contained in the networking-hyperv sub-project. See http://docs.openstack.org/developer/neutron/devref/contribute.html ** Affects: networking-hyperv Importance: Undecided Status: New ** Affects: neutron Importance: Medium Status: New ** Changed in: neutron Milestone: None => mitaka-1 ** Changed in: neutron Importance: Undecided => Medium ** Also affects: networking-hyperv 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/1520054 Title: HyperV third-party code still present in neutron tree Status in networking-hyperv: New Status in neutron: New Bug description: The HyperV ML2 mechanism driver and agent should be completely removed from the neutron tree. All HyperV code and artifacts should be contained in the networking-hyperv sub-project. See http://docs.openstack.org/developer/neutron/devref/contribute.html To manage notifications about this bug go to: https://bugs.launchpad.net/networking-hyperv/+bug/1520054/+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 1520719] [NEW] OsloDBDeprecationWarning: EngineFacade is deprecated
Public bug reported: neutron/tests/functional/db/test_ipam.py:41: OsloDBDeprecationWarning: EngineFacade is deprecated; please use oslo_db.sqlalchemy.enginefacade ** Affects: neutron Importance: Low Status: New ** Tags: db low-hanging-fruit ** Tags added: db ** Changed in: neutron Importance: Undecided => Low ** Tags added: low-hanging-fruit -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1520719 Title: OsloDBDeprecationWarning: EngineFacade is deprecated Status in neutron: New Bug description: neutron/tests/functional/db/test_ipam.py:41: OsloDBDeprecationWarning: EngineFacade is deprecated; please use oslo_db.sqlalchemy.enginefacade To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1520719/+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 1522903] Re: oslo code should be updated when you update neutron repo
This is not a neutron bug. If you feel it may be a bug in devstack, please file a bug in that project. ** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1522903 Title: oslo code should be updated when you update neutron repo Status in neutron: Invalid Bug description: There was patch to autogenerate core configuration recently max_length was added to oslo_config which works fine if you spin a new vm and install from scratch but if you update existing system (update neutron repo) stack.sh will end up in error becuase olso code is not updated log http://paste.openstack.org/show/480912/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1522903/+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 1524510] Re: Remove Neutron FWaaS static example configuration files
This bug seems to have been erroneously created by some automation. ** 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/1524510 Title: Remove Neutron FWaaS static example configuration files Status in neutron: Invalid Bug description: https://review.openstack.org/254698 commit 6713d0ac33a8a6355b4263bde01d55c01636039b Author: Martin Hickey Date: Tue Dec 8 11:18:04 2015 + Remove Neutron FWaaS static example configuration files Oslo config generator was introduced in patch [1] to automatically generate the sample Neutron FWaaS configuration files. This patch removes the static example configuration files from the repository as they are now redundant. [1] https://review.openstack.org/#/c/251974/ DocImpact: Update the docs that FWaaS no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them and the files generated now end with .sample extension. Change-Id: I31be3295606ba25929e9af9f40a035ff2b615234 Partially-Implements: blueprint autogen-neutron-conf-file Partial-bug: #1199963 Depends-On: Ic8208850a27408c8fbeed80ecdb43345aa7dfaa4 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1524510/+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 1524568] Re: Automatically generate neutron LBaaS configuration files
This bug seems to have been erroneously created by some automation. ** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1524568 Title: Automatically generate neutron LBaaS configuration files Status in neutron: Invalid Bug description: https://review.openstack.org/252981 commit e719861c00ab1e50e271c3bcdbc0b9130353d2d4 Author: Martin Hickey Date: Thu Dec 3 14:39:29 2015 + Automatically generate neutron LBaaS configuration files This adds a new tox environment, genconfig, which generates sample neutron LBaaS configuration file using oslo-config-generator. DocImpact: Update the docs that LBaaS no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them and the files generated now end with .sample extension. Partially-Implements: blueprint autogen-neutron-conf-file Change-Id: I25507f3bc6e995580aa91a912c2cf4110757df15 Partial-bug: #1199963 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1524568/+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 1524568] Re: Automatically generate neutron LBaaS configuration files
*** This bug is a duplicate of bug 1520722 *** https://bugs.launchpad.net/bugs/1520722 This was autogenerated because of DocImpact. Since the doc bug for the core patch covers fwaas, I am marking this as a duplicate. ** This bug has been marked a duplicate of bug 1520722 Automatically generate neutron core configuration files -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1524568 Title: Automatically generate neutron LBaaS configuration files Status in neutron: Invalid Bug description: https://review.openstack.org/252981 commit e719861c00ab1e50e271c3bcdbc0b9130353d2d4 Author: Martin Hickey Date: Thu Dec 3 14:39:29 2015 + Automatically generate neutron LBaaS configuration files This adds a new tox environment, genconfig, which generates sample neutron LBaaS configuration file using oslo-config-generator. DocImpact: Update the docs that LBaaS no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them and the files generated now end with .sample extension. Partially-Implements: blueprint autogen-neutron-conf-file Change-Id: I25507f3bc6e995580aa91a912c2cf4110757df15 Partial-bug: #1199963 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1524568/+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 1524510] Re: Remove Neutron FWaaS static example configuration files
*** This bug is a duplicate of bug 1520722 *** https://bugs.launchpad.net/bugs/1520722 Martin, no problem, it helped to weed out a messaging bug in the tooling: https://review.openstack.org/255715 Since the doc bug for the core patch covers fwaas, I am marking this as a duplicate. ** This bug has been marked a duplicate of bug 1520722 Automatically generate neutron core configuration files -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1524510 Title: Remove Neutron FWaaS static example configuration files Status in neutron: Invalid Bug description: https://review.openstack.org/254698 commit 6713d0ac33a8a6355b4263bde01d55c01636039b Author: Martin Hickey Date: Tue Dec 8 11:18:04 2015 + Remove Neutron FWaaS static example configuration files Oslo config generator was introduced in patch [1] to automatically generate the sample Neutron FWaaS configuration files. This patch removes the static example configuration files from the repository as they are now redundant. [1] https://review.openstack.org/#/c/251974/ DocImpact: Update the docs that FWaaS no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them and the files generated now end with .sample extension. Change-Id: I31be3295606ba25929e9af9f40a035ff2b615234 Partially-Implements: blueprint autogen-neutron-conf-file Partial-bug: #1199963 Depends-On: Ic8208850a27408c8fbeed80ecdb43345aa7dfaa4 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1524510/+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 1524661] Re: "neutron help net-update" shows insufficient parameter info
** Also affects: python-neutronclient
Importance: Undecided
Status: New
** No longer affects: neutron
** Changed in: python-neutronclient
Status: New => Confirmed
** Changed in: python-neutronclient
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1524661
Title:
"neutron help net-update" shows insufficient parameter info
Status in python-neutronclient:
Confirmed
Bug description:
update network name can work using "neutron net-update" command, but
in "neutron help net-update", it cannot show this parameter.
Setup:
centos liberty
Steps:
[root@46-37 ~(keystone_admin)]# neutron help net-update
usage: neutron net-update [-h] [--request-format {json,xml}]
[--qos-policy QOS_POLICY | --no-qos-policy]
NETWORK
Update network's information.
positional arguments:
NETWORK ID or name of network to update.
optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
The XML or JSON request format.
--qos-policy QOS_POLICY
Attach QoS policy ID or name to the resource.
--no-qos-policy Detach QoS policy from the resource.
[root@46-37 ~(keystone_admin)]# neutron net-show
7c32fd53-b138-4469-a1cb-580e6bffbac7
+---+--+
| Field | Value|
+---+--+
| admin_state_up| True |
| id| 7c32fd53-b138-4469-a1cb-580e6bffbac7 |
| mtu | 0|
| name | net-chen |
| provider:network_type | vxlan|
| provider:physical_network | |
| provider:segmentation_id | 92 |
| router:external | False|
| shared| False|
| status| ACTIVE |
| subnets | |
| tenant_id | 5e330189111048b9a74a76eea9a469ac |
+---+--+
[root@46-37 ~(keystone_admin)]# neutron net-update
7c32fd53-b138-4469-a1cb-580e6bffbac7 --name newnet
Updated network: 7c32fd53-b138-4469-a1cb-580e6bffbac7
[root@46-37 ~(keystone_admin)]# neutron net-show
7c32fd53-b138-4469-a1cb-580e6bffbac7
+---+--+
| Field | Value|
+---+--+
| admin_state_up| True |
| id| 7c32fd53-b138-4469-a1cb-580e6bffbac7 |
| mtu | 0|
| name | newnet |
| provider:network_type | vxlan|
| provider:physical_network | |
| provider:segmentation_id | 92 |
| router:external | False|
| shared| False|
| status| ACTIVE |
| subnets | |
| tenant_id | 5e330189111048b9a74a76eea9a469ac |
+---+--+
Expected result:
here is a good example for neutron subnet-update
[root@46-37 ~(keystone_admin)]# neutron help subnet-update
usage: neutron subnet-update [-h] [--request-format {json,xml}] [--name NAME]
[--gateway GATEWAY_IP | --no-gateway]
[--allocation-pool start=IP_ADDR,end=IP_ADDR]
[--host-route destination=CIDR,nexthop=IP_ADDR]
[--dns-nameserver DNS_NAMESERVER]
[--disable-dhcp] [--enable-dhcp]
SUBNET
Update subnet's information.
positional arguments:
SUBNETID or name of subnet to update.
optional arguments:
-h, --helpshow this help message and exit
--request-format {json,xml}
The XML or JSON request format.
--name NAME Name of this subnet.
--gateway GATEWAY_IP Gateway IP
[Yahoo-eng-team] [Bug 1524671] Re: Added CORS support to Neutron
** Also affects: openstack-manuals Importance: Undecided Status: New ** Changed in: neutron Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1524671 Title: Added CORS support to Neutron Status in neutron: Fix Released Status in openstack-manuals: New Bug description: https://review.openstack.org/236988 \Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to. commit 7f65b06033afca20399305f285ff5e6d43c5131c Author: Michael Krotscheck Date: Mon Oct 19 06:52:04 2015 -0700 Added CORS support to Neutron This adds the CORS support middleware to Neutron, allowing a deployer to optionally configure rules under which a javascript client may break the single-origin policy and access the API directly. For neutron, both the paste.ini and the direct-wrap method of deploying the middleware were chosen, since neutron is in a state of migration to pecan. Note that if someone deploys pecan-neutron behind other middleware, any responses provided by that middleware will not be CORS-enabled, as these responses would be returned before the headers could be annotated. This results in a response not readable by the user agent. OpenStack CrossProject Spec: http://specs.openstack.org/openstack/openstack-specs/specs/cors-support.html Oslo_Middleware Docs: http://docs.openstack.org/developer/oslo.middleware/cors.html OpenStack Cloud Admin Guide: http://docs.openstack.org/admin-guide-cloud/cross_project_cors.html DocImpact: Add link to CORS configuration in admin cloud guide. Change-Id: I02acea6124d28370d92e7c94ca2d1d6c5c8937ac To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1524671/+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 1524510] Re: Remove Neutron FWaaS static example configuration files
Removed duplicate since docs for *aaS are separate. ** This bug is no longer a duplicate of bug 1520722 Automatically generate neutron core configuration files ** Also affects: openstack-manuals Importance: Undecided Status: New ** Description changed: + DocImpact for FWaaS + https://review.openstack.org/254698 commit 6713d0ac33a8a6355b4263bde01d55c01636039b Author: Martin Hickey Date: Tue Dec 8 11:18:04 2015 + - Remove Neutron FWaaS static example configuration files - - Oslo config generator was introduced in patch [1] to - automatically generate the sample Neutron FWaaS configuration - files. - - This patch removes the static example configuration files from - the repository as they are now redundant. - - [1] https://review.openstack.org/#/c/251974/ - - DocImpact: Update the docs that FWaaS no longer includes static example - configuration files. Instead, use tools/generate_config_file_samples.sh - to generate them and the files generated now end with .sample extension. - - Change-Id: I31be3295606ba25929e9af9f40a035ff2b615234 - Partially-Implements: blueprint autogen-neutron-conf-file - Partial-bug: #1199963 - Depends-On: Ic8208850a27408c8fbeed80ecdb43345aa7dfaa4 + Remove Neutron FWaaS static example configuration files + + Oslo config generator was introduced in patch [1] to + automatically generate the sample Neutron FWaaS configuration + files. + + This patch removes the static example configuration files from + the repository as they are now redundant. + + [1] https://review.openstack.org/#/c/251974/ + + DocImpact: Update the docs that FWaaS no longer includes static example + configuration files. Instead, use tools/generate_config_file_samples.sh + to generate them and the files generated now end with .sample extension. + + Change-Id: I31be3295606ba25929e9af9f40a035ff2b615234 + Partially-Implements: blueprint autogen-neutron-conf-file + Partial-bug: #1199963 + Depends-On: Ic8208850a27408c8fbeed80ecdb43345aa7dfaa4 ** Changed in: neutron Status: Invalid => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1524510 Title: Remove Neutron FWaaS static example configuration files Status in neutron: Fix Released Status in openstack-manuals: New Bug description: DocImpact for FWaaS https://review.openstack.org/254698 commit 6713d0ac33a8a6355b4263bde01d55c01636039b Author: Martin Hickey Date: Tue Dec 8 11:18:04 2015 + Remove Neutron FWaaS static example configuration files Oslo config generator was introduced in patch [1] to automatically generate the sample Neutron FWaaS configuration files. This patch removes the static example configuration files from the repository as they are now redundant. [1] https://review.openstack.org/#/c/251974/ DocImpact: Update the docs that FWaaS no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them and the files generated now end with .sample extension. Change-Id: I31be3295606ba25929e9af9f40a035ff2b615234 Partially-Implements: blueprint autogen-neutron-conf-file Partial-bug: #1199963 Depends-On: Ic8208850a27408c8fbeed80ecdb43345aa7dfaa4 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1524510/+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 1524568] Re: Automatically generate neutron LBaaS configuration files
Removed duplicate since docs for *aaS are separate. ** This bug is no longer a duplicate of bug 1520722 Automatically generate neutron core configuration files ** Description changed: + DocImpact for LBaaS + https://review.openstack.org/252981 commit e719861c00ab1e50e271c3bcdbc0b9130353d2d4 Author: Martin Hickey Date: Thu Dec 3 14:39:29 2015 + - Automatically generate neutron LBaaS configuration files - - This adds a new tox environment, genconfig, which generates sample - neutron LBaaS configuration file using oslo-config-generator. - - DocImpact: Update the docs that LBaaS no longer includes static example - configuration files. Instead, use tools/generate_config_file_samples.sh - to generate them and the files generated now end with .sample extension. - - Partially-Implements: blueprint autogen-neutron-conf-file - - Change-Id: I25507f3bc6e995580aa91a912c2cf4110757df15 - Partial-bug: #1199963 + Automatically generate neutron LBaaS configuration files + + This adds a new tox environment, genconfig, which generates sample + neutron LBaaS configuration file using oslo-config-generator. + + DocImpact: Update the docs that LBaaS no longer includes static example + configuration files. Instead, use tools/generate_config_file_samples.sh + to generate them and the files generated now end with .sample extension. + + Partially-Implements: blueprint autogen-neutron-conf-file + + Change-Id: I25507f3bc6e995580aa91a912c2cf4110757df15 + Partial-bug: #1199963 ** Also affects: openstack-manuals Importance: Undecided Status: New ** Changed in: neutron Status: Invalid => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1524568 Title: Automatically generate neutron LBaaS configuration files Status in neutron: Fix Released Status in openstack-manuals: New Bug description: DocImpact for LBaaS https://review.openstack.org/252981 commit e719861c00ab1e50e271c3bcdbc0b9130353d2d4 Author: Martin Hickey Date: Thu Dec 3 14:39:29 2015 + Automatically generate neutron LBaaS configuration files This adds a new tox environment, genconfig, which generates sample neutron LBaaS configuration file using oslo-config-generator. DocImpact: Update the docs that LBaaS no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them and the files generated now end with .sample extension. Partially-Implements: blueprint autogen-neutron-conf-file Change-Id: I25507f3bc6e995580aa91a912c2cf4110757df15 Partial-bug: #1199963 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1524568/+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 1525319] [NEW] Cisco apic router_id field length incorrectly changed for Mitaka
Public bug reported: Bug #1465678 was intended to be included in Liberty but it did not make it into the Liberty release. The neutron patch must be reverted and instead the field size change must be done in the vendor repo for the Mitaka release. ** Affects: networking-cisco Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: In Progress ** Tags: cisco db ** Tags added: cisco ** Tags added: db ** Also affects: networking-cisco Importance: Undecided Status: New ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) ** Changed in: networking-cisco Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1525319 Title: Cisco apic router_id field length incorrectly changed for Mitaka Status in networking-cisco: New Status in neutron: In Progress Bug description: Bug #1465678 was intended to be included in Liberty but it did not make it into the Liberty release. The neutron patch must be reverted and instead the field size change must be done in the vendor repo for the Mitaka release. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-cisco/+bug/1525319/+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 1525424] Re: Automatically generate neutron VPNaaS configuration files
** Also affects: openstack-manuals Importance: Undecided Status: New ** Changed in: neutron Status: New => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1525424 Title: Automatically generate neutron VPNaaS configuration files Status in neutron: Fix Released Status in openstack-manuals: New Bug description: https://review.openstack.org/253399 Dear bug triager. This bug was created since a commit was marked with DOCIMPACT. commit 5c8941eeed6dabc9c467c8b9b11df79a25dd2c71 Author: Martin Hickey Date: Fri Dec 4 09:10:04 2015 + Automatically generate neutron VPNaaS configuration files This adds a new tox environment, genconfig, which generates sample neutron VPNaaS configuration file using oslo-config-generator. Updates to some configuration option help messages to reflect useful details that were missing in the code but were present in config files. DocImpact: Update the docs that VPNaaS no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them and the files generated now end with .sample extension. Partially-Implements: blueprint autogen-neutron-conf-file Change-Id: I4a6094b8218dfd320d05bfb1e3bc121e8930c551 Partial-bug: #1199963 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1525424/+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 1526108] Re: Octavia devstack install fails behind proxy
** Also affects: octavia
Importance: Undecided
Status: New
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1526108
Title:
Octavia devstack install fails behind proxy
Status in octavia:
New
Bug description:
The octavia devstack/plugin.sh script does a sudo pip install without
passing the user environment, meaning settings like
http_proxy/https_proxy are not passed and keeping the devstack from
working behind a proxy that needs those settings for pip installs if
set for the user only.
function octavia_install {
setup_develop $OCTAVIA_DIR
if ! [ "$DISABLE_AMP_IMAGE_BUILD" == 'True' ]; then
install_package qemu kpartx
git_clone https://git.openstack.org/openstack/diskimage-builder.git
$DE\
ST/diskimage-builder master
git_clone
https://git.openstack.org/openstack/tripleo-image-elements.gi\
t $DEST/tripleo-image-elements master
sudo pip install -r $DEST/diskimage-builder/requirements.txt
fi
The user could explicitly set http_proxy/https_proxy settings for root
as well to avoid the issue. But this error takes a long time to come
to when using client only proxy settings until octavia diskimage build
sudo fails.
Other services such as devstack/install_pip.sh do pass the user
enviornment to sudo with the -E flag. Suggested fix is to pass the
'-E' flag in this situation as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/octavia/+bug/1526108/+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 1367552] [NEW] Cisco test cases are using _do_side_effect() which has been renamed
Public bug reported: In https://review.openstack.org/78880 NeutronDbPluginV2TestCase._do_side_effect() was renamed to _fail_second_call(). But some cisco nexus test cases still use the old name. ** Affects: neutron Importance: Undecided Assignee: Henry Gessau (gessau) Status: New ** Changed in: neutron Assignee: (unassigned) => Henry Gessau (gessau) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1367552 Title: Cisco test cases are using _do_side_effect() which has been renamed Status in OpenStack Neutron (virtual network service): New Bug description: In https://review.openstack.org/78880 NeutronDbPluginV2TestCase._do_side_effect() was renamed to _fail_second_call(). But some cisco nexus test cases still use the old name. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1367552/+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
