Project

General

Profile

Actions
Copy link

action #150791

closed

Some autoyast installation tests fail with 'kdump' settings are in not 'right' format due to bsc#1217057

Added by rfan1 about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
rfan1
Target version:
Current
Start date:
2023-11-13
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Several autoyast installation tests [I added some but not all]
https://openqa.suse.de/tests/12797234#step/installation/44
https://openqa.suse.de/tests/12797230#step/installation/44
https://openqa.suse.de/tests/12797231#step/installation/44

fail with below error messages:

Please, file a bug(s) with expected error. Details:

2023-11-12 20:26:12 <3> install(3870) [Ruby] autoinstall/xml_validator.rb(validate):68 XML validation errors: ["ERROR: Extra element kdump in interleave", "108:0: ERROR: Element profile failed to validate content"]
2023-11-12 20:26:27 <3> install(3870) [Ruby] autoinstall/xml_validator.rb(validate):68 XML validation errors: ["ERROR: Extra element kdump in interleave", "108:0: ERROR: Element profile failed to validate content"]

After investigating the issue, I can find all these tests have the below kdump setting in autoyast file:

  <kdump>
    <add_crash_kernel config:type="boolean">true</add_crash_kernel>
    <crash_kernel>176M-:88M</crash_kernel>
    <general>
      <KDUMP_COMMANDLINE/>
      <KDUMP_COMMANDLINE_APPEND/>
      <KDUMP_COPY_KERNEL>yes</KDUMP_COPY_KERNEL>
      <KDUMP_DUMPFORMAT>lzo</KDUMP_DUMPFORMAT>
      <KDUMP_DUMPLEVEL>31</KDUMP_DUMPLEVEL>
      <KDUMP_FREE_DISK_SIZE>64</KDUMP_FREE_DISK_SIZE>
      <KDUMP_IMMEDIATE_REBOOT>yes</KDUMP_IMMEDIATE_REBOOT>
      <KDUMP_KEEP_OLD_DUMPS>5</KDUMP_KEEP_OLD_DUMPS>
      <KDUMP_KERNELVER/>
      <KDUMP_NOTIFICATION_CC/>
      <KDUMP_NOTIFICATION_TO/>
      <KDUMP_SAVEDIR>file:///var/crash</KDUMP_SAVEDIR>
      <KDUMP_SMTP_PASSWORD/>
      <KDUMP_SMTP_SERVER/>
      <KDUMP_SMTP_USER/>
      <KDUMP_TRANSFER/>
      <KDUMP_VERBOSE>3</KDUMP_VERBOSE>
      <KEXEC_OPTIONS/>
    </general>
  </kdump>

Acceptance criteria

AC1: Double check if the autoyast configuration file is changed recently
AC2: We may need file a bug to check with dev team if it is a product bug after collecting enough logs

OpenQA test sample

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by rfan1 about 1 year ago

  • Subject changed from Some autoyast installation tests fail due to 'kdump' related issues to Some autoyast installation tests fail due to 'kdump' settings are in not 'right' format
Actions
Copy link
 #2

Updated by JERiveraMoya about 1 year ago

  • Priority changed from Normal to High

Please, report bug/consult developers about this change, it brokes auto-installations in s390x in all job groups.

Actions
Copy link
 #4

Updated by rainerkoenig about 1 year ago

  • Status changed from New to Workable
Actions
Copy link
 #5

Updated by rfan1 about 1 year ago

  • Status changed from Workable to Blocked
  • Assignee set to rfan1

Developer has confirmed it is a product bug, let me mark it as blocked now. and will close it once the bug is fixed.

Actions
Copy link
 #6

Updated by rfan1 about 1 year ago

  • Subject changed from Some autoyast installation tests fail due to 'kdump' settings are in not 'right' format to Some autoyast installation tests fail due to 'kdump' settings are in not 'right' format due to bsc#1217057
Actions
Copy link
 #7

Updated by rfan1 about 1 year ago

  • Subject changed from Some autoyast installation tests fail due to 'kdump' settings are in not 'right' format due to bsc#1217057 to Some autoyast installation tests fail with 'kdump' settings are in not 'right' format due to bsc#1217057
Actions
Copy link
 #8

Updated by rfan1 about 1 year ago

  • Status changed from Blocked to Resolved

The bug is fixed now, and no issue with the openQA result.

Actions
Copy link

Also available in: Atom PDF