Bug 1719050 - Deploying 14z3 no share tab in the UI for openstack
Summary: Deploying 14z3 no share tab in the UI for openstack
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z3
: 14.0 (Rocky)
Assignee: Goutham Pacha Ravi
QA Contact: vhariria
URL:
Whiteboard:
Depends On:
Blocks: 1661395
TreeView+ depends on / blocked
 
Reported: 2019-06-10 22:09 UTC by Jason Grosso
Modified: 2019-07-02 20:09 UTC (History)
10 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.3.1-0.20190513171732.9995be9.el7ost.src.rpm
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1719485 (view as bug list)
Environment:
Last Closed: 2019-07-02 20:09:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1832302 0 None None None 2019-06-11 17:13:29 UTC
OpenStack gerrit 664634 0 'None' MERGED Re-enable manila dashboard 2020-12-02 22:20:03 UTC
Red Hat Product Errata RHBA-2019:1672 0 None None None 2019-07-02 20:09:52 UTC

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
Note You need to log in before you can comment on or make changes to this bug.