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
  • #3897
Closed
Open
Issue created Jun 23, 2015 by bmortier@bmortierMaintainer

Setup fails if root object is missing

Before we could create it at the checks step, now we can’t because the setup attempts to save the config in the LDAP first.

This must be tested in 1.0.9

(from redmine: issue id 3897, created on 2015-06-23, closed on 2015-07-06)

  • Relations:
    • copied_to #3884 (closed)
  • Changesets:
    • Revision 98102d4c by Côme Chilliet on 2015-06-29T15:24:30.000Z:
Fixes #3897 Setup fails if root object is missing
  • Revision 8ca72b84 by Côme Chilliet on 2015-06-29T15:24:48.000Z:
Fixes #3897 Setup fails if root object is missing
  • Revision 5beaa568 by Côme Chilliet on 2015-06-30T15:02:19.000Z:
Fixes #3897 Forcing base creation in setup
  • Revision d8558587 by Côme Chilliet on 2015-06-30T15:02:35.000Z:
Fixes #3897 Forcing base creation in setup
  • Custom Fields:
    • Bug in version: 1.0.8.7
  • Uploads:
    • 1435587372.64
    • 0001-Fixes-3897-Setup-fails-if-root-object-is-missing.patch
    • Screenshot-18-24-19
    • 0002-Fixes-3897-Forcing-base-creation-in-setup.patch
Assignee
Assign to
Time tracking