Bug 1326280

Summary: [RFE] [manila]: Show only Available Protocols for Shares in Share Protocol Drop-Down Menu
Product: Red Hat OpenStack Reporter: Robin Cernin <rcernin>
Component: openstack-manila-uiAssignee: Victoria Martinez de la Cruz <vimartin>
Status: CLOSED ERRATA QA Contact: Dustin Schoenbrun <dschoenb>
Severity: medium Docs Contact:
Priority: medium    
Version: 10.0 (Newton)CC: apevec, cschwede, ddomingo, dhill, dschoenb, hguemar, jliberma, lhh, nlevinki, pgrist, sclewis, scohen, tbarron, tvignaud, vimartin
Target Milestone: Upstream M3Keywords: FutureFeature, Triaged
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-manila-ui-2.7.1-0.20170127105750.b67e7e6.el7ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-17 19:29:04 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:

Comment 3 Stephen Gordon 2016-06-09 18:51:58 UTC
Bulk update to reflect scope of Red Hat OpenStack Platform 9 and Red Hat OpenStack Platform does not include this issue (No pm_ack+).

Comment 13 Thierry Vignaud 2017-02-14 17:11:06 UTC
Change is in openstack-manila-ui-2.7.1-0.20170127105750.b67e7e6.el7ost

Comment 22 Dustin Schoenbrun 2017-03-27 19:12:09 UTC
Using the 2017-03-08.3 puddle, openstack-manila-ui-2.7.1-0.20170214092823.2e2ae51.el7ost.noarch, and the workaround where we tell Horizon to use the v2 Keystone API endpoint instead of the v3 API endpoint, I was able to successfully set the list of enabled share protocols in the Horizon UI as well as verifying the default behavior of listing all known protocols if the list is not specified.

Comment 23 Sean Cohen 2017-03-27 22:51:47 UTC
*** Bug 1326119 has been marked as a duplicate of this bug. ***

Comment 24 errata-xmlrpc 2017-05-17 19:29:04 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-2017:1245