Bug 1295564 - tempest failure tempest.api.network.test_ports.PortsTestJSON.test_create_port_in_allowed_allocation_pools[
Summary: tempest failure tempest.api.network.test_ports.PortsTestJSON.test_create_port...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: y3
: 7.0 (Kilo)
Assignee: wes hayutin
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
: 1295565 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-04 21:13 UTC by wes hayutin
Modified: 2016-04-18 07:13 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-03 14:29:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description wes hayutin 2016-01-04 21:13:38 UTC
Description of problem:

2016-01-04 14:51:41,701 847 DEBUG    [tempest_lib.common.rest_client] Request - Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 'X-Auth-Token': '<omitted>'}
        Body: {"port": {"network_id": "96779667-fe9c-4b38-bd4f-eda08eea0f6f"}}
    Response - Headers: {'status': '409', 'content-length': '164', 'connection': 'close', 'date': 'Mon, 04 Jan 2016 19:51:40 GMT', 'content-type': 'application/json; charset=UTF-8', 'x-openstack-request-id': 'req-2969d075-20d5-4ae7-b5e7-5d4c2679689a'}
        Body: {"NeutronError": {"message": "No more IP addresses available on network 96779667-fe9c-4b38-bd4f-eda08eea0f6f.", "type": "IpAddressGenerationFailure", "detail": ""}}
2016-01-04 14:51:43,336 847 INFO     [tempest_lib.common.rest_client] Request (PortsTestJSON:_run_cleanups): 204 DELETE http://172.16.23.110:9696/v2.0/subnets/5ce0c602-f565-4adc-ae68-04c86a518ea4 1.633s
2016-01-04 14:51:43,337 847 DEBUG    [tempest_lib.common.rest_client] Request - Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 'X-Auth-Token': '<omitted>'}
        Body: None
    Response - Headers: {'date': 'Mon, 04 Jan 2016 19:51:42 GMT', 'status': '204', 'connection': 'close', 'content-length': '0', 'x-openstack-request-id': 'req-ca993a48-7a0e-4347-b47b-3f3d1a269ee6'}
        Body:
}}}

Traceback (most recent call last):
  File "/home/stack/tempest/tempest/api/network/test_ports.py", line 110, in test_create_port_in_allowed_allocation_pools
    body = self.client.create_port(network_id=net_id)
  File "/home/stack/tempest/tempest/services/network/json/network_client.py", line 139, in _create
    resp, body = self.post(uri, post_data)
  File "/usr/lib/python2.7/site-packages/tempest_lib/common/rest_client.py", line 252, in post
    return self.request('POST', url, extra_headers, headers, body)
  File "/usr/lib/python2.7/site-packages/tempest_lib/common/rest_client.py", line 629, in request
    resp, resp_body)
  File "/usr/lib/python2.7/site-packages/tempest_lib/common/rest_client.py", line 685, in _error_checker
    raise exceptions.Conflict(resp_body)
Conflict: An object with that identifier already exists
Details: {u'message': u'No more IP addresses available on network 96779667-fe9c-4b38-bd4f-eda08eea0f6f.', u'type': u'IpAddressGenerationFailure', u'detail': u''}
Traceback (most recent call last):
_StringException: Empty attachments:
  stderr
  stdout


https://github.com/redhat-openstack/tempest/blob/master/tempest/api/network/test_ports.py

Comment 1 Mike Burns 2016-01-04 21:20:51 UTC
*** Bug 1295565 has been marked as a duplicate of this bug. ***

Comment 2 Mike Burns 2016-01-04 21:21:04 UTC
The following test fails for the same reason

tempest.api.network.test_ports.PortsIpV6TestJSON.test_create_port_in_allowed_allocation_pools

Comment 3 Assaf Muller 2016-01-28 00:34:09 UTC
@Arie - This test is in the skip list for Wes' job. It's passing fine on your jobs that install with Packstack. However, looking at the test, this doesn't look like a difference between Packstack and OSP-d (The way just creates a port). I'm guessing that CONF.network.tenant_network_cidr is configured differently.


Note You need to log in before you can comment on or make changes to this bug.