Missing postgres vm

We have a postgres app in dfw with two volumes and a scale count of 2. We recently restarted the app in an attempt to resolve this error:

Only one vm came back after restarting. It’s reporting as healthy and is working fine for us, but it’s the only vm that started up. We tried scaling the count down to 0 and back up to 2 and we are still only getting a single instance. volumes list shows two volumes with only one attached vm. What can we do to get a VM to start and attach to the second volume?

Our monitoring tab has been stuck in a weird state as well:

releases for the app indicates that release v22 succeeded with a count of 2, but the dashboard (screenshot above) is still suck on v20.

1 Like