Project

General

Profile

Actions

action #150791

closed

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

Added by rfan1 6 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
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

Also available in: Atom PDF