[Yahoo-eng-team] [Bug 1608691] Re: exception translation for pymysql "Lock wait timeout exceeded" broken
Oslo.db fixes are here:
https://review.openstack.org/#/q/3277ef33f2a1f6a892f0832e2907acef7b45dc2b,n,z
** Changed in: oslo.db
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/1608691
Title:
exception translation for pymysql "Lock wait timeout exceeded" broken
Status in neutron:
In Progress
Status in oslo.db:
Fix Released
Bug description:
It looks like the classifier for "lock wait timeout exceeded" as a
DBDeadlock is not correct for pymysql. Snippet of traceback showing it
as the generic DBError:
2016-07-31 00:21:14.938 4145 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/pymysql/err.py", line 120, in
raise_mysql_exception
2016-07-31 00:21:14.938 4145 ERROR neutron.api.v2.resource
_check_mysql_exception(errinfo)
2016-07-31 00:21:14.938 4145 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/pymysql/err.py", line 115, in
_check_mysql_exception
2016-07-31 00:21:14.938 4145 ERROR neutron.api.v2.resource raise
InternalError(errno, errorvalue)
2016-07-31 00:21:14.938 4145 ERROR neutron.api.v2.resource DBError:
(pymysql.err.InternalError) (1205, u'Lock wait timeout exceeded; try restarting
transaction') [SQL: u'SELECT ipavailabilityranges.allocation_pool_id AS
ipavailabilityranges_allocation_pool_id, ipavailabilityranges.first_ip AS
ipavailabilityranges_first_ip, ipavailabilityranges.last_ip AS
ipavailabilityranges_last_ip \nFROM ipavailabilityranges INNER JOIN
ipallocationpools ON ipallocationpools.id =
ipavailabilityranges.allocation_pool_id \nWHERE ipallocationpools.subnet_id =
%(subnet_id_1)s \n LIMIT %(param_1)s FOR UPDATE'] [parameters: {u'param_1': 1,
u'subnet_id_1': u'344485c9-e600-40c0-8acf-d9ba98dacf99'}]
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1608691/+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 1612529] [NEW] [network] nova with neutron can not inject ip address to vm
Public bug reported: Description === With neutron, Although the subnet is not dhcp, we can not inject netconfig to guestos. Steps to reproduce == create a subnet with disable dhcp. create a vm with the network and keep config-drive true Expected result === we can see net config info in directory of content/ Actual result = no file of content/ Environment === Kilo ** Affects: nova Importance: Undecided Assignee: xhzhf (guoyongxhzhf) Status: New ** Tags: neutron ** Changed in: nova Assignee: (unassigned) => xhzhf (guoyongxhzhf) ** Tags added: neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1612529 Title: [network] nova with neutron can not inject ip address to vm Status in OpenStack Compute (nova): New Bug description: Description === With neutron, Although the subnet is not dhcp, we can not inject netconfig to guestos. Steps to reproduce == create a subnet with disable dhcp. create a vm with the network and keep config-drive true Expected result === we can see net config info in directory of content/ Actual result = no file of content/ Environment === Kilo To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1612529/+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 1612433] Re: neutron-db-manage autogenerate is generating empty upgrades
To have migration autogenerated we need to pass --autogenerate and --expand/contract: not allowed with argument --autogenerate. .tox/py27/bin/neutron-db-manage --config-file /etc/neutron/neutron.conf revision -m 'test' --autogenerate Running revision for neutron ... INFO [alembic.runtime.migration] Context impl PostgresqlImpl. INFO [alembic.runtime.migration] Will assume transactional DDL. INFO [alembic.ddl.postgresql] Detected sequence named 'nsxv_edge_vnic_bindings_vnic_index_seq' as owned by integer column 'nsxv_edge_vnic_bindings(vnic_index)', assuming $ERIAL and omitting INFO [alembic.ddl.postgresql] Detected sequence named 'ml2_ucsm_port_profiles_vlan_id_seq' as owned by integer column 'ml2_ucsm_port_profiles(vlan_id)', assuming SERIAL a$d omitting INFO [alembic.ddl.postgresql] Detected sequence named 'routerrules_id_seq' as owned by integer column 'routerrules(id)', assuming SERIAL and omitting INFO [alembic.ddl.postgresql] Detected sequence named 'cisco_ml2_nexus_nve_vni_seq' as owned by integer column 'cisco_ml2_nexus_nve(vni)', assuming SERIAL and omitting INFO [alembic.ddl.postgresql] Detected sequence named 'cisco_ml2_nexusport_bindings_binding_id_seq' as owned by integer column 'cisco_ml2_nexusport_bindings(binding_id)', assuming SERIAL and omitting INFO [alembic.ddl.postgresql] Detected sequence named 'ha_router_vrid_allocations_vr_id_seq' as owned by integer column 'ha_router_vrid_allocations(vr_id)', assuming SERI$L and omitting INFO [alembic.autogenerate.compare] Detected added column 'ha_router_agent_port_bindings.test' Generating /opt/stack/neutron/neutron/db/migration/alembic_migrations/versions/newton/expand/ce2aa5e76b04_test.py ... done OK So, I think this bug is not valid as if we use autogenerate, it will generate migration in expand or contract branch itself, and --expand/contract are used for creation just empty migrations. ** 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/1612433 Title: neutron-db-manage autogenerate is generating empty upgrades Status in networking-arista: New Status in neutron: Invalid Bug description: The alembic autogenerate wrapper, neutron-db-manage revision -m "description" --[contract|expand] is no longer collecting model/migration diffs and is generating empty upgrade scripts. Not sure when this broke. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-arista/+bug/1612433/+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 1611627] Re: revision plugin throwing objectdeletederror
Reviewed: https://review.openstack.org/353277 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9e8bcf45a53718da588e70785c77dd7215e12017 Submitter: Jenkins Branch:master commit 9e8bcf45a53718da588e70785c77dd7215e12017 Author: Kevin Benton Date: Fri Aug 5 16:25:29 2016 -0700 Make revision bump robust to concurrent removals If there expired objects in the session that are concurrently deleted by another sesssion, the revision code will get an ObjectDeletedError when it goes to check if the expired object is a related object to the object it is handling. So we need to catch this error an continue on since there is nothing it needs to do. Change-Id: Ie6034f36c34099f2646840cbdd569a4398534df5 Closes-Bug: #1611627 ** 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/1611627 Title: revision plugin throwing objectdeletederror Status in neutron: Fix Released Bug description: If there is an expired object in the session that got concurrently deleted by another session, the revision plugin may throw an ObjectDeletedError when it goes to bump the revision and references expired attributes (causing a DB lookup that returns nothing). 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource [req-c1b008ba-a6a7-4ac0-bb71-baf27253e098 tempest-NetworksTestDHCPv6-139641 -] create failed: No details. 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource Traceback (most recent call last): 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/opt/stack/new/neutron/neutron/api/v2/resource.py", line 79, in resource 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource result = method(request=request, **args) 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/opt/stack/new/neutron/neutron/api/v2/base.py", line 397, in create 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource return self._create(request, body, **kwargs) 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 151, in wrapper 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource ectxt.value = e.inner_exc 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource self.force_reraise() 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 139, in wrapper 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource return f(*args, **kwargs) 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/opt/stack/new/neutron/neutron/api/v2/base.py", line 510, in _create 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource obj = do_create(body) 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/opt/stack/new/neutron/neutron/api/v2/base.py", line 492, in do_create 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource request.context, reservation.reservation_id) 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource self.force_reraise() 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/opt/stack/new/neutron/neutron/api/v2/base.py", line 485, in do_create 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource return obj_creator(request.context, **kwargs) 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/opt/stack/new/neutron/neutron/common/utils.py", line 613, in inner 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource return f(self, context, *args, **kwargs) 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource File "/opt/stack/new/neutron/neutron/plugins/ml2/plugin.py", line 977, in create_subnet 2016-08-09 23:57:02.093 17791 ERROR neutron.api.v2.resource result, mech_context = self._create_subnet_db(context, subnet) 2016-08-09 23:57:02.093
[Yahoo-eng-team] [Bug 1612615] [NEW] test_get_allocated_net_topology_as_tenant failure in api job
Public bug reported: http://logs.openstack.org/12/354612/1/check/gate-neutron-dsvm- api/09c5da5/testr_results.html.gz Traceback (most recent call last): File "/opt/stack/new/neutron/neutron/tests/tempest/api/test_auto_allocated_topology.py", line 95, in test_get_allocated_net_topology_as_tenant self.assertEqual((1, self.num_subnetpools, 1), resources_after1) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 411, in assertEqual self.assertThat(observed, matcher, message) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: (1, 2, 1) != (1, 4, 1) Logstash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22in%20test_get_allocated_net_topology_as_tenant%5C%22 3 hits in 7 days. ** Affects: neutron Importance: High Status: New ** Tags: gate-failure tempest ** Changed in: neutron Importance: Undecided => High ** Tags added: api gate-failure ** Tags removed: api ** Tags added: tempest -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1612615 Title: test_get_allocated_net_topology_as_tenant failure in api job Status in neutron: New Bug description: http://logs.openstack.org/12/354612/1/check/gate-neutron-dsvm- api/09c5da5/testr_results.html.gz Traceback (most recent call last): File "/opt/stack/new/neutron/neutron/tests/tempest/api/test_auto_allocated_topology.py", line 95, in test_get_allocated_net_topology_as_tenant self.assertEqual((1, self.num_subnetpools, 1), resources_after1) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 411, in assertEqual self.assertThat(observed, matcher, message) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: (1, 2, 1) != (1, 4, 1) Logstash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22in%20test_get_allocated_net_topology_as_tenant%5C%22 3 hits in 7 days. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1612615/+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 1611533] Re: ml2 transaction_guard broke out of tree plugins
Reviewed: https://review.openstack.org/353236
Committed:
https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=616aff852c03a8bdf13c9c3af62dcafaec3a52fa
Submitter: Jenkins
Branch:master
commit 616aff852c03a8bdf13c9c3af62dcafaec3a52fa
Author: YAMAMOTO Takashi
Date: Wed Aug 10 12:40:48 2016 +0900
Specify GUARD_TRANSACTION=False where necessary
Closes-Bug: #1611533
Depends-On: I5aa099c2264636336ab0b76c0826b506e2dc44b6
Change-Id: I7afcad9acafbe7333f5bdbec8827d87d508f14da
** Changed in: networking-midonet
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/1611533
Title:
ml2 transaction_guard broke out of tree plugins
Status in networking-midonet:
Fix Released
Status in neutron:
In Progress
Bug description:
recent change [1] broke l3 plugin for networking-midonet.
[1] I9924600c57648f7eccaa5abb6979419d9547a2ff
l3 plugins for networking-odl and dragonflow seem to have similar code
and would be affected too.
eg.
http://logs.openstack.org/87/199387/36/check/gate-tempest-dsvm-networking-midonet-ml2/ceb0331/logs/q-svc.txt.gz?level=TRACE
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource
[req-af588d02-2944-411f-aa22-eafca4fdabeb
tempest-TestSecurityGroupsBasicOps-509565194 -] remove_router_interface failed:
No details.
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource Traceback (most
recent call last):
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/opt/stack/new/neutron/neutron/api/v2/resource.py", line 79, in resource
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource result =
method(request=request, **args)
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 151, in wrapper
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource ectxt.value =
e.inner_exc
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in
__exit__
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource
self.force_reraise()
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in
force_reraise
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource
six.reraise(self.type_, self.value, self.tb)
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/oslo_db/api.py", line 139, in wrapper
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource return
f(*args, **kwargs)
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/opt/stack/new/neutron/neutron/api/v2/base.py", line 217, in _handle_action
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource ret_value =
getattr(self._plugin, name)(*arg_list, **kwargs)
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/oslo_log/helpers.py", line 48, in
wrapper
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource return
method(*args, **kwargs)
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/opt/stack/new/networking-midonet/midonet/neutron/services/l3/l3_midonet.py",
line 190, in remove_router_interface
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource context,
router_id, interface_info)
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/opt/stack/new/neutron/neutron/db/l3_db.py", line 1756, in
remove_router_interface
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource context,
router_id, interface_info)
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/opt/stack/new/neutron/neutron/db/l3_db.py", line 924, in
remove_router_interface
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource context,
router_id, subnet_id, device_owner)
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/opt/stack/new/neutron/neutron/db/l3_db.py", line 901, in
_remove_interface_by_subnet
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource
l3_port_check=False)
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource File
"/opt/stack/new/neutron/neutron/common/utils.py", line 611, in inner
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource raise
RuntimeError(_("Method cannot be called within a "
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource RuntimeError:
Method cannot be called within a transaction.
2016-08-09 12:31:57.844 25876 ERROR neutron.api.v2.resource
2016-08-09 12:31:58.293 25876 ERROR neutron.api.v2.resource
[req-c9ae4bf8-2baf-4327-be58-bb3006b4d9c9
tempest-TestSecurityGroupsBasicOps-21125
[Yahoo-eng-team] [Bug 1612644] [NEW] not use ssl key and ca when connect to glance
Public bug reported:
had those errors when on compute node and set ssl_cert_file and ssl_key_file to
a file name in nova.conf but it doesn't exist, https clinet should not use
those , only ssl_ca_file is enough
like
https://github.com/openstack/nova/blob/master/nova/api/metadata/vendordata_dynamic.py#L69
- #L76
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 3077, in
_snapshot_instance
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher
update_task_state)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/virt/zvm/driver.py", line 825, in
snapshot
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher
image_meta = image_service.show(context, image_href)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/image/glance.py", line 311, in show
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher
_reraise_translated_image_exception(image_id)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/image/glance.py", line 607, in
_reraise_translated_image_exception
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher
six.reraise(new_exc, None, exc_trace)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/image/glance.py", line 309, in show
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher image =
self._client.call(context, version, 'get', image_id)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/image/glance.py", line 228, in call
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher version)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/image/glance.py", line 209, in
_create_onetime_client
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher
self.use_ssl, version)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/image/glance.py", line 132, in
_create_glance_client
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher
sslutils.is_enabled(CONF)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/oslo_service/sslutils.py", line 44, in
is_enabled
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher raise
RuntimeError(_("Unable to find cert_file : %s") % cert_file)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher RuntimeError:
Unable to find cert_file : /etc/nova/ssl/certs/nova.pem
** Affects: nova
Importance: Low
Assignee: jichenjc (jichenjc)
Status: New
** Changed in: nova
Assignee: (unassigned) => jichenjc (jichenjc)
** Changed in: nova
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1612644
Title:
not use ssl key and ca when connect to glance
Status in OpenStack Compute (nova):
New
Bug description:
had those errors when on compute node and set ssl_cert_file and ssl_key_file
to a file name in nova.conf but it doesn't exist, https clinet should not use
those , only ssl_ca_file is enough
like
https://github.com/openstack/nova/blob/master/nova/api/metadata/vendordata_dynamic.py#L69
- #L76
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 3077, in
_snapshot_instance
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher
update_task_state)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/virt/zvm/driver.py", line 825, in
snapshot
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher
image_meta = image_service.show(context, image_href)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/image/glance.py", line 311, in show
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher
_reraise_translated_image_exception(image_id)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/image/glance.py", line 607, in
_reraise_translated_image_exception
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher
six.reraise(new_exc, None, exc_trace)
2016-08-11 10:53:19.924 11266 ERROR oslo_messaging.rpc.dispatcher File
"/usr/lib/python2.7/site-packages/nova/image/glance.py", line 309, in show
2016-08-11 10:53:19.924
[Yahoo-eng-team] [Bug 1612656] [NEW] documentation problem regarding user groups
Public bug reported: In the latest documentation examples, the first example has an apparent error on line 14. http://cloudinit.readthedocs.io/en/latest/topics/examples.html ``` # Add users to the system. Users are added after groups are added. users: - default - name: foobar gecos: Foo B. Bar primary-group: foobar groups: users ``` It shows that a string is an acceptable value for the `groups` key. On line 23, it shows another string with comma-separated values. Both of these values cause errors. The `groups` key requires an array, even if there is only one value. This is implied at line 109, but not explicitly stated. Please fix? thanks! Sunil ** Affects: cloud-init Importance: Undecided Status: New ** Tags: documentation -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1612656 Title: documentation problem regarding user groups Status in cloud-init: New Bug description: In the latest documentation examples, the first example has an apparent error on line 14. http://cloudinit.readthedocs.io/en/latest/topics/examples.html ``` # Add users to the system. Users are added after groups are added. users: - default - name: foobar gecos: Foo B. Bar primary-group: foobar groups: users ``` It shows that a string is an acceptable value for the `groups` key. On line 23, it shows another string with comma-separated values. Both of these values cause errors. The `groups` key requires an array, even if there is only one value. This is implied at line 109, but not explicitly stated. Please fix? thanks! Sunil To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1612656/+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 1607787] Re: Missing secure fail mode on physical bridges
Reviewed: https://review.openstack.org/348889 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9429c2da01fa29cedcb2a65a26c1c29d0a713670 Submitter: Jenkins Branch:master commit 9429c2da01fa29cedcb2a65a26c1c29d0a713670 Author: Hynek Mlnarik Date: Wed Aug 10 10:05:57 2016 +0200 Set secure fail mode for physical bridges Physical bridges can cause network disruption when ofctl controller becomes inaccessible due to heavy load or when the traffic to controller is blocked. By setting secure fail mode, the openflow rules remain untouched on such an event, while with the default setting, the flows are cleared. Co-Authored-By: Jakub Libosvar Closes-Bug: 1607787 Change-Id: I1dffe0a248664d2a675fd1ca58530c233e335d2d UpgradeImpact ** 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/1607787 Title: Missing secure fail mode on physical bridges Status in neutron: Fix Released Bug description: Restarting current ovs neutron agent under a heavy load with Ryu (ofctl=native) leads intermittently to disruption of traffic as manifested by occasional failures in not-yet-commited fullstack test [1]. More specifically, the reason seems to be too slow restart of Ryu controller in combination with OVS vswitchd timeouts. The disruption of the traffic occurs always after the following log entry is recorded in ovs-vswitchd.log: fail_open|WARN|Could not connect to controller (or switch failed controller's post-connection admission control policy) for 15 seconds, failing open This issue is manifested regardless of network type (VLAN, flat) and vsctl interface (cli, native). It has not occured with ofctl=cli though. The issue occurs for physical switches as they are in default fail mode, meaning that once controller connection is lost, ovs takes over the management of the flows and clears them. This conclusion is based on flows dumped from situation just before the traffic was blocked and after that event when flows were cleared. Before the event: == br-eth23164fdb4 === Fri Jul 29 10:44:04 UTC 2016 OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0x921fc02d0b4f49e1, duration=16.137s, table=0, n_packets=16, n_bytes=1400, priority=4,in_port=2,dl_vlan=1 actions=set_field:5330->vlan_vid,NORMAL cookie=0x921fc02d0b4f49e1, duration=25.647s, table=0, n_packets=6, n_bytes=508, priority=2,in_port=2 actions=drop cookie=0x921fc02d0b4f49e1, duration=26.250s, table=0, n_packets=16, n_bytes=1400, priority=0 actions=NORMAL After the disruption: == br-eth23164fdb4 === Fri Jul 29 10:44:05 UTC 2016 OFPST_FLOW reply (OF1.3) (xid=0x2): The same bug apperars in this condition (courtesy of Jakub Libosvar): setup a phys bridge, block the traffic for the respective bridge controller via iptables until OVS timeout occurs, and then check openflow rules of the affected bridge. [1] https://review.openstack.org/#/c/334926/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1607787/+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 1596573] Re: warlock 1.3.0 breaks a few gates
Reviewed: https://review.openstack.org/338630
Committed:
https://git.openstack.org/cgit/openstack/python-glanceclient/commit/?id=d7db97c92605a11e312d17cdcdd8ac363bc10924
Submitter: Jenkins
Branch:master
commit d7db97c92605a11e312d17cdcdd8ac363bc10924
Author: Sabari Kumar Murugesan
Date: Wed Jul 6 18:02:28 2016 -0700
Fix warlock model creation
Commands like glance md-namespace-show fail because
of a breaking change in warlock 1.3.0's model creation factory
method.
Warlock introduced a new kwarg 'resolver' in model_factory method
but changed its position with the 'base_class' kwarg. Since we
were calling the model_factory method with positional arg, this
broke the model creation.
Closes-Bug: #1596573
Change-Id: Ic7821f4fdb1b752e0c7ed2bc486299a06bf485c1
** Changed in: python-glanceclient
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1596573
Title:
warlock 1.3.0 breaks a few gates
Status in OpenStack Dashboard (Horizon):
New
Status in python-glanceclient:
Fix Released
Status in python-openstackclient:
Fix Released
Status in OpenStack Search (Searchlight):
New
Bug description:
Our functional test
functional.tests.image.v2.test_image.ImageTests.test_image_unset is
now failing:
Captured traceback:
~~~
Traceback (most recent call last):
File "functional/tests/image/v2/test_image.py", line 71, in test_image_unset
self.openstack('image set --tag 01 ' + self.NAME)
File "functional/common/test.py", line 53, in openstack
return execute('openstack ' + cmd, fail_ok=fail_ok)
File "functional/common/test.py", line 42, in execute result_err)
tempest.lib.exceptions.CommandFailed: Command 'openstack image set --tag 01
7fbbb8c5da634c54aea88473e4e3c16b' returned non-zero exit status 1.
stdout:
stderr:
WARNING: openstackclient.common.utils is deprecated and will be removed after
Jun 2017. Please use osc_lib.utils
400 Bad Request
Invalid JSON pointer for this resource: '/tags/0'
(HTTP 400)
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1596573/+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 1612697] [NEW] ovs agent not ready ports should be listed as current
Public bug reported:
The ports that are not ready yet, shouldn't be listed as current ports,
see port log snippet
2016-08-12 15:00:44.593 12779 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Port
ca63b83a-763c-402c-84f2-7f28ccbf87e3 not ready yet on the bridge _process_port
neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:1303
2016-08-12 15:00:44.596 12779 DEBUG neutron.agent.linux.async_process [-]
Output received from [ovsdb-client monitor Interface name,ofport,external_ids
--format=json]:
{"data":[["9438e335-d7ce-47de-9888-2a96085b3bdf","old",null,["set",[]],null],["","new","trunk",2,["map",[["attached-mac","fa:16:3e:86:71:81"],["iface-id","ca63b83a-763c-402c-84f2-7f28ccbf87e3"],["iface-status","active"],"headings":["row","action","name","ofport","external_ids"]}
_read_stdout neutron/agent/linux/async_process.py:237
2016-08-12 15:00:44.629 12779 WARNING neutron.agent.linux.interface
[req-60d7c1c6-a0b3-4581-ac34-a52d7f36b53c - - - - -] No MTU configured for port
ca63b83a-763c-402c-84f2-7f28ccbf87e3
2016-08-12 15:00:45.619 12779 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Starting to
process devices in:{'removed': set([]), 'added':
set([u'ca63b83a-763c-402c-84f2-7f28ccbf87e3']), 'current':
set([u'ca63b83a-763c-402c-84f2-7f28ccbf87e3'])} rpc_loop
neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:2048
** 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/1612697
Title:
ovs agent not ready ports should be listed as current
Status in neutron:
New
Bug description:
The ports that are not ready yet, shouldn't be listed as current
ports, see port log snippet
2016-08-12 15:00:44.593 12779 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Port
ca63b83a-763c-402c-84f2-7f28ccbf87e3 not ready yet on the bridge _process_port
neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:1303
2016-08-12 15:00:44.596 12779 DEBUG neutron.agent.linux.async_process [-]
Output received from [ovsdb-client monitor Interface name,ofport,external_ids
--format=json]:
{"data":[["9438e335-d7ce-47de-9888-2a96085b3bdf","old",null,["set",[]],null],["","new","trunk",2,["map",[["attached-mac","fa:16:3e:86:71:81"],["iface-id","ca63b83a-763c-402c-84f2-7f28ccbf87e3"],["iface-status","active"],"headings":["row","action","name","ofport","external_ids"]}
_read_stdout neutron/agent/linux/async_process.py:237
2016-08-12 15:00:44.629 12779 WARNING neutron.agent.linux.interface
[req-60d7c1c6-a0b3-4581-ac34-a52d7f36b53c - - - - -] No MTU configured for port
ca63b83a-763c-402c-84f2-7f28ccbf87e3
2016-08-12 15:00:45.619 12779 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Starting to
process devices in:{'removed': set([]), 'added':
set([u'ca63b83a-763c-402c-84f2-7f28ccbf87e3']), 'current':
set([u'ca63b83a-763c-402c-84f2-7f28ccbf87e3'])} rpc_loop
neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:2048
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1612697/+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 1204956] Re: Read-only API for default quotas
Reviewed: https://review.openstack.org/313134 Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=d45442b3d46b26d928a5634874530168f961bb2b Submitter: Jenkins Branch:master commit d45442b3d46b26d928a5634874530168f961bb2b Author: Abhishek Raut Date: Tue May 3 05:17:12 2016 -0700 Add support to expose default quotas for tenants Neutron client should be able to show the default quotas set for tenants. This patch adds support for the same and introduces a new CLI to retrieve default quotas. Sample usage: neutron quota-default-show +---+---+ | Field | Value | +---+---+ | floatingip| 50| | l2-gateway-connection | -1| | network | 10| | port | 50| | rbac_policy | 10| | router| 10| | security_group| 10| | security_group_rule | 100 | | subnet| 10| | subnetpool| -1| +---+---+ Change-Id: Ie92c22862d2b8ace32a2cf4cb642a6d0bac7932d Closes-Bug: #1204956 ** Changed in: python-neutronclient 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/1204956 Title: Read-only API for default quotas Status in neutron: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: In Progress Status in OpenStack SDK: Fix Released Bug description: Having a read-only API to access the default quotas, similar to `nova quota-defaults` would be helpful to API consumers like Horizon (see e.g. bug 1109140). As far as I can tell, there is no way to get to this information at the moment. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1204956/+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 1612742] [NEW] incorrect references of s3 in migration scripts
Public bug reported: We have removed s3 references in patch https://review.openstack.org/#/c/348507/ However there are a few incorrect references of s3 in the below mentioned migration scripts. We have a project policy to not modify the migration scripts unless a significant impact exists. http://docs.openstack.org/developer/glance/contributing/minor-code- changes.html#database-migration-scripts So, this bug has been opened to gather feedback / opinions on the need for this change. https://github.com/openstack/glance/blob/d0f4316752d313bffeafd2be0283201813e1e9a2/glance/db/sqlalchemy/migrate_repo/versions/015_quote_swift_credentials.py#L157 https://github.com/openstack/glance/blob/d0f4316752d313bffeafd2be0283201813e1e9a2/glance/db/sqlalchemy/migrate_repo/versions/017_quote_encrypted_swift_credentials.py#L219 ** Affects: glance Importance: Low Status: New ** Changed in: glance Importance: Undecided => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1612742 Title: incorrect references of s3 in migration scripts Status in Glance: New Bug description: We have removed s3 references in patch https://review.openstack.org/#/c/348507/ However there are a few incorrect references of s3 in the below mentioned migration scripts. We have a project policy to not modify the migration scripts unless a significant impact exists. http://docs.openstack.org/developer/glance/contributing/minor-code- changes.html#database-migration-scripts So, this bug has been opened to gather feedback / opinions on the need for this change. https://github.com/openstack/glance/blob/d0f4316752d313bffeafd2be0283201813e1e9a2/glance/db/sqlalchemy/migrate_repo/versions/015_quote_swift_credentials.py#L157 https://github.com/openstack/glance/blob/d0f4316752d313bffeafd2be0283201813e1e9a2/glance/db/sqlalchemy/migrate_repo/versions/017_quote_encrypted_swift_credentials.py#L219 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1612742/+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 1602023] Re: Incorrect cellid in NUMA memnode
Reviewed: https://review.openstack.org/340599 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=b327006e8cd335c75e97aeebec48940f3f960962 Submitter: Jenkins Branch:master commit b327006e8cd335c75e97aeebec48940f3f960962 Author: Rafael Folco Date: Mon Jul 11 22:07:14 2016 + Fix incorrect cellid numbering for NUMA memnode cellid should contain node index, but it actually has the cell nodeset. For the given node topology cells: 0 1 16 17 Wrong cellid: Correct cellid: Change-Id: Iae337410492879a7964bcbb4711b057b920bdf79 Closes-Bug: #1602023 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1602023 Title: Incorrect cellid in NUMA memnode Status in OpenStack Compute (nova): Fix Released Bug description: Description === Nova generating wrong cellid for numa memnode. Some systems number nodeset for the NUMA topology in non-sequential way, as follows: node 0 1 16 17 Steps to reproduce == Create a flavor w/ hw:numa_nodes=4 (hw:cpu_policy unset) Spawn an instance across multiple nodes Check nodeset in the instance XML Expected result === Correct cellid: Actual result = Wrong cellid: Environment === Ubuntu Xenial 16.10, OpenStack Mitaka release, Libvirt 1.3.1 Note: This issue has been found / tested on Ubuntu KVM on Power (ppc64le arch), however, it *may* affect other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1602023/+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 1612798] [NEW] Move db retry logic away from API layer
Public bug reported: This has caused weird failure modes where DB errors get masked by integrity violation errors. ** Affects: neutron Importance: Low Assignee: Kevin Benton (kevinbenton) Status: Confirmed ** Changed in: neutron Status: New => Confirmed ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) ** Changed in: neutron 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/1612798 Title: Move db retry logic away from API layer Status in neutron: Confirmed Bug description: This has caused weird failure modes where DB errors get masked by integrity violation errors. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1612798/+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 1584237] Re: Support local validators
Reviewed: https://review.openstack.org/350259 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3c26a621f34e1ec3369f2a9d2ce6066c6343c2be Submitter: Jenkins Branch:master commit 3c26a621f34e1ec3369f2a9d2ce6066c6343c2be Author: Boden R Date: Tue Aug 2 14:33:49 2016 -0600 Use neutron-lib add_validator for registration As per [1], neutron-lib 0.3.0 provides a public add/get API for local validator registration/access. This API is preferred over directly accessing the validators dict module-level attribute that's done today when adding a new validator and in fact direct access to the validators dict is deprecated. This patch changes all neutron's usage of the validators dict to use the public API. Closes-Bug: #1584237 [1] https://review.openstack.org/#/c/324090/ Change-Id: I97680b0a8d88cb753199fce7949cfb24b506a0ff ** 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/1584237 Title: Support local validators Status in neutron: Fix Released Bug description: neutron-lib contains a number of API validators. If a new feature needs a new validator, there are two options available today: a) contribute the validator to neutron-lib/api and pull it down: this makes sense only if the validator can be useful across a number of projects; b) contribute the validator locally to the project of interest and modify the module variable neutron_lib.api.validators.validators with the local validator reference. This is definitely hack-ish and should be frowned upon; neutron-lib has a setter [1], but we'd want to clean/document things up a bit. For this reason, it would be nice to have a registration mechanism for local validators; [1] https://github.com/openstack/neutron- lib/blob/master/neutron_lib/api/validators.py#L526 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1584237/+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 1612804] [NEW] test_shelve_instance fails with sshtimeout
Public bug reported: Same failure mode of bug 1522824, root cause might be different. ** Affects: neutron Importance: Critical Status: Confirmed ** Tags: gate-failure l3-dvr-backlog ** Changed in: neutron Status: New => Confirmed ** Changed in: neutron Importance: Undecided => Critical ** Tags added: gate-failure -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1612804 Title: test_shelve_instance fails with sshtimeout Status in neutron: Confirmed Bug description: Same failure mode of bug 1522824, root cause might be different. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1612804/+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 1612812] [NEW] OS-VIF: Interface missing from Route Object. (OVS)
Public bug reported: When trying to boot and delete instances (Rally) saw this stack trace: 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/compute/manager.py", line 2075, in build_resources 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] yield resources 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/compute/manager.py", line 1919, in build_and_run_instance 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] block_device_info=block_device_info) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2658, in spawn 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] write_to_disk=True) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4693, in _get_guest_xml 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] context) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4525, in _get_guest_config 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] flavor, virt_type, self._host) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/vif.py", line 507, in get_config 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] vif_obj = os_vif_util.nova_to_osvif_vif(vif) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/network/os_vif_util.py", line 371, in nova_to_osvif_vif 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] vifobj = func(vif) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/network/os_vif_util.py", line 276, in _nova_to_osvif_vif_ovs 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] vif_name=_get_vif_name(vif)) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/network/os_vif_util.py", line 239, in _get_vif_instance 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] network=_nova_to_osvif_network(vif['network']), 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/network/os_vif_util.py", line 205, in _nova_to_osvif_network 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] subnets=_nova_to_osvif_subnets(network['subnets'])) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/network/os_vif_util.py", line 191, in _nova_to_osvif_subnets 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] objects=[_nova_to_osvif_subnet(subnet) for subnet in subnets]) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/network/os_vif_util.py", line 173, in _nova_to_osvif_subnet 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] routes=_nova_to_osvif_routes(subnet['routes'])) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/network/os_vif_util.py", line 157, in _nova_to_osvif_routes 20
[Yahoo-eng-team] [Bug 1499064] Re: expensive port request on validate networks
*** This bug is a duplicate of bug 1521788 *** https://bugs.launchpad.net/bugs/1521788 ** This bug has been marked a duplicate of bug 1521788 nova.network.neutronv2.api.validate_networks could be smarter when listing ports -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1499064 Title: expensive port request on validate networks Status in neutron: Incomplete Bug description: On validate_networks call, there is an expensive call to retrieve all ports when only the counter is needed. On the top of that, it should check first if quota is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1499064/+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 1612815] [NEW] Glance notifications documentation does not list all possible event groups
Public bug reported: The notifications reference in Glance developer docs currently only lists: image.* and task.* events. There are a number of other event types that can be emitted by the service: * image.member * metadef_namespace * metadef_object * metadef_property * metadef_resource_type * metadef_tag These all need to be properly documented here: http://docs.openstack.org/developer/glance/notifications.html. ** Affects: glance Importance: Undecided Status: New ** Tags: dev-docs documentation -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1612815 Title: Glance notifications documentation does not list all possible event groups Status in Glance: New Bug description: The notifications reference in Glance developer docs currently only lists: image.* and task.* events. There are a number of other event types that can be emitted by the service: * image.member * metadef_namespace * metadef_object * metadef_property * metadef_resource_type * metadef_tag These all need to be properly documented here: http://docs.openstack.org/developer/glance/notifications.html. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1612815/+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 1612812] Re: OS-VIF: Interface missing from Route Object. (OVS)
Some notes: (4:04:03 PM) mriedem: for neutron the route gets added here https://github.com/openstack/nova/blob/master/nova/network/neutronv2/api.py#L2158 (4:04:06 PM) mriedem: but interface isn't set (4:04:25 PM) patrickeast: mriedem: let me know what you'd like to have happen there, where its more info or a bug or whatever (4:04:29 PM) mriedem: https://github.com/openstack/nova/blob/master/nova/network/model.py#L223 (4:04:44 PM) mriedem: set on the os-vif route object here https://github.com/openstack/nova/blob/master/nova/network/os_vif_util.py#L139 (4:04:53 PM) mriedem: but we don't ever set nova.network.model.Route.interface anywhere in nova (4:04:57 PM) mriedem: AND (4:05:04 PM) mriedem: i don't see anything in the neutron data model for Route.interface (4:05:37 PM) mriedem: https://github.com/openstack/neutron/blob/master/neutron/objects/subnet.py#L67 (4:05:41 PM) mriedem: armax: HenryG: ^ (4:05:44 PM) mriedem: am i missing something? (4:05:45 PM) doffm: os-vif object with presumably non-optional interface field here https://github.com/openstack/os-vif/blob/master/os_vif/objects/route.py#L28 (4:05:56 PM) mriedem: or was Route.interface just added to nova's nw model but never used? (4:06:39 PM) mriedem: apparently we don't fail on this in the openstack CI b/c we aren't using subnets with routes (4:06:40 PM) mriedem: http://logs.openstack.org/99/340599/2/gate/gate-tempest-dsvm-neutron-full-ubuntu-xenial/3128550/logs/screen-n-cpu.txt.gz#_2016-08-12_17_08_55_248 (4:06:46 PM) mriedem: 'routes': [] (4:07:55 PM) mriedem: so looks to me like a lie was propagated to os-vif (4:08:01 PM) mriedem: and the interface field should be nullable=True ** Also affects: os-vif Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1612812 Title: OS-VIF: Interface missing from Route Object. (OVS) Status in OpenStack Compute (nova): New Status in os-vif: New Bug description: When trying to boot and delete instances (Rally) saw this stack trace: 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/compute/manager.py", line 2075, in build_resources 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] yield resources 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/compute/manager.py", line 1919, in build_and_run_instance 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] block_device_info=block_device_info) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2658, in spawn 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] write_to_disk=True) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4693, in _get_guest_xml 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] context) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4525, in _get_guest_config 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] flavor, virt_type, self._host) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/vif.py", line 507, in get_config 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] vif_obj = os_vif_util.nova_to_osvif_vif(vif) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/network/os_vif_util.py", line 371, in nova_to_osvif_vif 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] vifobj = func(vif) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/net
[Yahoo-eng-team] [Bug 1612821] [NEW] METADATA_PROXY_HANDLER_OPTS in agent metadata configuration has inconsistent spacing
Public bug reported: Not sure if this qualifies as a bug as much as it is again python standards. on branch: master in file: neutron/neutron/agent/metadata/config.py on lines: 52 - 83 the configuration for METADATA_PROXY_HANDLER_OPTS has indentation set to 5 rather than the python standard of 4. The rest of the file is also set to 4. For consistency this should be changed to 4 to match the standard and the rest of the file. ** 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/1612821 Title: METADATA_PROXY_HANDLER_OPTS in agent metadata configuration has inconsistent spacing Status in neutron: New Bug description: Not sure if this qualifies as a bug as much as it is again python standards. on branch: master in file: neutron/neutron/agent/metadata/config.py on lines: 52 - 83 the configuration for METADATA_PROXY_HANDLER_OPTS has indentation set to 5 rather than the python standard of 4. The rest of the file is also set to 4. For consistency this should be changed to 4 to match the standard and the rest of the file. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1612821/+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 1612231] Re: providing network-interfaces via meta-data broken in NoCloud
this was fixed in upstream commit 8028c9234ec4260eda9431bffc6728ac3703e243 but commit changelog referred to bug 1577982. I just uploaded 0.7.7-10-gbc2c326-0ubuntu1 to yakkety, so when this arrives it will be fix-released in ubuntu. ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Status: New => Fix Released ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1612231 Title: providing network-interfaces via meta-data broken in NoCloud Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Bug description: Originally reported after bug 1577982 was fixed, there is an issue providing network configuration to the NoCloud datasource via the meta-data key 'network-interfaces'. For example: $ cd /var/lib/cloud/seed/nocloud-net $ cat meta-data instance-id: 1470899540 local-hostname: soscared network-interfaces: | auto eth0 iface eth0 inet static hwaddr 00:16:3e:70:e1:04 address 103.225.10.12 netmask 255.255.255.0 gateway 103.225.10.1 dns-servers 8.8.8.8 It should be noted that without providing 'hwaddr' above, you'll be relying on kernel network or systemd network device naming to have the device named 'eth0'. If it is not named 'eth0', then configuration wont work. So the two options to do that right are: a.) provide 'hwaddr' as shown above b.) provide 'net.ifnames=0' on kernel command line (https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/). (Note, when run in lxc, you will get eth0 names consistently and you do not need the hwaddr or kernel command line). To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1612231/+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 1610784] Re: cloud-init openstack.py code does not recognize network type 'tap'
fixed in 8028c9234ec4260eda9431bffc6728ac3703e243 ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1610784 Title: cloud-init openstack.py code does not recognize network type 'tap' Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Confirmed Bug description: == System info == Xenial 16.04.1, Mitaka, MAAS 2.0 (RC2 currently), JuJu 2.0 (beta7 currently - awaiting beta14), 16.07 Charms, neutron-calico-11 (awaiting fix for another bug). == Config drive link == https://gist.github.com/anonymous/ce20298b9e12e7fe77851552c2a91243 == Error log == From line 574 in https://git.launchpad.net/cloud-init/tree/cloudinit/sources/helpers/openstack.py: if link['type'] in ['ethernet', 'vif', 'ovs', 'phy', 'bridge']: Jul 28 10:31:38 ubuntu cloud-init[1209]: failed run of stage init-local Jul 28 10:31:38 ubuntu cloud-init[1209]: Jul 28 10:31:38 ubuntu cloud-init[1209]: Traceback (most recent call last): Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 530, in status_wrapper Jul 28 10:31:38 ubuntu cloud-init[1209]: ret = functor(name, args) Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 277, in main_init Jul 28 10:31:38 ubuntu cloud-init[1209]: init.apply_network_config(bring_up=bool(mode != sources.DSMODE_LOCAL)) Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 631, in apply_network_config Jul 28 10:31:38 ubuntu cloud-init[1209]: netcfg, src = self._find_networking_config() Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 618, in _find_networking_config Jul 28 10:31:38 ubuntu cloud-init[1209]: if self.datasource and hasattr(self.datasource, 'network_config'): Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py", line 159, in network_config Jul 28 10:31:38 ubuntu cloud-init[1209]: self.network_json, known_macs=self.known_macs) Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/sources/helpers/openstack.py", line 599, in convert_net_json Jul 28 10:31:38 ubuntu cloud-init[1209]: 'Unknown network_data link type: %s' % link['type']) Jul 28 10:31:38 ubuntu cloud-init[1209]: ValueError: Unknown network_data link type: tap Jul 28 10:31:38 ubuntu cloud-init[1209]: To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1610784/+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 1612821] Re: METADATA_PROXY_HANDLER_OPTS in agent metadata configuration has inconsistent spacing
got it, I updated the state to invalid, thanks! ** 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/1612821 Title: METADATA_PROXY_HANDLER_OPTS in agent metadata configuration has inconsistent spacing Status in neutron: Invalid Bug description: Not sure if this qualifies as a bug as much as it is again python standards. on branch: master in file: neutron/neutron/agent/metadata/config.py on lines: 52 - 83 the configuration for METADATA_PROXY_HANDLER_OPTS has indentation set to 5 rather than the python standard of 4. The rest of the file is also set to 4. For consistency this should be changed to 4 to match the standard and the rest of the file. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1612821/+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 1611513] Re: ip_lib: Add support for 'Flush' command in iproute
Reviewed: https://review.openstack.org/349587 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=87488f345c47d587e432206b2f7289a727e7e528 Submitter: Jenkins Branch:master commit 87488f345c47d587e432206b2f7289a727e7e528 Author: Swaminathan Vasudevan Date: Mon Aug 1 08:54:40 2016 -0700 Add flush command to iproute in ip_lib IP route flush command to support flush the route entries. Closes-Bug: #1611513 Change-Id: I401b242cc86ba1de7a20943d8b0340e0f0005ba3 ** 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/1611513 Title: ip_lib: Add support for 'Flush' command in iproute Status in neutron: Fix Released Bug description: This would be enhancement to the ip_lib iproute library to provide additional support for the 'Flush' command that is not available right now. This is a dependency for a fix in DVR to cleanup the gateway rules. Ref: Bug: #1599287 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1611513/+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 1475740] Re: For instances spawned by Nova on ESX compute, there is no link in /dev/disk/by-id for SCSI (sdx) devices
Reviewed: https://review.openstack.org/205269 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2a6bdf8f0e0e22fc7703faa9669ace7380dc73c3 Submitter: Jenkins Branch:master commit 2a6bdf8f0e0e22fc7703faa9669ace7380dc73c3 Author: Johnson koil raj Date: Fri Jul 24 01:25:59 2015 +0530 VMware: Enable disk.EnableUUID=True in vmx Currently there is no link in /dev/disk/by-id for SCSI (sdx) devices because by default VMWare doesn't provide information needed by udev to generate /dev/disk/by-id. When this specific parameter disk.EnableUUID is set to True in vmx file inside the guest vm /dev/disk/by-id shows a link to UUID of the attached SCSI device Closes-Bug: #1475740 Change-Id: Ib2cdf994c37d4c5d2e095741cc579a7dc12be9e0 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1475740 Title: For instances spawned by Nova on ESX compute, there is no link in /dev/disk/by-id for SCSI (sdx) devices Status in OpenStack Compute (nova): Fix Released Bug description: By default VMWare doesn't provide information needed by udev to generate /dev/disk/by-id. Hence for instances spawned by Nova on ESX compute, there is no link in /dev/disk/by-id for SCSI (sdx) devices. The property disk.EnableUUID needs to be enabled by default for instances spawned by Nova. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1475740/+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 1610784] Re: cloud-init openstack.py code does not recognize network type 'tap'
This bug was fixed in the package cloud-init - 0.7.7-10-gbc2c326-0ubuntu1 --- cloud-init (0.7.7-10-gbc2c326-0ubuntu1) yakkety; urgency=medium * New upstream snapshot: - DigitalOcean: use the v1.json endpoint - MAAS: add vendor-data support (LP: #1612313) - Upgrade the minimum configobj package to one new enough to work - ConfigDrive: recognize 'tap' as a link type. (LP: #1610784) - NoCloud: fix bug providing network-interfaces via meta-data. (LP: #1577982) - Add distro tags on config modules that should have it - add ntp config module - SmartOS: more improvements for network configuration -- Scott Moser Fri, 12 Aug 2016 17:18:01 -0400 ** Changed in: cloud-init (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1610784 Title: cloud-init openstack.py code does not recognize network type 'tap' Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Bug description: == System info == Xenial 16.04.1, Mitaka, MAAS 2.0 (RC2 currently), JuJu 2.0 (beta7 currently - awaiting beta14), 16.07 Charms, neutron-calico-11 (awaiting fix for another bug). == Config drive link == https://gist.github.com/anonymous/ce20298b9e12e7fe77851552c2a91243 == Error log == From line 574 in https://git.launchpad.net/cloud-init/tree/cloudinit/sources/helpers/openstack.py: if link['type'] in ['ethernet', 'vif', 'ovs', 'phy', 'bridge']: Jul 28 10:31:38 ubuntu cloud-init[1209]: failed run of stage init-local Jul 28 10:31:38 ubuntu cloud-init[1209]: Jul 28 10:31:38 ubuntu cloud-init[1209]: Traceback (most recent call last): Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 530, in status_wrapper Jul 28 10:31:38 ubuntu cloud-init[1209]: ret = functor(name, args) Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 277, in main_init Jul 28 10:31:38 ubuntu cloud-init[1209]: init.apply_network_config(bring_up=bool(mode != sources.DSMODE_LOCAL)) Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 631, in apply_network_config Jul 28 10:31:38 ubuntu cloud-init[1209]: netcfg, src = self._find_networking_config() Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 618, in _find_networking_config Jul 28 10:31:38 ubuntu cloud-init[1209]: if self.datasource and hasattr(self.datasource, 'network_config'): Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py", line 159, in network_config Jul 28 10:31:38 ubuntu cloud-init[1209]: self.network_json, known_macs=self.known_macs) Jul 28 10:31:38 ubuntu cloud-init[1209]: File "/usr/lib/python3/dist-packages/cloudinit/sources/helpers/openstack.py", line 599, in convert_net_json Jul 28 10:31:38 ubuntu cloud-init[1209]: 'Unknown network_data link type: %s' % link['type']) Jul 28 10:31:38 ubuntu cloud-init[1209]: ValueError: Unknown network_data link type: tap Jul 28 10:31:38 ubuntu cloud-init[1209]: To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1610784/+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 1612875] [NEW] FixedIPsTestJson fails server build with "was re-scheduled: operation failed: filter 'nova-no-nd-reflection' already exists with uuid"
Public bug reported: Seen here: http://logs.openstack.org/98/355098/1/check/gate-tempest-dsvm-full- ubuntu- xenial/3c301f3/logs/screen-n-cond.txt.gz?level=TRACE#_2016-08-13_00_53_27_621 2016-08-13 00:53:27.621 15971 ERROR nova.scheduler.utils [req-e7b83619-01ae-43f2-b293-af02c5cb35a8 tempest-FixedIPsTestJson-2017152444 tempest-FixedIPsTestJson-2017152444] [instance: ac2c9a4a-1b07-43e1-8f4c-b75541331307] Error from last host: ubuntu-xenial-rax-ord-3453779 (node ubuntu-xenial-rax-ord-3453779): [u'Traceback (most recent call last):\n', u' File "/opt/stack/new/nova/nova/compute/manager.py", line 1778, in _do_build_and_run_instance\nfilter_properties)\n', u' File "/opt/stack/new/nova/nova/compute/manager.py", line 1973, in _build_and_run_instance\ninstance_uuid=instance.uuid, reason=six.text_type(e))\n', u"RescheduledException: Build of instance ac2c9a4a-1b07-43e1-8f4c-b75541331307 was re-scheduled: operation failed: filter 'nova-no-nd-reflection' already exists with uuid 1f47eeb2-d473-481e-998a-c4d64a44ac5e\n"] 2016-08-13 00:53:27.676 15971 WARNING nova.scheduler.utils [req-e7b83619-01ae-43f2-b293-af02c5cb35a8 tempest-FixedIPsTestJson-2017152444 tempest-FixedIPsTestJson-2017152444] Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available. Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 199, in inner return func(*args, **kwargs) File "/opt/stack/new/nova/nova/scheduler/manager.py", line 104, in select_destinations dests = self.driver.select_destinations(ctxt, spec_obj) File "/opt/stack/new/nova/nova/scheduler/filter_scheduler.py", line 74, in select_destinations raise exception.NoValidHost(reason=reason) NoValidHost: No valid host was found. There are not enough hosts available. 2016-08-13 00:53:27.676 15971 WARNING nova.scheduler.utils [req-e7b83619 -01ae-43f2-b293-af02c5cb35a8 tempest-FixedIPsTestJson-2017152444 tempest-FixedIPsTestJson-2017152444] [instance: ac2c9a4a- 1b07-43e1-8f4c-b75541331307] Setting instance to ERROR state. http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22was %20re-scheduled%3A%20operation%20failed%3A%20filter%20'nova-no-nd- reflection'%20already%20exists%20with%20uuid%5C%22%20AND%20tags%3A%5C%22screen-n-cond.txt%5C%22&from=7d 5 hits in 7 days, check queue only, but multiple changes. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1612875 Title: FixedIPsTestJson fails server build with "was re-scheduled: operation failed: filter 'nova-no-nd-reflection' already exists with uuid" Status in OpenStack Compute (nova): New Bug description: Seen here: http://logs.openstack.org/98/355098/1/check/gate-tempest-dsvm-full- ubuntu- xenial/3c301f3/logs/screen-n-cond.txt.gz?level=TRACE#_2016-08-13_00_53_27_621 2016-08-13 00:53:27.621 15971 ERROR nova.scheduler.utils [req-e7b83619-01ae-43f2-b293-af02c5cb35a8 tempest-FixedIPsTestJson-2017152444 tempest-FixedIPsTestJson-2017152444] [instance: ac2c9a4a-1b07-43e1-8f4c-b75541331307] Error from last host: ubuntu-xenial-rax-ord-3453779 (node ubuntu-xenial-rax-ord-3453779): [u'Traceback (most recent call last):\n', u' File "/opt/stack/new/nova/nova/compute/manager.py", line 1778, in _do_build_and_run_instance\nfilter_properties)\n', u' File "/opt/stack/new/nova/nova/compute/manager.py", line 1973, in _build_and_run_instance\ninstance_uuid=instance.uuid, reason=six.text_type(e))\n', u"RescheduledException: Build of instance ac2c9a4a-1b07-43e1-8f4c-b75541331307 was re-scheduled: operation failed: filter 'nova-no-nd-reflection' already exists with uuid 1f47eeb2-d473-481e-998a-c4d64a44ac5e\n"] 2016-08-13 00:53:27.676 15971 WARNING nova.scheduler.utils [req-e7b83619-01ae-43f2-b293-af02c5cb35a8 tempest-FixedIPsTestJson-2017152444 tempest-FixedIPsTestJson-2017152444] Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available. Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 199, in inner return func(*args, **kwargs) File "/opt/stack/new/nova/nova/scheduler/manager.py", line 104, in select_destinations dests = self.driver.select_destinations(ctxt, spec_obj) File "/opt/stack/new/nova/nova/scheduler/filter_scheduler.py", line 74, in select_destinations raise exception.NoValidHost(reason=reason) NoValidHost: No valid host was found. There are not enough hosts available. 2016-08-13 00:53:27.676 15971 WARNING nova.scheduler.utils [req- e7b83619-01ae-43f2-b293-af02c5cb35a8 tempest- FixedIPsTestJson-2017152444 tempest-FixedIPsTestJson-2017152444] [instance: ac2c9a4a-1b07-43e1-8f4c
[Yahoo-eng-team] [Bug 1609173] Re: [api] Document default domain config behaviour
Reviewed: https://review.openstack.org/354479
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=5289eefd6cca723c0b2cbfe1e8a3d796f6a7ce55
Submitter: Jenkins
Branch:master
commit 5289eefd6cca723c0b2cbfe1e8a3d796f6a7ce55
Author: Tin Lam
Date: Thu Aug 11 20:40:58 2016 -0500
api-ref: Add default domain config documentation
Add documentation for:
GET /domains/config/default
GET /domains/config/{group}/default
GET /domains/config/{group}/{option}/default
Change-Id: I1b6c8a5873edffdf4a091334b2cc0c9ce041aa62
Closes-Bug: #1609173
** Changed in: keystone
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1609173
Title:
[api] Document default domain config behaviour
Status in OpenStack Identity (keystone):
Fix Released
Bug description:
The following are not documented in our API site:
Document default domain config: GET /domains/config/default
http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3.html#domain-configuration-management
As well as these two:
Document default for domain config group: GET /domains/config/{group}/default
Document default for domain config group option: GET
/domains/config/{group}/{option}/default
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1609173/+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 1612890] [NEW] Support-matrix of ironic for vlan should be updated
Public bug reported: Description === As newton-3 is released, ironic has now support vlan network through neutron So we should update support matrix ** Affects: nova Importance: Undecided Assignee: xhzhf (guoyongxhzhf) Status: New ** Changed in: nova Assignee: (unassigned) => xhzhf (guoyongxhzhf) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1612890 Title: Support-matrix of ironic for vlan should be updated Status in OpenStack Compute (nova): New Bug description: Description === As newton-3 is released, ironic has now support vlan network through neutron So we should update support matrix To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1612890/+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 1612615] Re: test_get_allocated_net_topology_as_tenant failure in api job
Reviewed: https://review.openstack.org/355050 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=aa42906143f09a8cf40dfcd91bb211eac6689b80 Submitter: Jenkins Branch:master commit aa42906143f09a8cf40dfcd91bb211eac6689b80 Author: Armando Migliaccio Date: Fri Aug 12 12:51:14 2016 -0700 Make auto-allocate plugin handle sneaky DB errors DB errors or retry exceptions that bubble up to the plugin may get masked by integrity violation errors due to partial provisioning of resources. When that happens, we should make sure any pending resource is cleaned up before reattempting the operation. Closes-bug: #1612615 Change-Id: I76e9f8e4b61fb3566d70af4236c19e4c5a523646 ** 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/1612615 Title: test_get_allocated_net_topology_as_tenant failure in api job Status in neutron: Fix Released Bug description: http://logs.openstack.org/12/354612/1/check/gate-neutron-dsvm- api/09c5da5/testr_results.html.gz Traceback (most recent call last): File "/opt/stack/new/neutron/neutron/tests/tempest/api/test_auto_allocated_topology.py", line 95, in test_get_allocated_net_topology_as_tenant self.assertEqual((1, self.num_subnetpools, 1), resources_after1) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 411, in assertEqual self.assertThat(observed, matcher, message) File "/usr/local/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: (1, 2, 1) != (1, 4, 1) Logstash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22in%20test_get_allocated_net_topology_as_tenant%5C%22 3 hits in 7 days. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1612615/+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 1612891] [NEW] Vif-plug event was been sent to old node cause evacuate failed
Public bug reported: Description === When using host-evacuate command, some vms on failed host would be failed when evacuating because the vif-plug event was be sent to failed node not the node which vm launched on. Steps to reproduce == 1.create 8 vms on host1 2.nova service-force-down host1 nova-compute nova service-force-down host1 nova-conductor nova service-force-down host1 nova-scheduler 3.evacuate the vms on host1 nova host-evacuate host1 Expected result === After the execution of the steps above, all of vms on hosts1 should be evacuated to other hosts Actual result = only 2-3 vms can be evacuated, others became to failed Environment === 1. My openstack version is mitaka 2. Use Libvirt + Kvm in OpenStack 2. Use Ceph as backend storage 3. Use Neutron with OpenVSwitch ** Affects: nova Importance: Undecided Assignee: zhangjialong (zhangjl) Status: New ** Summary changed: - Vif-plug event was be sent to old node cause evacuate failed + Vif-plug event was been sent to old node cause evacuate failed ** Changed in: nova Assignee: (unassigned) => zhangjialong (zhangjl) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1612891 Title: Vif-plug event was been sent to old node cause evacuate failed Status in OpenStack Compute (nova): New Bug description: Description === When using host-evacuate command, some vms on failed host would be failed when evacuating because the vif-plug event was be sent to failed node not the node which vm launched on. Steps to reproduce == 1.create 8 vms on host1 2.nova service-force-down host1 nova-compute nova service-force-down host1 nova-conductor nova service-force-down host1 nova-scheduler 3.evacuate the vms on host1 nova host-evacuate host1 Expected result === After the execution of the steps above, all of vms on hosts1 should be evacuated to other hosts Actual result = only 2-3 vms can be evacuated, others became to failed Environment === 1. My openstack version is mitaka 2. Use Libvirt + Kvm in OpenStack 2. Use Ceph as backend storage 3. Use Neutron with OpenVSwitch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1612891/+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 1612894] [NEW] test_router_add_interface_delete_port_after_failure may fail due to extra port created
Public bug reported: In test_router_add_interface_delete_port_after_failure, when a subnet is created, a neutron DHCP port could be created if this subnet is DHCP-enabled. In this case, the test will fail because it only checks if a router-interface port is deleted and expects no more port in the system. But it misses the internal DHCP port is still there. ** Affects: neutron Importance: Undecided Assignee: Shih-Hao Li (shihli) Status: 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/1612894 Title: test_router_add_interface_delete_port_after_failure may fail due to extra port created Status in neutron: In Progress Bug description: In test_router_add_interface_delete_port_after_failure, when a subnet is created, a neutron DHCP port could be created if this subnet is DHCP-enabled. In this case, the test will fail because it only checks if a router-interface port is deleted and expects no more port in the system. But it misses the internal DHCP port is still there. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1612894/+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 1612896] [NEW] test_router_add_interface_port may fail due to extra port created
Public bug reported: test_router_add_interface_port may fail when an internal metadata network is created during add_router_interface action. The potential problem is introduced by Commit 6281fddbcb4c (https://review.openstack.org/#/c/285048/) which adds an additional update_port inside add_router_interface() to update device_id and device_owner on the newly created router port. The problem could happen when users attach a subnet (for example 10.0.0.0/24) to a router. During the add_router_interface action, vendor's plugin may create an internal metadata subnet (such as 169.254.169.252/30) and attach it to the same router. Since two router ports (10.0.0.1 and 169.254.169.253) are created during this operation, the extra update_port was called for both router ports. Before Commit 6281fddbcb4c, test_router_add_interface_port only saw one update_port call on 10.0.0.1. After the change, it now sees three update_port calls, two on 10.0.0.1 and one on 169.254.169.253. Because it doesn't expect to see the update_port call on port 169.254.169.253 (which is the last update_port call), the update_port.assert_called_with() fails. ** Affects: neutron Importance: Undecided Assignee: Shih-Hao Li (shihli) Status: 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/1612896 Title: test_router_add_interface_port may fail due to extra port created Status in neutron: In Progress Bug description: test_router_add_interface_port may fail when an internal metadata network is created during add_router_interface action. The potential problem is introduced by Commit 6281fddbcb4c (https://review.openstack.org/#/c/285048/) which adds an additional update_port inside add_router_interface() to update device_id and device_owner on the newly created router port. The problem could happen when users attach a subnet (for example 10.0.0.0/24) to a router. During the add_router_interface action, vendor's plugin may create an internal metadata subnet (such as 169.254.169.252/30) and attach it to the same router. Since two router ports (10.0.0.1 and 169.254.169.253) are created during this operation, the extra update_port was called for both router ports. Before Commit 6281fddbcb4c, test_router_add_interface_port only saw one update_port call on 10.0.0.1. After the change, it now sees three update_port calls, two on 10.0.0.1 and one on 169.254.169.253. Because it doesn't expect to see the update_port call on port 169.254.169.253 (which is the last update_port call), the update_port.assert_called_with() fails. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1612896/+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 1596124] Re: Python3 do not use dict.iteritems dict.iterkeys dict.itervalues
** No longer affects: nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1596124 Title: Python3 do not use dict.iteritems dict.iterkeys dict.itervalues Status in glance_store: Fix Released Status in python-glanceclient: In Progress Status in python-heatclient: Fix Released Status in OpenStack Object Storage (swift): In Progress Bug description: Python3 do not use dict.iteritemse dict.iterkeys dict.itervalues, which would raise AttributeError: 'dict' object has no attribute 'iterkeys'. To manage notifications about this bug go to: https://bugs.launchpad.net/glance-store/+bug/1596124/+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 1591857] Re: 'segments' set to service_plugins should be 'segment'
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1591857 Title: 'segments' set to service_plugins should be 'segment' Status in neutron: Expired Bug description: This is about segment extension. Alias of segment extension is 'segment'. service_plugins in neutron.conf must be set 'segments'. This causes confusion (at least for me). I think it is better that they are same. (I think definition of service_plugins should be 'segment' (i.e. fix setup.cfg)) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1591857/+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 1580648] Re: Two HA routers in master state during functional test
[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1580648 Title: Two HA routers in master state during functional test Status in neutron: Expired Bug description: Scheduling ha routers end with two routers in master state. Issue discovered in that bug fix - https://review.openstack.org/#/c/273546 - after preparing new functional test. ha_router.py in method - _get_state_change_monitor_callback() is starting a neutron-keepalived-state-change process with parameter --monitor-interface as ha_device (ha-xxx) and it's IP address. That application is monitoring using "ip netns exec xxx ip -o monitor address" all changes in that namespace. Each addition of that ha-xxx device produces a call to neutron-server API that this router becomes "master". It's producing false results because that device doesn't tell anything about that router is master or not. Logs from test_ha_router.L3HATestFailover.test_ha_router_lost_gw_connection Agent2: 2016-05-10 16:23:20.653 16067 DEBUG neutron.agent.linux.async_process [-] Launching async process [ip netns exec qrouter-962f19e6-f592-49f7-8bc4-add116c0b7a3@agent1@agent2 ip -o monitor address]. start /neutron/neutron/agent/linux/async_process.py:109 2016-05-10 16:23:20.654 16067 DEBUG neutron.agent.linux.utils [-] Running command: ['ip', 'netns', 'exec', 'qrouter-962f19e6-f592-49f7-8bc4-add116c0b7a3@agent1@agent2', 'ip', '-o', 'monitor', 'address'] create_process /neutron/neutron/agent/linux/utils.py:82 2016-05-10 16:23:20.661 16067 DEBUG neutron.agent.l3.keepalived_state_change [-] Monitor: ha-8aedf0c6-2a, 169.254.0.1/24 run /neutron/neutron/agent/l3/keepalived_state_change.py:59 2016-05-10 16:23:20.661 16067 INFO neutron.agent.linux.daemon [-] Process runs with uid/gid: 1000/1000 2016-05-10 16:23:20.767 16067 DEBUG neutron.agent.l3.keepalived_state_change [-] Event: qr-88c93aa9-5a, fe80::c8fe:deff:fead:beef/64, False parse_and_handle_event /neutron/neutron/agent/l3/keepalived_state_change.py:73 2016-05-10 16:23:20.901 16067 DEBUG neutron.agent.l3.keepalived_state_change [-] Event: qg-814d252d-26, fe80::c8fe:deff:fead:beee/64, False parse_and_handle_event /neutron/neutron/agent/l3/keepalived_state_change.py:73 2016-05-10 16:23:21.324 16067 DEBUG neutron.agent.l3.keepalived_state_change [-] Event: ha-8aedf0c6-2a, fe80::2022:22ff:fe22:/64, True parse_and_handle_event /neutron/neutron/agent/l3/keepalived_state_change.py:73 2016-05-10 16:23:29.807 16067 DEBUG neutron.agent.l3.keepalived_state_change [-] Event: ha-8aedf0c6-2a, 169.254.0.1/24, True parse_and_handle_event /neutron/neutron/agent/l3/keepalived_state_change.py:73 2016-05-10 16:23:29.808 16067 DEBUG neutron.agent.l3.keepalived_state_change [-] Wrote router 962f19e6-f592-49f7-8bc4-add116c0b7a3 state master write_state_change /neutron/neutron/agent/l3/keepalived_state_change.py:87 2016-05-10 16:23:29.808 16067 DEBUG neutron.agent.l3.keepalived_state_change [-] State: master notify_agent /neutron/neutron/agent/l3/keepalived_state_change.py:93 Agent1: 2016-05-10 16:23:19.417 15906 DEBUG neutron.agent.linux.async_process [-] Launching async process [ip netns exec qrouter-962f19e6-f592-49f7-8bc4-add116c0b7a3@agent1 ip -o monitor address]. start /neutron/neutron/agent/linux/async_process.py:109 2016-05-10 16:23:19.418 15906 DEBUG neutron.agent.linux.utils [-] Running command: ['ip', 'netns', 'exec', 'qrouter-962f19e6-f592-49f7-8bc4-add116c0b7a3@agent1', 'ip', '-o', 'monitor', 'address'] create_process /neutron/neutron/agent/linux/utils.py:82 2016-05-10 16:23:19.425 15906 DEBUG neutron.agent.l3.keepalived_state_change [-] Monitor: ha-22a4d1e0-ad, 169.254.0.1/24 run /neutron/neutron/agent/l3/keepalived_state_change.py:59 2016-05-10 16:23:19.426 15906 INFO neutron.agent.linux.daemon [-] Process runs with uid/gid: 1000/1000 2016-05-10 16:23:19.525 15906 DEBUG neutron.agent.l3.keepalived_state_change [-] Event: qr-88c93aa9-5a, fe80::c8fe:deff:fead:beef/64, False parse_and_handle_event /neutron/neutron/agent/l3/keepalived_state_change.py:73 2016-05-10 16:23:19.645 15906 DEBUG neutron.agent.l3.keepalived_state_change [-] Event: qg-814d252d-26, fe80::c8fe:deff:fead:beee/64, False parse_and_handle_event /neutron/neutron/agent/l3/keepalived_state_change.py:73 2016-05-10 16:23:19.927 15906 DEBUG neutron.agent.l3.keepalived_state_change [-] Event: ha-22a4d1e0-ad, fe80::1034:56ff:fe78:2b5d/64, True parse_and_handle_event /neutron/neutron/agent/l3/keepalived_state_change.py:73 2016-05-10 16:23:28.543 15906 DEBUG neutron.agent.l3.keepalived_state_change [-] Event: ha-22a4d1e0-ad, 169.254.0.1/24, True parse_and_handle_event /neutron/neutron/agent/l3/keepalived_state_change.py:73 2016-05-10 16:23
[Yahoo-eng-team] [Bug 1612812] Re: OS-VIF: Interface missing from Route Object. (OVS)
Reviewed: https://review.openstack.org/355098 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=1d57c1fd53e930b02c3ce0e9914f95ef68dd1f87 Submitter: Jenkins Branch:master commit 1d57c1fd53e930b02c3ce0e9914f95ef68dd1f87 Author: Matt Riedemann Date: Fri Aug 12 17:42:47 2016 -0400 os-vif: do not set Route.interface if None The Route.interface field in os-vif is currently non-nullable, which means it must be something other than None if set. There is no code in nova that sets the interface field on the nova.network.model.Route object, so it defaults to None and is always set to None on the os-vif Route object, which fails with: "ValueError: Fieldinterface' cannot be None" We don't hit this in the gate because we don't test with subnets that have host_routes set. Change-Id: Ideadf1fc009b3ee496acb4696226a3cc9722fb29 Closes-Bug: #1612812 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1612812 Title: OS-VIF: Interface missing from Route Object. (OVS) Status in OpenStack Compute (nova): Fix Released Status in os-vif: In Progress Bug description: When trying to boot and delete instances (Rally) saw this stack trace: 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/compute/manager.py", line 2075, in build_resources 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] yield resources 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/compute/manager.py", line 1919, in build_and_run_instance 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] block_device_info=block_device_info) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2658, in spawn 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] write_to_disk=True) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4693, in _get_guest_xml 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] context) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4525, in _get_guest_config 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] flavor, virt_type, self._host) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/virt/libvirt/vif.py", line 507, in get_config 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] vif_obj = os_vif_util.nova_to_osvif_vif(vif) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/network/os_vif_util.py", line 371, in nova_to_osvif_vif 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] vifobj = func(vif) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/network/os_vif_util.py", line 276, in _nova_to_osvif_vif_ovs 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] vif_name=_get_vif_name(vif)) 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File "/opt/bbc/openstack-11.0-master/nova/local/lib/python2.7/site-packages/nova/network/os_vif_util.py", line 239, in _get_vif_instance 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] network=_nova_to_osvif_network(vif['network']), 2016-08-12 15:21:58.859 38365 ERROR nova.compute.manager [instance: 47fbd50b-94ec-4395-884c-9131e0e3f335] File
[Yahoo-eng-team] [Bug 1612907] [NEW] Add setting default max_burst value if not given by user
Public bug reported: https://review.openstack.org/347017 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 8b5d04ff57223885a45dc34e7769a7fd424f7de5 Author: Sławek Kapłoński Date: Sat Apr 30 00:53:22 2016 +0200 Add setting default max_burst value if not given by user If user will not provide burst value for bandwidth limit rule there is need to set such value on appropriate to ensure that bandwith limit will work fine. To ensure at least proper limitation of TCP traffic we decided to set burst as 80% of bw_limit value. LinuxBridge agent already sets is like that. This patch add same behaviour for QoS extension driver in openvswitch L2 agent. DocImpact: Add setting default max_burst value in LB and OvS drivers Conflicts: neutron/agent/linux/tc_lib.py Change-Id: Ib12a7cbf88cdffd10c8f6f8442582bf7377ca27d Closes-Bug: #1572670 (cherry picked from commit f766fc71bedc58a0cff0c6dc6e5576f0ab5e2507) ** Affects: neutron Importance: Undecided Status: New ** Tags: doc 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/1612907 Title: Add setting default max_burst value if not given by user Status in neutron: New Bug description: https://review.openstack.org/347017 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 8b5d04ff57223885a45dc34e7769a7fd424f7de5 Author: Sławek Kapłoński Date: Sat Apr 30 00:53:22 2016 +0200 Add setting default max_burst value if not given by user If user will not provide burst value for bandwidth limit rule there is need to set such value on appropriate to ensure that bandwith limit will work fine. To ensure at least proper limitation of TCP traffic we decided to set burst as 80% of bw_limit value. LinuxBridge agent already sets is like that. This patch add same behaviour for QoS extension driver in openvswitch L2 agent. DocImpact: Add setting default max_burst value in LB and OvS drivers Conflicts: neutron/agent/linux/tc_lib.py Change-Id: Ib12a7cbf88cdffd10c8f6f8442582bf7377ca27d Closes-Bug: #1572670 (cherry picked from commit f766fc71bedc58a0cff0c6dc6e5576f0ab5e2507) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1612907/+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 1603162] Re: Pluggable IPAM rollback fails with reference driver
Reviewed: https://review.openstack.org/348956 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=67984850228f6f26a72504b9f464a5fbcaac59e6 Submitter: Jenkins Branch:master commit 67984850228f6f26a72504b9f464a5fbcaac59e6 Author: Carl Baldwin Date: Fri Jul 29 10:10:48 2016 -0600 Avoid IPAM driver reusing a session that has been rolled back With the in-tree pluggable IPAM driver, IPAM rollback tries to use the DB session after it has been rolled back due to an exception. This driver doesn't need roll back, so fix this by adding a method to the driver signalling that rollback shouldn't be attempted. Change-Id: Ic254789e58a8a51cd1aa943cb71de12410f4c0a7 Closes-Bug: #1603162 Related-Bug: #1516156 ** 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/1603162 Title: Pluggable IPAM rollback fails with reference driver Status in neutron: Fix Released Bug description: This bug is visible when pluggable IPAM is active. It can be seen with this patch [1]. It does not cause gate failures but it is still something that should be understood. This logstash query [2] seems to find where they occur. It is helpful to look at the DEBUG level logging around the time of the error. For example see this paste [3]. It seems that the session gets broken with an exception that causes a rollback. Then, the IPAM rollback attempts to use the same session for rollback which fails. Should the reference pluggable IPAM driver be using a different session? Or, should it call rollback? [1] https://review.openstack.org/#/c/181023 [2] http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22IP%20deallocation%20failed%20on%20external%20system%5C%22 [3] http://paste.openstack.org/show/532891/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1603162/+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
