action #32302
closed
[qam][opensuse] test fails in zypper_moo - output not validated
Added by vsvecova about 6 years ago.
Updated almost 5 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-12-SP2-Server-DVD-Updates-x86_64-mau-extratests@64bit fails in
zypper_moo
[2018-02-26T15:11:24.0137 CET] [debug] output does not pass the code block:
\\\
\\\_o
_\\\\'/_
[2018-02-26T15:11:24.0219 CET] [debug] # Test died: output not validating at /var/lib/openqa/cache/tests/sle/tests/console/zypper_moo.pm line 24.
However, the output looks the same as in previous runs where zypper_moo passed correctly:
https://openqa.suse.de/tests/1501328#step/zypper_moo/5
Reproducible¶
Fails since (at least) Build 20180220-3
Expected result¶
Last good: 20180220-2 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Subject changed from test fails in zypper_moo - output not validated to [QAM] test fails in zypper_moo - output not validated
- Has duplicate action #32326: zypper_moo: expected output no longer matches reality added
- Subject changed from [QAM] test fails in zypper_moo - output not validated to [qam][opensuse] test fails in zypper_moo - output not validated
- Priority changed from Normal to High
Could this failure in sle2docker be related?
https://openqa.suse.de/tests/1506742#step/sle2docker/13
Both expected and actual result seem to be matching.
There is also a similar message in autoinst-log:
[2018-02-27T16:22:58.0728 CET] [debug] # Test died: output not validating at /var/lib/openqa/cache/tests/sle/tests/console/sle2docker.pm line 36.
[2018-02-27T16:22:58.0637 CET] [debug] output does not pass the code block:
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 5
Server Version: 17.09.1-ce
Storage Driver: btrfs
Build Version: Btrfs v3.18.2+20150430
Library Version: 101
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: oci runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 06b9cb35161009dcb7123345749fef02f7cea8e0
runc version: 3f2f8b84a77f73d38244dd690525642a72156c64
init version: N/A (expected: )
Security Options:
apparmor
Kernel Version: 4.4.114-94.14-default
Operating System: SUSE Linux Enterprise Server 12 SP3
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 991.9MiB
Name: susetest
ID: DOHK:5LDG:HM5L:X2GU:UAID:2B4B:6VWD:XF3A:3LSB:VQAM:M36R:THLU
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
[2018-02-27T16:22:58.0728 CET] [debug] # Test died: output not validating at /var/lib/openqa/cache/tests/sle/tests/console/sle2docker.pm line 36.
- Has duplicate action #32383: [sle][functional][easy] test fails in zypper_moo - adapt expected output added
As pcervinka pointed out, it turns out that the sle2docker issue mentioned in my comment #5 is a different issue, result of previous docker* tests which do not clean downloaded images properly (tracked under poo#32434).
- Status changed from New to In Progress
- Assignee set to okurz
zypper_moo test is awesome. I asked "WHY?" on the first look, than I saw summary of the test and it made my day better :)
- Priority changed from High to Low
should be less prio now as I have disabled the module for now.
- Status changed from In Progress to Workable
- Assignee deleted (
okurz)
- Status changed from Workable to Closed
- Priority changed from Low to Normal
Also available in: Atom
PDF