action #102515


validate_self_update greps only in /var/log/y2log and misses compressed logs

Added by syrianidou_sofia over 2 years ago. Updated over 2 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:



openQA test in scenario sle-15-SP4-Online-ppc64le-yast_self_update@ppc64le fails in

After checking the y2logs, it seemed as if the self update was skipped. Yast team prompted for a bug report ( see bug#1192515 ) where they spotted that in compressed y2log-1 , the self update really happens. We need to investigate why the y2logs for ppc64le can be sporadically compressed (meaning probably that there are more logs during installation) and why there are logs for skipping self update (the following logs are spotted only in case of test failure:

2021-10-29 08:26:00 <1> install(4141) [Ruby] clients/inst_update_installer.rb(installer_updated?):203 /var/lib/YaST2/installer_updated exists
2021-10-29 08:26:00 <1> install(4141) [Ruby] clients/inst_update_installer.rb(main):70 Self update not needed, skipping
2021-10-29 08:26:00 <1> install(4141) [Interpreter] modules/ProductControl.rb:1346 Called YaST client returned.
2021-10-29 08:26:00 <0> install(4141) [Interpreter] modules/ProductControl.rb:1346 Called YaST client returned: `next
2021-10-29 08:26:00 <0> install(4141) [Ruby] modules/Hooks.rb(initialize):156 Creating hook 'after_update_installer' from ''
2021-10-29 08:26:00 <0> install(4141) [Ruby] modules/Hooks.rb(find_hook_files):188 Searching for hook files in '/var/lib/YaST2/hooks/installation'...
2021-10-29 08:26:00 <1> install(4141) [Ruby] modules/Hooks.rb(execute):165 Executing hook 'after_update_installer'
2021-10-29 08:26:00 <1> install(4141) [Ruby] modules/ProductControl.rb(RunFrom):1381 Calling `inst_update_installer ($["enable_back":true, "enable_next":true]) returned `next

If there is something suspicious, we should update bug#1192515, otherwise we should modify the test module validate_self_update to grep in compressed logs as well (or avoid compressing logs before the module runs, if there is a way).

I have ran the test 10 times here:
The module fails 4/10 , usually for workers in QA-Power8-4-kvm , but that is not a reliable indication because there is one failure for QA-Power8-5-kvm as well and also some tests have passed for QA-Power8-4-kvm workers.

Test suite description

Test suite conducts installation with self-update explicitly enabled. No hard checks are done that the self-updating is really disabled. Installation is validated by successful boot and that YaST does not report any issue.


Fails since (at least) Build 61.1 (current job)

Expected result

Last good: 58.2 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by syrianidou_sofia over 2 years ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Bugs in existing tests)
  • Target version set to Current
Actions #2

Updated by JERiveraMoya over 2 years ago

  • Tags set to qe-yast-refinement
  • Priority changed from Normal to High
Actions #3

Updated by openqa_review over 2 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: yast_self_update

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 #4

Updated by JERiveraMoya over 2 years ago

  • Tags deleted (qe-yast-refinement)
  • Status changed from New to Feedback
  • Assignee set to JERiveraMoya
Actions #5

Updated by JERiveraMoya over 2 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF