Comment 1 for bug 1936752

I tried a simple experiment to reproduce this. I had a simple demo charm with storage

storage:
    data:
        type: block
        multiple:
          range: 1+

In the data-storage-attached and data-storage-detaching hook I logged the output of "storage-get" to a file.

After deploying the charm, "juju storage --format yaml" and the storage location made available to the attached hook via storage-get both had "/dev/disk/azure/scsi1/lun1".

Then I "juju detach-storage data/1" and the detaching hook was also supplied the expected location "/dev/disk/azure/scsi1/lun1".

The bug says that "sometimes" the wrong path is used. How often does this happen? In such cases, what does "juju storage --format yaml" show before the storage is detached? Is it possible to get the storage, volume and volume attachment collection data from the "juju dump-db" output?
Is there a particular charm that the issues occurs for regularly?