Bug 37640 – S3->S4 inplace migration fails in case Master has more than one IPv4 address

Bug 37640 - S3->S4 inplace migration fails in case Master has more than one IPv4 address


Summary:	S3->S4 inplace migration fails in case Master has more than one IPv4 address

Status:	RESOLVED WONTFIX

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-01-28 13:19 CET by Arvid Requate
Modified:	2020-07-03 20:54 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	5: Blocking further progress on the daily work
User Pain:	0.086
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:

Flags:	requate: Patch_Available+

Attachments
adjusted 40_samba3upgrade.patch (7.24 KB, patch) 2015-01-28 13:23 CET, Arvid Requate	Details \| Diff
View All 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 Arvid Requate

2015-01-28 13:19:40 CET

The Samba3 to Samba4 inplace migration fails when the Master has more than one IP address:

======================================================================
    Failed to connect to ldap URL 'ldap://mydomain.local:7389' - LDAP client internal error: NT_STATUS_BAD_NETWORK_NAME
    Failed to connect to 'ldap://mydomain.local:7389' with backend 'ldap': (null)
    Could not open ldb connection to ldap://mydomain.local:7389, the error message is: (1, None)
    Trying to dig.
    Failed to connect to ldap URL 'ldap://10.200.8.10
    10.200.8.11:7389' - LDAP client internal error: NT_STATUS_BAD_NETWORK_NAME
    Failed to connect to 'ldap://10.200.8.10
    10.200.8.11:7389' with backend 'ldap': (null)
    ERROR(ldb): uncaught exception - None
      File "/usr/lib/python2.6/dist-packages/samba/netcmd/__init__.py", line 175, in _run
        return self.run(*args, **kwargs)
      File "/usr/lib/python2.6/dist-packages/samba/netcmd/domain.py", line 1399, in run
        useeadb=eadb, dns_backend=dns_backend, use_ntvfs=use_ntvfs, no_upn=no_upn)
      File "/usr/lib/python2.6/dist-packages/samba/upgrade.py", line 851, in upgrade_from_samba3
        ldb_object = Ldb(url.replace(url_hostname, stdout.rstrip('\n')), credentials=creds)
      File "/usr/lib/python2.6/dist-packages/samba/__init__.py", line 114, in __init__
        self.connect(url, flags, options)
    ERR: (No such object) "ldb_wait: No such object (32)" on DN flatname=MYDOMAIN,cn=Primary Domains at block before line 8
======================================================================

Comment 1 Arvid Requate

2015-01-28 13:23:31 CET

Created attachment 6636 [details]
adjusted 40_samba3upgrade.patch

The attached proposal is an adjusted version of our own samba4 40_samba3upgrade.patch.

This patch was necessary initially because samba4 itself fails to resolve DNS names during the update for some reason. The shortcomming of my original patch is that it didn't care to check for multiline answers from the dig query.

Comment 2 Ingo Steuwer

2020-07-03 20:54:01 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.