3rd post 1 week no response -- Upgrade to 2.7 from 2.7dev.

N8LBV

I keep asking and it's not getting any response.
and it's not covered in the docs.
I am still after a week trying to determine if this should work or not?
It currently does not and I have posted about this with details an no responses other than an outside link that is not official where somebody got it to work.
Can somebody please let me know if this is a "supported" upgrade path or not?
Trying to determine if I should file a bug report or if this just totally is by design.
Seems that it should work and does not.
I am NOT complaining about no response in a week but I'm surprised it has not been responded to, or there is zero interest.
Please and thanks.

bmeeks

I would not be surprised if there were issues with making the move. I would say it depends on the exact "version" of 2.7dev installed on your system. If your 2.7dev is old enough, the in-place update might go fine.

If it were me, I would play it safe and simply save off the config.xml file and reinstall from a fresh install image of 2.7.0 CE.

Once you save off a config.xml of your current setup, you could also roll the dice and try an in-place upgrade from 2.7dev to 2.7.0 CE. Worst case you wipe and reinstall like my first suggestion if the in-place upgrade fails.

No matter which way you choose, the very first step is to grab a config.xml backup using the menu option under DIAGNOSTICS. Store that backup in a safe place on a different system (such as the PC you connect from to manage pfSense).

N8LBV

@bmeeks Thanks... I am still continuing to ask if this upgrade process should work.
I have a number of 2.7dev boxes on various dev versions. some older some newer.
none of them work and simply present the "Unable to check for updates"

This DID work before 2.7 stables was released meaning it would update to the latest dev version.
Now any of them will not do anything except present they are unable to update.

So again I am asking if this update path is supported and should it actually work.
Thanks!
Steve

bmeeks

@N8LBV said in 3rd post 1 week no response -- Upgrade to 2.7 from 2.7dev.:

So again I am asking if this update path is supported and should it actually work.

I would say "no" based on your lack of response to the initial thread.

While in the past it was a simple matter to update from DEV to RELEASE, this particular time appears different because pfSense is using some new code around the pkg utility's repos configuration. I don't believe it was intentional that an update from a 2.7dev version to RELEASE not work, but more likely a casualty of trying to make the update from CE to Plus less painful. And the problems appear to have been random. I am pretty sure I recall seeing some users that updated from DEV to RELEASE without issue. But others had no end of problems and resorted to a reinstall with a backup.

You can try searching through all the threads about 2.7 upgrades and try the various fixes using command-line arguments with either the pkg or pkg-static utilities, or you can save yourself a lot of time and trouble and just reinstall using an exported and saved config.xml. A reinstall is maybe 10 minutes tops. You can spend hours trying the other approaches. There are several weird ways in which the pkg utility can lose its mind and not see available upgrade paths properly.

N8LBV

@bmeeks Thanks for your ideas.
I have been planning on re-installs.
But really wanted to find a solid answer on if this was supported or is supposed to be supported first before drawing any conclusions that re-installation is the only route.

I am also wondering if I should files a bug report that it does not work.
It can't hurt - and then maybe I will get a hard "no" from the dev. team on this and have the answer.