Project

General

Profile

Actions

action #107302

open

[qe-core] Work around serial console problems in Hyper-V

Added by szarate over 2 years ago. Updated 4 months ago.

Status:
Workable
Priority:
Normal
Assignee:
Category:
Spike/Research
Target version:
-
Start date:
2022-02-22
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

Hyper-V sporadically fails when the hypervisor is overloaded and the serial connection to the SUT is erratic (see poo#97745). This makes the first command after the root terminal is sellected to fail. Currently there is no movement on fixing the backend issue so we need to find a workaround.

openQA test in scenario sle-15-SP4-Online-x86_64-default@svirt-hyperv fails in
system_prepare

Test suite description

Maintainer: QE Core

The standard scenario where we mainly just follow installation suggestions without any adjustments.

Reproducible

Fails since (at least) Build 97.1

Acceptance Criteria

  • AC1: Workaround the sporadically failing serial console.
  • AC2: (Optional) Move the test off serial console to ssh or another type of console. Look at os-autoinst/consoles directory for options.

Expected result

Last good: 97.1 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 2 (2 open0 closed)

Related to openQA Infrastructure - action #97745: [virtualization][hyperv] ensure_serialdev_permissions fails for hypervNew2021-08-31

Actions
Blocks openQA Tests - action #107383: [opensuse]Leap 15.4 test fails in system_prepare - unexpected console login?Workable2022-02-23

Actions
Actions #1

Updated by szarate over 2 years ago

  • Description updated (diff)
Actions #2

Updated by szarate over 2 years ago

  • Description updated (diff)
Actions #3

Updated by tjyrinki_suse over 2 years ago

  • Subject changed from test fails in system_prepare - system prepare should run in serial mode (preferably a script) to [qe-core] test fails in system_prepare - system prepare should run in serial mode (preferably a script)
  • Status changed from New to Workable
  • Priority changed from Normal to High
  • Target version set to QE-Core: Ready
Actions #4

Updated by tjyrinki_suse over 2 years ago

  • Parent task set to #107323
Actions #5

Updated by szarate over 2 years ago

  • Status changed from Workable to New
  • Target version deleted (QE-Core: Ready)

Please see the ticket description before setting to workable

Actions #6

Updated by apappas over 2 years ago

  • Subject changed from [qe-core] test fails in system_prepare - system prepare should run in serial mode (preferably a script) to [qe-core] Work around serial console problems in Hyper-V
  • Description updated (diff)
  • Status changed from New to Workable

Refinement:
This fails because the SUT has a broken serial console. This should be worked around, either by moving it to ssh or with timeouts, or with whatever the assignee discovers.

Actions #7

Updated by okurz over 2 years ago

If I understood correctly currently on the hyperv host some rather old proprietary solution is used for the serial console serving from the Windows server whereas we use socat on client (backend) side. I already recommended in the scope of #105473 to also use socat on Windows for the server side.

Actions #8

Updated by okurz over 2 years ago

  • Related to action #97745: [virtualization][hyperv] ensure_serialdev_permissions fails for hyperv added
Actions #10

Updated by szarate over 2 years ago

  • Blocks action #107383: [opensuse]Leap 15.4 test fails in system_prepare - unexpected console login? added
Actions #11

Updated by szarate over 2 years ago

  • Category changed from Bugs in existing tests to Spike/Research
  • Assignee set to szarate

This is related to how the systems are set up and permissions in the console after a reboot... one idea is that changes in the console can be managed through udev rules.

Actions #12

Updated by szarate almost 2 years ago

These tickets are not on high prio

Actions #13

Updated by szarate almost 2 years ago

  • Tags set to bulkupdate

These tickets are not on high pro

Actions #14

Updated by szarate almost 2 years ago

  • Priority changed from High to Normal
Actions #15

Updated by slo-gin 4 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF