Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1719050

Summary: Deploying 14z3 no share tab in the UI for openstack
Product: Red Hat OpenStack Reporter: Jason Grosso <jgrosso>
Component: openstack-tripleo-heat-templatesAssignee: Goutham Pacha Ravi <gouthamr>
Status: CLOSED ERRATA QA Contact: vhariria
Severity: high Docs Contact:
Priority: high    
Version: 14.0 (Rocky)CC: apevec, gcharot, gouthamr, hguemar, lhh, mburns, pgrist, rhos-maint, vhariria, vimartin
Target Milestone: z3Keywords: Regression, Triaged, ZStream
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-9.3.1-0.20190513171732.9995be9.el7ost.src.rpm Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1719485 (view as bug list) Environment:
Last Closed: 2019-07-02 20:09:17 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:
Bug Depends On:    
Bug Blocks: 1661395    

Description Jason Grosso 2019-06-10 22:09:35 UTC 
Description of problem:
Manila UI appears broken and is missing in Horizon





How reproducible:
100% 

Steps to Reproduce:
1. Deploy Manila with NetApp backend running OSP15
2. On OpenStack Horizon; look for the Shares tab under Project > Compute.

Actual results:
The Shares tab does not exist in the manila-ui

Expected results:
Expect Shares tab under Project > Compute

Additional info:
The issue applies to multiple deployments, including cephFs NFS-Ganesha, so far OSP 14z3 and 15 and trying on 13z6
Comment 4 Paul Grist 2019-06-12 20:35:36 UTC 
Triaging it and setting blocker? to be sure we get this in the puddle re-spin.  The upstream regression imported breaks Manila UI and we need to be sure this fix gets in to the current Z
Comment 20 errata-xmlrpc 2019-07-02 20:09:17 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/RHBA-2019:1672