You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently upgraded an application to kamal 2.4.0 and got this when running kamal setup:
Releasing the deploy lock...
Finished all in 69.8 seconds
ERROR (RuntimeError): Exception while executing on host app0.schmit.net: kamal-proxy version v0.8.1 is too old, run `kamal proxy reboot` in order to update to at least v0.8.4
Error: Process completed with exit code 1.
I use kamal setup so if I add nodes then the CI job will provision them if they require it and then it will call deploy anyway. I wish there was an option to have kamal itself run kamal proxy reboot if the proxy was upgraded and needs to be rebooted, and then perhaps kamal could continue with re-running deploy. I was considering trying something like my CI job doing kamal setup || kamal proxy reboot || kamal deploy but that seems hacky as setup could fail for a number of different reasons in which case I don't want to run proxy reboot and deploy.
Would such a feature (where kamal detects that the proxy needs to be rebooted and there is a CLI option to auto-reboot the proxy if needed) be accepted by the maintainers of this project were I to submit a PR?
The text was updated successfully, but these errors were encountered:
I recently upgraded an application to kamal 2.4.0 and got this when running
kamal setup
:I use
kamal setup
so if I add nodes then the CI job will provision them if they require it and then it will calldeploy
anyway. I wish there was an option to have kamal itself runkamal proxy reboot
if the proxy was upgraded and needs to be rebooted, and then perhaps kamal could continue with re-running deploy. I was considering trying something like my CI job doingkamal setup || kamal proxy reboot || kamal deploy
but that seems hacky assetup
could fail for a number of different reasons in which case I don't want to runproxy reboot
anddeploy
.Would such a feature (where kamal detects that the proxy needs to be rebooted and there is a CLI option to auto-reboot the proxy if needed) be accepted by the maintainers of this project were I to submit a PR?
The text was updated successfully, but these errors were encountered: