2.3.1_1 update?

Dude, no. Clicking on a link to see information on an upgrade is not bad form.

There was no upgrade button to click on, which is what triggered the original question.

@jdillard:

hitting the upgrade button before reading the official release announcement is bad form.

ah, I misunderstood what button you hit.

phil.davis

There is a bit of a Catch-22 in production releases. The release person needs to put all the release kits (patches, packages…) onto the live release servers and give it a bit of a test from some online systems, to double-check that all the needed release components are found in the right places.
During that time, there is a live release available online, but no release announcement (and maybe no release notes).

A workflow that helps could be:

Post the release notes
Post a notification that a release is in the process of being released, and for users not to upgrade just yet
Put all the live release materials on the various server(s)
Test some upgrades from the release server(s)
Change the notification to say that the release is officially available

esseebee

The first update (2.3_1) that pfSense offered didn't require a reboot and didn't mention anything about uninstalling packages first, etc. Does update 2.3.1_1 require us to uninistall packages first before updating to it? Or, is that just best practice for a new pfSense release (2.3.1)?

cmb

@jdillard:

@dennypage:

However, when I click on the update link

Y U NO READ THE RELEASE NOTES?!

Hey, leave Denny alone! :D

cmb

@phil.davis:

There is a bit of a Catch-22 in production releases. The release person needs to put all the release kits (patches, packages…) onto the live release servers and give it a bit of a test from some online systems, to double-check that all the needed release components are found in the right places.

There was a gap of about a half hour or so from the update showing available to all the platforms having all their files in place (most considerably less than that). The reason is the automatic copy from staging to production didn't completely work, so some of it had to be done manually. Since part of it did succeed, the version notification came up, but then it wasn't actually available to install yet. We already know what the issue is, should have it fixed tomorrow so that delay between showing the version available and it actually being available won't happen in the future.

JMac87

Can someone confirm whether or not this update requires a reboot? Many people have asked, yet no official answer has been given. Thanks!

EDIT: I took one for the team. A REBOOT IS REQUIRED. The kernel gets upgraded.

dev

I've installed this update today. I don't think it rebooted (unless it was automatic, I was away while it was upgrading), however the entire OS started behaving REALLY weird. My internet connection just stopped working for no reason, and I couldn't find a reason why. I've reset the system to factory settings, but like 2 hours later I could no access webconfigurator without an SSH tunnel (connection times out)

Maybe it's just me, but I'm really confused as to what's going on.

Fogl

@dennypage:

On the system dashboard for my SG units, it is showing "Version 2.3.1_1 is available." However, when I click on the update link, the system update page says 2.3.1 is "Up to date." Is there a 2.3.1_1 update?

I still have this problem on one pfSense box as of now. Will not let me update. Second pfSense box updated just fine. :o