Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2153283

Summary: [16.2][OVS] - RebootTrunkTest::test_0_vlan_ip_addresses, create_neutron_resources
Product: Red Hat OpenStack Reporter: Fiorella Yanac <fyanac>
Component: openstack-neutronAssignee: Miro Tomaska <mtomaska>
Status: CLOSED CURRENTRELEASE QA Contact: Eran Kuris <ekuris>
Severity: high Docs Contact:
Priority: medium    
Version: 16.2 (Train)CC: chrisw, eolivare, lsvaty, mlavalle, mtomaska, scohen
Target Milestone: ---Keywords: TestOnly, Triaged
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: 2024-08-08 15:39:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 1 Miro Tomaska 2023-01-10 18:10:56 UTC 
I have setup my own enviroment[1] and run the test multiple times. I also run the whole trunk scenario few times and I did not reproduce this problem. I manually inspected trunk port, parent port, and the Ubuntu instance and everything looked ok. At this point I am suspecting that something might have gone wrong during the ubuntu VM instance setup(fixture) which caused interfaces not being configured on the Ubuntu instance. This is just my suspicion without any evidence.
I am going to set devel_ack reproducer and see if it reproduces in the next regular Jenkins run. If we dont find any further failures then I will be closing this BZ. 


[1] https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/DFG/view/network/view/neutron/job/DFG-network-neutron-16.2_director-rhel-virthost-3cont_2comp-ml2ovs-ipv4-vxlan-tobiko-tempest-nossl-ovsfirewall/31
Comment 3 Lukas Svaty 2023-06-08 11:07:31 UTC 
Raising severity due to the Regression keyword