Description of problem: ======================= Overcloud Horizon - unable to edit project Version-Release number of selected component (if applicable): ============================================================= python-django-horizon-2015.1.0-10.el7ost.noarch openstack-tripleo-heat-templates-0.8.6-15.el7ost.noarch How reproducible: ================= 100% Steps to Reproduce: =================== 1. Deploy overcloud 2. Log in to overcloud UI Horizon 3. Go to Identity -> Projects 4. Select any project (e.g admin), click 'Edit Project' Actual results: =============== Nothing, no edit dialog window opened Expected results: ================= Dialog window should open Additional info: ================ This bug occurs while installing by OSP-7 director, It doesn't happen using packstack
I suspect this is something we're configuring incorrectly. We've seen a couple other horizon issues as well. Ido, Are there horizon logs available for this issue? Can you collect the horizon configurations? @mrunge -- can you review the configuration and help us figure out where the misconfiguration is?
horizon.log =========== 2015-06-28 13:59:10,105 32298 WARNING openstack_dashboard.api.cinder Cinder v2 requested but no 'volumev2' service type available in Keystone catalog. 2015-06-28 13:59:10,125 32298 WARNING horizon.exceptions Recoverable error: Invalid URL '/os-quota-sets/b55615f0cb704900ba0da22d48ced52a?usage=False': No schema supplied. Perhaps you meant http:///os-quota-sets/b55615f0cb704900ba0da22d48ced52a?usage=False?
Mike, Horizon relies on volumev2 endpoint. It is called, when collecting quota information. I know, there has been an issue in director, where volumev2 endpoint was not created. I suspect, this setup was set up by a version not including the fix. This should be a duplicate of bug 1233956
Verified ======== os-cloud-config-0.2.8-4.el7ost.noarch python-django-horizon-2015.1.0-10.el7ost.noarch
adding pm_ack+ for TestOnly bug that's already verified
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-2015:1549