Project

General

Profile

action #92212

serial on svirt-hyperv doesn't work

Added by riafarov 6 months ago. Updated about 2 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
-
Start date:
2021-05-06
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:

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

History

#1 Updated by riafarov 6 months ago

  • Project changed from openQA Tests to openQA Project
  • Category changed from Bugs in existing tests to Concrete Bugs

#2 Updated by mloviska 6 months 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

#3 Updated by cdywan 6 months ago

  • Status changed from New to Feedback

#4 Updated by riafarov 6 months ago

  • Category deleted (Concrete Bugs)

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.

#5 Updated by okurz 6 months 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?

#6 Updated by mloviska 6 months 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"

#7 Updated by riafarov 6 months ago

We have recent failure: https://openqa.suse.de/tests/5961397 not sure if that service has died again...

#8 Updated by okurz 6 months ago

  • Project changed from openQA Project to openQA Tests
  • Category set to Infrastructure
  • Assignee set to mloviska

#9 Updated by mloviska 6 months 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!

#10 Updated by mloviska 6 months 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

#11 Updated by mloviska 6 months ago

  • Tags set to qac

#12 Updated by mloviska 6 months ago

Meh, the machine has rebooted itself after updates :/

#13 Updated by okurz about 2 months 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

#14 Updated by okurz about 2 months ago

  • Due date deleted (2021-05-20)

Also available in: Atom PDF