action #116644
closed
[qe-core][functional][sle15sp5]test fails in bootloader_svirt, the test is using different network bridge 'ovs-system' rather than 'br0'
Added by rfan1 over 1 year ago.
Updated over 1 year ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-SP4-JeOS-for-kvm-and-xen-Updates-x86_64-jeos-main@svirt-xen-hvm fails in
bootloader_svirt
Test suite description¶
Reproducible¶
Fails since (at least) Build 20220905-1 (current job)
Expected result¶
Last good: 20220902-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
The current vm network config is:
<interface type='bridge'>
<mac address='xx'/>
<source bridge='ovs-system'/>
<virtualport type='openvswitch'>
<parameters interfaceid='0bc7c8ae-8089-4251-b773-8f453e681514'/>
</virtualport>
<model type='netfront'/>
</interface>
However, the previous job with below configuration:
<interface type="network">
<model type="netfront"/>
<mac address="xx"/>
<source network="br0"/>
<virtualport type="openvswitch"/>
</interface>
So I am wondering there are some network configuration changes on xen host
server# virsh iface-list --all | grep -w active | awk '{ print $1 }' | tail -n1 | tr -d '\n'
ovs-system
Server# virsh iface-destroy ovs-system
Interface ovs-system destroyed
- Related to action #116257: [virtualization][svirt] Some workers in openqaworker2 time out while copying the assets in bootloader_svirt module added
- Status changed from New to In Progress
- Assignee set to rfan1
rcai wrote:
server# virsh iface-list --all | grep -w active | awk '{ print $1 }' | tail -n1 | tr -d '\n'
ovs-system
Server# virsh iface-destroy ovs-system
Interface ovs-system destroyed
Thanks @rcai!， as we discussed, we can stop this iface temporarily to see.
https://openqa.suse.de/tests/9525130#
- Status changed from In Progress to Feedback
Right now, destroy the iface 'ovs-system' can be a workaround.
However, I am not sure if any test cases require this network bridge. then it is safe to undefine it as well if no such requirements.
Server# virsh iface-undefine ovs-system
Then it will not start after xen host rebooting.
server# virsh iface-undefine ovs-system
Interface ovs-system undefined
Thanks, no feedback so far, so undefine it then it will not be up after next OS reboot.
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
- Related to action #125783: [jeos] Test fails in kdump_and_crash on SLE 12sp5 and 15sp4 XEN after worker migration from SLES to Leap 15.4 added
Also available in: Atom
PDF