Project

General

Profile

Actions

Regression #14436

closed

Upgrades from 23.05-RC/beta/dev fail server authentication

Added by Steve Wheeler over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Upgrade
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Release Notes:
Force Exclusion
Affected Plus Version:
23.05
Affected Architecture:
All

Description

Upgrades from earlier 23.05 versions can fail due to the configured branch no longer existing and server cert from that not matching the dynamically passed repo.

Similar to this: https://redmine.pfsense.org/issues/14137


Files

Actions #1

Updated by Luiz Souza over 2 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Fixed in the latest pfSense-upgrade package (1.0_67 for 23.05).

Actions #2

Updated by Jordan G over 2 years ago

Following a reboot on 8200 (which previously had gotten the latest pfSense-repoc, pfSense-upgrade; could pull, install and update packages), switching to the 23.09 branch and immediately back causes SSL errors when attempting to use pkg/pkg-static. Using "pkg-static upgrade -fy pfSense-repoc" allowed me to get things working again. I'll test rebooting again, to see if the condition returns but it's saying same versions are being installed/repaired.

Jun 10 14:49:10     pkg-static     79023     pfSense-repoc reinstalled: 20230605 -> 20230605
Jun 10 14:44:08     pkg-static     82697     pfSense-upgrade reinstalled: 1.0_67 -> 1.0_67
Jun 10 14:44:08     pkg-static     82697     pkg reinstalled: 1.19.1_1 -> 1.19.1_1
Jun 10 14:44:08     pkg-static     82697     pfSense-repo reinstalled: 23.05 -> 23.05
Actions #3

Updated by Jordan G over 2 years ago

this may have been from logging in as someone other than admin? don't seem to be able to replicate what I saw previously after running above commands...

Actions #4

Updated by Jordan G over 2 years ago

Still unable to hit this again when switching update branch or add/removing packages. Lets verify what branches should be visible on which versions to prevent any issues if set incorrectly.

Actions #5

Updated by Jordan G over 2 years ago

seeing some different choices in the branch selection just when cycling

Actions #6

Updated by Jim Pingle over 2 years ago

  • Tracker changed from Bug to Regression
  • Release Notes changed from Default to Force Exclusion
Actions #7

Updated by Jim Pingle over 2 years ago

  • Status changed from Feedback to Closed
  • Target version deleted (23.09)

This was fixed before 23.05 released.

Actions

Also available in: Atom PDF