[DHCP] after migration from .16 to .17 there previous configurations are not migrated to new one automatically.
[DHCP] after migration from .16 to .17 there previous configurations are not migrated to new one automatically.
After migration there is no any definitions in DHCP section which should point to previous DHCP configurations.
Also when I add manually new options in DHCP section, after browsing with Apache Directory Studio I saw that on baseDN are created those options with DN = cn=optionname. Is it better to be like for DNS plugin? For DNS plugi there is ou=dns and inside are all zones. For DHCP options also should be stored in for example ou=dhcp for better management.
Thanks, Aleksandar
(from redmine: issue id 5249, created on 2016-11-17, closed on 2017-01-02)
- Relations:
- relates #5295 (closed)
- Custom Fields:
- Bug in version: 1.0.17
Activity
UPDATE:
My DHCP configurations are in departments. I found that DHCP is migrated to ou=dhcp,ou=DEPARTMENT so seems like it is migrated to good place but it is not shown in DHCP list until I am click on "Search in subtrees". Then I can see DHCP lines but when I try to edit some of them "Global Options" I am receiving error:
You have no permission to move the object: cn=dhcp,ou=dhcp,ou=KTNC,dc=emisia,dc=net
Previously I had 2 servers with DHCP service each (for 2 departments). After migration I have 2 new DN for that services: cn=dhcp,ou=dhcp,ou=KTNC,dc=emisia,dc=net cn=dhcp,ou=dhcp,ou=ZEP,dc=emisia,dc=net
And when I try to edit Global Options for any of them I got mentioned error with changed ou about department. And also I can not see them in list until I am check Search in subtrees
(from redmine: written on 2016-11-18)
UPDATE 2: When I renamed CNs and moved both to base DN so my configurations are: cn=ktnc,dc=emisia,dc=net cn=zep,dc=emisia,dc=net
Everything seems to work. I can see configs in DHCP list and can edit Global Options without any error. So migration does not works well. PS: New DHCP configuration is stored on baseDN too. For example I have created cn=test and DN is: cn=test,dc=emisia,dc=net
(from redmine: written on 2016-11-18)
UPDATE 3:
I was very interested to see where is the problem and finally I find it.
By default FD DHCP default DN is ou=dhcp (it can be placed on baseDN or in departments). But FD DHCP plugin when you create new DHCP option it is placed ALWAYS on baseDN and outside of ou=dhcp. To be worst FD doesn't even looking in ou=dhcp so if you want to be able to see options you must check Search in subtrees.
Also migration performing moving to ou=dhcp and that is the reason why you dont see in DHCP section your options because they are in ou=dhcp and FD doesn't looking in that place (only on baseDN).
That is all from me. Now you can figure whole picture and fix DHCP plugin.
(from redmine: written on 2016-11-18)
Hi,
I have edited and saved but it wont shown in LDAP until I have make changes like ou=dhcpp and save and make changes again back to ou=dhcp and save. After that I am seeing in fdDhcpRDN ou=dhcp
Benoit MORTIER wrote:
hello,
did you open the fusiondirectory configuration plugin / edit /save and check the the fdDhcpRDN is saved into you fusiondirectory configuration object
Cheers
(from redmine: written on 2016-11-21)
It sounds like the problem was clearly that your dhcpRDN was empty to FD for some time, so it thought you wanted DHCP sections to be in the root and it messed things up. If you put ou=dhcp in this RDN and save the config, and then open/save the configuration it should move them to the right place I expect.
The default value should have been inserted automatically but maybe something happened like you opened FD after update but before updating the plugin schemas so it failed to put the value? Not sure here. But it’s always safer if you open/save the config after a big update.
Do you have any problem or bug left now that your configuration contains the right RDN?
(from redmine: written on 2016-12-06)
Finally I have test instance for upgrading purposes :) At this moment my production is not upgraded, but everything I described was on test instance. So after correct RDN everything works fine, but I need manually to rename (in LDAP) dhcp CN's. For both of them there was cn=dhcp so I am seeing the same name for both DHCP's in drop down and I cant find which one is correct when I select it. So I made changes manually in LDAP and now it is OK. I am still testing the rest of FD.
Côme Chilliet wrote:
It sounds like the problem was clearly that your dhcpRDN was empty to FD for some time, so it thought you wanted DHCP sections to be in the root and it messed things up. If you put ou=dhcp in this RDN and save the config, and then open/save the configuration it should move them to the right place I expect.
The default value should have been inserted automatically but maybe something happened like you opened FD after update but before updating the plugin schemas so it failed to put the value? Not sure here. But it’s always safer if you open/save the config after a big update.
Do you have any problem or bug left now that your configuration contains the right RDN?
(from redmine: written on 2016-12-06)
-
Aleksandar Spasojevic wrote:
Finally I have test instance for upgrading purposes :) At this moment my production is not upgraded, but everything I described was on test instance. So after correct RDN everything works fine, but I need manually to rename (in LDAP) dhcp CN's. For both of them there was cn=dhcp so I am seeing the same name for both DHCP's in drop down and I cant find which one is correct when I select it. So I made changes manually in LDAP and now it is OK. I am still testing the rest of FD.
Did you try fusiondirectory-setup --migrate-dhcp ?
(from redmine: written on 2016-12-12)
Whole issue is with tried fusiondirectory-setup --migrate-dhcp at 1st place. If you asked did I tried it after correct RDN then yes too. After migration, I got in both departments in ou=dhcp dhcp configurations with the same name cn=dhcp That mean I need to change name cn=dhcp to something like cn=ktnc and cn=dtp to be able to see differences in DHCP section. That is not able to rename from FD and I did it directly by editing LDAP with Apache Directory Studio.
Côme Chilliet wrote:
Aleksandar Spasojevic wrote:
Finally I have test instance for upgrading purposes :) At this moment my production is not upgraded, but everything I described was on test instance. So after correct RDN everything works fine, but I need manually to rename (in LDAP) dhcp CN's. For both of them there was cn=dhcp so I am seeing the same name for both DHCP's in drop down and I cant find which one is correct when I select it. So I made changes manually in LDAP and now it is OK. I am still testing the rest of FD.
Did you try fusiondirectory-setup --migrate-dhcp ?
(from redmine: written on 2016-12-13)
added Fixed label
