Project

General

Profile

Actions
Copy link

Regression #14137

closed

pfSense Plus Upgrade repo data remains on the system after upgradng

Added by Steve Wheeler about 1 year ago. Updated 11 months ago.

Status:
Resolved
Priority:
High
Assignee:
Luiz Souza
Category:
Upgrade
Target version:
23.05
Start date:
Due date:
% Done:

100%

Estimated time:
Release Notes:
Default
Affected Plus Version:
23.01
Affected Architecture:
amd64

Description

After upgrading from CE to pfSense Plus the repo data used for that should be removed from the firewall leaving it using the Latest Stable branch, 23.01.

After switching the Upgrade repo to use the 23.01 branch this is no longer being completed expected.

The result of this is that the pkg system uses the Plus Upgrade cert and key after upgrading and once those expire it is no longer able to update:

DBG(1)[39712]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz with opts "i" 
pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Bad Request
Unable to update repository pfSense
Error updating repositories!

Packages do not show in the Package Manager.

Also see: https://redmine.netgate.com/issues/10335

To work around this issue:

  1. Set the selected update repo branch back to 23.01 (Latest Stable Version). Go to System > Update > Update Settings and save the branch. 23.01 is the only available branch.
  2. Manually remove the custom repo files using:
    rm /usr/local/share/pfSense/pkg/repos/pfSense-repo-custom.*

Files

clipboard-202303210806-70feo.png (47.5 KB) clipboard-202303210806-70feo.png aleksei prokofiev, 03/21/2023 12:06 AM
Actions
Copy link

Also available in: Atom PDF