Project

General

Profile

Bug #8208

Restoring a config in 2.4.2 with 2.3.X Security/Errata Only repo selected breaks PHP

Added by Paighton Bisconer over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Renato Botelho
Category:
Config upgrade
Target version:
2.4.3
Start date:
12/13/2017
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.4.2
Affected Architecture:

Description

After attempting to repair repos for a failed upgrade, config was exported from 2.3.4-P1 and imported to a fresh install of 2.4.2.

Console began spitting errors citing "/etc/inc/certs.inc line 44".

Cause was found to be 2.3.X Security Errata Only repo selected before config export.

"<pkg_repo_conf_path>/usr/local/share/pfSense/pkg/repos/pfSense-repo-legacy-23.conf</pkg_repo_conf_path>"

Setting repo to 2.4.X prevents the issue.

Associated revisions

Revision 747b31dc (diff)
Added by Renato Botelho about 1 year ago

Ticket #8208

When restoring backup, do not call pfSense-upgrade on boot

Revision 8552be10 (diff)
Added by Renato Botelho about 1 year ago

Ticket #8208

When restoring backup, set default pkg repository

Revision a55718c8 (diff)
Added by Renato Botelho about 1 year ago

Fix #8208

When restoring backup, delete packages not present in new config.xml

History

#1 Updated by Jim Thompson over 1 year ago

  • Assignee set to Renato Botelho

#2 Updated by Jim Pingle about 1 year ago

  • Target version changed from 2.4.3 to 2.4.4

#3 Updated by Jim Pingle about 1 year ago

  • Target version changed from 2.4.4 to 2.4.3

#4 Updated by Renato Botelho about 1 year ago

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

#5 Updated by Paighton Bisconer about 1 year ago

2.3.4 Config with 2.3.X Errata Repo restored to 2.4 systems will break.
2.3.4 Config with 2.4.X Repo restored to 2.4 works as expected.
2.4.2-p1 Config with 2.3.X Errata Repo restored to 2.4.3-DEV (Pre-8208 fix) will break.
2.3.4 or 2.4.2-p1 Config with 2.3.X Errata Repo restored to 2.4.3-DEV (Post 8208 fix 2.4.3.a.20180313.1628 or later) works as expected and the issue is resolved.

#6 Updated by Renato Botelho about 1 year ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF