Project

General

Profile

action #47453

[qam][functional][y][fast] test fails in first_boot

Added by bfilho over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 23
Start date:
2019-02-12
Due date:
2019-02-26
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario OpenQA::Schema::Result::TestSuites=HASH(0xa6f4a78) fails in
first_boot

Reproducible

Fails since (at least) Build :10281:nginx

Expected result

Last good: :10308:openssl-1_1 (or more recent)

Further details

Previous tests goes directly to console screen (https://openqa.suse.de/tests/2451846#step/first_boot/1), current one gets to x11 login screen and fails.

Always latest result in this scenario: latest


Related issues

Related to openQA Tests - action #46682: [functional][y] lvm test need more than 2 hours to run - optimize select_patterns_and_packagesResolved2019-01-252019-02-26

History

#1 Updated by bfilho over 2 years ago

Do you guys things this is related to the changes from https://progress.opensuse.org/issues/46682 ?

#2 Updated by riafarov over 2 years ago

Indeed, we haven't un-selected all other patterns. We'll fix that as part of #46682

#3 Updated by bfilho over 2 years ago

  • Related to action #46682: [functional][y] lvm test need more than 2 hours to run - optimize select_patterns_and_packages added

#5 Updated by okurz over 2 years ago

  • Subject changed from [qam] test fails in first_boot to [qam][functional][y][fast] test fails in first_boot
  • Due date set to 2019-02-26
  • Status changed from New to Feedback
  • Assignee set to JERiveraMoya
  • Target version set to Milestone 23

Please assign the ticket to yourself then. PR merged.

#6 Updated by JERiveraMoya over 2 years ago

  • Status changed from Feedback to Resolved

It should be fine now.

#7 Updated by bfilho over 2 years ago

  • Status changed from Resolved to Closed

Latest results seems fine on OSD. Thank you

#8 Updated by JERiveraMoya over 2 years ago

  • Status changed from Closed to Workable

#9 Updated by JERiveraMoya over 2 years ago

  • Status changed from Workable to In Progress

#10 Updated by JERiveraMoya over 2 years ago

  • Status changed from In Progress to Resolved

Sorry for the mail notifications, we don't use that work-flow, we use status resolved instead of closed to account for the work and for our automation as well. I hope it is ok.

#11 Updated by okurz over 2 years ago

For further information regarding the ticket workflow: https://progress.opensuse.org/projects/openqav3/wiki/Wiki#ticket-workflow is what should be followed. Thanks JERiveraMoya for the explanation as well as the fast reaction and fast fix to the original issue :)

Also available in: Atom PDF