This message was deleted.

sparse-intern-71089

05/02/2019, 1:13 PM

This message was deleted.

-.sh

cold-coat-35200

05/03/2019, 12:29 PM

Any idea about this? Almost the same thing happened when I tried to destroy the whole stack, I got a

Copy code

Plan apply failed: deleting urn:pulumi:sbx::k8s-wordpress::aws:ec2/volumeAttachment:VolumeAttachment::wordpress-content-attachment: Failed to detach Volume (vol-0a5dc19036ac2232d) from Instance (i-0ba8081cc3cc886b1): IncorrectState: Volume 'vol-0a5dc19036ac2232d'is in the 'available' state.

but when I checked on the console, the volume was already detached, a refresh solved this too

white-balloon-205

05/03/2019, 3:35 PM

Sounds like you may need to set

skipDestroy: true

white-balloon-205

05/03/2019, 3:39 PM

Actually your case looks different than that. It appears you manually detached the volume outside of Pulumi? If so, then the refresh would indeed be needed before the destroy.

cold-coat-35200

05/03/2019, 5:47 PM

Don't feel I should use skipDestroy, I wanted to be destroyed, that's why I set

forceDetach: true

and I did not detached manually, outside of pulumi, in that case I know a refresh necessaary

cold-coat-35200

05/03/2019, 5:48 PM

looks like pulumi detaches it, but does not recognize this without refresh, so it's unable to fully destroy or replace it

white-balloon-205

05/03/2019, 7:04 PM

looks like pulumi detaches it,

Which action are you taking with Pulumi that causes the detach?

cold-coat-35200

05/03/2019, 8:13 PM

First I changed the userdata on the ec2 instance, which triggered a volume attachment replace, second time simply tried to destroy the whole stack

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.