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
• 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

hello,

after moving the dhcpServiceDN to the correct entry, everything was working again

dhcpServiceDN: cn=dhcp-zeus,ou=dhcp,dc=toto,dc=com

Cheers

(from redmine: written on 2017-01-23)

By bmortier on 2017-09-02T15:35:17 (imported from GitLab)

Hello, When I try to migrate from 1.0.16 to 1.1 I see this message

Migrating DHCP configurations for FD >= 1.0.17
There are 1 DHCP configurations in the LDAP
The following are not in the DHCP branch (ou=dhcp):
cn=dhcp,cn=test,ou=servers,ou=systems,dc=labo,dc=opensides,dc=be
Move these entries to the DHCP branch (ou=dhcp)? [Yes/No]?
yes
Could not add DHCP service on cn=test,ou=servers,ou=systems,dc=labo,dc=opensides,dc=be, LDAP error: Object class violation
You'll need to activate it yourself

And if I do --migrate-systems first I have this

Migrating your systems from FD < 1.1
Found no system using gotoWorkstation
The following systems are using the obsolete goServer objectClass:
cn=test,ou=servers,ou=systems,dc=labo,dc=opensides,dc=be
Migrate these entries to fdServer objectClass? [Yes/No]?
yes
cn=test+ipHostNumber=192.168.10.200,ou=servers,ou=systems,dc=labo,dc=opensides,dc=be: subordinate objects must be deleted first

Cheers.

(from redmine: written on 2017-04-24)

By Jonathan Swaelens on 2017-09-02T15:35:17 (imported from GitLab)

It's ok.

We need to do the next steps:

• Migrate DHCP
• Migrate Systems
• Activate the dhcp service with FusionDirectory.

Close issue

(from redmine: written on 2017-04-25)

By Jonathan Swaelens on 2017-09-02T15:35:17 (imported from GitLab)

closed

By Jonathan Swaelens on 2017-09-02T15:35:18 (imported from GitLab)

added Fixed label

By bmortier on 2018-09-24T14:24:35 (imported from GitLab)

added PJ1802-0188 label

removed Bugs label