action #46835
closed[functional][u] test fails in force_scheduled_tasks: timeout
0%
Description
Observation¶
openQA test in scenario OpenQA::Schema::Result::TestSuites=HASH(0xbc328e0) fails in
force_scheduled_tasks
Test died: command 'for i in $(systemctl list-units --type=timer --state=active --no-legend | sed -e 's/(\S+).timer\s.*/\1/'); do echo "Triggering systemd timed service $i" && systemctl start $i && systemctl mask $i.{service,timer}; done' timed out at /var/lib/openqa/cache/openqa.suse.de/tests/sle/tests/console/force_scheduled_tasks.pm line 45.
Reproducible¶
Fails since (at least) Build 0109
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz about 5 years ago
- Status changed from New to Feedback
- Assignee set to okurz
- Priority changed from Normal to High
- Target version set to Milestone 22
Updated by okurz about 5 years ago
- Related to action #46397: [functional][u] test fails in force_scheduled_tasks because the btrfs maintenance tasks already triggered before *we* triggered them, just wait longer in the script call? added
Updated by okurz about 5 years ago
- Related to action #46379: [sle][migration][sle15sp1]test fails in force_scheduled_tasks - Triggering systemd timed service timeout added
Updated by okurz about 5 years ago
@dheidler I recommend you invest a little bit more effort to fill the ticket with proper details that could help, e.g.
- proper scenario name (or help mkittler to solve the bug on osd)
- Find proper "Expected Result", e.g. a "last good" that makes sense
- Find related tickets. In most cases we do have some
Updated by okurz about 5 years ago
- Due date set to 2019-02-18
PR merged, waiting for verification on production if this still happens in any scenario. Reminding myself in a week.
Updated by okurz about 5 years ago
- Description updated (diff)
- Status changed from Feedback to Resolved