Bug 46642 – IP change of DC master in s4 env -> samba drs replication broken

Bug 46642 - IP change of DC master in s4 env -> samba drs replication broken


Summary:	IP change of DC master in s4 env -> samba drs replication broken

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Samba4
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:	Samba maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-03-13 19:23 CET by Felix Botner
Modified:	2021-05-14 16:34 CEST (History)
CC List:	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?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Felix Botner

2018-03-13 19:23:38 CET

UCS 4.3 master, backup, slave all with samba4

After an ip change on my master, drs replication is broken (as expected as i would add).

new master ip is 10.200.7.165

check_essential_samba4_dns_records.sh on backup and slave:

gc._msdcs.four.three has address 10.200.7.160
gc._msdcs.four.three has address 10.200.7.162
gc._msdcs.four.three has address 10.200.7.161

10.200.7.160 is no longer valid.

Comment 1 Ingo Steuwer

2021-05-14 15:43:11 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.