Univention Bugzilla – Bug 37389
renaming windowscomputer in UMC/UDM -> s4 connector traceback
Last modified: 2019-01-03 07:18:27 CET
Since we no longer allow renaming of windowscomputer objects in UDM/UMC with Bug #31083 this is maybe no longer relevant, nevertheless there is a problem Renaming a object are two operations in LDAP, modrdn (rename) and modfiy (set new cn). The s4 connector fails to handle the modrdn operation. The object is not renamed in S4. But the next operation is the modify of cn. Since this is the rdn attribute, it is not allowed to changed the cn if the object was not renamed in the first place. This results in a rejected object with such a traceback result = func(*args,**kwargs) NOT_ALLOWED_ON_RDN: {'info': "00002016: Modify of RDN 'cn' on cn=virt16,cn=computers,dc=ad,dc=in,dc=x,dc=de not permitted, must use 'rename' operation instead", 'desc': 'Operation not allowed on RDN'} Arvid provided a patch for the connector to fix the "rename handling".
Created attachment 6553 [details] udm_computer_rename.patch
> Since we no longer allow renaming of windowscomputer objects in UDM/UMC with Bug #31083 this is maybe no longer relevant Is this Bug still relevant? Bug 31083 Comment 10 states that we actually didn't disable the modification of the computer name in UMC/UDM, because this caused problems in the S4 connector. But you fixed the renaming in UDM/UMC via that bug, so I guess this one is a duplicate now?
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016. Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.