-
-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CHT Upgrade failing in docker helper 4.x #9235
Comments
Also found on the forum: https://forum.communityhealthtoolkit.org/t/error-while-updating-cht-from-4-5-to-4-9/3766 |
Upgrades should work! I have done this many times in the past and just now deployed a Here's a list of services running for my test upgrade just now:
so, this ticket is great to capture that upgrades at some point stopped working in helper. |
I wonder if this is still the case. Any updates on this? |
I tried this now in
However, I faced this issue on version CHT 4.6.0. So, I tried creating a Here are the logs:
|
Nice. Can we close this then? |
I'm not sure. On one hand, the upgrade is working but not of the exact version from which the issue was raised and the other is the reported version cannot be reached at the moment. |
im not sure what you mean by "reported version cannot be reached". if this is related to a specific version, we should at least change the issue title and mark it as won't fix (ancient) and close it. there's no point in keeping issues that we won't fix open. |
Sorry, I re-read your whole message. |
I am closing this as the upgrading is now working. Check comment. |
A new ticket has been created for the above mentioned issue. #9676 |
Hrm - I just installed version
so...maybe worth re-opening this ticket? |
Ok - not sure what was going on there with my past comment, but I tried a clean install of Guessing some docker detritus, I removed all containers ( This ticket is good to keep closed I think. |
Describe the bug
I tried upgrading a 4.x CHT docker helper instance of CHT version 4.6.0 to 4.9.0 and the upgrade failed. The browser shows the
502 Bad Gateway
page whereas the containers have been stopped if you look into the terminal.To Reproduce
Steps to reproduce the behavior:
Environment
Additional context
I'm not sure which logs to put here so I haven't put anything. Please request the necessary information as required.
The text was updated successfully, but these errors were encountered: