Bug 42985 - FAILED: 98univention-samba4-dns.inst
FAILED: 98univention-samba4-dns.inst
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-17 17:36 CET by Florian Best
Modified: 2019-01-03 07:19 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.206
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016111721000147, 2016122721000055
Bug group (optional): Error handling, 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 Florian Best univentionstaff 2016-11-17 17:36:43 CET
Domain setup (this might take a while): FAILED: 98univention-samba4-dns.inst

Version: 4.1-4 errata327 (Vahr)

Remark: I just add one domain backup to our domain controller but it's show up this error
Comment 1 Florian Best univentionstaff 2017-01-02 17:35:52 CET
Reported again, 4.1-4 errata366 (Vahr)
Comment 2 Stefan Gohmann univentionstaff 2017-01-24 08:55:03 CET
Do we have the join logfiles?
Comment 3 Florian Best univentionstaff 2017-01-24 09:49:52 CET
(In reply to Stefan Gohmann from comment #2)
> Do we have the join logfiles?
No.
Comment 4 Stefan Gohmann univentionstaff 2019-01-03 07:19:18 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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