Cloned from launchpad bug 1767520. Description: Description =========== In a vanilla installation of TripleO Queens using Docker horizon will return with error 500 after a "successful" deployment. Steps to reproduce ================== 1. Deploy undercloud according to the documentation at https://docs.openstack.org/tripleo-docs/latest/install/index.html 2. Create environment files: http://paste.openstack.org/show/720052/ 3. Run the following command to deploy overcloud: /bin/openstack overcloud deploy --templates /home/stack/tripleo-heat-templates -e /home/stack/tripleo-heat-templates/environments/network-isolation.yaml -e /home/stack/tripleo-heat-templates/environments/net-bond-with-vlans.yaml -e /home/stack/bond-with-vlans.yaml -e tripleo-heat-templates/environments/docker.yaml -e tripleo-heat-templates/environments/docker-ha.yaml --ntp-server 172.18.0.2 --control-scale 3 --compute-scale 1 --control-flavor control --compute-flavor compute --swift-storage-flavor swift-storage 4. ssh to the controller which has the external VIP 5. View the logs at /var/log/containers/horizon/horizon.log Expected result =============== The dashboard presents a login screen Actual result ============= The dashboard returned an error 500 when browsing to the external VIP Environment =========== 1. Exact version of OpenStack you are running. See the following Queens 2. Which storage type did you use? Ceph 3. Which networking type did you use? Neutron with Openvswitch Logs & Configs ============== /var/log/containers/horizon/horizon.log http://paste.openstack.org/show/720050/ Specification URL (additional information): https://bugs.launchpad.net/tripleo/+bug/1767520
This looks like it might be a blocker for 13. Requesting analysis.
When I try to install packstack with trove enabled, I get: Package openstack-trove-ui has not been found in enabled Yum repos. Do we even support it?
Trove is not supported on Red Hat OpenStack Platform. https://bugzilla.redhat.com/show_bug.cgi?id=1346936 https://bugzilla.redhat.com/show_bug.cgi?id=1346395
Thanks, I'm closing this bug then.