https://pulumi.com logo
#general
Title
# general
b

brainy-microphone-27448

11/27/2019, 1:26 PM
Hey! Could you take a look at https://github.com/avolkov-dev/pulumi-mount-issue ? i'm getting weird error (
VolumeInUse
) when reaattaching existed volume to new instance
w

white-balloon-205

11/27/2019, 5:07 PM
Could you open an issue in Pulumi-kubernetes and link to this? Someone might need to look a little deeper into this.
s

stocky-nail-30268

11/27/2019, 5:11 PM
It's not kubernetes related, it's AWS/EC2/EBS
w

white-balloon-205

11/27/2019, 5:18 PM
Ahh - got it. Took a quick look - haven’t tried it yet but I expect this is related to needing to use
deleteBeforeReplace: true
to ensure the old instance is deleted before the new one is created - else the volume will still be attached to the old instance.
b

brainy-microphone-27448

11/27/2019, 6:10 PM
That works perfectly fine for me. Thanks a lot!
s

stocky-nail-30268

11/27/2019, 6:17 PM
Thanks Luke
b

brainy-microphone-27448

11/27/2019, 7:45 PM
Is it possible to enforce pulumi to stop ec2 instance before detaching the volume on userdata change(and instance recreation)? https://github.com/avolkov-dev/pulumi-mount-issue/blob/master/index.ts#L16 Because now (without
forceDetach
) we are getting Error waiting for Volume (vol-xxx) to detach from Instance: i-xxx error) I believe this is because we trying to detach volume on running instance and getting timeouted