Project

General

Profile

Actions

action #132821

closed

agama test fails in validate_lvm due to wrong password setting

Added by syrianidou_sofia 10 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2023-07-16
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

During the beginning of the agama tests we set the root user to linux, but this variable is inherited throughout other test modules.
The actual installation settings are defined in the agama playwright tests here: https://github.com/jknphy/e2e-agama-playwright/pull/6
username: bernhard
password: nots3cr3t (same for root)

A record_info placed in the beginning of the validate_encrypt and validate_lvm module, shows that the worker variables are different that expected:
https://openqa.opensuse.org/tests/3433326#step/validate_encrypt/1
https://openqa.opensuse.org/tests/3433327#step/validate_lvm/1

The variables of password and username are defined in the agama libraries:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/tree/master/lib/Yam/agama

Acceptance criteria

  • Make sure that the $password and $username inherited by validate_lvm and valicate_encrypt are according to the test expectations. Possibly add a pre-run hook in the module, if needed.

Observation

openQA test in scenario alp-agama-2.1-staging-agama-live-default-Playwright-aarch64-agama_dolomite_lvm@aarch64 fails in
validate_lvm

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 1.36 (current job)

Expected result

Last good: 1.35 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by syrianidou_sofia 10 months ago

  • Subject changed from test fails in validate_lvm to agama test fails in validate_lvm due to wrong password setting
  • Description updated (diff)
Actions #2

Updated by syrianidou_sofia 10 months ago

  • Status changed from New to Resolved
  • Assignee set to leli
Actions

Also available in: Atom PDF