We're using cephadm with all 5 nodes on 16.2.6. Until today,
grafana has been running only on ceph05.
Before the 16.2.6 update, the embedded frames would pop up an expected security error for self-signed certificates, but after accepting would work. After the 16.2.6 update, the frames still pop up the cert warning, but then after accepting it instead of seeing graphs I now get orange text that simply states:
If you're
seeing this Grafana has failed to load its application files
2. If you host grafana under subpath make sure your grafana.ini root_url setting includes subpath
3. If you have a local dev build make sure you build frontend using: yarn start, yarn start:hot, or yarn build
4. Sometimes restarting grafana-server can help
I have restarted grafana with ceph orch stop/start grafana commands - worked, but no change.
I deleted the grafana daemon entirely from the cluster, then
recreated it and cephadm placed it on ceph01. Dashboard required a
disable/enable in order for the new IP address to start being
used, but after that, same error message.
Grafana is functional and accessible when accessed directly at
ceph01:3000 and the command ceph dashboard
get-grafana-api-ssl-verify is showing https://IP:3000 as expected.
I've made no modifications from whatever cephadm has as its default grafana/prometheus containerized daemon settings; this problem only started showing up after a completely ordinary upgrade from 16.2.5 to 16.2.6.
Searching "If you're seeing this Grafana has failed to load its application files" with "ceph" query doesn't yield much. We are not using a reverse proxy AFAIK.
Thanks for any insight you might have,
-Zach
_______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
