BOSH fails to change persistent disk size

Products

• Operations Manager

Issue/Introduction

From OpsManager changelog, BOSH failed to increase the persistent disk for a VM:

Task 151 | 12:22:10 | Updating instance worker: worker/8c2efee9-61a3-4be6-adc4-72b4715c642d (0) (canary) (00:04:58)
                    L Error: Action Failed get_task: Task f9e3b73f-3c50-48b1-6b19-19714d3f130c result: Mounting persistent disk: Getting real device path: Timed out getting real device path for '6000c29f-3e49-0147-b7b9-9ba689e149c1'
Task 151 | 12:27:08 | Error: Action Failed get_task: Task f9e3b73f-3c50-48b1-6b19-19714d3f130c result: Mounting persistent disk: Getting real device path: Timed out getting real device path for '6000c29f-3e49-0147-b7b9-9ba689e149c1'

Task 151 Started  Tue Jan 12 12:21:52 UTC 2021

Environment

Bosh vms

Resolution

If you run the lsblk command inside the VM, you can see the persistent disk name is sdd1 and mountpoint /var/vcap/store. When BOSH creates a VM, the persistent disk name is sdc1 and mountpoint /var/vcap/store.

worker/8c2efee9-61a3-4be6-adc4-72b4715c642d:/var/log# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sdd      8:48   0   50G  0 disk
└─sdd1   8:49   0   50G  0 part /var/vcap/store
sdb      8:16   0   32G  0 disk
├─sdb2   8:18   0 28.1G  0 part /var/vcap/data
└─sdb1   8:17   0  3.9G  0 part [SWAP]
sr0     11:0    1   50K  0 rom
sdc      8:32   0   20G  0 disk
└─sdc1   8:33   0   20G  0 part
sda      8:0    0    3G  0 disk
└─sda1   8:1    0    3G  0 part /

It means the VM persistent disk configuration had been changed at some point and the VM has never been recreated. In order to get back the correct disk configuration, you can recreate the VM with BOSH command (recommended method) or reboot the VM from the IaaS or Linux command.