action #165132
closedtest fails in openqa_worker with 'No such timeout policy "ovs_test_tp"' and other problems regarding move to scripts/
0%
Description
Observation¶
openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install_nginx@64bit-2G fails in
openqa_worker
Test suite description¶
[ 441.786345][T88691] tap141: entered promiscuous mode
[ 442.667581][T92652] No such timeout policy "ovs_test_tp"
34WDX-1-
Reproducible¶
Fails since (at least) Build :TW.30555 (current job)
Expected result¶
Last good: :TW.30554 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz 4 months ago
- Subject changed from test fails in openqa_worker with 'No such timeout policy "ovs_test_tp"' to test fails in openqa_worker with 'No such timeout policy "ovs_test_tp"' and other problems regarding move to scripts/
- Status changed from Resolved to In Progress
dimstar mentioned problems in https://suse.slack.com/archives/C02CANHLANP/p1723477633962919 . Like https://openqa.opensuse.org/tests/4399139# incompleting with
Reason: backend died: Open vSwitch command 'set_vlan' with arguments 'tap20 8' failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.opensuse.os_autoinst.switch was not provided by any .service files
and similar. I did
hosts="openqaworker21 openqaworker22 openqaworker23 openqaworker24 openqaworker25 openqaworker26 openqaworker27 openqaworker28 openqaworker-arm21 openqaworker-arm22 qa-power8-3"; for i in $hosts; do echo "### $i" && ssh root@$i "systemctl restart os-autoinst-openvswitch" ; done
Retriggered https://gitlab.suse.de/openqa/scripts-ci/-/jobs/2942218. Passed. Called ./openqa-advanced-retrigger-jobs
which retriggered about 40 incomplete jobs of today.
I guess we miss an according statement in the .spec file to restart the service on upgrade.
Updated by okurz 4 months ago
- Related to action #162284: Prevent multi-machine tests to be picked up if os-autoinst-openvswitch service does not work size:M added
Updated by openqa_review 4 months ago
- Due date set to 2024-08-27
Setting due date based on mean cycle time of SUSE QE Tools
Updated by livdywan 4 months ago · Edited
I guess we miss an according statement in the .spec file to restart the service on upgrade.
Discussed briefly in the daily. Considering we have #162284 and this is a corner case it may not be worth looking into here.
We've not seen related alerts this morning. I'm also double-checking tests atm for any more occurences by going through unreviewed jobs.
Updated by okurz 4 months ago
I checked the results of the OSD deployment https://gitlab.suse.de/openqa/osd-deployment/-/jobs/2943512 and found that the relevant code changes are deployed. There are no problems observed yet from deployment and also os-autoinst-openvswitch was automatically restarted, see ssh worker40.oqa.prg2.suse.org 'sudo systemctl status os-autoinst-openvswitch.service'
● os-autoinst-openvswitch.service - os-autoinst openvswitch helper
Loaded: loaded (/usr/lib/systemd/system/os-autoinst-openvswitch.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/os-autoinst-openvswitch.service.d
└─30-init-timeout.conf
Active: active (running) since Tue 2024-08-13 07:17:00 CEST; 4h 42min ago
Main PID: 100828 (os-autoinst-ope)
Tasks: 1 (limit: 19660)
CGroup: /system.slice/os-autoinst-openvswitch.service
└─ 100828 /usr/bin/perl /usr/lib/os-autoinst/script/os-autoinst-openvswitch
Aug 13 11:50:02 worker40 ovs-vsctl[95879]: ovs|00001|vsctl|INFO|Called as ovs-vsctl remove port tap24 tag 102
Aug 13 11:50:05 worker40 ovs-vsctl[95905]: ovs|00001|vsctl|INFO|Called as ovs-vsctl remove port tap0 tag 102
Aug 13 11:50:23 worker40 ovs-vsctl[95944]: ovs|00001|vsctl|INFO|Called as ovs-vsctl remove port tap14 tag 102
Aug 13 11:51:07 worker40 ovs-vsctl[96579]: ovs|00001|vsctl|INFO|Called as ovs-vsctl set port tap14 tag=101 vlan_mode=dot1q-tunnel
Aug 13 11:51:11 worker40 ovs-vsctl[97207]: ovs|00001|vsctl|INFO|Called as ovs-vsctl set port tap24 tag=101 vlan_mode=dot1q-tunnel
Aug 13 11:56:47 worker40 ovs-vsctl[98820]: ovs|00001|vsctl|INFO|Called as ovs-vsctl remove port tap14 tag 101
Aug 13 11:57:10 worker40 ovs-vsctl[98951]: ovs|00001|vsctl|INFO|Called as ovs-vsctl remove port tap24 tag 101
Aug 13 11:57:45 worker40 ovs-vsctl[100566]: ovs|00001|vsctl|INFO|Called as ovs-vsctl set port tap14 tag=117 vlan_mode=dot1q-tunnel
Aug 13 11:57:46 worker40 ovs-vsctl[100570]: ovs|00001|vsctl|INFO|Called as ovs-vsctl set port tap0 tag=117 vlan_mode=dot1q-tunnel
Aug 13 11:57:46 worker40 ovs-vsctl[100574]: ovs|00001|vsctl|INFO|Called as ovs-vsctl set port tap7 tag=117 vlan_mode=dot1q-tunnel