pfSense » pfSense Plus

Are you able to replicate this reliably? If so, please detail the steps to do so.

now that it has this new boot environment '0' if i try to edit it, it makes a new boot environment. Each time.
however, the new ones with proper names CAN be deleted. its just the one labeled '0' that cannot be deleted and gives that error message.

to get the initial issue;

what i did; i didnt read the limitation of what characters could be used, and used a "-" instead of the "_" as part of the name
i dont remember the name i used exactly, but it tossed the name i used, gave me the error i posted above, and just created it with "0" anyway
just tried it again with a couple combinations but i didnt duplicate it. would the config file help debug it or ?

did some more trials, and found if i just use the date as 20230306 it does it.
named it 20230306, the other day i named it that date of 20230304
clone from default
description was "Everything works, dmz zone". the other day it was "Everything works after update"

this time it created an environment labeled "1". so i guess it is just going to increment for these rogue named environments.
it also cannot be erased, getting the same error 3

more experimentation
if i create a new environment with the same name as the old damaged ones (now 0 or 1) it creates a new one with the next sequential number, in my case "2". so i have three environments that cannot be deleted via the gui.

The patch works well. I'm not hitting any of the problems I encountered previously. It only applies to the currently active boot environment so if you like to keep multiple available, you will need to boot each environment (including the auto_ created environments made before a pfSense upgrade) and apply the patch from within each one.

i installed the patch.
it renamed the two broken boot environments with the name i originally gave them, swapping it for the '0' or '1' name it was giving me
.
but when i go to erase them, it wont. now i get an error 'unable to delete boot environment '20230305', Error 21"

so progress since the names are now correct, but not quite fixed yet. and a different error number

more testing; i found that although the name is now correct, if i create a new clone off one of the 'broken' environments, it wont let me erase the original.
but if i erase the new/cloned one first, then i can erase the original/faulty environment. This is exactly what truenas had a couple years ago.

so im not sure yet if its entirely fixed. i will poke around with it tomorrow for a bit. for now i do have the faulty/now renamed ones deleted, and everything else works, so perhaps it was just a remnant from the broken names?

just want to be precise so you dont spend time on this if you dont have to;

the patch fixed the issue regarding naming, BUT i had boot environments that were created after those damaged(?) environments and it wasnt allowing me to erase the original issue boot environments (the ones the patch renamed properly).

but when i deleted those boot environments that were created after the damaged two, it allowed me to delete those original ones as well.

now it works ok. and i havent seen any issues post those deletions

so it may be done, since the patch fixed the improper naming issue etc.

fyi.

OK, it may still be worth a quick look to see if we can make that smoother in case users are stuck with the problem environments created before the patch. But if what we have is good enough then we can close this out.