action #92212
closedserial on svirt-hyperv doesn't work
0%
Description
Observation¶
On serial we get only "2021/05/05 10:04:14 socat[11798] E connect(5, AF=2 10.100.101.33:10020, 16): Connection timed out"
From the start, we don't get anything there, and validation of the boot parameters also fails.
I was not able to identify any particular workers to be broken, as it worked for the previous build just fine on the same instance of the same worker.
openQA test in scenario sle-15-SP3-Online-x86_64-lvm+RAID1@svirt-hyperv fails in
validate_lvm_raid1
Test suite description¶
Maintainer: slindomansilla, jrauch
Combination of LVM and RAID1, installation of RAID1 on top of LVM using expert partitioner.
(crypt-)LVM installations can take longer, especially on non-x86_64 architectures.
Reproducible¶
Fails since (at least) Build 183.1 (current job)
Expected result¶
Last good: 181.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by riafarov almost 3 years ago
- Project changed from openQA Tests to openQA Project
- Category changed from Bugs in existing tests to Regressions/Crashes
Updated by mloviska almost 3 years ago
Hello, should be resolved by now. The serial line is configured via Named TCP/IP pipes + socat and the app was not running. Should be fixed, sorry for the inconvenience!
https://openqa.suse.de/tests/5961243#live
Updated by riafarov almost 3 years ago
- Category deleted (
Regressions/Crashes)
mloviska wrote:
Hello, should be resolved by now. The serial line is configured via Named TCP/IP pipes + socat and the app was not running. Should be fixed, sorry for the inconvenience!
https://openqa.suse.de/tests/5961243#live
Thanks for the update! I will restart failed jobs.
Updated by okurz almost 3 years ago
- Due date set to 2021-05-20
- Category set to Support
- Assignee set to okurz
- Target version set to Ready
can you please explain how it was fixed? Any pull request that you can reference?
Updated by mloviska almost 3 years ago
- Category deleted (
Support) - Assignee deleted (
okurz) - Target version deleted (
Ready)
okurz wrote:
can you please explain how it was fixed? Any pull request that you can reference?
Log to the machine and start "Named Pipe TCP Proxy"
Updated by riafarov almost 3 years ago
We have recent failure: https://openqa.suse.de/tests/5961397 not sure if that service has died again...
Updated by okurz almost 3 years ago
- Project changed from openQA Project to openQA Tests
- Category set to Infrastructure
- Assignee set to mloviska
Updated by mloviska almost 3 years ago
riafarov wrote:
We have recent failure: https://openqa.suse.de/tests/5961397 not sure if that service has died again...
https://openqa.suse.de/tests/5961397#step/bootloader_start/53, nope this time it is firewall, working on it. thanks!
Updated by mloviska almost 3 years ago
So I have reconfigured firewall as in the 2016 host to allow any connection to Named pipe TCP proxy, and directly allow nonlocal connection in each opened port by this app. At the moment I can see 7 active connections to the hyperv2019 server. In case of any further issue, please do not hesitate to let me know. Thanks for your patience
Updated by mloviska almost 3 years ago
Meh, the machine has rebooted itself after updates :/
Updated by okurz over 2 years ago
This ticket had a due set but exceeded it already by more than 14 days. We would like to take the due date seriously so please update the ticket accordingly (resolve the ticket or update the due-date or remove the due-date). See https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives for details. This update was done as agreed within the SUSE QE Sync call 2021-09-01