This happens if the dashboard was created with a custom topic in 2.0 (and time specific dashlets like performance graphs).
Fix is currently in review and will be included in the next patch release
Possible workaround is to change the topic of the affected dashboard to a builtin topic and run “cmk-update-config” as site user again. The dashboard should be ok after that and you can change back to the custom topic