Project

General

Profile

Actions

action #155812

closed

coordination #151822: [epic] Soft-fails mitigation

Revisit soft-failures bsc#1151130

Added by JERiveraMoya 3 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
2023-12-01
Due date:
% Done:

0%

Estimated time:

Description

Motivation

See parent epic.
https://openqa.suse.de/tests/12938780#step/yast_dns_server/135 -> bsc#1151130

Acceptance criteria

AC1: Revisit soft-failure bsc#1151130


Related issues 1 (0 open1 closed)

Related to qe-yam - action #151906: Revisit soft-failures bsc#1151135Resolvedhjluo2023-12-01

Actions
Actions #1

Updated by JERiveraMoya 3 months ago

Actions #2

Updated by hjluo 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions #3

Updated by hjluo 2 months ago

Actions #4

Updated by JERiveraMoya 2 months ago

There is a dependent softfailure (where we need to investigate):
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18822/files#r1515901181

Actions #5

Updated by hjluo 2 months ago

Actions #6

Updated by JERiveraMoya 2 months ago

I gave some hints in the epic about reopening ** to avoid things like this:
https://bugzilla.suse.com/show_bug.cgi?id=1151130#c10
Please, bring your doubts in Slack so everyone can help.

Actions #7

Updated by hjluo 2 months ago

Now since the bsc#1151130 and bsc#151135 were filed year ago and for different sle versions. now I've checked this error still existed in the latest 15sp6 build.

So can I file a new bug for sles15sp6 and mark it as the new bug in the test case?

@JERiveraMoya do you agree? thanks

Actions #8

Updated by JERiveraMoya 2 months ago

hjluo wrote in #note-7:

Now since the bsc#1151130 and bsc#151135 were filed year ago and for different sle versions. now I've checked this error still existed in the latest 15sp6 build.

So can I file a new bug for sles15sp6 and mark it as the new bug in the test case?

@JERiveraMoya do you agree? thanks

seems reasonable. Depending on the answer we can continue.

Actions #10

Updated by hjluo about 2 months ago ยท Edited

  • As the developer Replied and this bug was marked INVALID and a giant waste of time. again, so I think now we can remove yast_dns_server module from mau_extratests_yast_cmd test or just let them softfail as before.

  • And I found this ticket also related to the same error, so can I take this ticket and apply it in the same PR?

What do you think of the upper suggestion? @JERiveraMoya

Actions #11

Updated by JERiveraMoya about 2 months ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF