PMM grafana dashboards not upgrading

Percona Monitoring and Management (PMM) PMM 1.x
1
  • Dashboards upgrade from version 1.1.5 to 1.2.2.
  • Waiting for Grafana to start
    200 [{“id”:2,“orgId”:1,“name”:“CloudWatch”,“type”:“cloudwatch”,“typeLogoUrl”:“public/app/plugins/datasource/cloudwatch/img/amazon-web-services.png”,“access”:“proxy”,“url”:“”,“password”:“”,“user”:“”,“database”:“”,“basicAuth”:false,“isDefault”:false,“jsonData”:“{“defaultRegion”:“us-east-1”}”},{“id”:1,“orgId”:1,“name”:“Prometheus”,“type”:“prometheus”,“typeLogoUrl”:“public/app/plugins/datasource/prometheus/img/prometheus_logo.svg”,“access”:“proxy”,“url”:“http://127.0.0.1:9090/prometheus/“,“password”:”“,“user”:”“,“database”:”",“basicAuth”:false,“isDefault”:true,"jsonData”:{}}]
    /usr/share/percona-dashboards/dashboards/Disk_Performance.json
    500 {“message”:“Failed to save dashboard”}
  • Cannot add /usr/share/percona-dashboards/dashboards/Disk_Performance.json Dashboard
2

can you enter inside PMM instance and run the following commands manually?

df -h
/usr/share/percona-dashboards/import-dashboards.py $(dirname $(ls /srv/grafana/grafana.db /var/lib/grafana/grafana.db 2>/dev/null))
3 
[root@2cb147402356 opt]# df -h
Filesystem Size Used Avail Use% Mounted on
none 2.4T 351G 1.9T 16% /
tmpfs 48G 0 48G 0% /dev
tmpfs 48G 0 48G 0% /sys/fs/cgroup
/dev/sdb 2.4T 351G 1.9T 16% /etc/hosts
shm 64M 0 64M 0% /dev/shm
/dev/sda2 97G 6.1G 86G 7% /etc/grafana/ldap.toml
tmpfs 48G 0 48G 0% /sys/firmware
[root@2cb147402356 opt]# /usr/share/percona-dashboards/import-dashboards.py $(dirname $(ls /srv/grafana/grafana.db /var/lib/grafana/grafana.db 2>/dev/null))
* Dashboards upgrade from version 1.1.5 to 1.2.2.
* Waiting for Grafana to start
200 [{"id":2,"orgId":1,"name":"CloudWatch","type":"cloudwatch","typeLogoUrl":"public/app/plugins/datasource/cloudwatch/img/amazon-web-services.png","access":"proxy","url":"","password":"","user":"","database":"","basicAuth":false,"isDefault":false,"jsonData":"{\"defaultRegion\":\"us-east-1\"}"},{"id":1,"orgId":1,"name":"Prometheus","type":"prometheus","typeLogoUrl":"public/app/plugins/datasource/prometheus/img/prometheus_logo.svg","access":"proxy","url":"http://127.0.0.1:9090/prometheus/","password":"","user":"","database":"","basicAuth":false,"isDefault":true,"jsonData":{}}]
/usr/share/percona-dashboards/dashboards/Disk_Performance.json
500 {"message":"Failed to save dashboard"}
* Cannot add /usr/share/percona-dashboards/dashboards/Disk_Performance.json Dashboard
[root@2cb147402356 opt]#
4 
t=2017-10-10T18:22:52+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=1 uname= method=GET path=/api/datasources status=403 remote_addr=127.0.0.1 time_ms=1 size=31 referer=
t=2017-10-10T18:22:52+0000 lvl=eror msg="Failed to save dashboard" logger=context userId=0 orgId=1 uname= error="UNIQUE constraint failed: dashboard_version.dashboard_id, dashboard_version.version"
5

While not ideal, since I did not have any custom dashboards, I moved the grafana db to the side and allowed it to create a new one. I am interested in figuring out why this happened though.