I don't think there's a clear path at this point, because create is an asynchronous operation in Cinder and so we don't know the result when sending the API call, only that Cinder has received correctly. I wonder if there's an error field in the volume details, like there is for Nova in the instance details? (A quick look at "cinder show" seems to suggest not...)
Overall though, I'm not sure I agree with surfacing errors like details like "Volume group "cinder-volumes" has insufficient free space (1279 extents): 1280 required." to end-users. It's not something they can act upon.
I don't think there's a clear path at this point, because create is an asynchronous operation in Cinder and so we don't know the result when sending the API call, only that Cinder has received correctly. I wonder if there's an error field in the volume details, like there is for Nova in the instance details? (A quick look at "cinder show" seems to suggest not...)
The following cinder blueprint may be of interest but hasn't seen an ounce of interest since its creation: https:/ /blueprints. launchpad. net/cinder/ +spec/return- error-messages- to-horizon
Overall though, I'm not sure I agree with surfacing errors like details like "Volume group "cinder-volumes" has insufficient free space (1279 extents): 1280 required." to end-users. It's not something they can act upon.