Project

General

Profile

action #32302

[qam][opensuse] test fails in zypper_moo - output not validated

Added by vsvecova over 4 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2018-02-26
Due date:
% Done:

0%

Estimated time:
Difficulty:

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


Related issues

Has duplicate openQA Tests - action #32326: zypper_moo: expected output no longer matches realityRejected2018-02-26

Has duplicate openQA Tests - action #32383: [sle][functional][easy] test fails in zypper_moo - adapt expected outputRejected2018-02-27

History

#1 Updated by okurz over 4 years ago

so coolo made the test useful with https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4489/files#diff-0a261a30d80d9373e34f70230e156e87 and now it fails :) So someone needs to check how the test can be written properly so that it really works - not me today at least.

#2 Updated by vsvecova over 4 years ago

  • Subject changed from test fails in zypper_moo - output not validated to [QAM] test fails in zypper_moo - output not validated

#3 Updated by okurz over 4 years ago

  • Has duplicate action #32326: zypper_moo: expected output no longer matches reality added

#4 Updated by okurz over 4 years ago

  • 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

#5 Updated by vsvecova over 4 years ago

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.

#6 Updated by okurz over 4 years ago

  • Has duplicate action #32383: [sle][functional][easy] test fails in zypper_moo - adapt expected output added

#7 Updated by vsvecova over 4 years ago

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).

#8 Updated by okurz over 4 years ago

  • Status changed from New to In Progress
  • Assignee set to okurz

#9 Updated by pcervinka over 4 years ago

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 :)

#10 Updated by okurz over 4 years ago

glad you like it :) Unfortunately so far I did not manage to fix the test for good. I created https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4552 to disable the test for now.

#11 Updated by okurz over 4 years ago

  • Priority changed from High to Low

should be less prio now as I have disabled the module for now.

#12 Updated by okurz almost 4 years ago

  • Status changed from In Progress to Workable
  • Assignee deleted (okurz)

#13 Updated by vpelcak about 3 years ago

  • Status changed from Workable to Closed
  • Priority changed from Low to Normal

Test no longer used

Also available in: Atom PDF