Project

General

Profile

action #111183

[sle][migration][sle15sp4][regression]test fails in install_service- garbage after JSON object, at character offset 15

Added by coolgw about 1 month ago. Updated 11 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-05-17
Due date:
% Done:

0%

Estimated time:
4.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP4-Regression-on-Migration-from-SLE15-SPx-s390x-offline_sles15sp3_pscc_basesys-srv-desk-dev-contm-lgm-tsm-wsm-pcm_all_full_console@s390x-kvm-sle12 fails in
install_service

Test suite description

Reproducible

Fails since (at least) Build 140.1

Expected result

Last good: 137.1 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by leli about 1 month ago

  • Estimated time set to 12.00 h

#2 Updated by leli about 1 month ago

From the journal log https://openqa.suse.de/tests/8763860/logfile?filename=autoinst-log.txt,
we can see:

[ 1058.099338] ruby.ruby2.5[22746]: Libica FIPS library integrity check passed.
[ 1058.528726] zypper[22748]: Libica FIPS library integrity check passed.
[{"identifier":"SLES","version":"15.3","arch":"s390x","status":"Registered","name":"SUSE Linux Enterprise Server test subscription s390x","regcode":"25af9a3177447b4a","starts_at":"2016-03-15 12:39:06 UTC","expires_at":"2024-04-23 09:36:32 UTC","subscription_status":"ACTIVE","type":"test"},{"identifier":"sle-module-basesystem","version":"15.3","arch":"s390x","status":"Registered"},{"identifier":"sle-module-server-applications","version":"15.3","arch":"s390x","status":"Registered"},{"identifier":"sle-module-desktop-applications","version":"15.3","arch":"s390x","status":"Registered"},{"identifier":"sle-module-development-tools","version":"15.3","arch":"s390x","status":"Registered"},{"identifier":"sle-module-containers","version":"15.3","arch":"s390x","status":"Registered"},{"identifier":"sle-module-legacy","version":"15.3","arch":"s390x","status":"Registered"},{"identifier":"sle-module-transactional-server","version":"15.3","arch":"s390x","status":"Registered"},{"identifier":"sle-module-web-scripting","version":"15.3","arch":"s390x","status":"Registered"},{"identifier":"sle-module-public-cloud","version":"15.3","arch":"s390x","status":"Registered"}]
SCRIPT_FINISHEDOA0W~-0-
[2022-05-16T07:37:48.941769+02:00] [debug] >>> testapi::wait_serial: SCRIPT_FINISHEDOA0W~-\d+-: ok
[2022-05-16T07:37:48.943124+02:00] [debug] tests/installation/install_service.pm:21 called service_check::install_services -> lib/service_check.pm:311 called testapi::record_info
[2022-05-16T07:37:48.943536+02:00] [debug] <<< testapi::record_info(title="docker", output="failed reason: garbage after JSON object, at character offset 15 (before \"ruby.ruby2.5[22746]:...\") at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/JSON.pm line 31.\n\tMojo::JSON::decode_json(\"[ 1058.099338] ruby.ruby2.5[22746]: Libica FIPS library integ\"...) called at sle/lib/containers/common.pm line

The json failure related with the unexpected fips output 'Libica FIPS library integrity check passed'.

If we can disable the fips output, then this could be easily confirmed.

Filed a bug for this issue, Bug 1199689 - [Build 151.1] openQA test fails in install_service - fips output mixed in console cause json with wrong format

#3 Updated by leli about 1 month ago

  • Status changed from New to Blocked

#4 Updated by leli about 1 month ago

  • Status changed from Blocked to Rejected
  • Estimated time changed from 12.00 h to 4.00 h

Reject this ticket for track on the bug 1199689, we can re-open it if need add workaround.

#5 Updated by openqa_review 20 days ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: offline_sles15sp3_pscc_basesys-srv-desk-dev-contm-lgm-tsm-wsm-pcm_all_full_console
https://openqa.suse.de/tests/8776567#step/install_service/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

#6 Updated by openqa_review 11 days ago

Re-opening tickets with unhandled openqa-review reminder comment, see https://progress.opensuse.org/projects/openqatests/wiki/Wiki#openqa-review-reminder-handling

#7 Updated by okurz 11 days ago

  • Status changed from Rejected to Feedback

Also available in: Atom PDF