Bug 52346 - 90_ucsschool/30_import-create_ou_via_cli fails because cleanup_ou() fails
90_ucsschool/30_import-create_ou_via_cli fails because cleanup_ou() fails
Status: RESOLVED FIXED
Product: UCS@school
Classification: Unclassified
Component: ucs-test
UCS@school 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Daniel Tröder
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-11-11 09:05 CET by Daniel Tröder
Modified: 2020-11-11 09:58 CET (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
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 Daniel Tröder univentionstaff 2020-11-11 09:05:47 CET
When a test-OU cannot be removed, the test fails.
The reason for not being able to remove a OU is almost always:
-----------
ldapError: Operation not allowed on non-leaf: subordinate objects must be deleted first
dn = 'cn=users,ou=kvxntk4syd,dc=autotest201,dc=local'
-----------
As the test creates and deletes 170 OUs, the likelihood of such a problem is high. Probably some interference / ping-pong with S4.

The test fails, because the cleanup_ou() function catches the wrong Exception class.
It should catch the right one and try to cleanup again.
Comment 1 Florian Best univentionstaff 2020-11-11 09:38:09 CET
Patch available at Bug #37685

*** This bug has been marked as a duplicate of bug 37685 ***
Comment 2 Daniel Tröder univentionstaff 2020-11-11 09:58:03 CET
Yes, Bug #37685 handles the root cause in UDM.
But this bug is only about the ucs-test case not failing because its tear-down code fails. Just a workaround, but it can be "released" today...