Project

General

Profile

Actions
Copy link

action #103704

closed

[timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.log

Added by geor about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
High
Assignee:
geor
Target version:
Current
Start date:
2021-12-08
Due date:
% Done:

0%

Estimated time:

Description

Test module ibft.pm seems to fail while grepping for the contents of /var/log/YaST2/mkinitrd.log, which does not exist in the system under test.

Observation

openQA test in scenario sle-15-SP4-Online-x86_64-autoyast_iscsi_ibft@64bit fails in
ibft

Test suite description

AutoYaST ibft installation on iSCSI disk. iSCSI configuration is validated in the installed system, as well as cloned profile is verified to check relevant sections.

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by geor about 3 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by JERiveraMoya about 3 years ago

  • Priority changed from Normal to High
Actions
Copy link
 #3

Updated by oorlov about 3 years ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Workable

Please, check with YaST development team, if they removed the /var/log/YaST2/mkinitrd.log log intentionally.

Identify it it is an issue or not, then act respectively: if it is a bug, create a ticket on Bugzilla, if not, fix the test module.

Actions
Copy link
 #4

Updated by JERiveraMoya about 3 years ago

  • Subject changed from Investigate failure in ibft - no /var/log/YaST2/mkinitrd.log to [timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.log
Actions
Copy link
 #5

Updated by openqa_review almost 3 years ago

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

This bug is still referenced in a failing openQA test: iscsi_ibft
https://openqa.suse.de/tests/7923995

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
Actions
Copy link
 #6

Updated by geor almost 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to geor
Actions
Copy link
 #7

Updated by geor almost 3 years ago

  • Status changed from In Progress to Closed

Filed bug for missing mkinitrd.log file after installation: https://bugzilla.suse.com/show_bug.cgi?id=1194335

Actions
Copy link
 #8

Updated by geor almost 3 years ago

So according to the comments in bugzilla, yast2-bootloader calls dracut now instead of mkinitrd, so, as expected, no /var/log/YaST2/mkinitrd.log is present now.
So this is not an issue, which raises the question, what should we do with the failing test? Should we modify it to grep for the iscsi ibft info in the y2log (if listed in the log)?

Actions
Copy link
 #9

Updated by geor almost 3 years ago

Grepping mkinitrd log only for <15-SP4, grepping y2log for the rest : PR

Actions
Copy link

Also available in: Atom PDF