Open andy-dean opened 6 years ago
From what I can see, self.vm_id
is probably None causing the assertion to fail. The root cause of the issue is that there is no documentation for vm_id
. Additionally, it appears that nixops
assumes that AWS APIs return an answer every single time, which is not the case.
If the size of your nixops deployment grows towards thousands of machines, the probability of a failed deployment will go to 1.
AWS APIs are rate limited, but there is nothing in nixops that tries to cope with failure. The automation in nixops seems to be limited currently, because of its many failure modes.
I occasionally get an error when running "nixops destroy" - probably 10-20% of the times I run "nixops destroy". When the error happens, I end up with a volume that is no longer attached to any EC2 instance.
Here's the command I use:
And here is the console output I see: