Bug 25118 - AD Connector: Löschen von Containern mit "sub"-Containern auf AD Seite
AD Connector: Löschen von Containern mit "sub"-Containern auf AD Seite
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 3.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Connector maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-12-02 17:22 CET by Felix Botner
Modified: 2017-08-08 07:08 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2011-12-02 17:22:56 CET
UCS 3.0 <= w2k8r2

syncmode read

Folgende Container angelegt:

TESTLIBPATH="/usr/share/ucs-test/lib"
source "$TESTLIBPATH/base.lib"
source "$TESTLIBPATH/udm.lib"
source "$TESTLIBPATH/adconnector.lib"

ad_createcontainer "CONTAINER1"
ad_createcontainer "CONTAINER2"
ad_createcontainer "CONTAINER3" "" "CN=CONTAINER1,DC=w2k8r2,DC=win"

Löschen von CONTAINER2 in AD wurde korrekt übernommen, beim Löschen von CONTAINER1 gab es jedoch folgenden Traceback:

30.11.2011 23:58:20,264 LDAP        (INFO   ): object_from_element: DN of removed object: CN=CONTAINER1,DC=w2k8r2,DC=win
30.11.2011 23:58:20,265 LDAP        (INFO   ): _ignore_object: Do not ignore CN=CONTAINER1,DC=w2k8r2,DC=win
30.11.2011 23:58:20,265 LDAP        (INFO   ): _object_mapping: map with key container and type con
30.11.2011 23:58:20,265 LDAP        (INFO   ): _dn_type con
30.11.2011 23:58:20,266 LDAP        (INFO   ): _ignore_object: Do not ignore cn=container1,dc=w2k8,dc=r2
30.11.2011 23:58:20,268 LDAP        (INFO   ): get_ucs_object: object found: cn=container1,dc=w2k8,dc=r2
30.11.2011 23:58:20,268 LDAP        (PROCESS): sync to ucs:   [     container] [    delete] cn=container1,dc=w2k8,dc=r2
30.11.2011 23:58:20,268 LDAP        (INFO   ): sync_to_ucs: set position to dc=w2k8,dc=r2
30.11.2011 23:58:20,273 LDAP        (INFO   ): delete object exception: Operation not allowed on non-leaf: subordinate objects must be deleted first
30.11.2011 23:58:20,273 LDAP        (ERROR  ): Unknown Exception during sync_to_ucs
30.11.2011 23:58:20,276 LDAP        (ERROR  ): Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/univention/connector/__init__.py", line 1069, in sync_to_ucs
    result = self.delete_in_ucs(property_type, object, module, position)
  File "/usr/lib/pymodules/python2.6/univention/connector/__init__.py", line 974, in delete_in_ucs
    ucs_object.remove()
  File "/usr/lib/pymodules/python2.6/univention/admin/handlers/__init__.py", line 455, in remove
    return self._remove(remove_childs)
  File "/usr/lib/pymodules/python2.6/univention/admin/handlers/__init__.py", line 936, in _remove
    self.lo.delete(self.dn)
  File "/usr/lib/pymodules/python2.6/univention/admin/uldap.py", line 426, in delete
    raise univention.admin.uexceptions.ldapError, _err2str(msg)
ldapError: Operation not allowed on non-leaf: subordinate objects must be deleted first
Comment 1 Stefan Gohmann univentionstaff 2012-10-04 18:18:26 CEST
Zur Erklärung: Bug #28698
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:37:54 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Stefan Gohmann univentionstaff 2017-08-08 07:08:32 CEST
This issue has been filed against UCS 3.0.

UCS 3.0 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.