Comment 13 for bug 1951182

Ran into this issue with the new postgres VM bundle - we managed a workaround by deleting `storage:` and `resource:` fields from our bundle.yaml, and letting the relevant charm handle them on its own.