I’ve had the same issue once after the upgrade process stalled and I had to rebuild - the “Upgrading…” status didn’t clear until I hit the “Reset Upgrade” button and then everything cleared up (no actual reset process seemed to take place, it just cleared the “phantom upgrade”, so to speak).
Would advise caution / checking with folks more knowledgeable about the system before trying this, though.
Had you started an upgrade in the web side before you did it on the command line? I’m just trying to understand how the flag got stuck in that position.
The git-reset looked like it had a Lot of files to change for being just 52 commits behind, and it had to bundle a lot of stuff… took about 3x longer than expected.
However, it made it through Ok.
I guess all that’s left to do here is have a rebuild clear any “currently upgrading” flag.
heh, clicking buttons in the UI the team built isn’t really gambling… I just didn’t see that because I didn’t think the “busy upgrading” button was clickable.
The underlying issue is that, after a failed rebuild (no disk space in my case) a full rebuild didn’t clear the flag.
I think once that’s accounted for, we’re good here.