This message was deleted.

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

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

Sounds like you may need to set

skipDestroy: true

. ? See also https://github.com/terraform-providers/terraform-provider-aws/issues/1017.

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

looks like pulumi detaches it,

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

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