[integration tests] Timeout during many instaces deleting on live-migration tests

Bug #1584727 reported by Georgy Dyuldin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
High
Georgy Dyuldin

Bug Description

Test result:

https://mirantis.testrail.com/index.php?/tests/view/6048961

Trace:

self = <mos_tests.nova.live_migration_test.TestLiveMigration object at 0x7f0050621e10>

    @pytest.yield_fixture
    def cleanup_instances(self):
        yield
> self.delete_instances(force=True)

mos_tests/nova/live_migration_test.py:241:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <mos_tests.nova.live_migration_test.TestLiveMigration object at 0x7f0050621e10>
force = True

    def delete_instances(self, force=False):
        for instance in self.instances:
            if force:
                delete = instance.force_delete
            else:
                delete = instance.delete
            try:
                delete()
            except nova_exceptions.NotFound:
                pass
        common.wait(
            lambda: all(self.os_conn.is_server_deleted(x.id)
                        for x in self.instances),
            timeout_seconds=2 * 60,
> waiting_for='instances to be deleted')
E TimeoutExpired: Timeout of 120 seconds expired waiting for instances to be deleted

mos_tests/nova/live_migration_test.py:235: TimeoutExpired

Tags: area-qa
Changed in mos:
assignee: nobody → MOS QA Team (mos-qa)
Changed in mos:
milestone: 10.0 → 9.0
Revision history for this message
Anna Babich (ababich) wrote :

It's not clear from test result's log, what could happen with instances that they couldn't be deleted, even force-deleted.

timeout_seconds=2 * 60 - is this value for single instance or for all booted during the test?

Changed in mos:
assignee: MOS QA Team (mos-qa) → Georgy Dyuldin (g-dyuldin)
status: Confirmed → Incomplete
Revision history for this message
Dina Belova (dbelova) wrote :

More than a month for the incomplete state -> moving to invalid. Please mark back to confirmed if this will be reproduced again

Changed in mos:
status: Incomplete → Invalid
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.