FWIW, we're seeing issues upgrading from 23.09.1 to 24.03 via the CLI

eelza

As in the quoted thread, we're unable to upgrade any of our deployed Netgate devices on 23.09.1 to 24.03 via the command line. Running suggestions from the quoted thread leads to the same results (with pfSense+ packages referenced instead of CE packages of course).

We found the following though. First go to System > Update > Update Settings and switch the branch to 24.03, then trigger an update from the command line or via 13) Update from console option of the rc.initial menu. Then pfSense recognizes that 24.03 is available and will proceed with the upgrade.

What we don't know however is how to change the branch via the command line.

Any suggestions?

stephenw10

How exactly were they failing when you try to update from the GUI?

eelza

This post is deleted!

eelza

@stephenw10

We're able to do updates via the GUI. We're not able to trigger updates via the CLI.

stephenw10

You have to set the repo branch in the GUI but having dome that you should be able to run the upgrade at the CLI.

eelza

@stephenw10

Yes, we've been using that as a workaround, but is there a way to change branches via CLI?

stephenw10

There is no command to do it. The only way to do it would be to set the symlink manually.

Why are you trying to upgrade from the CLI only here?

eelza

@stephenw10

Our workflows heavily involve the command line. When given the option, we use the command line.

Also, we've successfully upgraded our pfSense devices many times via option 13 in the past.

stephenw10

Starting with 23.09.1 the upgrade process requires the user to opt into the new repo branch. Previously the system would automatically be move to 'latest stable' when it was released whichg allowed the update check to see and display it on the dashboard. But it also then exposed the system to all the new pkgs, many of which might not be compatible, and that has caused many problems.
Now the update check can see the current repo or all available repos so it will show an upgrade is available without already setting it as default. Much safer.
However it does require selecting the new branch in the gui.

Let me see what I can find here....

stephenw10

Opened a feature request to track it: https://redmine.pfsense.org/issues/15476

eelza

@stephenw10

That's excellent, thank you.

Also many thanks for the clarification regarding the CLI upgrade process. I agree that not switching branches automatically makes much more sense.