Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
fusiondirectory
fusiondirectory
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 49
    • Issues 49
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • fusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #5334

Closed
Open
Opened Jan 23, 2017 by bmortier@bmortierMaintainer

when migrating from 1.0.16 to 1.0.19 with the new version of --migrate-dhcp there is till a reference not corrected

Hello,

a customer migrated from 1.0.16 to 1.0.19 and used -migrate-dhcp the entries correctly moved to ou=dhcp but on refererence was still pointing to the old entry

363 cn=zeus,ou=servers,ou=systems,dc=toto,dc=com cn: zeus description: dns dhcp ldap -slave .... objectClass: top objectClass: goServer objectClass: GOhard
objectClass: dhcpServer objectClass: argonautDNSConfig objectClass: argonautClient objectClass: fdDNSHost dhcpServiceDN: cn=dhcp,ou=dhcp,dc=master,dc=fdi

472 cn=dhcp-zeus,ou=dhcp,dc=master,dc=fdi .... objectClass: top objectClass: dhcpService dhcpPrimaryDN: cn=zeus,ou=servers,ou=systems,dc=master,dc=fdi cn: dhcp-zeus

as you can see the server point correctly to the cn=dhcp-zeus,ou=dhcp,dc=master,dc=fdi point correctly to the correct serveur hosting the dhcp service.

But the server dhcpServiceDN entry was pointing incorrectly to and old service entry not longer existing due to the migration

dhcpServiceDN: cn=dhcp,ou=dhcp,dc=master,dc=fdi

so it seems one entry was not correctly migrated

(from redmine: issue id 5334, created on 2017-01-23, closed on 2017-04-25)

  • Relations:
    • relates #5356
    • copied_to #5485 (closed)
  • Changesets:
    • Revision f4a67113 by Côme Chilliet on 2017-01-24T08:55:16.000Z:
Fixes #5334 fixed DHCP config DN saved in server after migration
  • Revision 4996946c by Côme Chilliet on 2017-01-24T08:55:55.000Z:
Fixes #5334 fixed DHCP config DN saved in server after migration
  • Revision 9967bc8c by Côme Chilliet on 2017-02-08T14:25:55.000Z:
Fixes #5334 fixed DHCP config DN saved in server after migration
  • Custom Fields:
    • Bug in version: 1.0.18
    • Support contract: Bronze
Assignee
Assign to
FusionDirectory 1.1
Milestone
FusionDirectory 1.1 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: fusiondirectory/fd#5334