action #123127
closedsalt_minion: debug message about lazy loading 'error:
0%
Description
Observation¶
This is a debug message and dies not sound like an actual error
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-salt-minion@64bit fails in
salt_minion
Test suite description¶
Maintainer: zluo@suse.de
MM tests for Tumbleweed
Reproducible¶
Fails since (at least) Build 20230113 (current job)
Expected result¶
Last good: 20230112 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by openqa_review over 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: salt-minion
https://openqa.opensuse.org/tests/3082057#step/salt_minion/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.
Updated by openqa_review about 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: salt-minion
https://openqa.opensuse.org/tests/3148124#step/salt_minion/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 56 days if nothing changes in this ticket.
Updated by slo-gin about 1 year ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by dimstar about 2 months ago
- Status changed from New to Closed
the problem seems to have vanished (or is not relevant enough)