#4548 Renaming object to current name invalidates all other modifications
Closed: Fixed None Opened 9 years ago by tbabej.

Suppose we have a user

[tbabej@vm-116 labtool]$ ipa user-show randomik
  User login: randomik
  First name: RAN
  Last name: dom
  Home directory: /home/random
.. snip..

The following command fails with "no modifications to be performed", when clearly, we are changing the first name to "someothername".

[tbabej@vm-116 labtool]$ ipa user-mod randomik --first someothername --rename randomik
ipa: ERROR: no modifications to be performed

The reason is that we are renaming the entry to its current name, which raises EmptyModList error. Without the --rename option, the command works as expected.

[tbabej@vm-116 labtool]$ ipa user-mod randomik --first someothername
------------------------
Modified user "randomik"
------------------------
  User login: randomik
  First name: someothername
  Last name: dom
  Home directory: /home/random

Conclusion: Renaming a object to its current name will invalidate all other modifications done in the same command. This applies to any object (not just users).


Tomas is handling it as part of 4.1 development.

master:

  • d83af7d baseldap: Properly handle the case of renaming object to the same name

ipa-4-1:

  • 0cf2dbc baseldap: Properly handle the case of renaming object to the same name

Metadata Update from @tbabej:
- Issue assigned to tbabej
- Issue set to the milestone: FreeIPA 4.1

7 years ago

Login to comment on this ticket.

Metadata