Unable to locate Linode Volume

[programingnotes]

Hello,

Although Linode Dashboard does show that the my volume exists, is attached to linode instance, and has a file system path, I am unable to locate saids linode volume by its file system path in my terminal.

Terraform Version

• Terraform v0.11.8

Affected Resource(s)

Please list the resources as a list, for example:

• linode_instance
• linode_volume

Terraform Configuration Files

provider "linode" {
  token = "${var.v4_api_token}"
}

resource "linode_instance" "test" {
  group           = "${var.group}"
  label           = "${var.group}-${var.label}"
  image           = "${var.image}"
  region          = "${var.region}"
  type            = "${var.type}"
  authorized_keys = "${chomp(file(var.root_ssh_keys))}"
  root_pass       = "${var.root_user_password}"
  swap_size = 1024 
}

resource "linode_volume" "docker" {
  size  = 20  
  label = "${linode_instance.test.label}-${var.docker_vol}"
  region = "${linode_instance.test.region}"

  linode_id = "${linode_instance.test.id}"
}

Debug Output

Log Output

Panic Output

Terraform does not produced a panic

Given

• volume created and attached it to a linode instance successfully (meaning no terraform failure)

resource "linode_instance" "test" {
  group           = "${var.group}"
  label           = "${var.group}-${var.label}"
  image           = "${var.image}"
  region          = "${var.region}"
  type            = "${var.type}"
  authorized_keys = "${chomp(file(var.root_ssh_keys))}"
  root_pass       = "${var.root_user_password}"
  swap_size = 1024 
}

resource "linode_volume" "docker" {
  size  = 20  
  label = "${linode_instance.test.label}-${var.docker_vol}"
  region = "${linode_instance.test.region}"

  linode_id = "${linode_instance.test.id}"
}

Expected Behavior

• running ls /dev/disk/by-id should return a list that includes the filesystem for the created volume

  root@localhost:~# ls -la /dev/disk/by-id/
  total 0
  drwxr-xr-x 2 root root  80 Oct 13 09:42 .
  drwxr-xr-x 5 root root 100 Oct 13 09:42 ..
  lrwxrwxrwx 1 root root   9 Oct 13 09:42 scsi-0Linode_Volume_T3st-Dis-WebServer-docker-volume"
  lrwxrwxrwx 1 root root   9 Oct 13 09:42 scsi-0QEMU_QEMU_HARDDISK_drive-scsi-disk-0 -> ../../sda
  lrwxrwxrwx 1 root root   9 Oct 13 09:42 scsi-0QEMU_QEMU_HARDDISK_drive-scsi-disk-1 -> ../../sdb

Actual Behavior

• running ls /dev/disk/by-id returns a list that does not include the filesystem for the created volume:

  root@localhost:~# ls -la /dev/disk/by-id/
  total 0
  drwxr-xr-x 2 root root  80 Oct 13 09:42 .
  drwxr-xr-x 5 root root 100 Oct 13 09:42 ..
  lrwxrwxrwx 1 root root   9 Oct 13 09:42 scsi-0QEMU_QEMU_HARDDISK_drive-scsi-disk-0 -> ../../sda
  lrwxrwxrwx 1 root root   9 Oct 13 09:42 scsi-0QEMU_QEMU_HARDDISK_drive-scsi-disk-1 -> ../../sdb

Kernel:

root@localhost:~# uname -a
Linux localhost 4.18.8-x86_64-linode117 #1 SMP PREEMPT Tue Sep 18 18:48:25 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. Given the above tf file

provider "linode" {
  token = "${var.v4_api_token}"
}

resource "linode_instance" "test" {
  group           = "${var.group}"
  label           = "${var.group}-${var.label}"
  image           = "${var.image}"
  region          = "${var.region}"
  type            = "${var.type}"
  authorized_keys = "${chomp(file(var.root_ssh_keys))}"
  root_pass       = "${var.root_user_password}"
  swap_size = 1024 
}

resource "linode_volume" "docker" {
  size  = 20  
  label = "${linode_instance.test.label}-${var.docker_vol}"
  region = "${linode_instance.test.region}"

  linode_id = "${linode_instance.test.id}"
}

2. run terraform init && terraform apply
3. log into linode
4. run ls -la /dev/disk/by-id

Important Factoids

There isn't anything atypical about my account.

References

No references that I have found thus far

[programingnotes]

with help from @displague, I was able to figure out that (at the time of this issue) the order of resource creation matters. There are 2 ways to explicity link volumes:

• Create the volume before the linode and then reference it in the linode config disks
• Create the volume after the linode and include a provisioner that initializes the volume within the linode resource

The method I used (above):

• Create the volume after the linode with a reference to the linode id requires a system reboot for the linode instance to be aware of the newly attached volume.