Project

General

Profile

Actions

Bug #9071

closed

Package restore after fresh install can fail, claiming packages do not exist

Added by Jim Pingle about 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Category:
Package System
Target version:
Start date:
10/26/2018
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4
Affected Architecture:
All

Description

Tested on a fresh SG-1000 and SG-3100 after a recovery install and then config restore. In both cases, no packages were restored. Instead, the GUI showed the following notices:

Package acme does not exist in current pfSense version and it has been removed. @ 2018-10-26 09:24:13
Package nmap does not exist in current pfSense version and it has been removed. @ 2018-10-26 09:24:14
Package sudo does not exist in current pfSense version and it has been removed. @ 2018-10-26 09:24:15
Package System_Patches does not exist in current pfSense version and it has been removed. @ 2018-10-26 09:24:16
Package Shellcmd does not exist in current pfSense version and it has been removed. @ 2018-10-26 09:24:17
Package openvpn-client-export does not exist in current pfSense version and it has been removed. @ 2018-10-26 09:24:18
Package reinstall process finished successfully @ 2018-10-26 09:24:22

At which point I could go to System > Packages, Available Packages tab and see them all and install them manually.

It seems to happen only if the firewall doesn't get a chance to check for updates or otherwise fetch the package metadata before restoring. I tried again and made sure to let it check for updates before restore and then it did work. Seems like something that routine should be doing on its own, however.

Could be another race similar to #9045

Actions

Also available in: Atom PDF