Bug 31781 - Old DN printed after object shift
Old DN printed after object shift
Status: RESOLVED DUPLICATE of bug 41694
Product: UCS
Classification: Unclassified
Component: UDM - CLI
UNSTABLE
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-20 12:26 CEST by Lukas Walter
Modified: 2018-04-13 13:28 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
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 Lukas Walter univentionstaff 2013-06-20 12:26:45 CEST
After moving an object to another position, the old DN (containing the old position) is printed.

See:
=====
root@master10:~# udm users/user create --set username="some_user" --set lastname="univention" --set password="univention"
Object created: uid=some_user,dc=ucs,dc=dev

root@master10:~# udm users/user move --dn "uid=some_user,dc=ucs,dc=dev" --position "cn=computers,dc=ucs,dc=dev"
Object modified: uid=some_user,dc=ucs,dc=dev



The new DN should be printed instead, like it is already done when an object attribute is modified which is part of the DN (e.g uid, zoneName or common name).

See:
=====
root@master10:~# udm users/user create --set username="old" --set lastname="univention" --set password="univention"
Object created: uid=old,dc=ucs,dc=dev

root@master10:~# udm users/user modify --dn uid="old,dc=ucs,dc=dev" --set username="new"
Object modified: uid=new,dc=ucs,dc=dev
Comment 1 Lukas Walter univentionstaff 2013-06-20 12:32:59 CEST
When this bug is fixed, univention/testing/udm.py.UCSTestUDM().move_object() should be adpdated to return the DN.
Comment 2 Stefan Gohmann univentionstaff 2014-02-18 21:29:20 CET
This issue has been filed against the UCS version "unstable" which does not really exist. Please change the version value.
Comment 3 Florian Best univentionstaff 2016-07-08 13:12:56 CEST

*** This bug has been marked as a duplicate of bug 41694 ***