https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-12-08T14:52:26ZopenSUSE Project Management Toolqe-yam - action #103704: [timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.loghttps://progress.opensuse.org/issues/103704?journal_id=4714642021-12-08T14:52:26Zgeorggkioulis@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/471464/diff?detail_id=445991">diff</a>)</li></ul> qe-yam - action #103704: [timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.loghttps://progress.opensuse.org/issues/103704?journal_id=4727102021-12-13T08:56:50ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul> qe-yam - action #103704: [timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.loghttps://progress.opensuse.org/issues/103704?journal_id=4735712021-12-15T10:15:48Zoorlovoorlov@suse.com
<ul><li><strong>Tags</strong> deleted (<del><i>qe-yast-refinement</i></del>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul><p>Please, check with YaST development team, if they removed the <code>/var/log/YaST2/mkinitrd.log</code> log intentionally. </p>
<p>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.</p>
qe-yam - action #103704: [timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.loghttps://progress.opensuse.org/issues/103704?journal_id=4742012021-12-17T07:31:05ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Subject</strong> changed from <i>Investigate failure in ibft - no /var/log/YaST2/mkinitrd.log</i> to <i>[timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.log</i></li></ul> qe-yam - action #103704: [timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.loghttps://progress.opensuse.org/issues/103704?journal_id=4768952022-01-01T00:14:59Zopenqa_reviewopenqa-review@suse.de
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: iscsi_ibft<br>
<a href="https://openqa.suse.de/tests/7923995" class="external">https://openqa.suse.de/tests/7923995</a></p>
<p>To prevent further reminder comments one of the following options should be followed:</p>
<ol>
<li>The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted</li>
<li>The openQA job group is moved to "Released" or "EOL" (End-of-Life)</li>
<li>The bugref in the openQA scenario is removed or replaced, e.g. <code>label:wontfix:boo1234</code></li>
</ol>
qe-yam - action #103704: [timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.loghttps://progress.opensuse.org/issues/103704?journal_id=4772792022-01-04T10:11:23Zgeorggkioulis@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>geor</i></li></ul> qe-yam - action #103704: [timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.loghttps://progress.opensuse.org/issues/103704?journal_id=4776002022-01-05T10:05:48Zgeorggkioulis@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li></ul><p>Filed bug for missing mkinitrd.log file after installation: <a href="https://bugzilla.suse.com/show_bug.cgi?id=1194335" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1194335</a></p>
qe-yam - action #103704: [timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.loghttps://progress.opensuse.org/issues/103704?journal_id=4776452022-01-05T13:04:39Zgeorggkioulis@suse.com
<ul></ul><p>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.<br>
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)?</p>
qe-yam - action #103704: [timebox:8h] Investigate failure in ibft - no /var/log/YaST2/mkinitrd.loghttps://progress.opensuse.org/issues/103704?journal_id=4776762022-01-05T18:28:05Zgeorggkioulis@suse.com
<ul></ul><p>Grepping mkinitrd log only for <15-SP4, grepping y2log for the rest : <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/13961" class="external">PR</a></p>