Bug 1469214

Summary: [RFE][manila] User messages support
Product: Red Hat OpenStack Reporter: Tom Barron <tbarron>
Component: openstack-manilaAssignee: Tom Barron <tbarron>
Status: CLOSED ERRATA QA Contact: Aharon Canan <acanan>
Severity: medium Docs Contact: mmurray
Priority: medium    
Version: 13.0 (Queens)CC: achernet, cschwede, dsariel, jschluet, lmarsh, mariel, pgrist, scohen, vimartin
Target Milestone: Upstream M2Keywords: FutureFeature, TestOnly, Triaged
Target Release: 14.0 (Rocky)Flags: jomurphy: needinfo+
Hardware: Unspecified   
OS: Unspecified   
URL: https://specs.openstack.org/openstack/manila-specs/specs/pike/user-messages.html
Whiteboard:
Fixed In Version: openstack-manila-6.0.0-0.20180122210259.4adbf82.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:47:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tom Barron 2017-07-10 16:23:31 UTC 
If manila operations fail, e.g. create share or create share group, user gets no detailed information whatsoever. Only the operation status is updated, e.g. error or failed, without any update to user.

We should address this by adding a /messages resource to the API in order for end-users to query for more information about errors.
Comment 18 Vince Green 2018-06-26 14:46:12 UTC 
Manila QE has run tempest manila API runs on OSP13 with user messages enabled in our regression and update testing. We did final tempest api testing on this feature on OSP 13 and OSP14.  

Link to polarion:
https://polarion.engineering.redhat.com/polarion/#/project/RHELOpenStackPlatform/testrun?id=20180626-1403

No issues found, tests for tempest passed.  Marking rfe as verified.
Comment 24 errata-xmlrpc 2019-01-11 11:47:34 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:0045