Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GCP persistent disk device name is 'sdb', not 'pkb-xxxxxxxx-0-data-0-0'

See original GitHub issue

This appears to be an issue with the GCP API, but not sure how/where to report that so raising the issue here as PKB users may run into the issue.

The error from PKB looks like this:

2019-09-26 08:54:31,060 406c8cfa Thread-42 mongodb_stress(1/1) INFO     Running: ssh -A -p 22 perfkit@35.225.149.231 -2 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o IdentitiesOnly=yes -o PreferredAuthentications=publickey -o PasswordAuthentication=no -o ConnectTimeout=5 -o GSSAPIAuthentication=no -o ServerAliveInterval=30 -o ServerAliveCountMax=10 -i /tmp/perfkitbenchmarker/runs/406c8cfa/perfkitbenchmarker_keyfile -o ControlPath="/tmp/perfkitbenchmarker/runs/406c8cfa/ssh/%C" -o ControlMaster=auto -o ControlPersist=30m [[ -d /mnt ]] && sudo umount /mnt; sudo mke2fs -F -E lazy_itable_init=0,discard -O ^has_journal -t ext4 -b 4096 /dev/pkb-406c8cfa-0-data-0-0
2019-09-26 08:54:31,299 406c8cfa Thread-42 mongodb_stress(1/1) INFO     Ran: {ssh -A -p 22 perfkit@35.225.149.231 -2 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o IdentitiesOnly=yes -o PreferredAuthentications=publickey -o PasswordAuthentication=no -o ConnectTimeout=5 -o GSSAPIAuthentication=no -o ServerAliveInterval=30 -o ServerAliveCountMax=10 -i /tmp/perfkitbenchmarker/runs/406c8cfa/perfkitbenchmarker_keyfile -o ControlPath="/tmp/perfkitbenchmarker/runs/406c8cfa/ssh/%C" -o ControlMaster=auto -o ControlPersist=30m [[ -d /mnt ]] && sudo umount /mnt; sudo mke2fs -F -E lazy_itable_init=0,discard -O ^has_journal -t ext4 -b 4096 /dev/pkb-406c8cfa-0-data-0-0}  ReturnCode:1
STDOUT:
STDERR: umount: /mnt: not mounted.
mke2fs 1.44.1 (24-Mar-2018)
The file /dev/pkb-406c8cfa-0-data-0-0 does not exist and no size was specified.

It appears the PKB is calling the CLI with the correct parameter to name the device:

2019-09-26 08:51:51,421 406c8cfa Thread-42 mongodb_stress(1/1) vm_util.py:338 INFO     Running: gcloud compute instances attach-disk pkb-406c8cfa-0 --format json --quiet --project ssg-benchmarks --zone us-central1-c --device-name pkb-406c8cfa-0-data-0-0 --disk pkb-406c8cfa-0-data-0-0

When I log in to the VM, I can see (via lsblk) that the device name is ‘sdb’ not pkb-xxxxxxxx-0-data-0-0.

Note that I see the same problem when creating a VM and attaching a disk through the console/GUI.