Horizon dashboard page is not opening instead redirecting the page to folder

Bug #1824999 reported by Mohammad Irshad Ahmad
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
openstack-helm
Expired
Undecided
Unassigned

Bug Description

Following the page (https://docs.openstack.org/openstack-helm/latest/install/developer/deploy-with-ceph.html) for openstack helm installation and after installing the Horizon.

./tools/deployment/developer/ceph/100-horizon.sh

ubuntu@ma582r-myopenstackhelm:~$ helm status horizon
LAST DEPLOYED: Fri Apr 12 14:55:11 2019
NAMESPACE: openstack
STATUS: DEPLOYED

RESOURCES:
==> v1/ConfigMap
NAME DATA AGE
horizon-bin 6 3d23h

==> v1/Deployment
NAME READY UP-TO-DATE AVAILABLE AGE
horizon 1/1 1 1 3d23h

==> v1/Job
NAME COMPLETIONS DURATION AGE
horizon-db-init 1/1 7s 3d23h
horizon-db-sync 1/1 3m45s 3d23h

==> v1/NetworkPolicy
NAME AGE
horizon-netpol 3d23h

==> v1/Pod(related)
NAME READY STATUS RESTARTS AGE
horizon-db-init-fmrq8 0/1 Completed 0 3d23h
horizon-db-sync-cqxcj 0/1 Completed 0 3d23h
horizon-f64c7c8f9-8svgb 1/1 Running 0 3d23h

==> v1/Secret
NAME TYPE DATA AGE
horizon-db-admin Opaque 1 3d23h
horizon-db-user Opaque 1 3d23h
horizon-etc Opaque 10 3d23h

==> v1/Service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
horizon ClusterIP 10.109.163.206 <none> 80/TCP,443/TCP 3d23h
horizon-int NodePort 10.106.98.3 <none> 80:31000/TCP 3d23h

==> v1/ServiceAccount
NAME SECRETS AGE
horizon 1 3d23h
horizon-db-init 1 3d23h
horizon-db-sync 1 3d23h

==> v1beta1/Ingress
NAME HOSTS ADDRESS PORTS AGE
horizon horizon,horizon.openstack,horizon.openstack.svc.cluster.local 80 3d23h

==> v1beta1/PodDisruptionBudget
NAME MIN AVAILABLE MAX UNAVAILABLE ALLOWED DISRUPTIONS AGE
horizon 0 N/A 1 3d23h

==> v1beta1/Role
NAME AGE
horizon-openstack-horizon 3d23h
horizon-openstack-horizon-db-init 3d23h
horizon-openstack-horizon-db-sync 3d23h

==> v1beta1/RoleBinding
NAME AGE
horizon-horizon 3d23h
horizon-horizon-db-init 3d23h
horizon-horizon-db-sync 3d23h

ubuntu@ma582r-myopenstackhelm:~$

Pod, service and ingress status for horizon are:
ubuntu@ma582r-myopenstackhelm:~$ kubectl get pods -n openstack -o wide | grep horizon
horizon-db-init-fmrq8 0/1 Completed 0 3d23h 192.168.84.84 ma582r-myopenstackhelm <none> <none>
horizon-db-sync-cqxcj 0/1 Completed 0 3d23h 192.168.84.87 ma582r-myopenstackhelm <none> <none>
horizon-f64c7c8f9-8svgb 1/1 Running 0 3d23h 192.168.84.78 ma582r-myopenstackhelm <none> <none>
ubuntu@ma582r-myopenstackhelm:~$ kubectl get svc -n openstack -o wide | grep horizon
horizon ClusterIP 10.109.163.206 <none> 80/TCP,443/TCP 3d23h app=ingress-api
horizon-int NodePort 10.106.98.3 <none> 80:31000/TCP 3d23h application=horizon,component=server,release_group=horizon
ubuntu@ma582r-myopenstackhelm:~$ kubectl get ingress -n openstack
NAME HOSTS ADDRESS PORTS AGE
cinder cinder,cinder.openstack,cinder.openstack.svc.cluster.local 80 3d21h
cloudformation cloudformation,cloudformation.openstack,cloudformation.openstack.svc.cluster.local 80 4d16h
glance glance,glance.openstack,glance.openstack.svc.cluster.local 80 3d21h
glance-reg glance-reg,glance-reg.openstack,glance-reg.openstack.svc.cluster.local 80 3d21h
heat heat,heat.openstack,heat.openstack.svc.cluster.local 80 4d16h
horizon horizon,horizon.openstack,horizon.openstack.svc.cluster.local 80 3d23h
keystone keystone,keystone.openstack,keystone.openstack.svc.cluster.local 80 4d17h
openstack-ingress-openstack *.openstack.svc.cluster.local 80 5d17h
rabbitmq-mgr-7b1733 rabbitmq-mgr-7b1733,rabbitmq-mgr-7b1733.openstack,rabbitmq-mgr-7b1733.openstack.svc.cluster.local 80 4d17h
radosgw radosgw,radosgw.openstack,radosgw.openstack.svc.cluster.local 80 3d22h
ubuntu@ma582r-myopenstackhelm:~$

The page is not visible instead it is redirecting to the folder structure:
Refer bowser Image

Revision history for this message
Mohammad Irshad Ahmad (ahmi01) wrote :
Revision history for this message
Gage Hugo (gagehugo) wrote :

Has there been any updates regarding this?

Changed in openstack-helm:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openstack-helm because there has been no activity for 60 days.]

Changed in openstack-helm:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.