action #43418
closed
[functional][y] test fails in snapper_create - unable to determine snapshot id column
Added by dimstar over 5 years ago.
Updated over 5 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 21
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_filesystem@64bit fails in
snapper_create
Test fails with:
# Test died: Unable to determine snapshot id column index at /var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/tests/console/snapper_create.pm line 36.
Reproducible¶
Fails since (at least) Build 20181101
Expected result¶
Last good: 20181031 (or more recent)
Suggestions¶
- Fix it
- update test module maintainership
Further details¶
Always latest result in this scenario: latest
The reason is a serial kernel msg interfering with the script_output function.
# wait_serial expected: 'SCRIPT_FINISHEDrkD5M-\\d+-'
# Result:
rkD5M
[ 1404.270994] BTRFS info (device vda2): qgroup scan completed (inconsistency flag cleared)
# | Type | Pre # | Date | User | Used Space | Cleanup | Description | Userdata
SCRIPT_FINISHEDrkD5M-0-
- Has duplicate action #43364: [functional][u] Call to snapper list| head-n1 returns 141 and makes get_last_snap_number added
You can try replacing the command with
(echo "Snapper:"; snapper list) | grep -A1 Snapper: | head -n1
This would still allow the kernel to spit log messages between the "Snapper:\n" and the output of "snapper list".
Especially as echo and snapper are two different processes.
I'm actually not even sure, if the kernel could just print the log messages at any position - not only newlines.
- Subject changed from test fails in snapper_create to [functional][y] test fails in snapper_create - unable to determine snapshot id column
- Description updated (diff)
- Assignee set to michalnowak
- Target version set to Milestone 21
@michalnowak as test module maintainer, would you like to take care?
- Assignee deleted (
michalnowak)
@okurz Nope, sorry, out of scope of my current assignments (i.e. virtualization in general).
- Description updated (diff)
- Status changed from New to Workable
I wonder why this happens that reliably always at exactly this position in the test.
- Status changed from Workable to In Progress
- Assignee set to dheidler
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
Also available in: Atom
PDF