samba-tool fsmo transfer - uncaught exception

[Julien Ropé]

 > Can I ask just what is the exact command you are running ?


Here they are :

samba-tool fsmo transfer --role= forestedns -U administrator

samba-tool fsmo transfer --role= domaindns -U administrator


Transferring other roles doesn't cause an issue, but as I understand, 
only the DNS-related roles require the drs_utils module.


Note that the transfer seems to be effective in the end, as shown with 
the command "samba-tool fsmo show". But this exception makes me think 
that something did not complete.



Le 23/05/2019 à 19:38, Rowland penny via samba-technical a écrit :
> On 23/05/2019 14:48, Julien Ropé via samba-technical wrote:
>> Hi,
>>
>> I have been confronted to a problem with role transfers for forestdns 
>> and domaindns.
>> Using the command "samba-tool fsmo transfer [...]", I get an error :
>>
>> ERROR(<type 'exceptions.AttributeError'>): uncaught exception - 
>> 'module' object has no attribute 'drs_utils'
>> File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", 
>> line 177, in _run
>> return self.run(*args, **kwargs)
>> File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 
>> 528, in run
>> transfer_dns_role(self.outf, sambaopts, credopts, role, samdb)
>> File "/usr/lib/python2.7/dist-packages/samba/netcmd/fsmo.py", line 
>> 133, in transfer_dns_role
>> except samba.drs_utils.drsException as e:
>>
>>
>>
>> This is using Samba 4.9.
>>
>> Looking on the net, I found several references of the same, dating as 
>> far as 2016 :
>>
>> https://lists.samba.org/archive/samba/2016-September/203363.html
>>
>> https://lists.samba.org/archive/samba/2017-August/210120.html
>>
>> http://samba.2283325.n4.nabble.com/samba-4-7-0-AD-DC-FSMO-roles-transfer-error-td4725099.html 
>>
>>
>>
>>
>> These show the error was found in 4.5, 4.6 and 4.7.
>>
>> Each time, the solution was to modify the file 
>> "[samba]/lib/python27/site-packages/samba/netcmd/fsmo.py", by adding 
>> the line "import samba.drs_utils".
>> I have verified that this fixes the issue for me.
>>
>>
>> I understand the problem is not seen in every environment, but it 
>> still seems to be there for some users.
>> If this issue is known and the fix is so easy, why isn't it applied?
>> If this is because there is something wrong with the environments of 
>> the people that see it, what should they (we) do to fix it? Is 
>> editing the code ourselves a good solution, or does that hide 
>> something else we should look at in our environment?
>>
> Can I ask just what is the exact command you are running ?
>
> Rowland
>
>
>
>
>
-- 
Julien ROPÉ
Support OSSA
Tél : 06.38.99.80.22 / 01 46 96 63 63
Courriel : jrope at linagora.com
www.linagora.com
--
Message envoyé grâce à OBM, la Communication Libre par Linagora