I think I may have messed things up royally with
epic-stack-template. It’s a bit of a unique project since it doesn’t have users and I actually would prefer the volumes to not be persistent because I make changes to the database schema and I actually don’t want to do migrations since it’s a template anyway.
Anyway, I needed to make a change to the database schema and so I went to delete the volume and it wouldn’t let me. So then I noticed the app was still on v1 so I followed the migration process and it somehow created two more volumes and ended up failing. I deleted all the volumes and tried again. It then said I needed a new volume so I made a new one and tried again. That time it worked (so I think I’m on v2 now), but now I can’t deploy anymore. I get the following error:
Error: creating a new machine in group 'app' requires an unattached 'data' volume. Create it with `fly volume create data`
But I definitely have a volume by that name:
$ fly vol list ID STATE NAME SIZE REGION ZONE ENCRYPTED ATTACHED VM CREATED AT vol_xme149km176vowpl created data 1GB sjc 514a true b6e02481 30 minutes ago
Here’s my status:
$ fly status App Name = epic-stack-template Owner = personal Version = 121 Status = suspended Hostname = epic-stack-template.fly.dev Platform = detached Deployment Status ID = 78a86d05-04e1-940c-e1c0-21ff128e6bd4 Version = v121 Status = successful Description = Deployment completed successfully Instances = 1 desired, 1 placed, 1 healthy, 0 unhealthy Instances ID PROCESS VERSION REGION DESIRED STATUS HEALTH CHECKS RESTARTS CREATED b6e02481 app 121 sjc run running 2 total, 2 passing 0 10m23s ago
It also says my platform is detached and my status is suspended. So I’m not sure what I’m doing wrong now… Like I said. I think I really messed it up.