Rolling deployment sometimes leaves old version's machines

1

I just deployed my app with bluegreen deployment, there was an old machine running from 2 months ago in a different region, the deployment left that machine there in a stopped state, which has an older image version.

I tried making many requests to see if Fly would route requests to it, it seems it does, the machine was previously stopped and after some load it was running. Now i destroyed it.

This is very dangerous because different app versions are not guaranteed to work together well.

The app is called websocket-preview, the deployment with this issue is v116

1 Like
2

I previously thought that the machine creation date also meant that the machine had an image version of that date, this does not seem to be the case.

Also my deployment code was rolling instead of bluegreen

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.