action #107326
closed
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version set to Current
- Status changed from Workable to In Progress
- Assignee set to rainerkoenig
- Status changed from In Progress to Feedback
- Status changed from Feedback to Blocked
Thanks for reopening, also please answer question about version in https://bugzilla.suse.com/show_bug.cgi?id=1197678#c6 and afteward uncheck the needinfo on you so investigation can keep going by developers.
Once we have a bug in a progress ticket we can set the status to Blocked and continue with other tasks, just replaying when it is needed.
Setting to Blocked.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: yast2_cmd
https://openqa.suse.de/tests/8569798#step/yast_dns_server/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
- Priority changed from High to Normal
Priority set to Normal. Not working in product validation at the moment. We will tackle later.
- Status changed from Blocked to Resolved
Thanks for the investigation.
I think from this point we can just reply to the bug if needed, we don't need this ticket for extra actions.
Also available in: Atom
PDF