Cannot destroy a Volume whose host can't be reached

1

I had both a machine and a volume that couldn’t be reached.

! WARNING: There are active host issues affecting your app. Please check fly incidents hosts list or visit your app in Sign in to Your Account · Fly

I then created a new volume using the snapshot of the existing volume.
I destroyed the existing faulty machine (had to use --force) and renamed my mounts source to the newly created volume.
I deployed the app and everything works fine.
I am trying to destroy the previous faulty volume but it is not working
We don’t have a --force flag for volumes as we do on machines.

how do I destroy the unreachable volume, because I no longer need it.

3

I think this question may be a duplicate of this one:

4

it’s not; that question was a display bug (volumes stay in pending_destroy for 24h before being fully deleted, but they shouldn’t be shown in UI).

there isn’t currently a way to force delete volumes when a host is down, but I believe this is something we are working on adding.

5

Ah, I merely meant that “if you can’t delete a volume, then you should email the billing alias, and someone will fix it for you”. Apologies to the OP for not being clearer. Do let me know if my clarified advice is incorrect!

6

the billing address is for billing and account (such as login/trust score) inquiries, or places where we explicitly tell people contact it in API responses; but unfortunately not for this kind of issue.

1 Like
7

Right, apologies. I thought that this issue would count as an account issue, as it is something that unavoidably needs staff attention, even if the customer does not have a support contract. I shall update my mental notes.

1 Like
8

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