Bug 1218700

Summary: [Build sofiasyria/os-autoinst-distri-opensuse#y2log_fail] openQA test fails in detect_yast2_failures
Product: [openSUSE] PUBLIC SUSE Linux Enterprise Server 15 SP6 Reporter: Sofia Syrianidou <sofia.syrianidou>
Component: InstallationAssignee: E-mail List <yast2-maintainers>
Status: RESOLVED FIXED QA Contact:
Severity: Minor    
Priority: P2 - High CC: jreidinger, rtsvetkov, sofia.syrianidou
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: SLES 15   
URL: https://openqa.suse.de/tests/13224929/modules/detect_yast2_failures/steps/524
Whiteboard:
Found By: openQA Services Priority:
Business Priority: Blocker: Yes
Marketing QA Status: --- IT Deployment: ---

Description Sofia Syrianidou 2024-01-10 12:32:56 UTC 
In y2log during instlallation, there are the following error messages detected:

/tmp/var/log/YaST2/y2log-2.gz:2023-12-16 06:50:17 <3> install(4251) [Ruby] bootloader/bootloader_factory.rb(bootloader_by_name):84 Factory receive nil name
/tmp/var/log/YaST2/y2log-2.gz:2023-12-16 06:53:29 <3> install(4251) [Interpreter] installation/proposal_store.rb:194 Can't find YCP client component clone_proposal: No such file or directory
/tmp/var/log/YaST2/y2log-2.gz:2023-12-16 06:53:32 <3> install(4251) [Interpreter] installation/proposal_store.rb:194 Can't find YCP client component clone_proposal: No such file or directory
/tmp/var/log/YaST2/y2log-2.gz:2023-12-16 06:53:34 <3> install(4251) [Ruby] bootloader/bootloader_factory.rb(bootloader_by_name):84 Factory receive nil name
/tmp/var/log/YaST2/y2log-2.gz:2023-12-16 06:53:44 <3> install(4251) [Interpreter] installation/proposal_store.rb:194 Can't find YCP client component clone_proposal: No such file or directory



## Observation

openQA test in scenario sle-15-SP6-Online-x86_64-detect_yast2_failures_dev@sofiasyria/os-autoinst-distri-opensuse#y2log_fail@64bit fails in
[detect_yast2_failures](https://openqa.suse.de/tests/13224929/modules/detect_yast2_failures/steps/524)

## Test suite description
Specific test displaying as much dialogs as possible to increase test coverage, which would fail hard in case any yast2 failure is found in logs.


## Reproducible

Fails since (at least) Build [sofiasyria/os-autoinst-distri-opensuse#y2log_fail](https://openqa.suse.de/tests/13224477)


## Expected result

Last good: [sofiasyria/os-autoinst-distri-opensuse#y2log_fail](https://openqa.suse.de/tests/13209039) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit&test=detect_yast2_failures_dev%40sofiasyria%2Fos-autoinst-distri-opensuse%23y2log_fail&version=15-SP6)
Comment 1 Sofia Syrianidou 2024-01-10 12:37:59 UTC 
@Josef Reidinger mentioned that commit: 
https://github.com/yast/yast-installation/commit/2a27af92618fbf4f28a6cd2be96685feeb8ca05d

has removed the clone proposal but in control file it is still mentioned as proposal client. So, it should be removed by the control file as well: https://github.com/yast/skelcd-control-leanos/blob/master/control/control.leanos.xml#L277
Comment 2 Radoslav Tzvetkov 2024-01-10 15:39:39 UTC 
Hi Sofia, why is this a blocker?
Comment 3 Josef Reidinger 2024-01-10 21:12:58 UTC 
yeah, this should not be blocker. It is just line in logs that indicate some problems, but none of log lines are critical.
Comment 4 Josef Reidinger 2024-01-10 23:07:00 UTC 
fix for clone proposal error https://github.com/yast/skelcd-control-leanos/pull/109
Comment 5 Josef Reidinger 2024-01-10 23:26:15 UTC 
and bootloader factory fix https://github.com/yast/yast-bootloader/pull/691
Comment 6 Lukas Ocilka 2024-01-11 08:20:47 UTC 
Rado, this is not even P2. It's just a log entry, invisible to the user. It's not really blocking anything anywhere. Maybe the test itself :) but honestly, it's test that "looks for problems" :DDD
Comment 7 Sofia Syrianidou 2024-01-11 09:22:35 UTC 
Nothing is blocked by the failure. The test just parses the y2log and fails when it detects new error messages.
Comment 8 Stefan Hundhammer 2024-01-11 09:51:54 UTC 
Both fixes are on the way.