[Yahoo-eng-team] [Bug 1951450] Re: [CI] Rally jobs failing 100% of times
This doesn't seem like a neutron bug. ** Also affects: devstack Importance: Undecided Status: New ** No longer affects: devstack -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1951450 Title: [CI] Rally jobs failing 100% of times Status in neutron: Fix Released Bug description: Rally jobs are always failing, both OVN and OVS. Error: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_803/817734/5/check/neutron- ovs-rally-task/803186b/job-output.txt Snippet: https://paste.opendev.org/show/811177/ This could have been caused by https://review.opendev.org/c/openstack/devstack/+/780417. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1951450/+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 1918653] Re: Designate DNS – create TLD using valid Unicode string
Not a neutron bug. I changed it to designate.
** Project changed: neutron => designate
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1918653
Title:
Designate DNS – create TLD using valid Unicode string
Status in Designate:
New
Bug description:
Scenario:
Try to create a new TLD using Unicode string, for example: “例え”
Actual Result:
API fails with:
Details: {'code': 400, 'type': 'invalid_object', 'message': 'Provided object
is not valid. Got a ValueError error with message \u4f8b\u3048 is not an TLD',
'request_id': 'req-fa7cb43e-a6e9-41f2-b878-1ced6a853a2a'}
Expected Result:
Should pass
Notes:
1) There is an tempest patch could be used to reproduce the scenario:
https://review.opendev.org/c/openstack/designate-tempest-plugin/+/779558
2) Documentation: https://docs.openstack.org/api-ref/dns/?expanded
=get-the-name-servers-for-a-zone-detail,list-all-recordsets-owned-by-
project-detail,create-zone-detail,create-tld-detail#create-tld
To manage notifications about this bug go to:
https://bugs.launchpad.net/designate/+bug/1918653/+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 1918155] Re: Can't create m2 interface on the 15.3.2
A similar bug: https://bugs.launchpad.net/neutron/+bug/1903531
As discussed above, there is known issue on upgrading from 15.3.0 to
15.3.2. It seems you were hitting that issue. However, based on
discussion on https://bugs.launchpad.net/neutron/+bug/1903531, this
issue won't be fixed.
Quoted from https://bugs.launchpad.net/neutron/+bug/1903531/comments/20
Based on discussion with release and requirements teams on
http://eavesdrop.openstack.org/irclogs/%23openstack-requirements
/%23openstack-requirements.2020-11-24.log.html#t2020-11-24T21:36:35 it's
the best to revert this patch now. I know it's very bad for people who
already updated their envs but we can't do much more there :/ Sorry for
that.
** Changed in: neutron
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1918155
Title:
Can't create m2 interface on the 15.3.2
Status in neutron:
Won't Fix
Bug description:
Ubuntu 18.04, Openstack Train from the official repository.
Using ml2 driver with the provider networks.
Everything worked fine on the neutron 15.3.0, but after upgrade I got this:
2021-03-08 04:54:59.948 4554 INFO
neutron.plugins.ml2.drivers.agent._common_agent
[req-e7b32ad7-9259-49a5-bad9-20a11f64b104 - - - - -] Linux bridge agent Agent
out of sync with plugin!
2021-03-08 04:54:59.948 4554 INFO neutron.agent.securitygroups_rpc
[req-e7b32ad7-9259-49a5-bad9-20a11f64b104 - - - - -] Preparing filters for
devices {'tap28c0b6e8-76'}
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent
[req-e7b32ad7-9259-49a5-bad9-20a11f64b104 - - - - -] Error in agent loop.
Devices info: {'current': {'tap28c0b6e8-76'}, 'timestamps': {'tap28c0b6e8-76':
15}, 'added': {'tap28c0b6e8-76'}, 'removed': set(), 'updated': set()}:
TypeError:
unexpected type for addr arg
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent Traceback (most recent call
last):
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent File
"/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/agent/_common_agent.py",
line 465, in daemon_loop
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent sync =
self.process_network_devices(device_info)
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent File
"/usr/lib/python3/dist-packages/osprofiler/profiler.py", line 160, in wrapper
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent result = f(*args, **kwargs)
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent File
"/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/agent/_common_agent.py",
line 207, in process_network_devices
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent device_info.get('updated'))
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent File
"/usr/lib/python3/dist-packages/neutron/agent/securitygroups_rpc.py", line 258,
in setup_port_filters
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent
self.prepare_devices_filter(new_devices)
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent File
"/usr/lib/python3/dist-packages/neutron/agent/securitygroups_rpc.py", line 123,
in decorated_function
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent *args, **kwargs)
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent File
"/usr/lib/python3/dist-packages/neutron/agent/securitygroups_rpc.py", line 135,
in prepare_devices_filter
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent
self._apply_port_filter(device_ids)
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent File
"/usr/lib/python3/dist-packages/neutron/agent/securitygroups_rpc.py", line 159,
in _apply_port_filter
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent security_groups,
security_group_member_ips)
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent File
"/usr/lib/python3/dist-packages/neutron/agent/securitygroups_rpc.py", line 176,
in _update_security_group_info
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent remote_sg_id, member_ips)
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent File
"/usr/lib/python3/dist-packages/neutron/agent/linux/iptables_firewall.py", line
150, in update_security_group_members
2021-03-08 04:55:00.294 4554 ERROR
neutron.plugins.ml2.drivers.agent._common_agent
self._update_ipset_members(sg_id, sg_members)
[Yahoo-eng-team] [Bug 1869136] Re: Use public flat network to create vm faild
** Changed in: neutron Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1869136 Title: Use public flat network to create vm faild Status in neutron: Invalid Bug description: When creating a VM, use a flat network(--public) to report an error, and use vxlan non public network to create a VM normally. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1869136/+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 1858993] Re: Too many security group policies
I don't think neutron will change the way to implement the OVS hybrid. You can try the OVS firewall as @Yulong suggested. ** Changed in: neutron Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1858993 Title: Too many security group policies Status in neutron: Won't Fix Bug description: The problem we encountered in production was that when using the security group policy for east-west isolation, the current mechanism would create a bridge for each virtual machine, and issue the same policy for the virtual machine under the same segment. Increasing the number of virtual machines will waste more resource and affect system performance. So what is the original intention to achieve the purpose? whether we should bound the virtual machine on the same node to a same bridge, Instead of creating a new bridge for each one To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1858993/+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 1858421] Re: [neutronclient]unit tests in py36 failed due to UnicodeEncodeError
** Also affects: python-neutronclient
Importance: Undecided
Status: New
** Changed in: python-neutronclient
Status: New => Confirmed
** Changed in: python-neutronclient
Importance: Undecided => Critical
** 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/1858421
Title:
[neutronclient]unit tests in py36 failed due to UnicodeEncodeError
Status in neutron:
Invalid
Status in python-neutronclient:
Confirmed
Bug description:
UTs report the following error:
UnicodeEncodeError: 'ascii' codec can't encode characters in position 19-21:
ordinal not in range(128)
2020-01-06 09:01:44.749984 | ubuntu-bionic | Traceback (most recent call
last):
2020-01-06 09:01:44.749996 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/cliff/app.py",
line 401, in run_subcommand
2020-01-06 09:01:44.750008 | ubuntu-bionic | result = cmd.run(parsed_args)
2020-01-06 09:01:44.750020 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/cliff/command.py",
line 185, in run
2020-01-06 09:01:44.750034 | ubuntu-bionic | return_code =
self.take_action(parsed_args) or 0
2020-01-06 09:01:44.750055 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/stestr/commands/run.py",
line 247, in take_action
2020-01-06 09:01:44.750069 | ubuntu-bionic |
all_attachments=all_attachments, pdb=args.pdb)
2020-01-06 09:01:44.750080 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/stestr/commands/run.py",
line 543, in run_command
2020-01-06 09:01:44.750091 | ubuntu-bionic |
all_attachments=all_attachments)
2020-01-06 09:01:44.750101 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/stestr/commands/run.py",
line 609, in _run_tests
2020-01-06 09:01:44.750111 | ubuntu-bionic | return run_tests()
2020-01-06 09:01:44.750122 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/stestr/commands/run.py",
line 606, in run_tests
2020-01-06 09:01:44.750132 | ubuntu-bionic |
all_attachments=all_attachments)
2020-01-06 09:01:44.750143 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/stestr/commands/load.py",
line 245, in load
2020-01-06 09:01:44.750155 | ubuntu-bionic | all_attachments)
2020-01-06 09:01:44.750166 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/stestr/commands/load.py",
line 278, in _load_case
2020-01-06 09:01:44.750177 | ubuntu-bionic | case.run(result)
2020-01-06 09:01:44.750187 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/testtools/testsuite.py",
line 171, in run
2020-01-06 09:01:44.750198 | ubuntu-bionic | result.status(**event_dict)
2020-01-06 09:01:44.750208 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/testtools/testresult/real.py",
line 468, in status
2020-01-06 09:01:44.750220 | ubuntu-bionic |
_strict_map(methodcaller('status', *args, **kwargs), self.targets)
2020-01-06 09:01:44.750231 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/testtools/testresult/real.py",
line 443, in _strict_map
2020-01-06 09:01:44.750242 | ubuntu-bionic | return list(map(function,
*sequences))
2020-01-06 09:01:44.750253 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/testtools/testresult/real.py",
line 570, in status
2020-01-06 09:01:44.750264 | ubuntu-bionic | target.status(**kwargs)
2020-01-06 09:01:44.750274 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/testtools/testresult/real.py",
line 468, in status
2020-01-06 09:01:44.750285 | ubuntu-bionic |
_strict_map(methodcaller('status', *args, **kwargs), self.targets)
2020-01-06 09:01:44.750297 | ubuntu-bionic | File
"/home/zuul/src/opendev.org/openstack/python-neutronclient/.tox/cover/lib/python3.6/site-packages/testtools/testresult/real.py",
line 443, in _strict_map
2020-01-06 09:01:44.750307 | ubuntu-bionic | return list(map(function,
*sequences))
2020-01-06 09:01:44.750318 | ubuntu-bionic | File
[Yahoo-eng-team] [Bug 1848131] Re: [FWaaS] Support blacklist filtering
I think "close by default" is the general practice in OpenStack, mainly for security reasons. I personally don't think it is a good idea to change that, but I marked this bug as "Opinion" so others can weight in this proposal. ** Tags added: fwaas ** Changed in: neutron Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1848131 Title: [FWaaS] Support blacklist filtering Status in neutron: Opinion Bug description: Currently, FWaaS v1/v2 insert default rule 'deny all' and admin should add white list to be allowed. I think in private cloud, whitelist based filtering which by default 'allow all' and add black list to be filtered, also will be necessary. For our cases, we have some sensitive services (DB[3306] for example) to be blocked from some projects. By default, what we need is to block the some ports from somewhere, we just changed default rule 'deny all' to 'allow all'. I will be happily accept if I can take this by config. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1848131/+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 1837169] Re: Stein: testing _make_floatingip fails in Debian Sid
As comment #1 suggested, this bug is fixed and I am going to close this ticket, but feel free to re-open it if needed. ** 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/1837169 Title: Stein: testing _make_floatingip fails in Debian Sid Status in neutron: Invalid Bug description: Hi, I'm trying to build Stein Neutron from Buster to Sid. There's the following 4 unit tests failing when building the debian package in Sid, all located in neutron.tests.unit.extensions: test_extraroute.ExtraRouteDBIntTestCase.test_floatingip_via_router_interface_returns_201 test_extraroute.ExtraRouteDBSepTestCase.test_floatingip_via_router_interface_returns_201 test_l3.L3NatDBIntTestCase.test_floatingip_via_router_interface_returns_201 test_l3.L3NatDBSepTestCase.test_floatingip_via_router_interface_returns_201 All of these tests fails with more or less the same stack dump, as seen below. (unstable-amd64-sbuild)root@buzig2:~/neutron# PYTOHN=python3 PYTHONPATH=`pwd`/debian/tmp/usr/lib/python3/dist-packages stestr run --subunit neutron.tests.unit.extensions.test_extraroute.ExtraRouteDBIntTestCase.test_floatingip_via_router_interface_returns_201 | subunit2pyunit neutron.tests.unit.extensions.test_extraroute.ExtraRouteDBIntTestCase.test_floatingip_via_router_interface_returns_201 neutron.tests.unit.extensions.test_extraroute.ExtraRouteDBIntTestCase.test_floatingip_via_router_interface_returns_201 ... FAIL == FAIL: neutron.tests.unit.extensions.test_extraroute.ExtraRouteDBIntTestCase.test_floatingip_via_router_interface_returns_201 neutron.tests.unit.extensions.test_extraroute.ExtraRouteDBIntTestCase.test_floatingip_via_router_interface_returns_201 -- _StringException: Traceback (most recent call last): File "/root/neutron/neutron/tests/base.py", line 176, in func return f(self, *args, **kwargs) File "/root/neutron/neutron/tests/base.py", line 176, in func return f(self, *args, **kwargs) File "/root/neutron/neutron/tests/unit/extensions/test_l3.py", line 3183, in test_floatingip_via_router_interface_returns_201 self._test_floatingip_via_router_interface(exc.HTTPCreated.code) File "/root/neutron/neutron/tests/unit/extensions/test_l3.py", line 3137, in _test_floatingip_via_router_interface http_status=http_status) File "/root/neutron/neutron/tests/unit/extensions/test_l3.py", line 510, in _make_floatingip self.assertEqual(http_status, res.status_int) File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 411, in assertEqual self.assertThat(observed, matcher, message) File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 498, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 201 != 500 -- Ran 1 test in 11.585s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1837169/+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 1824988] Re: updating multisegment network segmentation id does not raise error and although the update succeeds it doesn't work
I am going to close this bug, but please feel free to re-open it if comment #3 doesn't address your concern. ** 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/1824988 Title: updating multisegment network segmentation id does not raise error and although the update succeeds it doesn't work Status in neutron: Invalid Bug description: Creating a multi-segment network and then updating the VLAN segmentation ID of only one of the segment succeeds but it doesn't update. When a show of the network is done we observe that network segment id is not updated. Expected Behavior: A user should expect an error if update is not supported (or) the update should succeed correctly. In the above scenario, we don't see either of them occurring. Furthermore, this would also mean that when plugin calls update_precommit and update_post commit, it sets the data present in database from create in call context instead of setting the user provided data in the context. Also there were no ports created in the network. Output of the commands to reproduce are available at : http://paste.openstack.org/show/749350/ OpenStack version: master Deployment: Devstack Distro: Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1824988/+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 1824788] Re: installed neutron, but no provider network exists
Hi @Realtime, It seems the document below is what you need: https://docs.openstack.org/install-guide/launch-instance-networks- provider.html I am going to proceed to close this bug but please feel free to re-open it if it still has problems. ** 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/1824788 Title: installed neutron, but no provider network exists Status in neutron: Invalid Bug description: I installed neutron (Rocky) in Ubuntu exactly following the documentation https://docs.openstack.org/neutron/rocky/install/controller-install-ubuntu.html I ended up with having no provider network. Are there addional steps required to add a provider network? If so, why is the documentation keeping this fact secret? This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: Ending up with no provider network - [x] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 13.0.3.dev125 on 2019-04-12 05:13 SHA: 65bee80deb976b7be02091239255390dd2af5a5e Source: https://git.openstack.org/cgit/openstack/neutron/tree/doc/source/install/controller-install-ubuntu.rst URL: https://docs.openstack.org/neutron/rocky/install/controller-install-ubuntu.html To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1824788/+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 1810314] Re: neutron objects base get_values() fails with KeyError
I don't think this is a neutron bug. The error happened only in the case that the fake query class is used in unit tests. It should be resolved once the testing code is updated. See if this patch fixes your issue: https://review.openstack.org/#/c/629922/ ** Changed in: neutron Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1810314 Title: neutron objects base get_values() fails with KeyError Status in neutron: Won't Fix Status in Tricircle: In Progress Bug description: As of December 20 2018 the python unit test jobs for the tricircle project have been failing [1]. After going through the tricircle/neutron commits since that date, it seems some changes went into neutron that caused the breakage. If I run tricircle python 3.5 unit test with neutron commit 55c5139d79ef09869eea1201c736eee8de3ec651 (the last commit on neutron from Dec 19, 2018) the unit tests all pass. If I run the same UTs with neutron (latest) master they fail with the same errors found in the results of [2]. While this is just a guess, I suspect that maybe neutron changes that landed on Dec 20 related to "Convert Subnet to OVO in ipam_pluggable_backend.py" [3] introduced the breakage. In any case, something landed in neutron around Dec 20, 2018 that has broken tricircle. [1] http://zuul.openstack.org/builds?branch=master=openstack%2Ftricircle_name=openstack-tox-py35 [2] https://review.openstack.org/#/c/627888/ [3] https://review.openstack.org/#/c/610184/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1810314/+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 1809037] [NEW] [RFE] Add anti-affinity-group to binding:profile
Public bug reported: In SRIOV scenario, it is a common use case that a VM has two ports and users want to have the two ports scheduling to two different PFs for redundancy. The proposal for Neutron is to introduce a new key 'anti_affinity_group' in binding:profile. The value of 'anti_affinity_group' is a unique ID for grouping neutron ports. Nova is responsible to schedule ports that has the same 'anti-affinity_group' to different PFs. Nova BP: https://blueprints.launchpad.net/nova/+spec/schedule-vm-nics- to-different-pf ** Affects: neutron Importance: Undecided Assignee: Hongbin Lu (hongbin.lu) Status: New ** Tags: rfe ** Tags added: rfe ** Changed in: neutron Assignee: (unassigned) => Hongbin Lu (hongbin.lu) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1809037 Title: [RFE] Add anti-affinity-group to binding:profile Status in neutron: New Bug description: In SRIOV scenario, it is a common use case that a VM has two ports and users want to have the two ports scheduling to two different PFs for redundancy. The proposal for Neutron is to introduce a new key 'anti_affinity_group' in binding:profile. The value of 'anti_affinity_group' is a unique ID for grouping neutron ports. Nova is responsible to schedule ports that has the same 'anti- affinity_group' to different PFs. Nova BP: https://blueprints.launchpad.net/nova/+spec/schedule-vm-nics- to-different-pf To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1809037/+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 1808595] [NEW] fullstack test neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_gateway_ip_changed failed intermittently
Public bug reported:
Neutron fullstack test
'neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_gateway_ip_changed'
intermittently failed with the following error
Traceback (most recent call last):
File "/opt/stack/new/neutron/neutron/tests/base.py", line 151, in func
return f(self, *args, **kwargs)
File "/opt/stack/new/neutron/neutron/tests/fullstack/test_l3_agent.py", line
428, in test_gateway_ip_changed
self._test_gateway_ip_changed()
File "/opt/stack/new/neutron/neutron/tests/fullstack/test_l3_agent.py", line
116, in _test_gateway_ip_changed
{'ip_address': ip_2}])
File "/opt/stack/new/neutron/neutron/tests/fullstack/resources/client.py",
line 141, in update_port
return self._update_resource('port', port_id, kwargs)
File "/opt/stack/new/neutron/neutron/tests/fullstack/resources/client.py",
line 57, in _update_resource
resp = update(id, body=body)
File
"/opt/stack/new/neutron/.tox/dsvm-fullstack/lib/python3.5/site-packages/neutronclient/v2_0/client.py",
line 799, in update_port
revision_number=revision_number)
File
"/opt/stack/new/neutron/.tox/dsvm-fullstack/lib/python3.5/site-packages/neutronclient/v2_0/client.py",
line 2375, in _update_resource
return self.put(path, **kwargs)
File
"/opt/stack/new/neutron/.tox/dsvm-fullstack/lib/python3.5/site-packages/neutronclient/v2_0/client.py",
line 363, in put
headers=headers, params=params)
File
"/opt/stack/new/neutron/.tox/dsvm-fullstack/lib/python3.5/site-packages/neutronclient/v2_0/client.py",
line 331, in retry_request
headers=headers, params=params)
File
"/opt/stack/new/neutron/.tox/dsvm-fullstack/lib/python3.5/site-packages/neutronclient/v2_0/client.py",
line 294, in do_request
self._handle_fault_response(status_code, replybody, resp)
File
"/opt/stack/new/neutron/.tox/dsvm-fullstack/lib/python3.5/site-packages/neutronclient/v2_0/client.py",
line 269, in _handle_fault_response
exception_handler_v20(status_code, error_body)
File
"/opt/stack/new/neutron/.tox/dsvm-fullstack/lib/python3.5/site-packages/neutronclient/v2_0/client.py",
line 93, in exception_handler_v20
request_ids=request_ids)
neutronclient.common.exceptions.IpAddressAlreadyAllocatedClient: IP address
240.27.66.102 already allocated in subnet 814bfcc0-0d3d-4b45-8436-c76e7a000150
Neutron server returns request_ids: ['req-bf114fe1-66a9-4c86-8bc7-d759e10bf660']
Failure examples:
http://logs.openstack.org/36/617736/10/check/neutron-fullstack/61fa2eb/logs/testr_results.html.gz
http://logs.openstack.org/68/424468/34/check/neutron-fullstack/4422e70/logs/testr_results.html.gz
http://logs.openstack.org/08/620708/2/check/neutron-fullstack/51099db/logs/testr_results.html.gz
http://logs.openstack.org/09/608909/24/check/neutron-fullstack/2891c09/logs/testr_results.html.gz
http://logs.openstack.org/82/610182/13/check/neutron-fullstack/de0ad4f/logs/testr_results.html.gz
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
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/1808595
Title:
fullstack test
neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_gateway_ip_changed
failed intermittently
Status in neutron:
In Progress
Bug description:
Neutron fullstack test
'neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_gateway_ip_changed'
intermittently failed with the following error
Traceback (most recent call last):
File "/opt/stack/new/neutron/neutron/tests/base.py", line 151, in func
return f(self, *args, **kwargs)
File "/opt/stack/new/neutron/neutron/tests/fullstack/test_l3_agent.py",
line 428, in test_gateway_ip_changed
self._test_gateway_ip_changed()
File "/opt/stack/new/neutron/neutron/tests/fullstack/test_l3_agent.py",
line 116, in _test_gateway_ip_changed
{'ip_address': ip_2}])
File "/opt/stack/new/neutron/neutron/tests/fullstack/resources/client.py",
line 141, in update_port
return self._update_resource('port', port_id, kwargs)
File "/opt/stack/new/neutron/neutron/tests/fullstack/resources/client.py",
line 57, in _update_resource
resp = update(id, body=body)
File
"/opt/stack/new/neutron/.tox/dsvm-fullstack/lib/python3.5/site-packages/neutronclient/v2_0/client.py",
line 799, in update_port
revision_number=revision_number)
File
"/opt/stack/new/neutron/.tox/dsvm-fullstack/lib/python3.5/site-packages/neutronclient/v2_0/client.py",
line 2375, in _update_resource
return self.put(path, **kwargs)
File
"/opt/stack/new/neutron/.tox/dsvm-fullstack/lib/python3.5/site-packages/neutronclient/v2_0/client.py",
line 363, in put
headers=h
[Yahoo-eng-team] [Bug 1798688] Re: iptables_hybrid tests tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server failed
This happened again: http://logs.openstack.org/26/615126/5/check /tempest-full/69d913a/job-output.txt.gz#_2018-11-06_19_51_54_083047 ** Also affects: nova 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/1798688 Title: iptables_hybrid tests tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server failed Status in neutron: Incomplete Status in OpenStack Compute (nova): New Bug description: * Job: neutron-tempest-iptables_hybrid * Failed test: tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server * Example of failure: http://logs.openstack.org/80/610280/8/check/neutron-tempest-iptables_hybrid/caa373a/job-output.txt.gz Details: (ServersNegativeTestJSON:tearDown) Server 7e7cf40f-0ab7-4f22 -91ce-6f4e22a54ac2 failed to reach ACTIVE status and task state "None" within the required time (196 s). Current status: SHELVED_OFFLOADED. Current task state: None. * Logstash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22failed%20to%20reach%20ACTIVE%20status%20and%20task%20state%20%5C%5C%5C%22None%5C%5C%5C%22%20within%20the%20required%20time%5C%22 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1798688/+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 1800915] [NEW] Neutron's endpoint cannot tell the difference between '-' and '_'
Public bug reported: The current neutron API seems to treat '-' and '_' the same. For example, both "/v2.0/security-groups" and "/v2.0/security_groups" will process by the same controller and succeed. More examples is as below: $ curl -g -i -X GET http://10.0.2.15:9696/v2.0/security-groups -H "Accept: application/json" -H "X-Auth-Token: $TOKEN" HTTP/1.1 200 OK $ curl -g -i -X GET http://10.0.2.15:9696/v2.0/security_groups -H "Accept: application/json" -H "X-Auth-Token: $TOKEN" HTTP/1.1 200 OK $ curl -g -i -X GET http://10.0.2.15:9696/v2.0/availability-zones -H "Accept: application/json" -H "X-Auth-Token: $TOKEN" HTTP/1.1 200 OK $ curl -g -i -X GET http://10.0.2.15:9696/v2.0/availability_zones -H "Accept: application/json" -H "X-Auth-Token: $TOKEN" HTTP/1.1 200 OK IMHO, neutron should be strict between '-' and '_'. For example, the second and third commands above should fail or we should update the API documentation about that. ** Affects: neutron Importance: Undecided Assignee: Hongbin Lu (hongbin.lu) Status: New ** Tags: api ** Tags added: api ** Changed in: neutron Assignee: (unassigned) => Hongbin Lu (hongbin.lu) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1800915 Title: Neutron's endpoint cannot tell the difference between '-' and '_' Status in neutron: New Bug description: The current neutron API seems to treat '-' and '_' the same. For example, both "/v2.0/security-groups" and "/v2.0/security_groups" will process by the same controller and succeed. More examples is as below: $ curl -g -i -X GET http://10.0.2.15:9696/v2.0/security-groups -H "Accept: application/json" -H "X-Auth-Token: $TOKEN" HTTP/1.1 200 OK $ curl -g -i -X GET http://10.0.2.15:9696/v2.0/security_groups -H "Accept: application/json" -H "X-Auth-Token: $TOKEN" HTTP/1.1 200 OK $ curl -g -i -X GET http://10.0.2.15:9696/v2.0/availability-zones -H "Accept: application/json" -H "X-Auth-Token: $TOKEN" HTTP/1.1 200 OK $ curl -g -i -X GET http://10.0.2.15:9696/v2.0/availability_zones -H "Accept: application/json" -H "X-Auth-Token: $TOKEN" HTTP/1.1 200 OK IMHO, neutron should be strict between '-' and '_'. For example, the second and third commands above should fail or we should update the API documentation about that. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1800915/+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 1687027] Re: test_walk_versions tests fail with "IndexError: tuple index out of range" after timeout
Still happening: http://logs.openstack.org/88/555088/29/check/neutron- functional/0b00b31/job-output.txt.gz#_2018-10-25_22_18_28_107639 ** Changed in: neutron Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1687027 Title: test_walk_versions tests fail with "IndexError: tuple index out of range" after timeout Status in neutron: Confirmed Bug description: http://logs.openstack.org/99/460399/1/check/gate-neutron-dsvm- functional-ubuntu-xenial/25de43d/testr_results.html.gz Traceback (most recent call last): File "neutron/tests/base.py", line 115, in func return f(self, *args, **kwargs) File "neutron/tests/base.py", line 115, in func return f(self, *args, **kwargs) File "neutron/tests/functional/db/test_migrations.py", line 551, in test_walk_versions self._migrate_up(config, engine, dest, curr, with_data=True) File "neutron/tests/functional/db/test_migrations.py", line 537, in _migrate_up migration.do_alembic_command(config, 'upgrade', dest) File "neutron/db/migration/cli.py", line 109, in do_alembic_command getattr(alembic_command, cmd)(config, *args, **kwargs) File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/command.py", line 254, in upgrade script.run_env() File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/script/base.py", line 416, in run_env util.load_python_file(self.dir, 'env.py') File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/util/pyfiles.py", line 93, in load_python_file module = load_module_py(module_id, path) File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/util/compat.py", line 75, in load_module_py mod = imp.load_source(module_id, path, fp) File "neutron/db/migration/alembic_migrations/env.py", line 120, in run_migrations_online() File "neutron/db/migration/alembic_migrations/env.py", line 114, in run_migrations_online context.run_migrations() File "", line 8, in run_migrations File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/runtime/environment.py", line 817, in run_migrations self.get_context().run_migrations(**kw) File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/runtime/migration.py", line 323, in run_migrations step.migration_fn(**kw) File "/opt/stack/new/neutron/neutron/db/migration/alembic_migrations/versions/mitaka/expand/3894bccad37f_add_timestamp_to_base_resources.py", line 36, in upgrade sa.Column(column_name, sa.DateTime(), nullable=True) File "", line 8, in add_column File "", line 3, in add_column File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/operations/ops.py", line 1551, in add_column return operations.invoke(op) File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/operations/base.py", line 318, in invoke return fn(self, operation) File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/operations/toimpl.py", line 123, in add_column schema=schema File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/ddl/impl.py", line 172, in add_column self._exec(base.AddColumn(table_name, column, schema=schema)) File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/alembic/ddl/impl.py", line 118, in _exec return conn.execute(construct, *multiparams, **params) File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 945, in execute return meth(self, multiparams, params) File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/sqlalchemy/sql/ddl.py", line 68, in _execute_on_connection return connection._execute_ddl(self, multiparams, params) File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1002, in _execute_ddl compiled File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1189, in _execute_context context) File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1398, in _handle_dbapi_exception util.raise_from_cause(newraise, exc_info) File "/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause reraise(type(exception), exception, tb=exc_tb,
[Yahoo-eng-team] [Bug 1799790] [NEW] Scenario job neutron_tempest_plugin.scenario.test_floatingip.FloatingIPPortDetailsTest.test_floatingip_port_details timeout
Public bug reported: Job: any tempest plugin scenario jobs Failed test: neutron_tempest_plugin.scenario.test_floatingip.FloatingIPPortDetailsTest.test_floatingip_port_details Sample failure: http://logs.openstack.org/36/610536/1/check/neutron-tempest-plugin-scenario-linuxbridge/dbac8ec/job-output.txt.gz Traceback (most recent call last): File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 247, in test_floatingip_port_details fip = self._wait_for_fip_port_down(fip['id']) File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 317, in _wait_for_fip_port_down raise exceptions.TimeoutException(message) tempest.lib.exceptions.TimeoutException: Request timed out Details: Floating IP f7628133-7448-43d9-8fd3-f14784d9ecf9 attached port status failed to transition to DOWN (current status BUILD) within the required time (120 s). Logstash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22attached%20port%20status%20failed%20to%20transition%20to%20DOWN%5C%22 (10 hits in 7 days) ** Affects: neutron Importance: Undecided Status: New ** Tags: gate-failure ** Tags added: gate-failure ** Description changed: Job: any tempest plugin scenario jobs Failed test: neutron_tempest_plugin.scenario.test_floatingip.FloatingIPPortDetailsTest.test_floatingip_port_details Sample failure: http://logs.openstack.org/36/610536/1/check/neutron-tempest-plugin-scenario-linuxbridge/dbac8ec/job-output.txt.gz - Traceback (most recent call last): -File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 247, in test_floatingip_port_details - fip = self._wait_for_fip_port_down(fip['id']) -File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 317, in _wait_for_fip_port_down - raise exceptions.TimeoutException(message) - tempest.lib.exceptions.TimeoutException: Request timed out - Details: Floating IP f7628133-7448-43d9-8fd3-f14784d9ecf9 attached port status failed to transition to DOWN (current status BUILD) within the required time (120 s). + Traceback (most recent call last): + File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 247, in test_floatingip_port_details + fip = self._wait_for_fip_port_down(fip['id']) + File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 317, in _wait_for_fip_port_down + raise exceptions.TimeoutException(message) + tempest.lib.exceptions.TimeoutException: Request timed out + Details: Floating IP f7628133-7448-43d9-8fd3-f14784d9ecf9 attached port status failed to transition to DOWN (current status BUILD) within the required time (120 s). Logstash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22attached%20port%20status%20failed%20to%20transition%20to%20DOWN%5C%22 + (10 hits in 7 days) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1799790 Title: Scenario job neutron_tempest_plugin.scenario.test_floatingip.FloatingIPPortDetailsTest.test_floatingip_port_details timeout Status in neutron: New Bug description: Job: any tempest plugin scenario jobs Failed test: neutron_tempest_plugin.scenario.test_floatingip.FloatingIPPortDetailsTest.test_floatingip_port_details Sample failure: http://logs.openstack.org/36/610536/1/check/neutron-tempest-plugin-scenario-linuxbridge/dbac8ec/job-output.txt.gz Traceback (most recent call last): File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 247, in test_floatingip_port_details fip = self._wait_for_fip_port_down(fip['id']) File "/opt/stack/neutron-tempest-plugin/neutron_tempest_plugin/scenario/test_floatingip.py", line 317, in _wait_for_fip_port_down raise exceptions.TimeoutException(message) tempest.lib.exceptions.TimeoutException: Request timed out Details: Floating IP f7628133-7448-43d9-8fd3-f14784d9ecf9 attached port status failed to transition to DOWN (current status BUILD) within the required time (120 s). Logstash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22attached%20port%20status%20failed%20to%20transition%20to%20DOWN%5C%22 (10 hits in 7 days) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1799790/+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 1798688] [NEW] iptables_hybrid tests tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server failed
Public bug reported: * Job: neutron-tempest-iptables_hybrid * Failed test: tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server * Example of failure: http://logs.openstack.org/80/610280/8/check/neutron-tempest-iptables_hybrid/caa373a/job-output.txt.gz Details: (ServersNegativeTestJSON:tearDown) Server 7e7cf40f-0ab7-4f22 -91ce-6f4e22a54ac2 failed to reach ACTIVE status and task state "None" within the required time (196 s). Current status: SHELVED_OFFLOADED. Current task state: None. * Logstash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22failed%20to%20reach%20ACTIVE%20status%20and%20task%20state%20%5C%5C%5C%22None%5C%5C%5C%22%20within%20the%20required%20time%5C%22 ** Affects: neutron Importance: Undecided Status: New ** Tags: gate-failure ** 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/1798688 Title: iptables_hybrid tests tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server failed Status in neutron: New Bug description: * Job: neutron-tempest-iptables_hybrid * Failed test: tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server * Example of failure: http://logs.openstack.org/80/610280/8/check/neutron-tempest-iptables_hybrid/caa373a/job-output.txt.gz Details: (ServersNegativeTestJSON:tearDown) Server 7e7cf40f-0ab7-4f22 -91ce-6f4e22a54ac2 failed to reach ACTIVE status and task state "None" within the required time (196 s). Current status: SHELVED_OFFLOADED. Current task state: None. * Logstash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22failed%20to%20reach%20ACTIVE%20status%20and%20task%20state%20%5C%5C%5C%22None%5C%5C%5C%22%20within%20the%20required%20time%5C%22 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1798688/+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 1798689] [NEW] Fullstack test test_create_one_default_qos_policy_per_project failed
Public bug reported: * Job: neutron-fullstack-python36 * Failed tests: test_create_one_default_qos_policy_per_project, test_create_two_default_qos_policies_per_project, test_update_default_status, test_update_default_status_conflict * Example failure: http://logs.openstack.org/80/610280/8/check/neutron-fullstack-python36/9811ceb/logs/testr_results.html.gz * Sample trace: http://paste.openstack.org/show/732449/ * Logstash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22ValueError%3A%20Field%20%60project_id'%20cannot%20be%20None%5C%22 ** Affects: neutron Importance: Undecided Status: New ** Tags: gate-failure ** 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/1798689 Title: Fullstack test test_create_one_default_qos_policy_per_project failed Status in neutron: New Bug description: * Job: neutron-fullstack-python36 * Failed tests: test_create_one_default_qos_policy_per_project, test_create_two_default_qos_policies_per_project, test_update_default_status, test_update_default_status_conflict * Example failure: http://logs.openstack.org/80/610280/8/check/neutron-fullstack-python36/9811ceb/logs/testr_results.html.gz * Sample trace: http://paste.openstack.org/show/732449/ * Logstash: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22ValueError%3A%20Field%20%60project_id'%20cannot%20be%20None%5C%22 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1798689/+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 1794865] [NEW] Failed to check policy on listing loggable resources
Public bug reported: Use the sample policy file and non-admin credential. Try to list loggable resources but failed. $ source /opt/stack/devstack/openrc demo demo $ openstack network loggable resources list Failed to check policy tenant_id:%(tenant_id)s because Unable to verify match:%(tenant_id)s as the parent resource: tenant was not found. Neutron server returns request_ids: ['req-55c56d3f-246c-486c-8763-8b27248fef09'] ** Affects: neutron Importance: Undecided Assignee: Hongbin Lu (hongbin.lu) Status: In Progress ** Description changed: Use the sample policy file and try to list loggable resources but failed. + $ source /opt/stack/devstack/openrc demo demo $ openstack network loggable resources list Failed to check policy tenant_id:%(tenant_id)s because Unable to verify match:%(tenant_id)s as the parent resource: tenant was not found. Neutron server returns request_ids: ['req-55c56d3f-246c-486c-8763-8b27248fef09'] ** Description changed: - Use the sample policy file and try to list loggable resources but - failed. + Use the sample policy file and non-admin credential. Try to list + loggable resources but failed. $ source /opt/stack/devstack/openrc demo demo $ openstack network loggable resources list Failed to check policy tenant_id:%(tenant_id)s because Unable to verify match:%(tenant_id)s as the parent resource: tenant was not found. Neutron server returns request_ids: ['req-55c56d3f-246c-486c-8763-8b27248fef09'] -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1794865 Title: Failed to check policy on listing loggable resources Status in neutron: In Progress Bug description: Use the sample policy file and non-admin credential. Try to list loggable resources but failed. $ source /opt/stack/devstack/openrc demo demo $ openstack network loggable resources list Failed to check policy tenant_id:%(tenant_id)s because Unable to verify match:%(tenant_id)s as the parent resource: tenant was not found. Neutron server returns request_ids: ['req-55c56d3f-246c-486c-8763-8b27248fef09'] To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1794865/+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 1788184] Re: Failed to bind port on host in case DEVSTACK_GATE_VIRT_DRIVER=fake
I am going to mark this bug as "invalid" because it doesn't seem to be a
neutron bug.
** 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/1788184
Title:
Failed to bind port on host in case DEVSTACK_GATE_VIRT_DRIVER=fake
Status in neutron:
Invalid
Bug description:
We have problems with rally job in gate. When
DEVSTACK_GATE_VIRT_DRIVER=fake, it isn’t possible to boot instance, it
fails with ERROR state due to neutron.
ERROR neutron.plugins.ml2.managers [None req-db962060-2e20-440a-97ab-
5409ed8eecfb service neutron] Failed to bind port
146ee17f-4212-4f40-b291-5bdc0305226c on host ubuntu-xenial-ovh-
gra1-00013555231 for vnic_type normal using segments [{'network_id':
'8ee3524d-b732-45e6-a7c6-f31a9a21ba59', 'segmentation_id': 75,
'physical_network': None, 'id':
'61075d8d-d373-49d1-8010-8997a0eb5841', 'network_type': u'vxlan'}]
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1788184/+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 1788045] Re: Cannot delete security group rules with unicode chars in their description
FYI, this bug is forwarded to openstacksdk: https://storyboard.openstack.org/#!/story/2003517 ** Also affects: python-openstacksdk 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/1788045 Title: Cannot delete security group rules with unicode chars in their description Status in neutron: Invalid Status in OpenStack SDK: New Bug description: Some editing programs, like gdoc, will mutate double quotes to their unicode equivalent if you haven't disabled that feature. If someone accidentally creates a security group rule with a magic quote (due to an errant copy and paste) they could create a security group with a magic double quote in the description. Subsequent attempts to delete that rule will fail with "Failed to delete rule with name or ID 'fc52f547-300e-43cd-ae8e-833d856b304a': 'ascii' codec can't encode character u'\u201d' in position 136: ordinal not in range(128)" To fix this I had to go into the DB and update the description line to remove the errant magic quote, at which point the delete succeeded. I'm including the following in case anyone else hits this and wants a quick example of how to fix it: mysql> use neutron; mysql> select * from securitygrouprules where id='fc52f547-300e-43cd-ae8e-833d856b304a' \G *** 1. row *** project_id: 335384b960d53910a94b201fbb78a13a id: fc52f547-300e-43cd-ae8e-833d856b304a security_group_id: e595a97d-1729-4686-b5e7-123b4af30dba remote_group_id: e595a97d-1729-4686-b5e7-123b4af30dba direction: ingress ethertype: IPv4 protocol: icmp port_range_min: 11 port_range_max: NULL remote_ip_prefix: 0.0.0.0/0 standard_attr_id: 977 1 row in set (0.00 sec) mysql> select * from standardattributes where id=977; +-++-+-+---+-+ | id | resource_type | created_at | updated_at | description | revision_number | +-++-+-+---+-+ | 977 | securitygrouprules | 2018-08-08 22:37:56 | 2018-08-08 22:37:56 | ICMP Ping”| 0 | +-++-+-+---+-+ 1 row in set (0.00 sec) mysql> update standardattributes set description = "ICMP PING" where id=977; Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 (openstack) security group rule delete fc52f547-300e-43cd-ae8e-833d856b304a (openstack) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1788045/+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 1788045] Re: Cannot delete security group rules with unicode chars in their description
I am going to mark this bug as "invalid" since it doesn't seem to be a neutron bug. ** 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/1788045 Title: Cannot delete security group rules with unicode chars in their description Status in neutron: Invalid Bug description: Some editing programs, like gdoc, will mutate double quotes to their unicode equivalent if you haven't disabled that feature. If someone accidentally creates a security group rule with a magic quote (due to an errant copy and paste) they could create a security group with a magic double quote in the description. Subsequent attempts to delete that rule will fail with "Failed to delete rule with name or ID 'fc52f547-300e-43cd-ae8e-833d856b304a': 'ascii' codec can't encode character u'\u201d' in position 136: ordinal not in range(128)" To fix this I had to go into the DB and update the description line to remove the errant magic quote, at which point the delete succeeded. I'm including the following in case anyone else hits this and wants a quick example of how to fix it: mysql> use neutron; mysql> select * from securitygrouprules where id='fc52f547-300e-43cd-ae8e-833d856b304a' \G *** 1. row *** project_id: 335384b960d53910a94b201fbb78a13a id: fc52f547-300e-43cd-ae8e-833d856b304a security_group_id: e595a97d-1729-4686-b5e7-123b4af30dba remote_group_id: e595a97d-1729-4686-b5e7-123b4af30dba direction: ingress ethertype: IPv4 protocol: icmp port_range_min: 11 port_range_max: NULL remote_ip_prefix: 0.0.0.0/0 standard_attr_id: 977 1 row in set (0.00 sec) mysql> select * from standardattributes where id=977; +-++-+-+---+-+ | id | resource_type | created_at | updated_at | description | revision_number | +-++-+-+---+-+ | 977 | securitygrouprules | 2018-08-08 22:37:56 | 2018-08-08 22:37:56 | ICMP Ping”| 0 | +-++-+-+---+-+ 1 row in set (0.00 sec) mysql> update standardattributes set description = "ICMP PING" where id=977; Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 (openstack) security group rule delete fc52f547-300e-43cd-ae8e-833d856b304a (openstack) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1788045/+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 1787028] [NEW] neutron returned internal server error on updating tags
098
neutron-server[25320]: ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py", line
66, in __exit__
Aug 14 20:27:13.553503 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource
compat.reraise(exc_type, exc_value, exc_tb)
Aug 14 20:27:13.553764 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 2344,
in _flush
Aug 14 20:27:13.554255 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource flush_context.execute()
Aug 14 20:27:13.554546 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line
391, in execute
Aug 14 20:27:13.554774 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource rec.execute(self)
Aug 14 20:27:13.555115 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line
556, in execute
Aug 14 20:27:13.555799 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource uow
Aug 14 20:27:13.556067 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line
177, in save_obj
Aug 14 20:27:13.556317 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource mapper, table, update)
Aug 14 20:27:13.556543 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line
791, in _emit_update_statements
Aug 14 20:27:13.557347 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource (table.description,
len(records), rows))
Aug 14 20:27:13.557557 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource StaleDataError: UPDATE
statement on table 'standardattributes' expected to update 1 row(s); 0 were
matched.
Aug 14 20:27:13.557743 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource
Aug 14 20:27:13.561375 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: INFO neutron.wsgi [None
req-d0268850-9176-4fad-a645-d772b462c36c service kuryr] 198.72.124.15 "PUT
/v2.0/networks/e658851d-a85d-48a4-9635-3d517dc58b6e/tags/kuryr.net.uuid.lh:caa6ea05f9fae965c1d8e3aa76ad1faf
HTTP/1.1" status: 500 len: 368 time: 1.2829261
** Affects: kuryr-libnetwork
Importance: Undecided
Status: New
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: In Progress
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1787028
Title:
neutron returned internal server error on updating tags
Status in kuryr-libnetwork:
New
Status in neutron:
In Progress
Bug description:
Starting from Aug 14, 2018, kuryr-libnetwork's gate failed often with
the following error:
* job-output.txt.gz:
2018-08-14 20:27:14.391592 | primary | 2018-08-14 20:27:14.390 | {3}
kuryr_libnetwork.tests.fullstack.test_ipam.IpamTest.test_container_ipam_release_address_with_existing_network
[6.935607s] ... FAILED
2018-08-14 20:27:14.393446 | primary | 2018-08-14 20:27:14.392 |
2018-08-14 20:27:14.394830 | primary | 2018-08-14 20:27:14.394 | Captured
traceback:
2018-08-14 20:27:14.396797 | primary | 2018-08-14 20:27:14.396 |
~~~
2018-08-14 20:27:14.398457 | primary | 2018-08-14 20:27:14.398 |
Traceback (most recent call last):
2018-08-14 20:27:14.401028 | primary | 2018-08-14 20:27:14.400 | File
"kuryr_libnetwork/tests/fullstack/test_ipam.py", line 295, in
test_container_ipam_release_address_with_existing_network
2018-08-14 20:27:14.403113 | primary | 2018-08-14 20:27:14.402 |
ipam=fake_ipam)
2018-08-14 20:27:14.405412 | primary | 2018-08-14 20:27:14.404 | File
"/opt/stack/new/kuryr-libnetwork/.tox/fullstack/local/lib/python2.7/site-packages/docker/api/network.py",
line 152, in create_network
2018-08-14 20:27:14.407611 | primary | 2018-08-14 20:27:14.406 |
return self._result(res, json=True)
2018-08-14 20:27:14.409240 | primary | 2018-08-14 20:27:14.408 | File
"/opt/stack/new/kuryr-libnetwork/.tox/fullstack/local/lib/python2.7/site-packages/docker/api/client.py",
line 235, in _result
2018-08-14 20:27:14.411630 | pri
[Yahoo-eng-team] [Bug 1786347] [NEW] Incorrect entry point of metering iptables driver
Public bug reported: At the entry point 'neutron.services.metering_drivers', the alias 'iptables' is wrong. It was: iptables = neutron.services.metering.iptables.iptables_driver:IptablesMeteringDriver But it should be: iptables = neutron.services.metering.drivers.iptables.iptables_driver:IptablesMeteringDriver This cause the metering agent unable to load iptables driver via alias. ** Affects: neutron Importance: Undecided Assignee: Hongbin Lu (hongbin.lu) 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/1786347 Title: Incorrect entry point of metering iptables driver Status in neutron: In Progress Bug description: At the entry point 'neutron.services.metering_drivers', the alias 'iptables' is wrong. It was: iptables = neutron.services.metering.iptables.iptables_driver:IptablesMeteringDriver But it should be: iptables = neutron.services.metering.drivers.iptables.iptables_driver:IptablesMeteringDriver This cause the metering agent unable to load iptables driver via alias. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1786347/+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 1781156] Re: Randomly choose from multiple IPv6 stateless subnets
By referring to the multiple ipv6 prefixes spec [1], it is intentional
to include all the stateless IPv6 addresses into the port. The current
implementation seems to be correct. In addition, you can look at this
bug [2], in which people was complaining that neutron was not picking
all the SLAAC addresses.
[1]
https://specs.openstack.org/openstack/neutron-specs/specs/kilo/multiple-ipv6-prefixes.html
[2] https://bugs.launchpad.net/neutron/+bug/1358709
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1781156
Title:
Randomly choose from multiple IPv6 stateless subnets
Status in neutron:
Invalid
Bug description:
If we create a dual-stack network, both with two IPv4 and IPv6
subnets, we will get one IPv4 and two IPv6 addresses:
# neutron port-create test
neutron CLI is deprecated and will be removed in the future. Use openstack
CLI instead.
Created a new port:
+---+-+
| Field | Value
|
+---+-+
| admin_state_up| True
|
| allowed_address_pairs |
|
| binding:host_id |
|
| binding:profile | {}
|
| binding:vif_details | {}
|
| binding:vif_type | unbound
|
| binding:vnic_type | normal
|
| created_at| 2018-07-11T07:58:14Z
|
| description |
|
| device_id |
|
| device_owner |
|
| extra_dhcp_opts |
|
| fixed_ips | {"subnet_id":
"36c4f1cc-4043-4d62-a6ee-db5704dc929a", "ip_address": "30.20.30.3"}
|
| | {"subnet_id":
"1bb187de-dce2-429f-8e0f-f0e5357d5f49", "ip_address":
"fdf8:f53b:82e4:0:f816:3eff:fe05:ef6e"} |
| | {"subnet_id":
"b7624e84-b956-41d2-a4d6-ca6a150200fc", "ip_address":
"fdf8:f53c:82e4:0:f816:3eff:fe05:ef6e"} |
| id| b7bc35ea-8c26-4fab-9ef4-8b009d3cba4a
|
| mac_address | fa:16:3e:05:ef:6e
|
| name |
|
| network_id| 75f2f23a-ab63-4560-bd61-92023700840d
|
| port_security_enabled | True
|
| project_id| 213ea3d880074bbdab84918d70747a20
|
| qos_policy_id |
|
| revision_number | 2
|
| security_groups | 04efec82-a93c-4d19-ad52-a34a7e1a558c
|
| status| DOWN
|
| tags |
[Yahoo-eng-team] [Bug 1780327] [NEW] Send a POST request with invalid object in body return 500
Public bug reported:
This is an edge case that neutron server should return 400 response, but
actually it returned 500
To reproduce:
$ curl -g -i -X POST "http://localhost:9696/v2.0/networks; \
> -H "Accept: application/json" -H "Content-Type: application/json" -H
"X-Auth-Token: $TOKEN" \
> -d '{"network": "webservers"}'
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 150
X-Openstack-Request-Id: req-78b967c0-1f30-4e64-9b1c-1d68e019a835
Date: Thu, 05 Jul 2018 20:43:22 GMT
{"NeutronError": {"message": "Request Failed: internal server error
while processing your request.", "type": "HTTPInternalServerError",
"detail": ""}}
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1780327
Title:
Send a POST request with invalid object in body return 500
Status in neutron:
New
Bug description:
This is an edge case that neutron server should return 400 response,
but actually it returned 500
To reproduce:
$ curl -g -i -X POST "http://localhost:9696/v2.0/networks; \
> -H "Accept: application/json" -H "Content-Type: application/json" -H
"X-Auth-Token: $TOKEN" \
> -d '{"network": "webservers"}'
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 150
X-Openstack-Request-Id: req-78b967c0-1f30-4e64-9b1c-1d68e019a835
Date: Thu, 05 Jul 2018 20:43:22 GMT
{"NeutronError": {"message": "Request Failed: internal server error
while processing your request.", "type": "HTTPInternalServerError",
"detail": ""}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1780327/+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 1773827] [NEW] Sort flavors with tenant_id return 500
Public bug reported:
I tried to list flavors with 'tenant_id' as a sort key and neutron
server returned 500 response. I expected the response to be 4xx.
$ curl -s -g -X GET
"http://10.0.0.15:9696/v2.0/flavors?sort_dir=asc_key=tenant_id; -H
"Accept: application/json" -H "X-Auth-Token: $TOKEN"
{"NeutronError": {"message": "Request Failed: internal server error while
processing your request.", "type": "HTTPInternalServerError", "detail": ""}}
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1773827
Title:
Sort flavors with tenant_id return 500
Status in neutron:
New
Bug description:
I tried to list flavors with 'tenant_id' as a sort key and neutron
server returned 500 response. I expected the response to be 4xx.
$ curl -s -g -X GET
"http://10.0.0.15:9696/v2.0/flavors?sort_dir=asc_key=tenant_id; -H
"Accept: application/json" -H "X-Auth-Token: $TOKEN"
{"NeutronError": {"message": "Request Failed: internal server error while
processing your request.", "type": "HTTPInternalServerError", "detail": ""}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1773827/+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 1768952] [NEW] List availability zones with filters return 500
Public bug reported:
List availability zones with filter parameters and Neutron server return
internal server error:
$ curl -s -g -X GET "http://10.0.0.15:9696/v2.0/availability_zones?name=nova;
-H "Accept: application/json" -H "X-Auth-Token: $TOKEN"
{"NeutronError": {"message": "Request Failed: internal server error while
processing your request.", "type": "HTTPInternalServerError", "detail": ""}}
This is the trace in neutron server log:
http://paste.openstack.org/show/720318/
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1768952
Title:
List availability zones with filters return 500
Status in neutron:
New
Bug description:
List availability zones with filter parameters and Neutron server
return internal server error:
$ curl -s -g -X GET
"http://10.0.0.15:9696/v2.0/availability_zones?name=nova; -H "Accept:
application/json" -H "X-Auth-Token: $TOKEN"
{"NeutronError": {"message": "Request Failed: internal server error while
processing your request.", "type": "HTTPInternalServerError", "detail": ""}}
This is the trace in neutron server log:
http://paste.openstack.org/show/720318/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1768952/+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 1766267] [NEW] neutron server failed with 'NoForeignKeysError'
vh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service File "/opt/stack/new/neutron/neutron/db/api.py", line 403, in _listen_for_changes Apr 23 10:02:01.270085 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service remote_mapper.add_property(name, backref_prop) Apr 23 10:02:01.270217 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/mapper.py", line 1854, in add_property Apr 23 10:02:01.270321 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service self._configure_property(key, prop, init=self.configured) Apr 23 10:02:01.270425 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/mapper.py", line 1731, in _configure_property Apr 23 10:02:01.270528 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service prop.init() Apr 23 10:02:01.270648 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/interfaces.py", line 184, in init Apr 23 10:02:01.270788 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service self.do_init() Apr 23 10:02:01.270897 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/relationships.py", line 1656, in do_init Apr 23 10:02:01.271003 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service self._setup_join_conditions() Apr 23 10:02:01.271168 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/relationships.py", line 1731, in _setup_join_conditions Apr 23 10:02:01.271292 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service can_be_synced_fn=self._columns_are_mapped Apr 23 10:02:01.271396 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/relationships.py", line 1998, in __init__ Apr 23 10:02:01.271510 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service self._determine_joins() Apr 23 10:02:01.271630 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/relationships.py", line 2103, in _determine_joins Apr 23 10:02:01.271736 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service "specify a 'primaryjoin' expression." % self.prop) Apr 23 10:02:01.271853 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service NoForeignKeysError: Could not determine join condition between parent/child tables on relationship ProviderResourceAssociation._provider_backref - there are no foreign keys linking these tables. Ensure that referencing columns are associated with a ForeignKey or ForeignKeyConstraint, or specify a 'primaryjoin' expression. ** Affects: neutron Importance: Undecided Assignee: Hongbin Lu (hongbin.lu) 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/1766267 Title: neutron server failed with 'NoForeignKeysError' Status in neutron: In Progress Bug description: The failure was found from Heat gate: http://logs.openstack.org/03/559803/2/gate/heat-functional-convg- mysql-lbaasv2/825236e/logs/screen-q-svc.txt.gz#_Apr_23_10_02_01_252456 The error message and traceback is as following: Apr 23 10:02:01.252456 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service [None req-494752bd-c98f-45d2-9a16-8e6c9dd02b8e None None] Unrecoverable error: please check log for details.: NoForeignKeysError: Could not determine join condition between parent/child tables on relationship ProviderResourceAssociation._provider_backref - there are no foreign keys linking these tables. Ensure that referencing columns are associated with a ForeignKey or ForeignKeyConstraint, or specify a 'primaryjoin' expression. Apr 23 10:02:01.253089 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service Traceback (most recent call last): Apr 23 10:02:01.253204 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service File "/opt/stack/new/neutron/neutron/service.py", line 86, in serve_wsgi Apr 23 10:02:01.253315 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERROR neutron.service service.start() Apr 23 10:02:01.253425 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]: ERR
[Yahoo-eng-team] [Bug 1765452] [NEW] Unable to use project_id as sort_key
Public bug reported:
List any neutron resource and sort the list result with 'project_id' as
a sort_key. Neutron will return error. However, sorting with 'tenant_id'
is working so the API behavior is asymmetric and odd.
* We cannot sort by 'project_id'
$ curl -g -X GET
"http://10.0.0.15:9696/v2.0/networks?sort_dir=asc_key=project_id; -H
"Accept: application/json" -H "X-Auth-Token: $TOKEN"
{"NeutronError": {"message": "[u'project_id'] is invalid attribute for
sort_keys", "type": "HTTPBadRequest", "detail": ""}}
* Sort by 'tenant_id' has no problem
$ curl -g -X GET
"http://10.0.0.15:9696/v2.0/networks?sort_dir=asc_key=tenant_id; -H
"Accept: application/json" -H "X-Auth-Token: $TOKEN"
{"networks":[{"ipv6_address_scope":null,"dns_domain":"","revision_number":3,"port_security_enabled":true,"id":"3becdf9f-429b-4e9d-9856-403a5c8582de","router:external":false,"availability_zone_hints":[],"availability_zones":[],"ipv4_address_scope":null,"shared":true,"project_id":"a7a7fa10fd7a4c80acb7e4b224480495","l2_adjacency":true,"status":"ACTIVE","subnets":[],"description":"","tags":[],"updated_at":"2018-04-12T20:45:07Z","qos_policy_id":null,"name":"secret_network","admin_state_up":true,"tenant_id":"a7a7fa10fd7a4c80acb7e4b224480495","created_at":"2018-04-12T20:43:33Z","mtu":1450},{"updated_at":"2018-03-19T19:17:21Z","dns_domain":"","revision_number":7,"port_security_enabled":true,"id":"ad93b454-4836-46c7-bfc8-64a20a2ab95a","router:external":true,"availability_zone_hints":[],"availability_zones":["nova"],"ipv4_address_scope":null,"shared":false,"project_id":"a7a7fa10fd7a4c80acb7e4b224480495","l2_adjacency":true,"status":"ACTIVE","subnets":["c7b4904f-bf9b-4bd4-94e7-786a3d9d22fb","62d3fb30-082f-4ed1-93b8-286bd26e2530"],"description":"","tags":[],"ipv6_address_scope":null,"is_default":true,"qos_policy_id":null,"name":"public","admin_state_up":true,"tenant_id":"a7a7fa10fd7a4c80acb7e4b224480495","created_at":"2018-03-19T19:17:07Z","mtu":1500},{"ipv6_address_scope":null,"dns_domain":"","revision_number":4,"port_security_enabled":true,"id":"02dd8479-ef26-4398-a102-d19d0a7b3a1f","router:external":false,"availability_zone_hints":[],"availability_zones":["nova"],"ipv4_address_scope":null,"shared":false,"project_id":"b629c7f622ad4a7bbfc8fb0128cec046","l2_adjacency":true,"status":"ACTIVE","subnets":["49a703b8-e53e-420a-af20-3b30d6c73409","ae522c5a-7aea-4ce8-9412-73c0f5438cc4"],"description":"","tags":[],"updated_at":"2018-03-19T19:17:00Z","qos_policy_id":null,"name":"private","admin_state_up":true,"tenant_id":"b629c7f622ad4a7bbfc8fb0128cec046","created_at":"2018-03-19T19:16:56Z","mtu":1450}]}
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1765452
Title:
Unable to use project_id as sort_key
Status in neutron:
New
Bug description:
List any neutron resource and sort the list result with 'project_id'
as a sort_key. Neutron will return error. However, sorting with
'tenant_id' is working so the API behavior is asymmetric and odd.
* We cannot sort by 'project_id'
$ curl -g -X GET
"http://10.0.0.15:9696/v2.0/networks?sort_dir=asc_key=project_id; -H
"Accept: application/json" -H "X-Auth-Token: $TOKEN"
{"NeutronError": {"message": "[u'project_id'] is invalid attribute for
sort_keys", "type": "HTTPBadRequest", "detail": ""}}
* Sort by 'tenant_id' has no problem
$ curl -g -X GET
"http://10.0.0.15:9696/v2.0/networks?sort_dir=asc_key=tenant_id; -H
"Accept: application/json&q
[Yahoo-eng-team] [Bug 1763161] [NEW] Segment ignore sorting parameters
Public bug reported:
Send a request to get a list of network segments sorted by name but the
response doesn't seem to be sorted (below is an example). Segment should
support sorting to align with other API resources.
$ curl -g -s -X GET
"http://10.0.0.15:9696/v2.0/segments?sort_dir=asc_key=name; -H "Accept:
application/json" -H "X-Auth-Token: $TOKEN" | jq .
{
"segments": [
{
"name": null,
"network_id": "02dd8479-ef26-4398-a102-d19d0a7b3a1f",
"segmentation_id": 24,
"network_type": "vxlan",
"physical_network": null,
"id": "0a046acf-594f-4488-80a5-89b01f4c0f7d",
"description": null
},
{
"name": "segment1",
"network_id": "a650210a-6ad6-44fc-8a17-fee8829352ca",
"segmentation_id": 55,
"network_type": "vxlan",
"physical_network": null,
"id": "d0cc2af3-903b-4451-9d4a-8d7d8216fa16",
"description": null
},
{
"name": "segment2",
"network_id": "a650210a-6ad6-44fc-8a17-fee8829352ca",
"segmentation_id": 2016,
"network_type": "vxlan",
"physical_network": null,
"id": "5a0e733b-bc40-4225-9dab-729338107d1a",
"description": null
},
{
"name": null,
"network_id": "ad93b454-4836-46c7-bfc8-64a20a2ab95a",
"segmentation_id": null,
"network_type": "flat",
"physical_network": "public",
"id": "6131da02-f769-4b31-997d-cefa46c5198c",
"description": null
}
]
}
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1763161
Title:
Segment ignore sorting parameters
Status in neutron:
New
Bug description:
Send a request to get a list of network segments sorted by name but
the response doesn't seem to be sorted (below is an example). Segment
should support sorting to align with other API resources.
$ curl -g -s -X GET
"http://10.0.0.15:9696/v2.0/segments?sort_dir=asc_key=name; -H "Accept:
application/json" -H "X-Auth-Token: $TOKEN" | jq .
{
"segments": [
{
"name": null,
"network_id": "02dd8479-ef26-4398-a102-d19d0a7b3a1f",
"segmentation_id": 24,
"network_type": "vxlan",
"physical_network": null,
"id": "0a046acf-594f-4488-80a5-89b01f4c0f7d",
"description": null
},
{
"name": "segment1",
"network_id": "a650210a-6ad6-44fc-8a17-fee8829352ca",
"segmentation_id": 55,
"network_type": "vxlan",
"physical_network": null,
"id": "d0cc2af3-903b-4451-9d4a-8d7d8216fa16",
"description": null
},
{
"name": "segment2",
"network_id": "a650210a-6ad6-44fc-8a17-fee8829352ca",
"segmentation_id": 2016,
"network_type": "vxlan",
"physical_network": null,
"id": "5a0e733b-bc40-4225-9dab-729338107d1a",
"description": null
},
{
"name": null,
"network_id": "ad93b454-4836-46c7-bfc8-64a20a2ab95a",
"segmentation_id": null,
"network_type": "flat",
"physical_network": "public",
"id": "6131da02-f769-4b31-997d-cefa46c5198c",
"description": null
}
]
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1763161/+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 1762752] [NEW] Support filter by attribute with null value
Public bug reported: Right now, it seems it is impossible to list resources with a filter that contains null value. For example, it is impossible to list subnets that doesn't have subnetpool. I tried the following, but it doesn't seem to work (it returned an empty list instead of the filtered list). GET "/subnets?subnetpool_id=null" IMHO, we can consider to add support for that. ** 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/1762752 Title: Support filter by attribute with null value Status in neutron: New Bug description: Right now, it seems it is impossible to list resources with a filter that contains null value. For example, it is impossible to list subnets that doesn't have subnetpool. I tried the following, but it doesn't seem to work (it returned an empty list instead of the filtered list). GET "/subnets?subnetpool_id=null" IMHO, we can consider to add support for that. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1762752/+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 1761823] [NEW] [RFE] Introduce /ip-address resource
Public bug reported:
This RFE is created according to the feedback of the neutron driver team
meeting [1].
@yamamoto suggested to introduce a new API /ip-address/{ip-address}.
This API will determine whether the {ip-address} is fixed and floating
and then respond with the relevant data, including the data of the port
that this address is/was associated with.
There are two major use cases:
* Provide a unified view for two types of IP address (fixed and floating). This
facilitates information lookup by an address of unknown type.
* Provide history of an address (i.e. which VM this address is/was associated
with in a specific time).
[1]
http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-04-06-14.00.log.html
** Affects: neutron
Importance: Undecided
Status: New
** Description changed:
This RFE is created according to the feedback of the neutron driver team
meeting [1].
@yamamoto suggested to introduce a new API /ip-address/{ip-address}.
This API will determine whether the {ip-address} is fixed and floating
and then respond with the relevant data, including the data of the port
that this address is/was associated with.
There are two major use cases:
- * Provide a unified view for two type of IP address (fixed and floating).
+ * Provide a unified view for two types of IP address (fixed and floating).
This facilitates information lookup by an address of unknown type.
* Provide history of an address (i.e. which VM this address is/was associated
with in a specific time).
[1]
http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-04-06-14.00.log.html
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1761823
Title:
[RFE] Introduce /ip-address resource
Status in neutron:
New
Bug description:
This RFE is created according to the feedback of the neutron driver
team meeting [1].
@yamamoto suggested to introduce a new API /ip-address/{ip-address}.
This API will determine whether the {ip-address} is fixed and floating
and then respond with the relevant data, including the data of the
port that this address is/was associated with.
There are two major use cases:
* Provide a unified view for two types of IP address (fixed and floating).
This facilitates information lookup by an address of unknown type.
* Provide history of an address (i.e. which VM this address is/was associated
with in a specific time).
[1]
http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-04-06-14.00.log.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1761823/+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 1760902] [NEW] Standard attributes are missing in segment response
Public bug reported: The response of segment resource doesn't contain standard attributes, i.e. created_at, updated_at, revision_number. These attributes should be visible in the response as other resources. ** Affects: neutron Importance: Undecided Assignee: Hongbin Lu (hongbin.lu) Status: New ** Changed in: neutron Assignee: (unassigned) => Hongbin Lu (hongbin.lu) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1760902 Title: Standard attributes are missing in segment response Status in neutron: New Bug description: The response of segment resource doesn't contain standard attributes, i.e. created_at, updated_at, revision_number. These attributes should be visible in the response as other resources. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1760902/+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 1759959] [NEW] api-ref: documentation of address scope extension is missing
Public bug reported: There is an address scope API extension defined in neutron-lib https://github.com/openstack/neutron- lib/blob/master/neutron_lib/api/definitions/address_scope.py , but its documentation seems to be missing in API reference. ** 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/1759959 Title: api-ref: documentation of address scope extension is missing Status in neutron: New Bug description: There is an address scope API extension defined in neutron-lib https://github.com/openstack/neutron- lib/blob/master/neutron_lib/api/definitions/address_scope.py , but its documentation seems to be missing in API reference. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1759959/+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 1749820] [NEW] Unpredictable response on invalid query parameters
Public bug reported:
Problem
===
If users provide different kinds of invalid query parameters, the behavior of
neutron server looks unpredictable. Sometimes, it tolerates the invalid inputs
and return a successful response. Sometimes, it invalidates the inputs and
return an error response. In addition, the error type is unpredictable and the
format of the error message is inconsistent.
1. Invalid sort_key and/or sort_dir:
Neutron returns at least two error types: BadRequest [1] [2], HTTPBadRequest
[3] [4][5]. In addition, the format of error message looks inconsistent. For
example, it has the following forms:
* Bad networks request: Attribute '...' references another resource and cannot
be used to sort '...' resources. [1]
* Bad networks request: '...' is an invalid attribute for sort key. [2]
* [u'...'] is invalid attribute for sort_keys [3]
2. Invalid limit and/or marker:
Sometimes, neutron returns error with one of the following types:
BadRequest [6], NetworkNotFound [7]. Sometimes, neutron doesn't return
error [8].
3. Invalid filter
Sometimes, neutron returns error with one of the following types:
InvalidInput [9], NotImplementedError [10]. Sometimes, neutron doesn't
return error [11]
4. Invalid fields
Neutron always returns a successful response [12] regardless of validity
of the inputs.
Proposal
Improve the predictability of neutron server by handling invalid query
parameters consistently. Optimally, neutron server behaves as following:
* Always returns error (i.e. 400 response) on invalid user inputs. IMHO,
ignoring invalid inputs (like [8][11][12]) is bad.
* Make error type predictable. There are several options to achieve this. One
option is to group different kinds of invalid inputs and define a specific
error type for each group (i.e. InvalidSorting for #1, InvalidPagination for
#2, InvalidFilter for #3, etc.).
* Make the format of error message consistent. For example, the format of error
messages [1][2][3] can be consolidated into one.
Referred examples
=
[1] GET "/v2.0/networks?sort_dir=desc_key=segments"
{"NeutronError": {"message": "Bad networks request: Attribute 'segments'
references another resource and cannot be used to sort 'networks' resources.",
"type": "BadRequest", "detail": ""}}
[2] GET "/v2.0/networks?sort_dir=desc_key=provider:physical_network"
{"NeutronError": {"message": "Bad networks request: 'provider:physical_network'
is an invalid attribute for sort key.", "type": "BadRequest", "detail": ""}}
[3] GET "/v2.0/networks?sort_dir=desc_key=xxx"
{"NeutronError": {"message": "[u'xxx'] is invalid attribute for sort_keys",
"type": "HTTPBadRequest", "detail": ""}}
[4] GET "/v2.0/networks?sort_dir=xxx"
{"NeutronError": {"message": "The number of sort_keys and sort_dirs must be
same", "type": "HTTPBadRequest", "detail": ""}}
[5] GET "/v2.0/networks?sort_dir=xxx_key=id"
{"NeutronError": {"message": "[u'xxx'] is invalid value for sort_dirs, valid
value is 'asc' and 'desc'", "type": "HTTPBadRequest", "detail": ""}}
[6] GET "/v2.0/networks?limit=-1"
{"NeutronError": {"message": "Bad limit request: Limit must be an integer 0 or
greater and not '-1'.", "type": "BadRequest", "detail": ""}}
[7] GET "/v2.0/networks?limit=1=xxx"
{"NeutronError": {"message": "Network xxx could not be found.", "type":
"NetworkNotFound", "detail": ""}}
[8] GET "/v2.0/networks?marker=xxx"
{"networks":...}
[9] GET "/v2.0/networks?admin_state_up=xxx"
{"NeutronError": {"message": "Invalid input for operation: 'xxx' cannot be
converted to boolean.", "type": "InvalidInput", "detail": ""}}
[10] GET "/v2.0/networks?subnets=11"
{"NotImplementedError": {"message": "in_() not yet supported for relationships.
For a simple many-to-one, use in_() against the set of foreign key values.",
"type": "NotImplementedError", "detail": ""}}
[11] GET "/v2.0/networks?xxx=11"
{"networks":...}
[12] GET "/v2.0/networks?fields=xxx"
{"networks":...}
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Description changed:
Problem
===
If users provide different kinds of invalid query parameters, the
behavior of neutron server
[Yahoo-eng-team] [Bug 1749304] [NEW] Support filter by attribute with empty value
Public bug reported:
Right now, it seems it is impossible to list resources with a filter
that contains blank value (null or ""). For example:
* It is impossible to list unbound ports (whose device_id is ""). I
tried the following, but it doesn't seem to work (it returned all ports
instead of the filtered ports).
GET "/ports?device_id="
* It is impossible to list subnets that doesn't have subnetpool. I tried
the following, but it doesn't seem to work (it returned an empty list
instead of the filtered list).
GET "/subnets?subnetpool_id=null"
IMHO, we need to add support for that. Otherwise, the filtering feature
is incomplete.
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1749304
Title:
Support filter by attribute with empty value
Status in neutron:
New
Bug description:
Right now, it seems it is impossible to list resources with a filter
that contains blank value (null or ""). For example:
* It is impossible to list unbound ports (whose device_id is ""). I
tried the following, but it doesn't seem to work (it returned all
ports instead of the filtered ports).
GET "/ports?device_id="
* It is impossible to list subnets that doesn't have subnetpool. I
tried the following, but it doesn't seem to work (it returned an empty
list instead of the filtered list).
GET "/subnets?subnetpool_id=null"
IMHO, we need to add support for that. Otherwise, the filtering
feature is incomplete.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1749304/+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 1749030] [NEW] Filter by 'created_at' return 500
Public bug reported:
Neutron server will return 500 if we try to list ports with 'created_at'
as filter. For example:
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
"http://10.0.0.19:9696/v2.0/ports?created_at=test;
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 150
X-Openstack-Request-Id: req-78d586d8-2ad1-4303-89e9-e93ffe4229cb
Date: Mon, 12 Feb 2018 23:12:17 GMT
{"NeutronError": {"message": "Request Failed: internal server error
while processing your request.", "type": "HTTPInternalServerError",
"detail": ""}}
IMO, the neutron server should return a 4xx error in this case.
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1749030
Title:
Filter by 'created_at' return 500
Status in neutron:
New
Bug description:
Neutron server will return 500 if we try to list ports with
'created_at' as filter. For example:
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
"http://10.0.0.19:9696/v2.0/ports?created_at=test;
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 150
X-Openstack-Request-Id: req-78d586d8-2ad1-4303-89e9-e93ffe4229cb
Date: Mon, 12 Feb 2018 23:12:17 GMT
{"NeutronError": {"message": "Request Failed: internal server error
while processing your request.", "type": "HTTPInternalServerError",
"detail": ""}}
IMO, the neutron server should return a 4xx error in this case.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1749030/+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 1749024] [NEW] api-ref: document the list of valid sort_keys
Public bug reported: The api-ref describe how the sorting works in general: https://developer.openstack.org/api-ref/network/v2/#sorting . However, it doesn't explicitly list all the valid sort_keys for each API resources. Listing all the sort_keys for each API resources is necessary because the list are different across resources. End-users cannot predict which sort_key will work for which resource unless the information is explicitly documented. We could refer how nova's did for documenting the sorting feature: https://developer.openstack.org/api-ref/compute/#list-servers-detailed ** Affects: neutron Importance: Undecided Assignee: Hongbin Lu (hongbin.lu) Status: New ** Changed in: neutron Assignee: (unassigned) => Hongbin Lu (hongbin.lu) ** Description changed: The api-ref describe how the pagination works in general: https://developer.openstack.org/api-ref/network/v2/#pagination . However, it doesn't explicitly list all the valid sort_keys for each API resources. Listing all the sort_keys for each API resources is necessary because the list are different across resources. End-users cannot predict which sort_key will work for which resource. - NOTE: nova's api-ref does list all the sort_keys: + We could refer how nova's did for documenting the sorting feature: https://developer.openstack.org/api-ref/compute/#list-servers-detailed ** Description changed: - The api-ref describe how the pagination works in general: - https://developer.openstack.org/api-ref/network/v2/#pagination . - However, it doesn't explicitly list all the valid sort_keys for each API + The api-ref describe how the sorting works in general: + https://developer.openstack.org/api-ref/network/v2/#sorting . However, + it doesn't explicitly list all the valid sort_keys for each API resources. Listing all the sort_keys for each API resources is necessary because the list are different across resources. End-users cannot predict which - sort_key will work for which resource. + sort_key will work for which resource unless the information is + explicitly documented. We could refer how nova's did for documenting the sorting feature: https://developer.openstack.org/api-ref/compute/#list-servers-detailed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1749024 Title: api-ref: document the list of valid sort_keys Status in neutron: New Bug description: The api-ref describe how the sorting works in general: https://developer.openstack.org/api-ref/network/v2/#sorting . However, it doesn't explicitly list all the valid sort_keys for each API resources. Listing all the sort_keys for each API resources is necessary because the list are different across resources. End-users cannot predict which sort_key will work for which resource unless the information is explicitly documented. We could refer how nova's did for documenting the sorting feature: https://developer.openstack.org/api-ref/compute/#list-servers-detailed To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1749024/+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 1748982] [NEW] api-ref: 'tags' is missing in response parameters and sample
Public bug reported: In the api-ref, the parameter 'tags' is not documented in either response parameters or response sample. This applies to all API resources that support tags (i.e. network, subnet). It is better to add this missing documentation. ** 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/1748982 Title: api-ref: 'tags' is missing in response parameters and sample Status in neutron: New Bug description: In the api-ref, the parameter 'tags' is not documented in either response parameters or response sample. This applies to all API resources that support tags (i.e. network, subnet). It is better to add this missing documentation. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1748982/+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 1747995] [NEW] api-ref: document all the filters of each resource
Public bug reported: Currently, the only documentation about filters is: https://developer.openstack.org/api-ref/network/v2/#filtering-and- column-selection . It explains the high level behavior about filters but doesn't have detailed information about the exact list of filters for each resource. It would be nice if neutron can document all the filters for each API resources. This is desirable because the behavior of each filter is heterogeneous across different API resources. From end-users point of view, they need to know exactly which filter is supported by which resource and how to specify each filter value. If the filters documentation is missing or incomplete, it is hard to predict the API behavior which will cause issue like: https://bugs.launchpad.net/neutron/+bug/1418635 . ** Affects: neutron Importance: Undecided Assignee: Hongbin Lu (hongbin.lu) Status: New ** Changed in: neutron Assignee: (unassigned) => Hongbin Lu (hongbin.lu) ** Description changed: It would be nice if neutron can document all the filters for each API resources. This is desirable because the behavior of each filter is heterogeneous across different API resources. From end-users point of view, they need to know exactly which filter is supported by which resource and how to specify each filter value. If the filters documentation is missing or incomplete, it is hard to predict the API behavior which will cause issue like: - https://developer.openstack.org/api-ref/network/v2/#filtering-and- - column-selection . + https://bugs.launchpad.net/neutron/+bug/1418635 . ** Description changed: + Currently, the only documentation about filters is: + https://developer.openstack.org/api-ref/network/v2/#filtering-and- + column-selection . It explains the high level behavior about filters but + doesn't have detailed information about the exact list of filters for + each resource. + It would be nice if neutron can document all the filters for each API resources. This is desirable because the behavior of each filter is heterogeneous across different API resources. From end-users point of view, they need to know exactly which filter is supported by which resource and how to specify each filter value. If the filters documentation is missing or incomplete, it is hard to predict the API behavior which will cause issue like: https://bugs.launchpad.net/neutron/+bug/1418635 . -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1747995 Title: api-ref: document all the filters of each resource Status in neutron: New Bug description: Currently, the only documentation about filters is: https://developer.openstack.org/api-ref/network/v2/#filtering-and- column-selection . It explains the high level behavior about filters but doesn't have detailed information about the exact list of filters for each resource. It would be nice if neutron can document all the filters for each API resources. This is desirable because the behavior of each filter is heterogeneous across different API resources. From end-users point of view, they need to know exactly which filter is supported by which resource and how to specify each filter value. If the filters documentation is missing or incomplete, it is hard to predict the API behavior which will cause issue like: https://bugs.launchpad.net/neutron/+bug/1418635 . To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1747995/+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 1747540] [NEW] Predictable error for invalid sort_key
Public bug reported:
Description
===
Neutron return unpredictable error type & message on invalid various invalid
sort_keys. There are at least three types of errors:
1. {"message": "Bad networks request: Attribute 'xxx' references another
resource and cannot be used to sort 'xxx' resources.", "type": "BadRequest",
"detail": ""}
2. {"message": "Bad networks request: 'xxx' is an invalid attribute for sort
key.", "type": "BadRequest", "detail": ""}
3. {"message": "[u'xxx'] is invalid attribute for sort_keys", "type":
"HTTPBadRequest", "detail": ""}
Reproduce
=
1.
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?sort_dir=desc_key=segments'
HTTP/1.1 400 Bad Request
Content-Type: application/json
Content-Length: 188
X-Openstack-Request-Id: req-6bfeeddb-ed4c-4d6e-a107-1d65cda75883
Date: Mon, 05 Feb 2018 23:17:22 GMT
{"NeutronError": {"message": "Bad networks request: Attribute 'segments'
references another resource and cannot be used to sort 'networks'
resources.", "type": "BadRequest", "detail": ""}}
2.
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?sort_dir=desc_key=provider:physical_network'
HTTP/1.1 400 Bad Request
Content-Type: application/json
Content-Length: 156
X-Openstack-Request-Id: req-9c1179bc-fa49-4692-9719-3620617eddf0
Date: Mon, 05 Feb 2018 23:18:00 GMT
{"NeutronError": {"message": "Bad networks request:
'provider:physical_network' is an invalid attribute for sort key.",
"type": "BadRequest", "detail": ""}}
3.
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?sort_dir=desc_key=xxx'
HTTP/1.1 400 Bad Request
Content-Length: 116
Content-Type: application/json
X-Openstack-Request-Id: req-a2b43d49-f16a-40ae-ba76-51d2162cb72b
Date: Mon, 05 Feb 2018 23:18:45 GMT
{"NeutronError": {"message": "[u'xxx'] is invalid attribute for
sort_keys", "type": "HTTPBadRequest", "detail": ""}}
Expected
The 'type' is the same and the 'message' is of the same form for request #1, #2
and #3.
Actual
==
The combination of 'message' and 'type' are of different forms for request #1,
#2 and #3.
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1747540
Title:
Predictable error for invalid sort_key
Status in neutron:
New
Bug description:
Description
===
Neutron return unpredictable error type & message on invalid various invalid
sort_keys. There are at least three types of errors:
1. {"message": "Bad networks request: Attribute 'xxx' references another
resource and cannot be used to sort 'xxx' resources.", "type": "BadRequest",
"detail": ""}
2. {"message": "Bad networks request: 'xxx' is an invalid attribute for sort
key.", "type": "BadRequest", "detail": ""}
3. {"message": "[u'xxx'] is invalid attribute for sort_keys", "type":
"HTTPBadRequest", "detail": ""}
Reproduce
=
1.
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?sort_dir=desc_key=segments'
HTTP/1.1 400 Bad Request
Content-Type: application/json
Content-Length: 188
X-Openstack-Request-Id: req-6bfeeddb-ed4c-4d6e-a107-1d65cda75883
Date: Mon, 05 Feb 2018 23:17:22 GMT
{"NeutronError": {"message": "Bad networks request: Attribute
'segments' references another resource and cannot be used to sort
'networks' resources.", "type": "BadRequest", "detail": ""}}
2.
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?sort_dir=desc_key=provider:physical_network'
HTTP/1.1 400 Bad Request
Content-Type: application/json
Content-Length: 156
X-Openstack-Request-Id: req-9c1179bc-fa49-4692-9719-3620617eddf0
Date: Mon, 05 Feb 2018 23:18:00 GMT
{"NeutronError": {"message": "Bad networks request:
'provider:physical_network' is an invalid attribute for sort key.",
"type": "BadRequest", "detail": ""}}
3.
$ curl -g -i -X GET -H "X-Auth-Token:
[Yahoo-eng-team] [Bug 1747534] [NEW] ist networks with 'subnets' as filter return 500
Public bug reported:
Neutron return 500 on listing networks with 'subnets=xxx' as filter. The
command below can reproduce the error:
$ TOKEN=$(openstack token issue | awk '/ id /{print $4}')
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?subnets=11'
HTTP/1.1 501 Not Implemented
Content-Type: application/json
Content-Length: 203
X-Openstack-Request-Id: req-9e3fc06f-ce9b-4e19-bfc0-63cfcec511db
Date: Mon, 05 Feb 2018 22:21:13 GMT
{"NotImplementedError": {"message": "in_() not yet supported for
relationships. For a simple many-to-one, use in_() against the set of
foreign key values.", "type": "NotImplementedError", "detail": ""}}
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
** Description changed:
- eutron return 500 on listing networks with 'subnets' as filter. The
+ Neutron return 500 on listing networks with 'subnets' as filter. The
command below can reproduce the error:
$ TOKEN=$(openstack token issue | awk '/ id /{print $4}')
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?subnets=11'
HTTP/1.1 501 Not Implemented
Content-Type: application/json
Content-Length: 203
X-Openstack-Request-Id: req-9e3fc06f-ce9b-4e19-bfc0-63cfcec511db
Date: Mon, 05 Feb 2018 22:21:13 GMT
{"NotImplementedError": {"message": "in_() not yet supported for
relationships. For a simple many-to-one, use in_() against the set of
foreign key values.", "type": "NotImplementedError", "detail": ""}}
** Description changed:
- Neutron return 500 on listing networks with 'subnets' as filter. The
+ Neutron return 500 on listing networks with 'subnets=xxx' as filter. The
command below can reproduce the error:
$ TOKEN=$(openstack token issue | awk '/ id /{print $4}')
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?subnets=11'
HTTP/1.1 501 Not Implemented
Content-Type: application/json
Content-Length: 203
X-Openstack-Request-Id: req-9e3fc06f-ce9b-4e19-bfc0-63cfcec511db
Date: Mon, 05 Feb 2018 22:21:13 GMT
{"NotImplementedError": {"message": "in_() not yet supported for
relationships. For a simple many-to-one, use in_() against the set of
foreign key values.", "type": "NotImplementedError", "detail": ""}}
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1747534
Title:
ist networks with 'subnets' as filter return 500
Status in neutron:
New
Bug description:
Neutron return 500 on listing networks with 'subnets=xxx' as filter.
The command below can reproduce the error:
$ TOKEN=$(openstack token issue | awk '/ id /{print $4}')
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?subnets=11'
HTTP/1.1 501 Not Implemented
Content-Type: application/json
Content-Length: 203
X-Openstack-Request-Id: req-9e3fc06f-ce9b-4e19-bfc0-63cfcec511db
Date: Mon, 05 Feb 2018 22:21:13 GMT
{"NotImplementedError": {"message": "in_() not yet supported for
relationships. For a simple many-to-one, use in_() against the set of
foreign key values.", "type": "NotImplementedError", "detail": ""}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1747534/+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 1747528] [NEW] List networks with 'description' as sort_key return 500
Public bug reported:
Neutron return 500 on listing networks with 'description' as sort_key.
The command below can reproduce the error:
$ TOKEN=$(openstack token issue | awk '/ id /{print $4}')
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?sort_dir=desc_key=description'
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 150
X-Openstack-Request-Id: req-39134412-ccf8-4231-9927-c20a84107892
Date: Mon, 05 Feb 2018 22:05:55 GMT
{"NeutronError": {"message": "Request Failed: internal server error
while processing your request.", "type": "HTTPInternalServerError",
"detail": ""}}
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
** Description changed:
- Reproduce:
+ Neutron return 500 on listing networks with 'description' as sort_key.
+ The command below can reproduce the error:
- $ TOKEN=$(openstack token issue | awk '/ id /{print $4}')
- $ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?sort_dir=desc_key=description'
+ $ TOKEN=$(openstack token issue | awk '/ id /{print $4}')
+ $ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?sort_dir=desc_key=description'
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 150
X-Openstack-Request-Id: req-39134412-ccf8-4231-9927-c20a84107892
Date: Mon, 05 Feb 2018 22:05:55 GMT
{"NeutronError": {"message": "Request Failed: internal server error
while processing your request.", "type": "HTTPInternalServerError",
"detail": ""}}
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1747528
Title:
List networks with 'description' as sort_key return 500
Status in neutron:
New
Bug description:
Neutron return 500 on listing networks with 'description' as sort_key.
The command below can reproduce the error:
$ TOKEN=$(openstack token issue | awk '/ id /{print $4}')
$ curl -g -i -X GET -H "X-Auth-Token: $TOKEN"
'http://10.0.0.19:9696/v2.0/networks?sort_dir=desc_key=description'
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 150
X-Openstack-Request-Id: req-39134412-ccf8-4231-9927-c20a84107892
Date: Mon, 05 Feb 2018 22:05:55 GMT
{"NeutronError": {"message": "Request Failed: internal server error
while processing your request.", "type": "HTTPInternalServerError",
"detail": ""}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1747528/+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 1747510] [NEW] Migrate legacy jobs to zuul v3 syntax
Public bug reported: It looks neutron still use the legacy jobs syntax. This bug suggested to migrate to zuul v3 syntax. See comment from Andreas Jaeger at https://review.openstack.org/#/c/511983/35 (Patch Set 35). ** 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/1747510 Title: Migrate legacy jobs to zuul v3 syntax Status in neutron: New Bug description: It looks neutron still use the legacy jobs syntax. This bug suggested to migrate to zuul v3 syntax. See comment from Andreas Jaeger at https://review.openstack.org/#/c/511983/35 (Patch Set 35). To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1747510/+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 1746820] [NEW] Cannot delete network if mtu is changed
Public bug reported:
Create a network, change the mtu to a larger value, then delete the
network. The network is not allowed to be deleted with 400 error.
This can be reproduced by the following commands:
$ openstack network create testnet
$ neutron subnet-create testnet --name testsubnet --gateway 10.10.0.1
10.10.0.0/24
$ TOKEN=$(openstack token issue | awk '/ id /{print $4}')
$ NET_ID=$(openstack network show testnet | awk '/ id /{print $4}')
$ curl -g -i -X PUT http://10.0.0.19:9696/v2.0/networks/$NET_ID -H
"Content-Type: application/json" -H "X-Auth-Token: $TOKEN" -d '{"network":
{"mtu": 9000}}'
$ openstack subnet delete testsubnet
$ openstack network delete testnet
Failed to delete network with name or ID 'testnet': HttpException: Bad Request
(HTTP 400) (Request-ID: req-96b3-e7c2-42c7-9a7c-410fe181f11e), Invalid
input for operation: Requested MTU is too big, maximum is 1450.
The failure on deletion is strange. IMHO, we should either validate the
mtu on network create/update, or allow the deletion regardless of the
mtu value.
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1746820
Title:
Cannot delete network if mtu is changed
Status in neutron:
New
Bug description:
Create a network, change the mtu to a larger value, then delete the
network. The network is not allowed to be deleted with 400 error.
This can be reproduced by the following commands:
$ openstack network create testnet
$ neutron subnet-create testnet --name testsubnet --gateway 10.10.0.1
10.10.0.0/24
$ TOKEN=$(openstack token issue | awk '/ id /{print $4}')
$ NET_ID=$(openstack network show testnet | awk '/ id /{print $4}')
$ curl -g -i -X PUT http://10.0.0.19:9696/v2.0/networks/$NET_ID -H
"Content-Type: application/json" -H "X-Auth-Token: $TOKEN" -d '{"network":
{"mtu": 9000}}'
$ openstack subnet delete testsubnet
$ openstack network delete testnet
Failed to delete network with name or ID 'testnet': HttpException: Bad
Request (HTTP 400) (Request-ID: req-96b3-e7c2-42c7-9a7c-410fe181f11e),
Invalid input for operation: Requested MTU is too big, maximum is 1450.
The failure on deletion is strange. IMHO, we should either validate
the mtu on network create/update, or allow the deletion regardless of
the mtu value.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1746820/+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 1745658] Re: Value of network's is_default is incorrect in create
** Also affects: neutron Importance: Undecided Status: New ** Changed in: neutron Assignee: (unassigned) => Hongbin Lu (hongbin.lu) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1745658 Title: Value of network's is_default is incorrect in create Status in neutron: New Status in python-openstackclient: New Bug description: Description === Create a network with '--default' option, the network was created and the 'is_default' attribute was shown as 'True'. However, the 'is_default' attribute was actually not set because it is for external network only. Reproduce = $ openstack network create --default testnet +---+--+ | Field | Value| +---+--+ ... | is_default| True | ... +---+--+ $ openstack network show testnet +---+--+ | Field | Value| +---+--+ ... | is_default| None | ... +---+--+ Expected The response of the create command should have 'is_default' set to None Actual == The response of the create command have 'is_default' set to True To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1745658/+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
