action #48170
closed[functional][u][svirt][xen] SUTs are not able to reach SUSE network, e.g. failed to reach proxy.scc.suse.de
0%
Description
Observation¶
openQA test in scenario sle-15-SP1-Installer-DVD-x86_64-create_hdd_gnome@svirt-xen-pv fails in
welcome
Reproducible¶
Fails since yesterday. Retriggered an older build for reproduction which failed the same: https://openqa.suse.de/tests/2483025#
Expected result¶
Last good: 173.1
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 6 years ago
- Status changed from New to Blocked
- Assignee set to xlai
@xlai could you help to track https://infra.nue.suse.com/Ticket/Display.html?id=131822 which you created as I do not have access?
Updated by mgriessmeier almost 6 years ago
so after some debugging and restarting the bridge, we killed the host completely - it doesn't get any dhcp offers from qanet...
Alice, I'm not sure but if you move the ticket to the openQA queue, we might be able to see it as well?
Updated by xlai almost 6 years ago
mgriessmeier wrote:
so after some debugging and restarting the bridge, we killed the host completely - it doesn't get any dhcp offers from qanet...
Alice, I'm not sure but if you move the ticket to the openQA queue, we might be able to see it as well?
I have asked the infra ticket owner to help change the queue since I do not have any feasible way to do that.
Updated by mgriessmeier almost 6 years ago
well, the ticket is actually about something else in my opinion.
I will open a new one, once I'm in the office for the issues in the small qalab regarding openqaw5-xen and openqaipmi5
Updated by cachen almost 6 years ago
I am afraid openqaw5-xen-1.qa.suse.de has same issue...
https://openqa.nue.suse.com/tests/2488504
@mgriessmeier please also kindly take a look.
Thanks guys!
Updated by okurz almost 6 years ago
Isn't the dhcp server actually running on qamaster?
Updated by mgriessmeier almost 6 years ago
okurz wrote:
Isn't the dhcp server actually running on qamaster?
no, it's running on qanet
Updated by mgriessmeier almost 6 years ago
yeah, sorry - forget my comment - I misread it and thought it's about fixing grenache.
to clarify, would you mind to comment in the ticket that the actual issue is that all machines (at least) in the small qa-lab are not be able to get any dhcp address from qanet?
Updated by xlai almost 6 years ago
mgriessmeier wrote:
yeah, sorry - forget my comment - I misread it and thought it's about fixing grenache.
to clarify, would you mind to comment in the ticket that the actual issue is that all machines (at least) in the small qa-lab are not be able to get any dhcp address from qanet?
Done.
Updated by okurz almost 6 years ago
- Blocks action #48260: [sle][functional][u][s390x][kvm] test fails in reboot_after_installation - "The console isn't responding correctly. Maybe half-open socket?" added
Updated by mgriessmeier almost 6 years ago
seems like svirt is up and running again: https://openqa.suse.de/tests/2495398
can someone check ipmi please?
Updated by okurz almost 6 years ago
Well, at least the jobs on the machine "64bit-ipmi" seem to be fine, you mean other machines within the QA lab maybe?
Updated by xlai almost 6 years ago
mgriessmeier wrote:
seems like svirt is up and running again: https://openqa.suse.de/tests/2495398
can someone check ipmi please?
The affected ipmi worker grenache-1:10 ipmi connection is normal now.
FYI, According to feedback from https://infra.nue.suse.com/Ticket/Display.html?id=131822 yesterday, they hadn't found how to solve it. Now the ticket status is still open. In case any further investigation operations on the switch, I will not add this worker back until that infra ticket is marked as fixed.
Updated by okurz almost 6 years ago
- Status changed from Blocked to Resolved
@xlai suggested to close https://infra.nue.suse.com/Ticket/Display.html?id=131822 and I brought back the disabled workers in the workers config (salt config). The network seems to be fine again. I think we are done here?
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: xfs@svirt-xen-pv
https://openqa.suse.de/tests/2688219