This is all fine, and I can upgrade Discourse fine by rebuilding the app, so Discourse is working again. I don’t need help upgrading - this isn’t what the topic is about (which is why it’s not a support request, but a bug report)
Notice after an upgrade fail from
2ad7564 (as highlighted in the first post) leaves docker manager in a broken state, providing incorrect information.
What has happened:
- Docker manager has
git reset --hard from
- Rake tasks have failed post
git reset, and we’re stuck in a lobotomised state
Problems with Docker manager:
- “discourse (
1a31eb1)” being displayed is incorrect. It was the last commit that we were on before upgrading, but we’re actually on
2ad7564 without rake tasks performed
- Likewise, docker manager displays ‘0 new commits’. This is actually correct because we are on
2ad7564, but the display message is wrong (we have failed in upgrading, whereas the rest of this section is suggestive of ‘updates available’)
- When selecting ‘Upgrade to the Latest Version’, we are presented with a screen that shows half the information from the old broken upgrade, plus a button to start upgrading, despite the progress bar already being partly progressed.
In conclusion, as a user it is not clear from these screens that an upgrade has previously failed, no options are provided to rectify the situation (such as reverting the the last known working commit), and the information that is provided is inconsistent with the current state of discourse.