[system tests] Test nova_delete_vips failed by waiting timeout(vip is not recovered for 60 s)

Bug #1460969 reported by Tatyanka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Bogdan Dobrelya

Bug Description

http://jenkins-product.srt.mirantis.net:8080/job/6.1.system_test.centos.thread_5/143/testReport/junit/(root)/ha_nova_delete_vips/ha_nova_delete_vips/

 Delete management and public VIPs 10 times.
        Verify that they are restored.
        Verify cluster by OSTF

        Scenario:
            1. Delete 10 time public and management VIPs
            2. Wait while it is being restored
            3. Verify it is restored
            4. Run OSTF

Test failed with timeout error. Resource has not been restored for a 60 sec.

Assign this issue to the QA team, to reproduce it manually, and try to understand what time we should waiting for recovered vip

Revision history for this message
Nastya Urlapova (aurlapova) wrote :
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

It is not duplicate of https://bugs.launchpad.net/fuel/+bug/1460654, in 1460654 ostf fail with 401 error, but here vip does not appear in ns, so we fail before ostf execution

Changed in fuel:
assignee: MOS QA Team (mos-qa) → Fuel Library Team (fuel-library)
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Bogdan Dobrelya (bogdando)
status: New → Confirmed
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

I will reproduce this bug and investigate if this is an HA issue or the test case related only

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

I cannot reproduce this bug after 1500 delete vip iterations. The test script was http://pastebin.com/ftHKW75w
The failover time for removed IP address to reappear was ~10-18 seconds.

Changed in fuel:
status: In Progress → Invalid
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Marked as invalid as for this specific case the failure was caused by lost pacemaker quorum: http://pastebin.com/UaSFPHf5

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

The RC of the quorum lost seems multiple link issues on hapr* interfaces http://pastebin.com/TDHheZUt

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Although, I can be wrong with the RCA as these "link lost" messages could be related to the test case activities - when it removes VIP from hapr-m interface

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

But anyway, this test does not expect a quorum loss in pacemaker, hence invalid case

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.