Test cli_node_deletion_check fail due to deletion controller node

Bug #1593315 reported by Egor Kotko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
High
Volodymyr Shypyguzov
Mitaka
Confirmed
High
Volodymyr Shypyguzov

Bug Description

Test cli_node_deletion_check fail on the step network verification due to deletion controller node.

Steps to reproduce:

            1. Revert snapshot 'cli_selected_nodes_deploy'
            2. Check 'slave-03' is present
            3. Destroy 'slave-03'
            4. Wait until 'slave-03' become offline
            5. Delete offline 'slave-03' from db
            6. Check presence of 'slave-03'

Expected result: test passed

Actual result: failed, the vrouter is located on the namespace of the controller node, the default route for compute nodes should be via vrouter ip.
In the test we need or change the reverted snapshot with higher number of controllers, or delete node with not controller role. Because after deletion node with default route ip, checking mirrors impossible due to lack of Internet connection.

Dmitry Klenov (dklenov)
tags: added: area-qa
Changed in fuel:
status: New → Confirmed
assignee: Fuel QA Team (fuel-qa) → Volodymyr Shypyguzov (vshypyguzov)
Revision history for this message
Nastya Urlapova (aurlapova) wrote :
Changed in fuel:
status: Confirmed → Invalid
Revision history for this message
Egor Kotko (ykotko) wrote :

In the test cli_node_deletion_check node deleting by devops name "slave-03", it can be any role in the cluster, according to the snapshot contains 3 nodes the test should randomly fail with ~0.33% probability of fail.

Changed in fuel:
status: Invalid → New
Changed in fuel:
status: New → Confirmed
Roman Vyalov (r0mikiam)
Changed in fuel:
status: Confirmed → Won't Fix
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.