Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #5187
Closed
Open
Issue created Oct 11, 2016 by bmortier@bmortierMaintainer

When saving again after an error, it tries to move if dn changed

If I try to save and there is an error, the second time I try to save, if the computed dn is not the same it attempt to move the object while it’s not saved yet

(from redmine: issue id 5187, created on 2016-10-11, closed on 2017-02-13)

  • Relations:
    • relates #4893
  • Changesets:
    • Revision ebd0da98 by Côme Chilliet on 2016-10-11T12:33:00.000Z:
Fixes #5187 Reverting dn to old one if saving fails
Assignee
Assign to
Time tracking