Project

General

Profile

action #93949

[Tumbleweed][s390x] test fails in reconnect_mgmt_console because passwords are forbidden

Added by AdaLovelace almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-06-14
Due date:
% Done:

100%

Estimated time:
Difficulty:
hard

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-s390x-textmode-server@s390x-zVM-vswitch-l2 fails in
reconnect_mgmt_console
(everywhere for s390x)

The test is trying to identify the entered password. Passwords are forbidden since last week.
The test has to be rewritten that you can authenticate without passwords.

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

Reproducible

Fails since (at least) Build 20210609

Expected result

Last good: 20210607 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues

Related to openQA Tests - action #93829: [qe-core] default config does not permit password-login for root over sshResolved2021-06-10

History

#1 Updated by AdaLovelace almost 2 years ago

  • Related to action #93829: [qe-core] default config does not permit password-login for root over ssh added

#2 Updated by AdaLovelace almost 2 years ago

  • Subject changed from [s390x] test fails in reconnect_mgmt_console because passwords are forbidden to [Tumbleweed][s390x] test fails in reconnect_mgmt_console because passwords are forbidden

#4 Updated by AdaLovelace over 1 year ago

I have integrated the referenced command for enabling passwords.
I have got a timeout now to fix.
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/12757

#5 Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: install_ltp_s390x
https://openqa.opensuse.org/tests/1817048

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#6 Updated by AdaLovelace over 1 year ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 90

#7 Updated by AdaLovelace over 1 year ago

  • Status changed from Feedback to Closed
  • % Done changed from 90 to 100

Finnished

Also available in: Atom PDF