Project

General

Profile

Actions
Copy link

action #38273

closed

[sle][functional][u][fast][ppc64le] test fails in await_install - failed to install python3-base

Added by jorauch almost 6 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
Urgent
Assignee:
jorauch
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 18
Start date:
2018-07-06
Due date:
2018-07-31
% Done:

0%

Estimated time:
Difficulty:
medium

Description

Observation

openQA test in scenario sle-12-SP4-Server-DVD-ppc64le-multipath@ppc64le-no-tmpfs fails in
await_install

Reproducible

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

Expected result

Last good: 0281 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by oorlov almost 6 years ago

Actions
Copy link
 #2

Updated by okurz almost 6 years ago

  • Assignee set to jorauch

@jorauch, @oorlov cool that you found this. his ticket is a good example for some topics which I would like best to address with you in person. Please bring it to my intention when all three of us are in office. Keywords: product vs. test issue, severity, blocker, attachments

Actions
Copy link
 #3

Updated by okurz almost 6 years ago

  • Target version set to Milestone 17
Actions
Copy link
 #4

Updated by okurz almost 6 years ago

  • Subject changed from [sle][functional][ppc64le] test fails in await_install - failed to install python3-base to [sle][functional][u][fast][ppc64le] test fails in await_install - failed to install python3-base
  • Due date set to 2018-07-31
  • Priority changed from Normal to Urgent
  • Target version changed from Milestone 17 to Milestone 18

As we missed to discuss this let's make it more visible. Please bring it up in the daily

Actions
Copy link
 #5

Updated by jorauch almost 6 years ago

According to the first comment in the bug it is not valid, not sure how to proceed here?

Actions
Copy link
 #6

Updated by mgriessmeier almost 6 years ago

let's discuss in daily

Actions
Copy link
 #7

Updated by okurz almost 6 years ago

Misinterpreting the debug output does not make the bug invalid. Again as discussed in person: What could the test possibly do differently? We just click "do install" and wait. Jeff also mentioned "It's possible we're hitting a spurious ENOSPC here, but we should've been seeing this on SLE15 as well.".

IMHO this progress ticket is invalid and can simply be "rejected" after we made sure no job failure is labeled with this but with the bug instead. @jorauch you can set the ticket to "rejected" unless you disagree or want to discuss it in details, e.g. in daily today. We can also do that based on personal preference.

Actions
Copy link
 #8

Updated by jorauch almost 6 years ago

  • Status changed from New to Rejected

Closing as discussed in daily 23.07.2018

Actions
Copy link

Also available in: Atom PDF