Attempting to update to 23.01 DEVEL corrupts my pfSense installation
-
@stephenw10 I’m away right now but can easily reinstall 22.05 over the now broken installation and reattempt the 23.01 upgrade. Can you tell me specifically what commands you need me to run or screenshots to grab so that I can provide it? Has anyone at netgate been able to reproduce this issue?
-
I would connect to the serial console and use option 13 at the menu to run the upgrade. Log the console output and should show everything we need to see.
-
@stephenw10 OK, fresh install of 22.05. Everything left at default; didn't even run the wizard. Go to Updates and first let it check for 22.05 updates. None. Set the repo to 23.01 and it tells me there is a build from today 29 Nov. Go into console and press 13 and here is what I get:
Enter an option: 13 >>> Creating automatic rollback boot environment... done. >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: .. done pfSense-core repository update completed. 15 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: .......... done Processing entries: .......... done pfSense repository update completed. 551 packages processed. All repositories are up to date. >>> Locking package pkg... done. >>> Upgrading pfSense-upgrade... done. >>> Unlocking package pkg... done. >>> Setting vital flag on pfSense-upgrade... done. cp: /usr/local/etc/pkg/repos/pfSense.conf: No such file or directory >>> 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. >>> Locking package pkg... done. >>> Upgrading pfSense-upgrade... failed.I have seen this message - /usr/local/etc/pkg/repos//pfSense.conf repeatedly.
From this point, my pkg config will be all screwed up as I've reported.
-
Ok, thanks. Testing....
-
@stephenw10 look forward to seeing your findings.
-
@stephenw10 It also choked on mine as well when going to option 13 in addition to the web cinfigurator. Package repos were missing and constant Unable to Checks. FWIW and I'm probably wrong it seemed moving up and down between 2.6 to 2.7 and of course 22.05 to 23.01 was potentially corrupting a file that does not get deleted on fresh reinstalls. Why I say this is I had to use disk management software in order to truly blow away the disk and get a clean install, once done all installs went as expected.
-
Ok I partially replicated that. Digging...
-
@stephenw10 are you able to explain what you saw/found? Based on what I see, there is something jacked up with whatever file/information is downloaded by the router when I switch to the 23.01 repo. For kicks, I tried another fresh install, then switched to 23.01 repo....after the router downloaded whatever it pulls back from Netgate, 23.01 changed to 22.09 and then it couldn't check for updates. I tried again, and then 22.09 just became DEVEL. And now the router is unable to check for updates regardless of the repo I set. But it all starts the instant I try to use the devel repo. I feel like, and strongly suspect, that there is a bad configuration in whatever Netgate's setup/file is.
-
Yeah, we found the problem. Devs are working on a solution now.
Yes, the updated pfSebse-upgrade script is essentially switching to the new pkg system from 23.01 before it's actually pulled in the required info to use it.
A fix should be incoming shortly.
Steve
-
@stephenw10 woohoo! I’m not a freaking lunatic! You’ve helped me save my sanity. Do you have an estimate when the fix might be live? I won’t hold your feet to the fire over it but just a ballpark idea.
-
I was digging into it last night myself. I simply commented out the code to confirm what was breaking but that's not a fix. The main developer on this was also working on it so it may be fixed already.
I'll reply here when I know more this morning.Steve
Edit: It's not fixed yet, waiting to hear more...
-
@stephenw10 ok will standby. I’m embarrassed to even think about the number of times I’ve reinstalled pfsense on that router over the last week as I’ve tried various combinations of ways to maybe get things to work.
-
@gabacho4 Ran into the same issue. Posting here for updates on the matter.
Ted Quade
-
@stephenw10 wanted to check in and see if you had any idea when a fix would be completed. At this point, it’s been at least 2 weeks since I was able to install or update a 23.01 development build. Doing so itches a personal interest of course, but it’s also enabled me to help find bugs - including this show stopping bug/regression - and test fixes. I’d love to get back at it but have no ability.
Is this the redmine entry?
-
No that's not the Redmine entry for this. Let me see if there's an update yet....
-
@stephenw10 that’d be great! Is there a redmine entry for this issue?
-
Only internally right now. Let me see...
-
Trying to upgrade from 22.09 -> 23.01.a.20221205.0600 failing:
ERROR: It was not possible to determine pkg remote version __RC=1 __REBOOT_AFTER=10 ERROR: It was not possible to determine pkg remote version __RC=1 __REBOOT_AFTER=10 >>> 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. >>> Locking package pkg... done. ERROR: It was not possible to determine pfSense-upgrade remote version >>> Unlocking package pkg... done. __RC=1 __REBOOT_AFTER=10 ERROR: It was not possible to determine pfSense-upgrade remote version __RC=1 __REBOOT_AFTER=10 >>> Upgrading pfSense-upgrade... failed. -
@cloudroot yeah that’s the same issue. Guess it still hasn’t been fixed.
-
Indeed, I'm still hitting it this morning. Bug link incoming....
