Attempting to update to 23.01 DEVEL corrupts my pfSense installation
-
This post is deleted! -
@gabacho4 said in Attempting to update to 23.01 DEVEL corrupts my pfSense installation:
Notice now that the branches display differently as I have only:
Latest Stable Version (22.05)
DEVEL Version (devel)
PREVIOUS Version (22.01)Now when I select the 22.05 branch, the router checks for updates and returns "Unable to check for updates." Selecting the PREVIOUS version does the same and if I select the DEVEL version, it tells me that it is up to date:
Current base system: 22.05
Latest base ssytem: 22.05Exactly same thing just happened to me on a white box. So you are not losing your mind :-)
Oh well, I guess I wait for the beta and try that.
-
@rpotter28 sorry to hear it yet oh so happy to know I am not crazy. There’s indeed something broken.
-
@gabacho4 Had the same issues with a protectli. It was occuring around TDay so figured servers were on auto watch. Anyway, gave up after a couple shots.
-
@mynamehear I’ve tried probably no less than 20. Thank you for also confirming I’m not insane.
-
The silence from Netgate on this issue is making me uneasy honestly.
-
@gabacho4 said in Attempting to update to 23.01 DEVEL corrupts my pfSense installation:
The silence from Netgate on this issue is making me uneasy honestly.
Have you created a Redmine ticket for the issue? The Netgate folks do check in here from time to time, but for any software development team their Issue Reporting System (Redmine in this instance) is the go-to location for identifying bugs and tracking them to resolution.
I recognize your moniker as a long-time forum member, so you probably have the Redmine URL already. But just in case, here it is: https://redmine.pfsense.org/projects/pfsense.
-
@bmeeks I’ll do that. Had held off until others could duplicate the issue and that objective has been met. I’ll get a report submitted. Had hoped to get some sort of engagement from netgate but understand they are probably busy with trying to get 23.01 ready for release.
-
Sorry numerous issues in play.....
Your NDI looks good. It should pull the pkg repos from what I can see here.
Do you have a more complete upgrade log we can review? How far through the upgrade does it show that error?
Steve
-
@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...
