Description of problem: Currently there is no release of the Manila Horizon UI Plugin for OSP-8 so there is no way to manage your Manila infrastructure through the Horizon UI. There is a branch available for this for OSP-7 but nothing for OSP-8. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Attempt to install the "openstack-manila-ui" package in OSP-8 2. Observe that the package is not available. 3. Actual results: There is no package named "openstack-manila-ui" Expected results: The Manila Horizon UI Plugin shall be installed successfully. Additional info:
cross-tagged build from osp 7
New build (rebased to 1.2.0)
Installed openstack-manila-ui in RHEL-OSP8 Beta 7. I can confirm that after restarting httpd, a "Shares" tab appears to the right of the "Access & Security" tab in Horizon.
Created attachment 1144192 [details] No Manila UI
Failed QA ========= Was Verified on HA Director deployment. For each overcloud-controller (3): ================================== openstack-manila-1.0.1-3.el7ost.noarch openstack-manila-ui-1.2.0-1.el7ost.noarch openstack-manila-share-1.0.1-3.el7ost.noarch and, systemctl restart httpd Actual results: =============== There is no "Shares" tab on Horizon Screenshot is enclosed.
Dustin, Can you validate this one in the context of https://bugzilla.redhat.com/show_bug.cgi?id=1285516? Sean
(In reply to Sean Cohen from comment #11) > Dustin, > Can you validate this one in the context of > https://bugzilla.redhat.com/show_bug.cgi?id=1285516? > Sean Sure thing. When I get some bits for OSP-10 I'll make sure that I can install the Horizon Plugin via OSP-Director and that it functions properly. I'll create new bugs for anything that I find outside of the installation of the UI plugin.
Tested with 2016-10-6.1 puddle version and can verify that the Manila UI is available in the openstack-manila-ui package and it is also installed with OSP-Director. Looks good to me!
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://rhn.redhat.com/errata/RHEA-2016-2948.html