Bug #8457
closedPackages do not remove on factory default
Added by Anonymous over 6 years ago. Updated over 6 years ago.
100%
Description
Install 2.4.2 CE. Upgrade to latest 2.4.4 snap. Install Squid. Factory Default the appliance. The package will remain.
Tested on 2.4.4.a.20180412.1121, gitsync'd to master, using the WebGUI and Console options to factory default.
Files
12-04-2018_15_34_02.png (38.4 KB) 12-04-2018_15_34_02.png | Anonymous, 04/12/2018 02:37 PM | ||
Screenshot from 2018-05-05 11-30-51.png (22.9 KB) Screenshot from 2018-05-05 11-30-51.png | status menu, no suricata | Chris Macmahon, 05/05/2018 10:32 AM | |
05-05-2018_15_08_09.png (60.5 KB) 05-05-2018_15_08_09.png | Packages still listed in Services, after the Factory Default reboot. | Anonymous, 05/05/2018 02:49 PM | |
09-06-2018_15_59_47.png (41.7 KB) 09-06-2018_15_59_47.png | screenshot 1 | Anonymous, 06/09/2018 03:22 PM | |
09-06-2018_15_59_57.png (16.1 KB) 09-06-2018_15_59_57.png | screenshot 2 | Anonymous, 06/09/2018 03:22 PM | |
09-06-2018_16_15_04.png (12.2 KB) 09-06-2018_16_15_04.png | screenshot 3 | Anonymous, 06/09/2018 03:22 PM | |
09-06-2018_16_15_15.png (18.3 KB) 09-06-2018_16_15_15.png | screenshot 4 | Anonymous, 06/09/2018 03:22 PM | |
acme-install-log-before-reset.log (1.65 KB) acme-install-log-before-reset.log | Anonymous, 06/09/2018 03:23 PM |
Updated by Chris Macmahon over 6 years ago
Tested 2.4.4, hardware reset did not clear the packages like it did on 2.4.3.
Hardware reset worked on 2.4.3, but not 2.4.4
Updated by Anonymous over 6 years ago
- Target version set to 2.4.4
- Affected Version set to 2.4.3
- Affected Architecture All added
- Affected Architecture deleted (
)
Updated by Chris Macmahon over 6 years ago
also tested via menu option 4. the Packages I Installed (acme, Nut Ladvd) were not removed
Updated by Jim Thompson over 6 years ago
- Category set to Package System
- Assignee changed from Renato Botelho to Anonymous
Assigned to PM for future reassignment.
Updated by Chris Macmahon over 6 years ago
Adding notes: All packages are removed from the menu, but not removed from the system:
stunnel-5.44_1,1 SSL encryption wrapper for standard network daemons
sudo-1.8.22 Allow others to run commands as root
suricata-4.0.4 High Performance Network IDS, IPS and Security Monitoring engine
syslog-ng-3.14.1 Powerful syslogd replacement
talloc-2.1.11 Hierarchical pool based memory allocator
telegraf-1.6.1 Time-series data collect
Updated by Anonymous over 6 years ago
- File 05-05-2018_15_08_09.png 05-05-2018_15_08_09.png added
In a VM .. pfSense-CE-2.4.4-DEVELOPMENT-amd64-20180503-1839 installed, synced to master, setup wizard clicked through, Squid and SquidGuard installed .. then Factory Reset from the Diagnostics menu, after the reset and reboot, before clicking through the setup wizard, the packages remain listed under Services, visiting System > Package Manager > Installed Packages still lists the packages.
Updated by Anonymous over 6 years ago
On a SG-2440 .. pfSense-CE-memstick-ADI-2.4.3-RELEASE-amd64 installed, Branch set to Latest development snapshots and upgraded to 2.4.4.a.20180504.1639, setup wizard clicked through, Squid and SquidGuard installed .. then Factory Reset using the physical reset button, after the reset and reboot, before clicking through the setup wizard, the packages remain listed under Services, also System > Package Manager > Installed Packages still lists the packages.
Updated by Anonymous over 6 years ago
Just tried this on 2.4.3 Factory running on a SG-2440, using the hardware reset button the packages did not remove.
Updated by Jim Pingle over 6 years ago
- Assignee changed from Anonymous to Renato Botelho
Somehow pkg_delete_all() in pfSense upgrade is not getting any packages to iterate. The query looks OK and works when I run it, but in the script it gets nothing back.
If I change the _pkg call on line 908 to pkg-static directly, it works.
Updated by Renato Botelho over 6 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Fixed in pfSense-upgrade 0.44 (pfSense-2.4.x) and 0.27_11 (pfSense-2.3.x)
Updated by Jim Pingle over 6 years ago
- Status changed from Feedback to Resolved
Updated by Jim Pingle over 6 years ago
- Target version changed from 2.4.4 to 2.4.3-p1
Updated by Anonymous over 6 years ago
- File 09-06-2018_15_59_47.png 09-06-2018_15_59_47.png added
- File 09-06-2018_15_59_57.png 09-06-2018_15_59_57.png added
- File 09-06-2018_16_15_04.png 09-06-2018_16_15_04.png added
- File 09-06-2018_16_15_15.png 09-06-2018_16_15_15.png added
- File acme-install-log-before-reset.log acme-install-log-before-reset.log added
On SG-2440 2.4.4.a.20180609.0944, installed acme, performed hardware reset, the package appeared to be removed (shown in screenshot 1), there was "nopkg" under Installed packages (shown in screenshot 2) .. went to install acme and the only output was
"Please wait while the update system initializes"
after a while, I visited installed packages and it was there. Went to remove it and the only output was
"Please wait while the update system initializes" again, after a while went to available packages and it was there.
Reinstalled 2.4.4.a.20180609.0944, installed acme, performed Factory reset with WebGUI and after the reset the package looked like it had been removed (shown in screenshot 3) and was not shown in available packages ( shown in screenshot 4) but try to reinstall the package and the only output is "Package pfSense-pkg-acme is up to date
Success"
Then, if you go to Installed packages, the package is installed.
Also attached is the output from installing acme on a fresh stock system that has not been reset.
Updated by Anonymous over 6 years ago
On 2.4.4.a.20180705.0032 this behavior is still present:
"installed acme, performed Factory reset with WebGUI and after the reset the package looked like it had been removed ( shown in screenshot ) and was not shown in available packages ( shown in screenshot ) but try to reinstall the package and the only output is "Package pfSense-pkg-acme is up to date Success" Then, if you go to Installed packages, the package is installed."
Appears to need more work.
Updated by Anonymous over 6 years ago
Behavior described in last update appeared to be limited to acme ... created https://redmine.pfsense.org/issues/8623 to address that behavior separately. This issue appears to be resolved.