Univention Bugzilla – Bug 43073
samba.conf uses python-netifaces - breaks with PXE installation badly
Last modified: 2017-04-04 18:28:47 CEST
services/univention-samba/conffiles/etc/samba/smb.conf.d/01univention-samba_main uses python-netifaces to get the list of network interfaces; they are used to generate the "interfaces" statements specifying the interfaces samba should listen on.
In some scenarios (PXE installation, interfaces/restart/auto=no) the runtime configuration differs from the configured configuration: During installation the bridge "br0" is not yet available and thus does NOT get added to "interfaces". After the reboot /etc/samba/smb.conf is not committed again and thus only "lo" remains as the only usable interface. This breaks Kerberos authentication, login as Administrator, joining Windows clients, etc...
Task #4777 2016-11-24/25 - UCS-Technikschulung - Bremen
IIRC I've also seen "eth0 eth1 eth2 eth3 eth4 eth5" [...] listed, even though only eth0 was configured.
(In reply to Arvid Requate from comment #1)
> IIRC I've also seen "eth0 eth1 eth2 eth3 eth4 eth5" [...] listed, even
> though only eth0 was configured.
It also picks up the tap interfaces of all VMs running at the time smb.conf is committed.
But samba seems to use only those interfaces with an IP configuration, thus ventX and ethY are ignored as they are IP-less members of a brZ.
Nevertheless I would appreciate it if Samba would use the configured interfaces as every other service in UCS does.
*** Bug 41056 has been marked as a duplicate of this bug. ***
Fixed in univention-samba and univention-samba4.
Tests: OK, it doesn't break anything even if the configured interface doesn't exist. The docker interface is still by default excluded. If one excluded lo, it won't work any longer, but I think in this case samba/interfaces can be used.
Code review: OK (r76761 + r76758)
UCS 4.2 has been released:
If this error occurs again, please use "Clone This Bug".