Bug 1571592
Summary: | Orchestration tab not present in horizon | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Yolanda Robla <yroblamo> | |
Component: | openstack-tripleo-heat-templates | Assignee: | Beth White <beth.white> | |
Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 13.0 (Queens) | CC: | beth.white, brault, emacchi, godfrey_tan2001, jrist, mburns, molasaga, rdopiera, tvignaud, wlehman, yaron.aboodaga | |
Target Milestone: | --- | Keywords: | Triaged, ZStream | |
Target Release: | 13.0 (Queens) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openstack-tripleo-heat-templates-8.2.0-6.el7ost | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1667902 (view as bug list) | Environment: | ||
Last Closed: | 2019-03-14 13:54:50 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: | 1667902 |
Description
Yolanda Robla
2018-04-25 07:51:09 UTC
Hi, Which directory should horizon.yaml be in for Orchestration tab to appear? I have All-in-One Queens and Orchestration tab is missing. I don't understand the question. Hi, After I installed Openstack Packstack Allinone, the Orchestration tab in Horizon dashboard is missing eventhough HEAT/Orchestration seems to be running. This article seems to indicate a solution. Hence, is there a place in Packstack that I should place the horizon.yaml file? The horizon.yaml is used by tripleo when deploying horizon in a container. Packstack doesn't use it. To get the orchestration tab in packstack, simply install the openstack-heat-ui package. Hi Radomir, Thanks so much. It's worked. 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:0448 |