Bug #15097
closed
Upgrade to 23.09.1 is not offered for 23.05.1
0%
Description
Since the release of 23.09.1, devices that upgrade to 23.05.1 from a previous version are unable to upgrade to 23.09.1 due to the symlink to the current repo not being present under /usr/local/etc/pkg/repos/pfSense.conf.
Currently users can workaround this problem by going to System --> Update --> Update Settings, clicking save without making any changes, and the symlink will be regenerated.
Here is the output of "pfSense-upgrade -d -c" immediately after upgrading to 23.05.1 with an affected system:
cp: /usr/local/etc/pkg/repos/pfSense.conf: No such file or directory
pkg-static: Unable to open '/usr/local/etc/pkg/repos//pfSense.conf':No such file or directory
Messages:
Your Netgate device has pfSense+ as part of your device purchase.
ERROR: It was not possible to determine pkg remote version
ERROR: It was not possible to determine pkg remote version
Updating repositories metadata...
pkg-static: Unable to open '/usr/local/etc/pkg/repos//pfSense.conf':No such file or directory
No active remote repositories configured.
ERROR: It was not possible to determine pfSense remote version
ERROR: It was not possible to determine pfSense-base remote version
ERROR: It was not possible to determine pfSense-kernel-pfSense remote version
Your system is up to date
Updated by Kris Phillips 5 months ago
Can confirm that this seems to consistently happen basically every time someone upgrades from 23.01 to 23.05.1.
Updated by Danilo Zrenjanin 5 months ago
- Status changed from New to Confirmed
Yeah, I can confirm this behavior on Netgate 6100.
cp: /usr/local/etc/pkg/repos/pfSense.conf: No such file or directory Messages: Your Netgate device has pfSense+ as part of your device purchase. ERROR: It was not possible to determine pkg remote version ERROR: It was not possible to determine pkg remote version >>> Updating repositories metadata... No active remote repositories configured. ERROR: It was not possible to determine pfSense remote version ERROR: It was not possible to determine pfSense-base remote version ERROR: It was not possible to determine pfSense-kernel-pfSense remote version Your system is up to date
The recommended workaround didn't help.
Currently users can workaround this problem by going to System --> Update --> Update Settings, clicking save without making any changes, and the symlink will be regenerated.
Updated by Kris Phillips 5 months ago
Danilo Zrenjanin wrote in #note-2:
Yeah, I can confirm this behavior on Netgate 6100.
[...]
The recommended workaround didn't help.
[...]
If, for whatever reason this doesn't work, flipping the branches from previous and stable will definitely resolve it.
Updated by Marcos M 5 months ago
- Subject changed from Repo Symlink Missing on 23.05.1 After 23.09.1 Repos Became Available to Upgrade to 23.09.1 is not offered for 23.05.1
- Status changed from Confirmed to Resolved
- Assignee set to Marcos M
- Release Notes changed from Default to Force Exclusion
- Affected Architecture amd64 added
- Affected Architecture deleted (
All)
The system link does exist:
[23.05.1-RELEASE][root@gw]/root: ls -lha /usr/local/etc/pkg/repos total 12 drwxr-xr-x 2 root wheel 512B Nov 7 18:19 . drwxr-xr-x 3 root wheel 512B Jun 27 2023 .. -rw-r--r-- 1 root wheel 26B Jun 27 2023 FreeBSD.conf lrwxr-xr-x 1 root wheel 60B Nov 7 18:19 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-23_09_rel.conf
However, the file it points to does not:
[23.05.1-RELEASE][root@gw]/root: ls -lha /usr/local/etc/pfSense/pkg/repos total 64 drwxr-xr-x 2 root wheel 1.0K Dec 29 13:58 . drwxr-xr-x 3 root wheel 512B Dec 29 13:58 .. -rw-r--r-- 1 root wheel 2.0K Dec 29 13:58 pfSense-repo-23_09_1_rel-cert.pem -rw-r--r-- 1 root wheel 3.2K Dec 29 13:58 pfSense-repo-23_09_1_rel-key.pem -rw-r--r-- 1 root wheel 16B Dec 29 13:58 pfSense-repo-23_09_1_rel.abi -rw-r--r-- 1 root wheel 17B Dec 29 13:58 pfSense-repo-23_09_1_rel.altabi -rw-r--r-- 1 root wheel 512B Dec 29 13:58 pfSense-repo-23_09_1_rel.conf -rw-r--r-- 1 root wheel 32B Dec 29 13:58 pfSense-repo-23_09_1_rel.descr -rw-r--r-- 1 root wheel 11B Dec 29 13:58 pfSense-repo-23_09_1_rel.name -rw-r--r-- 1 root wheel 2.0K Dec 29 13:58 pfSense-repo-stable-point-cert.pem -rw-r--r-- 1 root wheel 3.2K Dec 29 13:58 pfSense-repo-stable-point-key.pem -rw-r--r-- 1 root wheel 16B Dec 29 13:58 pfSense-repo-stable-point.abi -rw-r--r-- 1 root wheel 17B Dec 29 13:58 pfSense-repo-stable-point.altabi -rw-r--r-- 1 root wheel 512B Dec 29 13:58 pfSense-repo-stable-point.conf -rw-r--r-- 1 root wheel 31B Dec 29 13:58 pfSense-repo-stable-point.descr -rw-r--r-- 1 root wheel 12B Dec 29 13:58 pfSense-repo-stable-point.name
Additional logs:
[23.05.1-RELEASE][root@gw]/root: cat /usr/local/etc/pkg.conf ABI=FreeBSD:14:amd64 ALTABI=freebsd:14:x86:64 [23.05.1-RELEASE][root@gw]/root: pkg-static info | egrep 'pfSense-[^pSm]|pkg-[0-9]' pkg-static: Unable to open '/usr/local/etc/pkg/repos//pfSense.conf':No such file or directory pfSense-23.05.1 Meta package to install pfSense required ports pfSense-base-23.05.1 pfSense core files pfSense-boot-23.05.1 pfSense boot files pfSense-default-config-23.05.1 pfSense default config pfSense-kernel-pfSense-23.05.1 pfSense kernel (pfSense) pfSense-rc-23.05.1 pfSense rc script and rc.initial shell pfSense-repo-23.05.1 Setup pfSense pkg(8) repositories pfSense-repoc-20230605 pfSense dynamic repository client pfSense-upgrade-1.0_68 pfSense upgrade script pkg-1.20.8_2 Package manager [23.05.1-RELEASE][root@gw]/root: pfSense-upgrade -dc cp: /usr/local/etc/pkg/repos/pfSense.conf: No such file or directory pkg-static: Unable to open '/usr/local/etc/pkg/repos//pfSense.conf':No such file or directory ERROR: It was not possible to determine pkg remote version ERROR: It was not possible to determine pkg remote version >>> Updating repositories metadata... pkg-static: Unable to open '/usr/local/etc/pkg/repos//pfSense.conf':No such file or directory No active remote repositories configured. ERROR: It was not possible to determine pfSense remote version ERROR: It was not possible to determine pfSense-base remote version ERROR: It was not possible to determine pfSense-kernel-pfSense remote version Your system is up to date
The issue is due to a missing .default file, e.g. /usr/local/etc/pfSense/pkg/repos/pfSense-repo-23_09_1_rel.default. This is now fixed.
Updated by Tom L 5 months ago
Marcos M wrote in #note-4:
The issue is due to a missing
.defaultfile, e.g./usr/local/etc/pfSense/pkg/repos/pfSense-repo-23_09_1_rel.default. This is now fixed.
I am having the same issue - however - the recommendations above did not correct the issue. I see the note that it is fixed - how do I apply the fix? Creating an empty file to replace the .default doesn't solve the issue - I assumed there was more to it then that.
that said my error message did change -
pfSense-upgrade -d
failed to read the repo data.
failed to update the repository settings!!!
failed to update the repository settings!!!
I found a default file under /pfSense-tmp/ and the file just had a 1 in it - so I did try that as well but I get the same error. I have tried on both the current and previous repo settings as well.
update:
actually -- I have another issue - if I just run pkg - I get the following ...
pkg
ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg"
so - I think perhaps the upgrade to 23.09 partially failed someplace - so it would seem the original error is corrected by creating the .default ( or changing the repo version back and forth as stated above ) and I am back off on a search.
thank you
Updated by Clément PAPPALARDO 5 months ago
I had this issue on appliances while upgrading to 23.09 two branches back, where new version check was always failing.
my workaround was to go to System --> Update --> Update Settings, wait for red text indicates that it failed, change current branch from stable to other (which trigger a page refresh)
The check failed again, and then I put back Stable branch again, and that triggers a page refresh and it's now found and I can upgrade.
I had to do this at least on 4 appliances