Bug 35325 - Configure bonding interface for kdc/server
Configure bonding interface for kdc/server
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-09 11:53 CEST by Arvid Requate
Modified: 2020-07-03 20:55 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: 2014060421010861
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 Arvid Requate univentionstaff 2014-07-09 11:53:14 CEST
Apparently the new default 127.0.0.1 for kerberos/kdc (introduced via Bug 29291) doesn't work for setups where bonding interfaces are configured.

Maybe we can improve the default by checking interfaces/primary (and possibly samba/interfaces?).



+++ This bug was initially created as a clone of Bug #35303 +++

If using a bonding scenario with samba4 you have to set kerberos/kdc to the vonding interface ip. This gets set to localhost by some update... 2014060421010861

We should document this.
Comment 1 Ingo Steuwer univentionstaff 2020-07-03 20:55:23 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.