Univention Bugzilla – Bug 30813
Appliance: windows/wins-server not updated after join.
Last modified: 2013-11-19 06:43:01 CET
On a UCS DC Slave with Samba4 created from an appliance template machine the UCR variable windows/wins-server was set to a server name which did not match the FQDN of the DC master in the domain. In the specific case the relevant UCR variables after finishing the system setup of the appliance (with samba4 selected) but before finally joining the DC Slave were:
root@slave14:~# ucr search --brief windows/wins-server ldap/server/name windows/domain ^domainname
domainname: arucs31i0.qa ## this is the new domain name
ldap/server/name: master.univention.qa ## this is some legacy name
After joining, windows/wins-server was still unchanged. Probably the variable should not be initialized in the postinst but in the join script instead.
The initiation of the UCR variable windows/wins-server has beend moved from univention-samba4.postinst to the join script 96univention-samba4.inst. This has the consequence that the variable has the right value after joining.
We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2.
As such, this bug is moved to the new target milestone.
Currently the joinscript sets this variable only on Samba4 DCs that are joined "normally", which probably is the right thing to do. But I think it would be good to then not set it statically to $ldap_master, but to nove the code inside the bash function samba_domain_join and set the variable either to samba4/dc or to the fqdn of the specific server. On the other hand, if normal broadcast-join works, then the variable does not need to be set.
Initialization of windows/wins-support should also be moved from postinst to the joinscript: It should be set ='yes' for provisioned DCs and ?'no' on DCs that are "normally" joined.
The behaviour and the changelogs have been adjusted accordingly.
Actually the stuff was still in the postinst, I removed it,.
(In reply to Arvid Requate from comment #3)
> Currently the joinscript sets this variable only on Samba4 DCs that are
> joined "normally", which probably is the right thing to do. But I think it
> would be good to then not set it statically to $ldap_master, but to nove the
> code inside the bash function samba_domain_join and set the variable either
> to samba4/dc or to the fqdn of the specific server. On the other hand, if
> normal broadcast-join works, then the variable does not need to be set.
For S3 it is still set statically to $ldap_master if the broadcast join was successful.
All other tests were successful.
UCS 3.2 has been released:
If this error occurs again, please use "Clone This Bug".