Univention Bugzilla – Bug 30792
join into site ignores given samba4-join-dc and fails
Last modified: 2013-05-30 10:28:37 CEST
If the UCS DC Master is no Samba4 DC but a DC Backup, the join of a DC Slave with Samba4 into a AD/Samba4-"site" fails (both samba4/join/site and samba4/dc are set). In 96univention-samba4.inst the "create_site()"-function ignores the given samba4/dc and tries to search Samba4 on ldap/master, which fails.
the join fails completely with an not working but somehow registered Samba4 DC -> higher priority
Fixed in errata3.1-1 and ucs3.1-2. Advisory: 2013-05-07-univention-samba4.yaml Changelog: changelog-3.1-2.tex
Now the join fails, but the scenario S4 on DC Slave and no S4 on DC Master is supported. See also Bug #31555. As far as I can see, the error was introduced with Bug #27497. Maybe we could remove the create_site call since the site is created during the provisioning?
*** Bug 31555 has been marked as a duplicate of this bug. ***
(In reply to comment #0) > If the UCS DC Master is no Samba4 DC but a DC Backup, the join of a DC Slave > with Samba4 into a AD/Samba4-"site" fails (both samba4/join/site and samba4/dc > are set). > > In 96univention-samba4.inst the "create_site()"-function ignores the given > samba4/dc and tries to search Samba4 on ldap/master, which fails. I was not able to reproduce it. Sure the site creation of the site failed at this point, but the site is created later, see Bug #27497. Do you have any logs from the system?
(In reply to comment #5) > (In reply to comment #0) > > If the UCS DC Master is no Samba4 DC but a DC Backup, the join of a DC Slave > > with Samba4 into a AD/Samba4-"site" fails (both samba4/join/site and samba4/dc > > are set). > > > > In 96univention-samba4.inst the "create_site()"-function ignores the given > > samba4/dc and tries to search Samba4 on ldap/master, which fails. > > I was not able to reproduce it. Sure the site creation of the site failed at > this point, but the site is created later, see Bug #27497. In my tests univention-join stopped because 96univention-samba4.inst failed, the issue here is not that the site isn't created but that univention-join failed. AFAIR the site has been created, but I'm unsure if it worked. We always deleted it an any references to have a "clean" test-scenario. > Do you have any logs from the system? No (customer system). Maybe an Errata in the last 3 month changed the behaviour?
> Maybe an Errata in the last 3 month changed the behaviour? Indeed, this one ;-) I removed the "exit 1" again that I added before for the case of failure. Now only a warnig is issued.
3.1-1 errata: OK, I was able to join against the DC Backup (samba4/dc + samba4/join/site) YAML: OK 3.1-2: OK (Code comparison) Changelog: OK
http://errata.univention.de/ucs/3.1/114.html