action #155812
closed
- Status changed from Workable to In Progress
- Assignee set to hjluo
- now in 15sp5 MU we still hit this bug
- updated bug 1151130 and 1151135 with y2log and wait the developer to take a look.
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
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.
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
- Status changed from In Progress to Resolved
Also available in: Atom
PDF