samba-interop works well with ADB - however, in a world where fault tolerance is everything, clustered samba instances using the open source ctdb makes samba sessions across hosts lock-aware. It does this by keeping the tdb files of both samba instances in step and allows each node to be the locking master so that users working on open files can seemless continue if a samba server goes down.
However, because the samba-interop keeps the computer account password in the secrets.tdb also in step, the real ADB computer account password is overridden from time to time making the domain join fail if the nodes switches between the cluster. Support for this would simply mean allowing ADB to assert the computer account password into the samba secrets.tdb all the time as oppoased to only once when the interoperability is installed.
Samba normally backs off from managing the computer account secrets by the key:
machine password timeout = 0
but this is ignored with clustersing turned on in the latest ctdb versions because while the local samba instance does not attempt to change the computer account password (as it's given that up to ADB), the clustering copies the computer account password between all the nodes messing up the work that ADB does as join time.