EBS volumes fail to format on nitro instances about terraform-aws-couchbase

[brikis98]

Indeed. Using nvme is quite a bit more complicated:

1. You have to detect if the system is using nvme using lsblk.
2. You then run nvme list to get the list of nvme volumes (note: this requires the nvme utility to be installed).
3. You then have to find the device you want using nvme id-ctrl.
4. And then when mounting the volume, you have to mount it using its UUID, as that's the only thing consistent across reboots.

I don't think we're going to be able to get a fix in soon. Does anyone have some cycles to submit a PR for this in the meantime?

[tinomen]

Keep in mind that your step 3 assumes you can reuse the terraform device name. This however throws an error when ASG tries to create the ebs volume. So your solution would have to create a second volume name and pass it forward thru the functions.

[brikis98]

Keep in mind that your step 3 assumes you can reuse the terraform device name. This however throws an error when ASG tries to create the ebs volume.

What error?

[tinomen]

The asg is unable to start the instances because the EBS volume fails creation. I don’t recall the words. Give it a try.

[brikis98]

We use the approach described in #73 (comment) (which we have in a private script) with a number of ASGs, and it works OK, so I'm not sure how to repro...

[tinomen]

What device name are you using? I tired nvme1 and nvme1n1 and the instances failed to start due to a failed ebs volume.

Well, hopefully the issue and this closed pr will help someone overcome the hurdles in making these scripts production ready.

[brikis98]

As I wrote above, we use the UUID, which we look up using blkid.

[ellisonc]

This repo is being archived, feel free to use a fork if necessary.