Comment 5 for bug 1798001

The only real way to fix this regardless of how EC2 behaviour might change underneath us is punt on assuming a NVMe block device link is valid for a newly attached machine volume even though it may not be. This is because we have to real way of querying how an attached volume will be exposed on a machine instance. This has no practical effect other than potentially printing an incorrect device link when printing storage volume information in YAML. The device name (eg xvdf) is accurate. To update the Juju model after the volume is recorded as attached is messy because we don't want to encode AWS specific behaviour at that layer.

I deployed a 2.4.4 controller and deployed postgresql and observed the storage issue. I then upgraded the controller with the abve fix and observed storage come good and postgresql became active.