Comment 4 for bug 1798001

Digging into the storage processing code, tt looks like the problem is that the EBS volumes are being exposed as NVMe block devices. This is relatively new behaviour that was previously confined to c5 and m5 instance types but now appears to have been more widely implemented. The issue is that the block device names become unpredictable which messes up how Juju determines whether a volume has become attached to a machine. This in turn blocks the initialisation of the unit agent since it waits for storage to become attached before installing the charm.

I need to look further to find a tasteful solution that works in all cases.