Bug 52861 - Check if samba4 is installed from the system diagnostic
Check if samba4 is installed from the system diagnostic
Status: RESOLVED DUPLICATE of bug 51886
Product: UCS
Classification: Unclassified
Component: UMC - System diagnostic
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2021-03-02 11:28 CET by Christina Scheinig
Modified: 2021-03-03 09:49 CET (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a 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?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2021022521000228
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 Christina Scheinig univentionstaff 2021-03-02 11:28:20 CET
"Check if samba4 is installed" is the diagnostic message, if samba4 is not installed on the central master.

This message caused a customer to just install samba4 (not even properly) on the system, which causes a lot of problems.
Maybe this message is misleading, because samba4 is not necessary on a central master.

As I recall from Bug 52464 this is not a good idea at all?
Comment 1 Erik Damrose univentionstaff 2021-03-02 12:02:02 CET
It is not totally clear from the ticket and the diagnostic message... Is this a duplicate of bug 51886?
Comment 2 Christina Scheinig univentionstaff 2021-03-03 09:35:41 CET
So, this seems to be Bug 51886. I haven't found it. The bugfix has not been released yet, hasn't it?

I put my ticket on the other bug. For me it is okay, when we close this bug.
Comment 3 Florian Best univentionstaff 2021-03-03 09:49:19 CET

*** This bug has been marked as a duplicate of bug 51886 ***