Upgrade from 23.09.1 to 24.11 failed

Gertjan

kea - imho, starts to be ok when you've installed 24.11. Any versions before, do what the thousands of forum post already told you : stay with ISC.

Btw : You came from 2.7.2. I might be wrong, but if you want to fully exploit the ZFS system (Boot Environments) I would recommend you to install 'from scratch'.

SteveITS

@inferno480 you switch to Kea, it reboots, and you end up in an older boot environment? And does a normal reboot succeed?

stephenw10

Hmm, something odd there. A reboot should not be required to switch DHCP backends.

SteveITS

@stephenw10 I think OP is saying, it boots on its own after the crash. So, odder.

inferno480

sorry, I'll re-cap.

(FYI: This is amd64 / DIY hardware, not a Netgate appliance btw)

was initially running on 2.7.2 (with Kea DHCP, and already was using ZFS and boot environments) running fine ever since the fresh install with 2.7.2 CE.
decided I wanted to be on 2024.11, so I purchased a TAC Lite license, uninstalled all my packages, entered my registration code, backed up my configuration and upgraded to pfSense+
after the upgrade, the system was on pfSense+ 23.09.1 but was functioning fine (no errors or crash dumps) so I switched to the Current train and upgraded to 24.11
Upgrade went fine, the system automatically rebooted as part of the normal process. During the boot-up process, it posted the PHP error pertaining to the Kea DHCP settings and (I wish I had a cut'n pasteable or at least screenshot, but I don't) had a prompt stating the current boot environment (default) had failed and that it was going to revert back to the previous (23.09.1) boot environment after a period of time if I didn't press anything. I pressed Enter to acknowledge it and tell it to continue to revert to the previous boot env, but it was going to after a delay if I didn't press anything, I believe.
Made my original post where it was suggested to revert to ISC DHCP , so I did that and attempted the 24.11 upgrade again. The 24.11 upgrade went off without a hitch, and everything was functioning fine. I re-installed a couple of my packages [Avahi/pimd], and my configurations for them (even from 2.7.2) were seemingly preserved, which was nice.
Then I pushed my luck and thought "I wonder if I could switch this back over to Kea DHCP now..." and while it succeeded through the UI and everything was seemingly working, I decided to try a reboot "just to be sure".

Apparently during the boot-up process the same exact PHP error was encountered, but I did not get to the console in time to verify the same prompt about reverting back to the old boot message was there, but after a while it did in fact boot back to 23.09.1 all on its own without me interacting on the console at all.

At that point my settings were reverted back to ISC DHCP as well, so I re-did the 24.11 upgrade and left it at ISC DHCP for now (everything's working).

stephenw10

@inferno480 said in Upgrade from 23.09.1 to 24.11 failed:

was initially running on 2.7.2 (with Kea DHCP, and already was using ZFS and boot environments)

That could potentially be an issue. Since BEs are not supported in the GUI in CE I assume you created one at the CLI? It's possible the filesystem layout changes are not compatible.

Though that doesn't really fit the PHP error shown above. Do you have any DHCP6 static mappings?

inferno480

@stephenw10 Not sure, I don't really recall doing anything special to enable boot environments. Maybe it was created as part of the 23.09.1 update to pfSense+?

Yes, I did have one dhcpv6 static mapping ... here is what I tried tonight:

deleted my DHCPv6 static mapping
rebooted pfSense
after reboot completed, enabled Kea DHCP
all seemed well, rebooted again, then...

Same error on boot-up, and it auto-reverted to the 23.09.1 image and self-rebooted again. I was able to upgrade back to 24.11, keeping it set for ISC DHCP once again (my static DHCPv6 mapping is still showing as deleted, however).

This time I saved a screenshot:

Gertjan

@inferno480

I would go for the shell, and edit the /conf/config.xml file.

Search for <dhcpdv6> and in there, for every interface, remove the (or all) offending (example)

			<staticmap>
				<duid>00:01:00:01:21:28:c4:6d:80:ee:73:ce:85:9f</duid>
				<ipaddrv6>::cc</ipaddrv6>
				<hostname>epackferpar22</hostname>
				<descr><![CDATA[EPACKFERPAR22]]></descr>
				<filename></filename>
				<rootpath></rootpath>
			</staticmap>

or, for every network (like <lan>), add

			<earlydnsregpolicy>disable</earlydnsregpolicy>

save, and reboot.

inferno480

@Gertjan @stephenw10

Ok, I tried editing /conf/config.xml and removing the staticmapping for dhcpv6 manually (it was still in there!), I also added the earlydnsreg disable parameters. Rebooted (still on ISC), switched to Kea and rebooted and still got the same error. I sense a full reinstall in my future.

stephenw10

Yup I would reinstall clean to be sure at this point.