System is on a later version than the official release / Latest 0.18_1
-
I just applied patch 0.20 to my systems.
System rebooted afterwards and looking healthy again.
To be clear, the update is valid right? Not a cosmetic bug.
I thought the update was part of the new patch-system.
Thanks for the great work! -
There was an update for pfSense-upgrade, not the whole system. That update is good/legitimate.
-
Yeah.. since i pressed the update key in the notion of "nothing bad will happen", i was NOT expecting a full reboot…....
But well.. A couple of unhappy faces can be survived on a late friday i guess ::)
C
-
I've pushed a fix, it's on pfSense-upgrade 0.19.
pfSense-upgrade was considering its new version as a new firmware version. The issue is harmless and if you finish the upgrade nothing bad will happen.
Fix is on version 0.19. As soon as it's available it's safe to manually run 'pkg upgrade pfSense-upgrade' on console to go to latest verssion.
This issue is being tracked at https://redmine.pfsense.org/issues/7343
Sorry for the inconvenience
So the only way to fix this "issue" is to run pkg upgrade pfSense-upgrade from the console?
And it won't reboot the box ? -
Dunno about the console command, but running the upgrade on the web-gui updated AND rebooted… But showing "you are on the latest version" now, so its "good" :)
C
-
Mine also showed the "upgrade" to 0.20 and after pressing Confirm to let it do it, all is well reporting 2.3.3
The issue is that there are multiple "parts/packages" that make up "pfSense". Normally "parts" would be released along with actual new code that has a "proper" release version. So it would find the "main" version to display and say that "2.3.4" (for example) is available. But in this case there have been some changes/fixes to the bit called pfsense-upgrade going from about 0.16 to 0.20. The GUI code sees that 0.20<2.3.3 and thus says that the system 2.3.3 is newer than what it thinks is the release version (0.20).
I guess the code that parses the results of checking for upgrades needs to be smarter, and understand what pieces might come separately from the complete release. Then it needs to work out how to explain to the user that the "main" version is still 2.3.3 but that some component(s) upgrade is available.
-
The proper solution to this would be to present two types of updates to the user, one that is the "firmware" level update and one that only updates the individual packages within a version of the firmware.
-
I've pushed a fix, it's on pfSense-upgrade 0.19.
pfSense-upgrade was considering its new version as a new firmware version. The issue is harmless and if you finish the upgrade nothing bad will happen.
Fix is on version 0.19. As soon as it's available it's safe to manually run 'pkg upgrade pfSense-upgrade' on console to go to latest verssion.
This issue is being tracked at https://redmine.pfsense.org/issues/7343
Sorry for the inconvenience
So the only way to fix this "issue" is to run pkg upgrade pfSense-upgrade from the console?
And it won't reboot the box ?Using the GUI upgrade button will fix this, but will reboot.
Using the console 'pkg upgrade pfSense-upgrade' will fix this and does not require a reboot.
-
[2.3.3-RELEASE][root@somewhere.local]/root: pkg upgrade pfSense-upgrade Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-upgrade: 0.17 -> 0.20 [pfSense] Number of packages to be upgraded: 1 11 KiB to be downloaded. Proceed with this action? [y/N]: y Fetching pfSense-upgrade-0.20.txz: 100% 11 KiB 11.5kB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading pfSense-upgrade from 0.17 to 0.20... [1/1] Extracting pfSense-upgrade-0.20: 100% [2.3.3-RELEASE][root@somewhere.local]/root:
-
I'm seeing the same thing as well but am showing the latest base system as 0.20. Looked at the issue tracking and saw I'm not the only one who sees 0.20.
-
@nipstech:
I'm seeing the same thing as well but am showing the latest base system as 0.20. Looked at the issue tracking and saw I'm not the only one who sees 0.20.
That is true. Just do the suggested "upgrade". It will install that component that is v0.20. Then it will understand that the system as a whole is up-to-date running 2.3.3.
The logic there just needs to know that components might be needing an update, not the "system as a whole", and have a way to "explain" that to the user.
-
The system is on a later version than
the official release.Current Base System
2.3.3
Latest Base System
0.20
Confirm UpdateGoing to try the update
Strange, it just fixed itself before I could run the update
The system is on the latest version. -
If you don't have console access just go to Diagnostics –> Command Prompt and in "Execute Shell Command" type
pkg upgrade --yes pfsense-upgrade
This will upgrade you from 0.17 to 0.20 without needing console access or to reboot.
-
Thanks all. I too was caught by this and in System/Update seeing current base system 2.3.3, latest base system .20. After reading the posts here, got the confidence to hit the confirm button, let it do it's thing, it rebooted, and now I'm back up and working along with showing 2.3.3 and system is on the latest version.
-
"System rebooted afterwards"
You mean you rebooted - that update pfsense-upgrade wouldn't cause a reboot.
-
I've pushed a fix, it's on pfSense-upgrade 0.19.
pfSense-upgrade was considering its new version as a new firmware version. The issue is harmless and if you finish the upgrade nothing bad will happen.
Fix is on version 0.19. As soon as it's available it's safe to manually run 'pkg upgrade pfSense-upgrade' on console to go to latest verssion.
This issue is being tracked at https://redmine.pfsense.org/issues/7343
Sorry for the inconvenience
So the only way to fix this "issue" is to run pkg upgrade pfSense-upgrade from the console?
And it won't reboot the box ?Using the GUI upgrade button will fix this, but will reboot.
Using the console 'pkg upgrade pfSense-upgrade' will fix this and does not require a reboot.
The console command worked for me. It did not require a reboot, as you said.
-
fixed in 2.3.3_p1
-
I'm getting this again, but it may be user-induced (by me). In the GUI, out of curiosity I changed the update branch to the Development and Nightly (2.4) branches and Saved but never actually upgraded. Instead I changed the setting back to the Stable branch.
I'm now getting the "System is on a later version…" error again. I've also done 1) Click Stable branch and "Save" again, and 2) Manually rebooted.
GUI still showing:
Current Base System
2.3.3_1Latest Base System
2.3.3.r.20170215.0027Doing pfSense-upgrade -c -d gives me:
Updating repositories metadata…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Your system is up to date^ So obviously everything is good on the back end, but the GUI thinks I'm ahead a version. Same with the GUI "Installed Packages" widget on the Dashboard: lots of exclamation marks "!" next to packages but when I drill down in "System / Package Manager / Installed Packages" everything is perfect.
This is all cosmetic, so I'm cool with waiting until the next stable patch but thought I'd report it.
Edited to Add:
Steps to Reproduce:
1) Start with a stable system on 2.3.3_p1 RELEASE.
2) Go to "System / Update / Update Settings" and change from Stable branch to Development Snapshots branch. Save.
3) Go to Dashboard and see that a new version is available.
4) Go to "System / Update / Update Settings" and change from Development Snapshots branch to Next Major Version branch. Save.
5) Go to Dashboard and see that a new version is available.
6) Decide you're done playing and go to "System / Update / Update Settings" and change from Next Major Version branch back to Stable branch. Save.
7) Go to Dashboard and observe error message that you're ahead a version. -
Anyone?
-
Hopefully the screenshots will help garner an answer. How would I fix this?
