action #60545

[tools] test fails in first_boot stuck on "displaymanager" needle though password prompt was already handled

Added by okurz 4 months ago. Updated 4 months ago.

Status:ResolvedStart date:03/12/2019
Priority:NormalDue date:
Assignee:okurz% Done:

0%

Category:Bugs in existing tests
Target version:openQA Project - Current Sprint
Difficulty:
Duration:

Description

Observation

openQA test in scenario sle-15-SP2-Online-aarch64-lvm_thin_provisioning@aarch64 fails in
first_boot

Test suite description

Complete OS deployment with unencrypted LVM drive management. Test creates 2 LVM and BIOS boot partitions. Thin pool and thin lv resides on the second LVM partition, where /home (XFS) is being mounted. Maintainer: mloviska, poo#39023

Reproducible

Fails since (at least) Build 99.1 (current job)

Expected result

Last good: 97.1 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues

Related to openQA Tests - action #60395: [sle]][functional][u]test fails in cleanup_before_shutdow... Rejected 28/11/2019

History

#1 Updated by okurz 4 months ago

  • Related to action #60395: [sle]][functional][u]test fails in cleanup_before_shutdown - could not reach login prompt in time added

#2 Updated by okurz 4 months ago

  • Status changed from In Progress to Resolved

removed a needle "displaymanager-20191122" as it was producing false matches on the password prompt screen. Created a new one but realized there was already "displaymanager-20191203" created by someone.

Could only find failures on aarch64, maybe the password authentication handling is slower there even giving the opportunity for a false-match. Monitoring https://openqa.suse.de/tests/overview?result=none&result=failed&result=incomplete&result=skipped&result=obsoleted&result=parallel_failed&result=parallel_restarted&result=user_cancelled&result=user_restarted&result=timeout_exceeded&arch=&machine=&modules=first_boot&modules_result=failed&distri=sle&version=15-SP2&build=99.1#

Retriggered tests. https://openqa.suse.de/tests/3654137#step/first_boot/9 passed correctly. and more, e.g. https://openqa.suse.de/tests/3654449 . I guess we are good again although I will monitor three other jobs that failed for other reasons. Maybe I can also fixe that just now.

Also available in: Atom PDF