Assigning a floating IP to an instance is sometimes failed with timeout in OSTF tests

Bug #1466853 reported by Dennis Dmitriev
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Dennis Dmitriev
6.1.x
Fix Committed
Medium
Dennis Dmitriev
7.0.x
Fix Released
Medium
Dennis Dmitriev

Bug Description

Reproduced on CI: http://jenkins-product.srt.mirantis.net:8080/view/6.1_swarm/job/6.1.system_test.ubuntu.thread_5/160/ , test 'ha_nova_mysql_termination'

        Scenario:
            1. Create Ubuntu cluster with IBP
            2. Add 3 nodes with controller roles
            3. Add 2 nodes with compute roles
            4. Deploy the cluster
            5. Terminate mysql on a controller
            6. Wait while it is being restarted
            7. Verify it is restarted
            8. Repeat from step 5 for each controler
            9. Run OSTF

Expected result: OSTF tests passed

Actual result: OSTF failed with the following error:
[{u'Check network connectivity from instance via floating IP (failure)': u'Can not assign floating ip to instance Please refer to OpenStack logs for more details.'}]

Actually, floating IP 10.109.1.128 was assigned to instance, the request taken 'time: 11.0909641' : http://paste.openstack.org/show/304576/

root@node-1:~# nova floating-ip-list
+--------------+-----------+----------+------+
| Ip | Server Id | Fixed Ip | Pool |
+--------------+-----------+----------+------+
| 10.109.1.128 | - | - | nova |
+--------------+-----------+----------+------+

Looks like sometimes 10 seconds of timeout is not enough for assigning floating IP in OSTF tests on CI.

Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-ostf (stable/6.1)

Fix proposed to branch: stable/6.1
Review: https://review.openstack.org/193525

Changed in fuel:
assignee: MOS QA Team (mos-qa) → Dennis Dmitriev (ddmitriev)
status: New → In Progress
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

Lets do simple test, run n test for n vm assign floating ip, because it looks really strange that 10 sec in not enough for such light operation, so we should confirm that this timeouts only on ostf side

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-ostf (stable/6.1)

Reviewed: https://review.openstack.org/193525
Committed: https://git.openstack.org/cgit/stackforge/fuel-ostf/commit/?id=79bae9e000b379fb9025a0e3676bf29d9febb1c4
Submitter: Jenkins
Branch: stable/6.1

commit 79bae9e000b379fb9025a0e3676bf29d9febb1c4
Author: Dennis Dmitriev <email address hidden>
Date: Fri Jun 19 15:59:59 2015 +0300

    Increase timeout for assigning floating IP

    Sometimes 10 seconds is not enouth for the request of assigning
    floating IP.

    Change-Id: I6aed163d4f161793f7919a0b4d82ed1724c0679c
    Closes-Bug:#1466853

tags: added: 6.1-mu-1
tags: removed: 6.1-mu-1
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

Tatyanka, this timeout is caused by re-connection of oslo-messaging to rabbitmq during executing the request. So request pass, but takes an additional time.

Revision history for this message
Nastya Urlapova (aurlapova) wrote :

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "7.0"
  openstack_version: "2015.1.0-7.0"
  api: "1.0"
  build_number: "301"
  build_id: "301"
  nailgun_sha: "4162b0c15adb425b37608c787944d1983f543aa8"
  python-fuelclient_sha: "486bde57cda1badb68f915f66c61b544108606f3"
  fuel-agent_sha: "50e90af6e3d560e9085ff71d2950cfbcca91af67"
  fuel-nailgun-agent_sha: "d7027952870a35db8dc52f185bb1158cdd3d1ebd"
  astute_sha: "6c5b73f93e24cc781c809db9159927655ced5012"
  fuel-library_sha: "5d50055aeca1dd0dc53b43825dc4c8f7780be9dd"
  fuel-ostf_sha: "2cd967dccd66cfc3a0abd6af9f31e5b4d150a11c"
  fuelmain_sha: "a65d453215edb0284a2e4761be7a156bb5627677"

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

Other bug subscribers

Remote bug watches

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