Project

General

Profile

Actions
Copy link

action #151894

open

coordination #151822: [epic] Soft-fails mitigation

Revisit soft-failure bsc#1202478

Added by JERiveraMoya 8 months ago. Updated 9 days ago.

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

0%

Estimated time:
Tags:
qe-yam-aug-sprint

Description

Motivation

See parent epic.
https://openqa.suse.de/tests/12908368#step/patch_sle/144 -> bsc#1202478

Acceptance criteria

AC1: Revisit soft-failure bsc#1202478

Actions
Copy link
 #1

Updated by tinawang123 7 months ago

  • Status changed from Workable to In Progress
  • Assignee set to tinawang123
Actions
Copy link
 #2

Updated by JERiveraMoya 7 months ago

  • Tags changed from qe-yam-dec-sprint, qe-yam-jan-sprint to qe-yam-jan-sprint
Actions
Copy link
 #3

Updated by tinawang123 7 months ago

The bug has not fixed.
Reopened bug: https://bugzilla.suse.com/show_bug.cgi?id=1202478

Actions
Copy link
 #5

Updated by tinawang123 7 months ago

  • Status changed from In Progress to Resolved

Confirmed the bug hasn't fixed.
Cannot remove the softfail.

Actions
Copy link
 #6

Updated by tinawang123 7 months ago

  • Status changed from Resolved to In Progress
Actions
Copy link
 #7

Updated by tinawang123 6 months ago

Checked the bug. No update information.

Actions
Copy link
 #8

Updated by tinawang123 6 months ago

Checked the bug. No update information.

Actions
Copy link
 #9

Updated by JERiveraMoya 6 months ago

  • Tags deleted (qe-yam-jan-sprint)
  • Status changed from In Progress to New

Thanks for the tracking, I commented there, the developer express his intention to fix this on month ago, so still reasonable to wait before taking actions.
Let's move the ticket back to backlog for now, I will leave assign to you, but you can clear it anytime.

Actions
Copy link
 #10

Updated by JERiveraMoya 5 months ago

  • Assignee deleted (tinawang123)
Actions
Copy link
 #11

Updated by JERiveraMoya 5 months ago

  • Status changed from New to Workable
Actions
Copy link
 #12

Updated by JERiveraMoya 4 months ago

  • Status changed from Workable to New
Actions
Copy link
 #13

Updated by JERiveraMoya 4 months ago

  • Tags set to qe-yam-apr-sprint
Actions
Copy link
 #14

Updated by JERiveraMoya 4 months ago

  • Status changed from New to Workable
Actions
Copy link
 #15

Updated by JERiveraMoya 3 months ago

  • Tags changed from qe-yam-apr-sprint to qe-yam-may-sprint
Actions
Copy link
 #16

Updated by leli 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to leli
Actions
Copy link
 #17

Updated by leli 2 months ago

First to try to remove workaround to see whether the bug is still there or not.

Actions
Copy link
 #18

Updated by leli 2 months ago

The issue still present on build 90.1, http://openqa.suse.de/tests/14317827#step/patch_sle/159 (removed workaround in branch)

Actions
Copy link
 #19

Updated by JERiveraMoya about 2 months ago

  • Tags changed from qe-yam-may-sprint to qe-yam-jan-sprint
Actions
Copy link
 #20

Updated by JERiveraMoya about 2 months ago

  • Tags changed from qe-yam-jan-sprint to qe-yam-jun-sprint
Actions
Copy link
 #21

Updated by leli 21 days ago

The issue still present on build 93.5, https://openqa.suse.de/tests/14736477#step/patch_sle/156 (removed workaround on branch).

Actions
Copy link
 #22

Updated by JERiveraMoya 21 days ago

  • Tags changed from qe-yam-jun-sprint to qe-yam-jul-sprint
Actions
Copy link
 #23

Updated by leli 12 days ago

  • Tags changed from qe-yam-jul-sprint to qa-yam-aug-sprint

As the reply of developer, https://suse.slack.com/archives/C02CLB8TZP1/p1720057132324429, we won't get the bug fix soon. Let's put the ticket to next sprint.

Actions
Copy link
 #24

Updated by JERiveraMoya 9 days ago

  • Status changed from In Progress to Workable

leli wrote in #note-23:

As the reply of developer, https://suse.slack.com/archives/C02CLB8TZP1/p1720057132324429, we won't get the bug fix soon. Let's put the ticket to next sprint.

thanks, that is the right approach, but please also set to Workable, due to that might create confusion that we are working on ticket in next sprint (it already happened in the past).

Actions
Copy link
 #25

Updated by JERiveraMoya 9 days ago

it is qe-yam-aug-sprint, not "qa", this will end up in a bunch ticket invisible to us (PO/SM) if nobody removes the wrong label (only admin can do that). Please check that in #eng-testing.

Actions
Copy link
 #26

Updated by JERiveraMoya 9 days ago

  • Tags changed from qa-yam-aug-sprint to qe-yam-aug-sprint
Actions
Copy link
 #27

Updated by leli 9 days ago

JERiveraMoya wrote in #note-25:

it is qe-yam-aug-sprint, not "qa", this will end up in a bunch ticket invisible to us (PO/SM) if nobody removes the wrong label (only admin can do that). Please check that in #eng-testing.

Thanks, should be 'qe-yam-aug-sprint'.

Actions
Copy link

Also available in: Atom PDF