DeepSea grafana dashboards not found when loaded via openattic api

grafana dashboards not found when loaded via openattic api

Open khodayard opened this issue 5 years ago • 3 comments

Description of Issue/Question

Hi, I've installed ceph and openattic with deepsea in a test env consisting of only one node named: cl5.opn.shft with two nics. Everything has gone OK and ceph is operating now. but none of grafana dashboards load and all of them show a "Page not found 404 Error". When I access the grafana dashboard directly I can find and load all of dashboards which are all there, load correctly and perfectly, but when openattic tries to load them through its api they cannot be loaded, I can see list of all the dashboards even through api as well, but they cannot load.

Setup

cl5:~ # cat /srv/pillar/ceph/proposals/policy.cfg role-master/cluster/cl5.opn.shft.sls role-admin/cluster/.sls cluster-ceph/cluster/.sls role-prometheus/cluster/.sls role-grafana/cluster/.sls role-mon/cluster/.sls role-mgr/cluster/.sls role-mds/cluster/.sls role-igw/cluster/.sls role-rgw/cluster/.sls role-ganesha/cluster/.sls role-openattic/cluster/.sls config/stack/default/global.yml config/stack/default/ceph/cluster.yml profile-default/cluster/.sls profile-default/stack/default/ceph/minions/*.yml cl5:~ #

Steps to Reproduce Issue

cl5:~ # journalctl -xefu grafana-server.service -xefu apache2.service -xefu openattic-systemd.service Mar 29 21:10:00 cl5 grafana-server[137366]: t=2019-03-29T21:10:00+0430 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/dashboard/db/ceph-cluster status=301 remote_addr=127.0.0.1 time_ms=82 size=61 referer=http://xxx.xxx.xxx.xxx/openattic/

cl5:~ # tailf /var/log/grafana/grafana.log t=2019-03-29T21:07:35+0430 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/dashboard/db/ceph-cluster status=301 remote_addr=127.0.0.1 time_ms=80 size=61 referer=http://xxx.xxx.xxx.xxx/openattic/

cl5:~ # tailf /var/log/apache2/error_log [Fri Mar 29 18:27:03.398716 2019] [wsgi:error] [pid 137419] Reading settings from /etc/sysconfig/openattic

cl5:~ # tailf /var/log/openattic/openattic.log 2019-03-29 14:57:03,927 137419 mod_wsgi INFO root#get_django_app_modules - Loaded restapi modules: ifconfig.restapi, userprefs.restapi, cmdlog.restapi, rest.restapi, ceph.restapi, ceph_deployment.restapi, taskqueue.restapi

Versions Report

cl5:~ # salt-run deepsea.version 0.8.9+git.0.c638bee79 cl5:~ # rpm -qi salt-minion Name : salt-minion Version : 2016.11.4 Release : 8.1 Architecture: x86_64 Install Date: Mon Mar 25 12:31:18 2019 Group : System/Management Size : 37807 License : Apache-2.0 Signature : RSA/SHA256, Mon Aug 7 15:31:24 2017, Key ID b88b2fd43dbdc284 Source RPM : salt-2016.11.4-8.1.src.rpm Build Date : Mon Aug 7 15:30:15 2017 Build Host : cloud125 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://saltstack.org/ Summary : The client component for Saltstack Description : Salt minion is queried and controlled from the master. Listens to the salt master and execute the commands. Distribution: openSUSE Leap 42.3 cl5:~ # rpm -qi salt-master Name : salt-master Version : 2016.11.4 Release : 8.1 Architecture: x86_64 Install Date: Mon Mar 25 12:31:18 2019 Group : System/Management Size : 1662854 License : Apache-2.0 Signature : RSA/SHA256, Mon Aug 7 15:31:24 2017, Key ID b88b2fd43dbdc284 Source RPM : salt-2016.11.4-8.1.src.rpm Build Date : Mon Aug 7 15:30:15 2017 Build Host : cloud125 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://saltstack.org/ Summary : The management component of Saltstack with zmq protocol supported Description : The Salt master is the central server to which all minions connect. Enabled commands to remote systems to be called in parallel rather than serially. Distribution: openSUSE Leap 42.3 cl5:~ #

Thanks Untitled Untitled1 Untitled2 Untitled4