OSTF test 'Check network connectivity from instance via floating IP' failed on creation new floating ip

Bug #1485905 reported by Dmitry Tyzhnenko
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Dmitry Tyzhnenko

Bug Description

OSTF test 'Check network connectivity from instance via floating IP' failed on creation new floating ip

Fuel ISO 7.0-176

Scenario:
 1. Create new environment
 2. Choose Neutron, TUN
 3. Choose Ceph for volumes and Ceph for images
 4. Add 5 controller
 5. Add 2 compute
 6. Add 2 ceph
 7. Verify networks
 8. Deploy the environment
 9. Verify networks
 10. Run OSTF tests

Actual result:
  Step 10 failed

Expected result:
  All steps pass

OSTF Scenario:

1. Create a new security group (if it doesn`t exist yet).
2. Create router
3. Create network
4. Create subnet
5. Uplink subnet to router.
6. Create an instance using the new security group
in created subnet.
7. Create a new floating IP
8. Assign the new floating IP to the instance.
9. Check connectivity to the floating IP using ping command.
10. Check that public IP 8.8.8.8 can be pinged from instance.
11. Disassociate server floating ip.
12. Delete floating ip
13. Delete server.
14. Remove router.
15. Remove subnet
16. Remove network

OSTF Actual result:
  Step 7 failed

Expected result:
  All steps pass

OSTF error from log - http://paste.openstack.org/show/420124/

Snapshot log - https://drive.google.com/a/mirantis.com/file/d/0B8U7EvTbuAOlWHRTQy1NSzhaN3M/view?usp=sharing

Tags: nova
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

Dmitry, the error says there is no more floating IPs available in the pool:

urllib3.connectionpool: DEBUG: "POST http://192.168.0.2:8774/v2/d7ced399a0f043e2b0793861e7baace3/os-floating-ips HTTP/1.1" 404 85
fuel_health.common.test_mixins: DEBUG: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/fuel_health/common/test_mixins.py", line 177, in verify
    result = func(*args, **kwargs)
  File "/usr/lib/python2.6/site-packages/fuel_health/nmanager.py", line 688, in _create_floating_ip
    pool=floating_ips_pool[0].name)
  File "/usr/lib/python2.6/site-packages/novaclient/v1_1/floating_ips.py", line 44, in create
    return self._create("/os-floating-ips", {'pool': pool}, "floating_ip")
  File "/usr/lib/python2.6/site-packages/novaclient/base.py", line 100, in _create
    _resp, body = self.api.client.post(url, body=body)
  File "/usr/lib/python2.6/site-packages/novaclient/client.py", line 492, in post
    return self._cs_request(url, 'POST', **kwargs)
  File "/usr/lib/python2.6/site-packages/novaclient/client.py", line 467, in _cs_request
    resp, body = self._time_request(url, method, **kwargs)
  File "/usr/lib/python2.6/site-packages/novaclient/client.py", line 440, in _time_request
    resp, body = self.request(url, method, **kwargs)
  File "/usr/lib/python2.6/site-packages/novaclient/client.py", line 433, in request
    raise exceptions.from_response(resp, body, url, method)
NotFound: No more floating ips in pool net04_ext. (HTTP 404) (Request-ID: req-240c9387-d693-4bbb-8d2d-eb53a60136d9)

Are you sure net04_ext has enough IP addresses?

Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

From astute.log

    net04_ext:
      shared: false
      L2:
        network_type: local
        router_ext: true
        physnet:
        segment_id:
      L3:
        nameservers: []
        subnet: 10.109.1.0/24
        floating: 10.109.1.13:10.109.1.14
        gateway: 10.109.1.1
        enable_dhcp: false
      tenant: admin

I think, 10.109.1.13:10.109.1.14 indicates the problem here: one IP address must be used for a neutron router. and there is no IPs left to be used by tenants

Changed in fuel:
assignee: MOS Nova (mos-nova) → Dmitry Tyzhnenko (dtyzhnenko)
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

^ means it's either a problem with this particular env or with the test that deployed it. Dmitry, please proceed accordingly: either mark this bug as Invalid or fix the test.

Changed in fuel:
status: New → Confirmed
status: Confirmed → Incomplete
Revision history for this message
Dmitry Tyzhnenko (dtyzhnenko) wrote :

Yep, mistake in environment configuration.

10.109.1.13:10.109.1.14 should be a 10.109.1.13:10.109.1.24

move it to invalid

Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.