Bug #7963
closed
Unable to upgrade pfSense v2.3.4-RELEASE to v2.3.4-RELEASE-p1 via web admin site. Clicking 'y' on console continues upgrade successfully.
0%
Description
When I trigger an upgrade via the web console it hangs stating:
Downloading upgrade packages...
I left it for a while and decided to see what the console was saying. It reported:
Reboot Required.
Proceed with upgrade? (y/N)
When I clicked 'y', the console reported that the upgrade started and completed successfully.
Returning back to the web console, whilst the text box mirrored the text shown on the console detailing the successful upgrade process, the status bar (underneath System / Update / System Update) states: "System update failed!" ... which it clearly did not.
pfSense rebooted after the upgrade and successfully shows the updated release of 2.3.4-RELEASE-p1.
Updated by Jim Pingle about 8 years ago
- Status changed from New to Feedback
Be sure to go to System > Update, Update Settings tab. Set the branch to Security/Errata Only and then try again.
Updated by Steve Tanti about 8 years ago
Jim Pingle wrote:
Be sure to go to System > Update, Update Settings tab. Set the branch to Security/Errata Only and then try again.
Hi Jim,
I understand what you're asking, but I don't think the version I'm upgrading to is the issue.
The console is expecting a 'y/n' answer regarding the required reboot before the upgrade process begins. The web console is not automating/skipping this question.
Whilst I don't have access to future full releases, I suspect this will occur whether or not it's a 'p' update or a full release update being applied.
Updated by Steve Tanti about 8 years ago
Steve Tanti wrote:
Jim Pingle wrote:
Be sure to go to System > Update, Update Settings tab. Set the branch to Security/Errata Only and then try again.
Hi Jim,
I understand what you're asking, but I don't think the version I'm upgrading to is the issue.The console is expecting a 'y/n' answer regarding the required reboot before the upgrade process begins. The web console is not automating/skipping this question.
Whilst I don't have access to future full releases, I suspect this will occur whether or not it's a 'p' update or a full release update being applied.
Ok, it looks like something was fixed in the 2.3.4_p1 update as it's now showing v2.4.0 is available. I'm upgrading that now and it looks to be running unattended when initiated via the web admin console.
Updated by Jim Pingle about 8 years ago
- Status changed from Feedback to Not a Bug
- Affected Version deleted (
2.3.4)