cold-coat-35200
05/02/2019, 1:13 PMnew aws.ec2.VolumeAttachment(`wordpress-content-attachment`, {
instanceId: ec2Instance.id,
volumeId: dataVolume.id,
deviceName: '/dev/xvdc',
forceDetach: true
})
When something changed in the instance, it will trigger a volume attachment replace too.
You can see in the code sample how it's handled by pulumi, nothing changed in the code between the commands.
Basically first it's say that volume in use, looks like it ignores forceDetach, then the second time realizes, that it's detached from the previous one, therefore unable to detach it and after a refresh everything is good.
Is it normal?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 toowhite-balloon-205
skipDestroy: true
.
? See also https://github.com/terraform-providers/terraform-provider-aws/issues/1017.cold-coat-35200
05/03/2019, 5:47 PMforceDetach: true
and I did not detached manually, outside of pulumi, in that case I know a refresh necessaarywhite-balloon-205
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