Bug 46365 - Request for: CLI Support; DNS checks; KRB messages; skip certain checks
Request for: CLI Support; DNS checks; KRB messages; skip certain checks
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - System diagnostic
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-21 15:39 CET by Johannes Kenkel
Modified: 2020-07-03 20:52 CEST (History)
0 users

See Also:
What kind of report is it?: Feature Request
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?: Yes
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Kenkel univentionstaff 2018-02-21 15:39:59 CET
Regarding the UMC system diagnostic and a related Blog article: <<https://www.univention.com/2018/02/module-system-diagnostic-your-problem-solving-assistant-in-ucs/#comments>> Moritz Bunkus indicated the following feature requests:

• Being able to run the same checks from the CLI (e.g. for easier access during remote upgrades, but also for integrating into monitoring solutions such as Nagios)
• DNS checks for server name resolution discrepancies: in the forum i often stumble across user setups where the UCS servers resolve e.g. the DC Master's host name correctly, but a client machine doesn't, and where it turns out that the external resolver (e.g. a FritzBox) resolves that name to the public, external IP address. Verifying that all nameservers configured via UCR and the ones handed out via DHCP serve the same addresses for at least the DC Master would be nice.
• Samba Kerberos vs. network interfaces: I had a couple of clients who had configured Samba to only listen on certain network interfaces (e.g. eth0 but not lo). This can lead to the Kerberos KDC not being reachable, especially when /etc/krb5.conf is configured to use 127.0.0.1. While there is a check for that already, its error messages are somewhat misleading. This could be vastly improved.
• Regarding a CLI mode & integration into monitoring solutions: it would be nice to be able to deactivate or skip certain checks. For example, we have one customer with host names with underscores, and he's perfectly fine with them — but the check always emits a warning.
Comment 1 Ingo Steuwer univentionstaff 2020-07-03 20:52:17 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 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.