Bug 48543 - univention-system-check does not check if s4-connector is running
univention-system-check does not check if s4-connector is running
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Sysinfo
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-01-29 17:57 CET by Christian Völker
Modified: 2021-05-14 16:34 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019012921000138
Bug group (optional): Error handling
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Völker univentionstaff 2019-01-29 17:57:16 CET
univention-system-check does not check if s4-connector is running.

When started on a server (ie backup) it simply reports the misleading error from bug #48203 :


running [basic]    - FAILED   - joinstatus.sh
[...]
Tests failed: 1

Test failed: univention-system-check.d/basic/joinstatus.sh, Impact: no domain functionallity
        + IMPACT='no domain functionallity'
        + univention-check-join-status
        Warning: 'univention-s4-connector' is not configured.
        Error: Not all install files configured: 1 missing
root@solid:~# univention-s4connector-list-rejected
Traceback (most recent call last):
  File "/usr/sbin/univention-s4connector-list-rejected", line 73, in <module>
    import mapping
ImportError: No module named mapping


Either univention-system-check should check if s4 connector is running and in this case ignore the error.

Or bug #48203 should be fixed.
Comment 1 Ingo Steuwer univentionstaff 2021-05-14 15:41:57 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.