fusiondirectory-setup should allow to migrate systems from 1.0.16 to 1.1

(from redmine: issue id 5178, created on 2016-10-06, closed on 2017-02-08)

• Relations:
  • copied_to #5474
• Changesets:
  • Revision 7bb234cd by Côme Chilliet on 2016-10-06T09:24:47.000Z:

Fixes #5178 Added --migrate-systems option to fusiondirectory-setup

• Revision 4702149c by Côme Chilliet on 2017-01-17T16:19:34.000Z:

Fixes #5178 Improved --migrate-systems option for fusiondirectory-setup

• Revision 6f92dd1c by Côme Chilliet on 2017-02-08T13:28:15.000Z:

Fixes #5178 Migrating gotoMode into fdMode

• Revision 5602e7f9 by Côme Chilliet on 2017-02-08T13:31:08.000Z:

Fixes #5178 Migrating gotoMode into fdMode

• Revision e742e087 by Côme Chilliet on 2017-04-10T15:03:03.000Z:

Fixes #5178 Removing argonautLdap2zoneAllowNotify from migrated servers

Option --migrate-systems was added to fusiondirectory-setup. It was not tested yet.

(from redmine: written on 2016-10-06)

By Côme Chilliet on 2017-09-02T15:33:39 (imported from GitLab)

Hello, I migrate my FusionDirectory 1.0.13 to 1.0.16-fixes first; I didn't had any deprecated so I upgrade to 1.1.

I have the following error error when I try to use --migrate-systems

structuralObjectClass 'GOhard' is OBSOLETE

Cheers.

(from redmine: written on 2016-10-28)

By Jonathan Swaelens on 2017-09-02T15:33:39 (imported from GitLab)

Tried a new way of migrating nodes, please test again.

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

By Côme Chilliet on 2017-09-02T15:33:39 (imported from GitLab)

Close issue

(from redmine: written on 2017-02-08)

By Jonathan Swaelens on 2017-09-02T15:33:39 (imported from GitLab)

closed

By Jonathan Swaelens on 2017-09-02T15:33:40 (imported from GitLab)

added Fixed label

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

removed Bugs label

added PJ1802-0188 label