You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had a deployment running EC2 Spot instance that some of them were destroyed because of lack of capacity on the AWS side. We then re-deployed using on-demand instances by setting ec2.spotInstancePrice to zero.
This worked as expected by bringing up the lost instance on-demand (verified using the AWS console), but our in-house deployment tool (based on NixOps) was still reporting them as Spot instances.
After manually investigating the NixOps state file, we found that the nix arguments were updated (set to 0 in the DeploymentAttrs table) whereas the actual spot price wasn't (spotInstancePrice field in the ResourceAttrs table).
The text was updated successfully, but these errors were encountered:
We had a deployment running EC2 Spot instance that some of them were destroyed because of lack of capacity on the AWS side. We then re-deployed using on-demand instances by setting
ec2.spotInstancePrice
to zero.This worked as expected by bringing up the lost instance on-demand (verified using the AWS console), but our in-house deployment tool (based on NixOps) was still reporting them as Spot instances.
After manually investigating the NixOps state file, we found that the nix arguments were updated (set to 0 in the
DeploymentAttrs
table) whereas the actual spot price wasn't (spotInstancePrice
field in theResourceAttrs
table).The text was updated successfully, but these errors were encountered: