Creating a new postgres: deployment does not complete

1

I’ve just tried to make a new postgres in syd but the deployment does not complete. It’s been stuck for about 20 minutes now:

fly pg create --name postgres-latency-testing --region syd
... etc ...
Save your credentials in a secure place, you won't be able to see them again!

Monitoring Deployment

v0 is being deployed

fly status shows no vms running. 0 placed:

fly status --app postgres-latency-testing
App
  Name     = postgres-latency-testing          
  Owner    =                             
  Version  = 0                                 
  Status   = pending                           
  Hostname = postgres-latency-testing.fly.dev  

Deployment Status
  ID          = 240c1246-e767-f6de-72fb-d181282f4198         
  Version     = v0                                           
  Status      = running                                      
  Description = Deployment is running                        
  Instances   = 1 desired, 0 placed, 0 healthy, 0 unhealthy  

Instances
ID	PROCESS	VERSION	REGION	DESIRED	STATUS	HEALTH CHECKS	RESTARTS	CREATED

So there are no vm IDs to debug.

fly logs is empty.

Interestingly I see a volume was created for it:

fly volumes list --app postgres-latency-testing
ID                  	STATE  	NAME   	SIZE	REGION	ZONE	ATTACHED VM	CREATED AT     
vol_mjn924o5pw2v03lq	created	pg_data	1GB 	syd   	af82	           	20 minutes ago

… so that bit worked. Just no vm. Weird!

Any known issues at the moment? When I created a database before it took seconds, so something is wrong. My commands seem correct, based on the docs.

Thanks!

2

We’re working on slow VM provisions in Sydney. We hadn’t considered it a status page worthy thing, but if you’re seeing it happen we should update the status page.

—edit—

Updated: Fly.io Status - Slow VM provisions in Sydney

1 Like
3

Ah … well that would explain it. Thanks @kurt

Ok … well the best thing for me may be to simply delete that app and volume and simply try a different region. Wasn’t sure where the problem was.

I assume deleting an app mid-deploy is ok. I’ve not tried that before!

4

Yes that’ll work just fine!