Bug 44804 - Test case 00_checks.99check_log_files.test fails in UCS 4.2
Test case 00_checks.99check_log_files.test fails in UCS 4.2
Status: CLOSED FIXED
Product: UCS Test
Classification: Unclassified
Component: General
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Felix Botner
Florian Best
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-16 08:41 CEST by Stefan Gohmann
Modified: 2021-05-25 10:11 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2017-06-16 08:41:32 CEST
http://jenkins.knut.univention.de:8080/job/UCS-4.2/job/UCS-4.2-0/job/AutotestJoin/lastCompletedBuild/SambaVersion=s3,Systemrolle=master/testReport/00_checks/99check_log_files/test/

Test Test case 00_checks.99check_log_files.test fails in UCS 4.2:

[2017-06-15 23:54:51.792474] 
[2017-06-15 23:54:51.792597] An error occured while trying to check the installation profile for 'call_master_joinscripts' setting: IOError(2, 'Datei oder Verzeichnis nicht gefunden') Adjusting patterns to ignore respective 'join' messages.
[2017-06-15 23:54:51.831164] 
[2017-06-15 23:54:51.831219] The file '/var/log/univention/installation.log' cannot be found, skipping...
[2017-06-15 23:54:51.831282] 
[2017-06-15 23:54:51.831326] The file '/var/log/univention/installation.log.gz' cannot be found, skipping...
[2017-06-15 23:54:51.839530] 
[2017-06-15 23:54:51.839577] The file '/var/log/univention/installer.log' cannot be found, skipping...
[2017-06-15 23:54:51.839631] 
[2017-06-15 23:54:51.839673] The file '/var/log/univention/installer.log.gz' cannot be found, skipping...
[2017-06-15 23:54:51.952130] 
[2017-06-15 23:54:51.952157] Errors found in '/var/log/univention/updater.log':
[2017-06-15 23:54:51.952202] 
[2017-06-15 23:54:51.952273]  E: updater.log:295, Job for univention-management-console-server.service failed. See 'systemctl status univention-management-console-server.service' and 'journalctl -xn' for details.
[2017-06-15 23:54:51.952344]  E: updater.log:296, invoke-rc.d: initscript univention-management-console-server, action "reload" failed.
[2017-06-15 23:54:51.952411]  E: updater.log:303, Job for univention-management-console-server.service failed. See 'systemctl status univention-management-console-server.service' and 'journalctl -xn' for details.
[2017-06-15 23:54:51.952472]  E: updater.log:304, invoke-rc.d: initscript univention-management-console-server, action "reload" failed.
[2017-06-15 23:54:51.952563]  E: updater.log:311, Job for univention-management-console-server.service failed. See 'systemctl status univention-management-console-server.service' and 'journalctl -xn' for details.
[2017-06-15 23:54:51.952624]  E: updater.log:312, invoke-rc.d: initscript univention-management-console-server, action "reload" failed.
[2017-06-15 23:54:51.952687]  E: updater.log:507, Job for univention-management-console-server.service failed. See 'systemctl status univention-management-console-server.service' and 'journalctl -xn' for details.
[2017-06-15 23:54:51.952746]  E: updater.log:508, invoke-rc.d: initscript univention-management-console-server, action "reload" failed.
Comment 1 Stefan Gohmann univentionstaff 2017-06-29 07:01:32 CEST
The error messages are now ignored: 

r80602:
* 00_checks/99check_log_files: Ignore some more error messages
  (Bug #44804)
Comment 2 Florian Best univentionstaff 2017-06-29 20:45:57 CEST
The real error message from journalctl -xn is:
"Unit univention-management-console-server.service cannot be reloaded because it is inactive."

I don't know how to fix this?! It seems to automatically detect that the service is not running and prevents a reload then.
Comment 3 Felix Botner univentionstaff 2017-12-01 16:13:54 CET
disabled this test case, too unstable
Comment 4 Florian Best univentionstaff 2017-12-01 16:23:31 CET
I'm okay with it. We should somewhen add a list of known errors which should not occur inside of the log files.
Probably we should also grep for Tracebacks.