I was able to reproduce this. The client code hasn’t changed in a meaningful way. It looks like the problem is that a call to /admin/docker/upgrade is now throwing a 504 gateway timeout.
Our error handler then tells it to mark its state as “not upgrading”, which means when the message bus notification for complete comes through that it’s not marked as finished.
It seems to me the root cause here is the 504 timeout that we didn’t see before. I suspect some kind of proxy/rails change here. Maybe something in our docker image? @sam are you aware of anything or can maybe assign to dev ops?