@Brian: I think you are right. I missed the q-svc errors.
I'll address via the offending patch.
** 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/1618500
Title:
Unable to automatically allocate a network for project
Status in neutron:
Invalid
Bug description:
It appears we have an intermittent error related to auto-allocating
networks. The failure stack looks something like this:
2016-08-30 14:26:03.961058 | Captured traceback:
2016-08-30 14:26:03.961078 | ~~~~~~~~~~~~~~~~~~~
2016-08-30 14:26:03.961105 | Traceback (most recent call last):
2016-08-30 14:26:03.961172 | File
"tempest/api/compute/admin/test_auto_allocate_network.py", line 177, in
test_server_multi_create_auto_allocate
2016-08-30 14:26:03.961202 | min_count=3)
2016-08-30 14:26:03.961236 | File "tempest/common/compute.py", line
128, in create_test_server
2016-08-30 14:26:03.961255 | **kwargs)
2016-08-30 14:26:03.961295 | File
"tempest/lib/services/compute/servers_client.py", line 73, in create_server
2016-08-30 14:26:03.961332 | resp, body = self.post('servers',
post_body)
2016-08-30 14:26:03.961365 | File "tempest/lib/common/rest_client.py",
line 276, in post
2016-08-30 14:26:03.961409 | return self.request('POST', url,
extra_headers, headers, body, chunked)
2016-08-30 14:26:03.961448 | File
"tempest/lib/services/compute/base_compute_client.py", line 48, in request
2016-08-30 14:26:03.961474 | method, url, extra_headers, headers,
body, chunked)
2016-08-30 14:26:03.961502 | File "tempest/lib/common/rest_client.py",
line 665, in request
2016-08-30 14:26:03.961517 | resp, resp_body)
2016-08-30 14:26:03.961547 | File "tempest/lib/common/rest_client.py",
line 768, in _error_checker
2016-08-30 14:26:03.961572 | raise exceptions.BadRequest(resp_body,
resp=resp)
2016-08-30 14:26:03.961594 | tempest.lib.exceptions.BadRequest: Bad
request
2016-08-30 14:26:03.961641 | Details: {u'code': 400, u'message': u'Unable
to automatically allocate a network for project
2292070aef564ffc9a4e9c3009d3dfb9'}
2016-08-30 14:26:03.961650 |
Based on my log search [1] it appears this issue was occurring back on
8/23/16 and has again resurfaced (sporadically) in the past 2 days.
[1]
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Unable%20to%20automatically%20allocate%20a%20network%20for%20project%5C%22
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1618500/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
