Project

General

Profile

Actions
Copy link

action #158751

open

coordination #151822: [epic] Soft-fails mitigation

Revisit soft-failure bsc#1151138

Added by JERiveraMoya 10 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
2024-04-10
Due date:
% Done:

0%

Estimated time:

Description

Motivation

See parent epic.
https://openqa.suse.de/tests/13988642#step/yast_dns_server/36 -> bsc#1151138

Acceptance criteria

AC1: Revisit soft-failure bsc#1151138

Actions
Copy link
 #1

Updated by JERiveraMoya 10 months ago

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

Updated by JERiveraMoya 9 months ago

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

Updated by JERiveraMoya 9 months ago

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

Updated by JERiveraMoya 8 months ago

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

Updated by rainerkoenig 6 months ago

  • Tags changed from qe-yam-jul-sprint, qe-yam-aug-sprint to qe-yam-aug-sprint
Actions
Copy link
 #6

Updated by leli 6 months ago

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

Updated by leli 6 months ago

Checked the history of yast2_dns_server but haven't seen the same issue, https://openqa.suse.de/tests/9825584#step/yast2_dns_server/1

I think this is a private test as described in the bug, 'yast2 dns-server commands stop named.service if it's used to add/remove dns zone/record.' I will try to reproduce it.

Actions
Copy link
 #8

Updated by JERiveraMoya 6 months ago

if you cannot find it anymore in our test coverage then we can resolve the ticket (in a quick look I wasn't able either...)

Actions
Copy link
 #9

Updated by leli 6 months ago

  • Status changed from In Progress to Resolved

Since we can't find the issue in our test coverage(neither the yast2_dns_server or new libyui test yast2_dns_server_*), so close this ticket.

Actions
Copy link
 #10

Updated by JERiveraMoya about 2 months ago

  • Tags changed from qe-yam-aug-sprint to qe-yam-jan-sprint-fy25
  • Status changed from Resolved to Workable
  • Assignee deleted (leli)

Issue is still present in YaST Maintenance Updates, let's revisit it in next sprints.
https://openqa.suse.de/tests/16201033#step/yast_dns_server/36

Actions
Copy link
 #11

Updated by JERiveraMoya about 2 months ago

  • Tags changed from qe-yam-jan-sprint-fy25 to qe-yam-dec-sprint-fy25
Actions
Copy link
 #12

Updated by JERiveraMoya about 1 month ago

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

Updated by JERiveraMoya about 1 month ago

  • Tags deleted (qe-yam-dec-sprint-fy25)
Actions
Copy link

Also available in: Atom PDF