Restore issues: Apply Changes button missing, Save does not reboot
-
@SteveITS said in Restore issues: Apply Changes button missing, Save does not reboot:
Perhaps that is not a good idea to leave unused ones in the file, for future migration reasons.
Well it makes it easier to import into a device that has fewer interfaces certainly but you should still be able to remove unused interfaces. However I think that's what you were hitting, when you delete an interface it applies immediately and would also apply any other saved settings. That could easily lock you out.
-
@stephenw10 Yeah. I mean, I’ve done many restores over the last 15 years but this past week for every one that changed hardware I was like, “what just happened?”
Thinking about it all, it sounds like Save applies other changes such as IPs and passwords and maybe that is a separate bug, if those should apply after Apply Changes/reboot.
Also, per the above discussion, when changing out hardware with the same number of interfaces, then one would not add/delete any, and thus the Apply Changes button would never appear…? :) Maybe the page needs to detect when a dropdown value is changed, not just add/delete.
And/or the original banner text should say to “click Save, then click the Apply Changes button that will appear.”
-
@SteveITS said in Restore issues: Apply Changes button missing, Save does not reboot:
And/or the original banner text should say to “click Save, then click the Apply Changes button that will appear.”
This would also be more consistent with, say, firewall rule or alias edits.
-
It should present the existing config, which will be incorrect for the hardware, and allow you to change them and save that. Then the apply appears but you should have an oppotunity at that point to make any other changes needed before applying them which should then trigger the reboot.
There have always been edge cases here, the interface resignment cannot allow for all setups. If you have LAGGs and VLANs etc it's often easier to manually edit the config that try to add back all the interfaces and assign them without getting locked out. However I think there is a regression here.
-
@stephenw10
at least I’m not crazy :). Let me know if I can help. After swapping the routers I’m down to the 2100 being available but it is at the office currently. One of the configs may still be visible in a conversion ticket from me to TAC about two weeks ago. -
We converted it to the 2100?
-
@stephenw10 correct, and I used the same original config on the 6100s. It and its HA pair. The 2100 was a temp we put in service for a week when the backup died.
-
FWIW the (short) email chain with TAC doesn't have a ticket number but it was on June 25; Ryan's reply was 12:14 PM CDT. Subject "Config migration to 2100"
-
Circling back, I didn't see a Redmine yet so I created one: https://redmine.pfsense.org/issues/14591
-
I rediscovered this today restoring two 3100 configs to 2100s. Short version, clicking Save before clicking Apply does work. Clicking Apply first results in an inaccessible router (aside from console).
