Bug 2090601

Summary: fs020 and full-tempest-scenario job failing on tempest test neutron_tempest_plugin.scenario.test_trunk.TrunkTest.test_trunk_subport_lifecycle
Product: Red Hat OpenStack Reporter: Yatin Karel <ykarel>
Component: python-networking-ovnAssignee: OSP Team <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Eran Kuris <ekuris>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16.2 (Train)CC: apevec, lhh, majopela, scohen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-26 06:11:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yatin Karel 2022-05-26 06:04:20 UTC 
This bug was initially created as a copy of Bug #2089304

I am copying this bug because: The issue is also impacting 16.2


Description of problem:

Since 20th may, tempest test "neutron_tempest_plugin.scenario.test_trunk.TrunkTest.test_trunk_subport_lifecycle" is failing on both 16.2 and 17 integration line in fs020 and full-tempest-scenario job.

Version-Release number of selected component (if applicable):

* 16.2 on rhel-8
* 17 on rhel-8
* 17 on rhel-9


How reproducible:

Everytime


Steps to Reproduce:
1. Deploy a standalone environment
2. Run tempest tests


Actual results:

neutron_tempest_plugin.scenario.test_trunk.TrunkTest.test_trunk_subport_lifecycle fails:-

Error Snippet:

neutron_tempest_plugin.scenario.test_trunk.TrunkTest.test_trunk_subport_lifecycle[id-bb13fe28-f152-4000-8131-37890a40c79e]
--------------------------------------------------------------------------------------------------------------------------

Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):
      File "/usr/lib/python3.9/site-packages/neutron_tempest_plugin/common/utils.py", line 83, in wait_until_true
        eventlet.sleep(sleep)
      File "/usr/lib/python3.9/site-packages/eventlet/greenthread.py", line 36, in sleep
        hub.switch()
      File "/usr/lib/python3.9/site-packages/eventlet/hubs/hub.py", line 313, in switch
        return self.greenlet.switch()
    eventlet.timeout.Timeout: 60 seconds
    
    During handling of the above exception, another exception occurred:
    
    Traceback (most recent call last):
      File "/usr/lib/python3.9/site-packages/neutron_tempest_plugin/scenario/test_trunk.py", line 263, in test_trunk_subport_lifecycle
        self._wait_for_port(port, status=constants.DOWN)
      File "/usr/lib/python3.9/site-packages/neutron_tempest_plugin/scenario/test_trunk.py", line 164, in _wait_for_port
        utils.wait_until_true(
      File "/usr/lib/python3.9/site-packages/neutron_tempest_plugin/common/utils.py", line 87, in wait_until_true
        raise exception
    RuntimeError: Timed out waiting for port '463791ef-a113-4e61-87d4-01cfb7a5ebb6' to transition to get status 'DOWN'.
~~~


Expected results:

Tempest test should pass


Additional info:

This may not be a neutron related bug but we need help from the neutron experts in isolating the issue.