Description of problem: Based on the discussion in bug 976279 especially comment 3, it would be useful if Cinder could offer an API for the user to understand why a volume ended up in an error state, e.g. not enough space (cf. bug 976279), attachment failure (cf. bug 981418), etc. This would enable front-ends like Horizon to provide more useful information to the user in case of failure / error. Additional info: This upstream blueprint may also be relevant: https://blueprints.launchpad.net/cinder/+spec/return-error-messages-to-horizon
See current Telemetry & Nagios Logging, Monitoring and Troubleshooting guide [1] we have also introduced in OSP7 several operational tools in tech-preview that include: centralized logging tools such as Fluentd, ElasticSearch & Kibana [2] [1] https://access.redhat.com/webassets/avalon/d/Red_Hat_Enterprise_Linux_OpenStack_Platform-7-Logging_Monitoring_and_Troubleshooting_Guide-en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform-7-Logging_Monitoring_and_Troubleshooting_Guide-en-US.pdf [2] https://access.redhat.com/documentation/en/red-hat-enterprise-linux-openstack-platform/version-7/architecture-guide/ - see Logging and monitoring section.