Bug 40812 - Rejoin 10univention-ldap-server.inst fails in AD member mode if join user is not Administrator
Rejoin 10univention-ldap-server.inst fails in AD member mode if join user is ...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-01 19:38 CET by Stefan Gohmann
Modified: 2019-01-03 07:23 CET (History)
1 user (show)

See Also:
What kind of report is it?: ---
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:
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 Stefan Gohmann univentionstaff 2016-03-01 19:38:07 CET
The join script 10univention-ldap-server.inst fails if UCS is joined into a AD domain and the join user is not Administrator.

See 

http://jenkins.knut.univention.de:8080/job/UCS-4.1/job/UCS-4.1-1/job/ADMemberMultiEnv/lastCompletedBuild/Mode=module,Version=w2k12-german-other-join-user/testReport/10_ldap/100_ldapserver_policy/test/

2016-02-29 16:06:21.953693]** Running checks on situation before test...
[2016-02-29 16:06:21.967190]** Adding a DC backup...
[2016-02-29 16:06:21.967353]Creating computers/domaincontroller_backup object with {'set': {'position': 'cn=dc,cn=computers,dc=autotest224,dc=local', 'domain': 'autotest224.local', 'name': 'klbs7ljddg'}}
[2016-02-29 16:06:22.541968]<closed file '<fdopen>', mode 'rb' at 0x22e2390>
[2016-02-29 16:06:23.734343]<closed file '<fdopen>', mode 'rb' at 0x22e24b0>
[2016-02-29 16:06:24.810555]CMD: ['univention-run-join-scripts', '-dcaccount', 'Administrator', '-dcpwd', '/var/lib/ucs-test/pwdfile', '--force', '--run-scripts', '10univention-ldap-server.inst']
[2016-02-29 16:06:54.258194]Running 10univention-ldap-server.inst�[60Gfailed (exitcode: 3)
[2016-02-29 16:06:54.261582]### FAIL ###
[2016-02-29 16:06:54.261605]LDAP server policy does not contain all DC master and DC backups. ldapserver_policy[ldapServer]: ['admember224.autotest224.local'] ldap_servers: ['admember224.autotest224.local', 'klbs7ljddg.autotest224.local']
[2016-02-29 16:06:54.261620]###      ###
[2016-02-29 16:06:54.261629]Cleanup after exception: <type 'exceptions.SystemExit'> 1
[2016-02-29 16:06:54.261637]Performing UCSTestUDM cleanup...
[2016-02-29 16:06:54.531755]UCSTestUDM cleanup done


The join.log:
univention-run-join-scripts started
Mo 29. Feb 16:06:25 EST 2016

RUNNING 10univention-ldap-server.inst
2016-02-29 16:06:25.623998216-05:00 (in joinscript_init)
Adding SRV record "ldap tcp 0 100 7389 admember224.autotest224.local." to zone autotest224.local...
done
Adding ZONE record "root@autotest224.local. 1 28800 10800 604800 108001 admember224.autotest224.local." to zone 10.210...
Adding SRV record "domaincontroller_master tcp 0 0 0 admember224.autotest224.local." to zone autotest224.local...
done
Object exists: cn=Univention,cn=packages,cn=univention,dc=autotest224,dc=local
Object exists: cn=Fernwartung,cn=packages,cn=univention,dc=autotest224,dc=local
Object exists: cn=Tools,cn=packages,cn=univention,dc=autotest224,dc=local
Object exists: cn=Multimedia,cn=packages,cn=univention,dc=autotest224,dc=local
Object exists: cn=Entwicklung,cn=packages,cn=univention,dc=autotest224,dc=local
LDAP Error: Type or value exists: modify/add: uniqueMember: value #0 already exists
EXITCODE=3
Comment 1 Stefan Gohmann univentionstaff 2016-03-01 19:39:47 CET
ucs-test r67827:
* 10_ldap/100_ldapserver_policy: Skip in AD member setups since
  (Bug #40812)
Comment 2 Florian Best univentionstaff 2016-12-23 14:33:16 CET
Could be fixed by Bug #43247.
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:23:53 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.