Does that user have the permission to view config reports?
In the role filter ensure that Resource type -> Config reports, view config reports is enabled for that user role.

Yes I made sure that the user's role had view config reports. Initially the role did not have this permission and the user did not even see the Config reports menu item. After adding the "view config reports" filter the menu appeared but this error is received when attempting to view a report.

This foreman server was upgraded from 1.10.0.

Shlomi Zadok wrote:

Does that user have the permission to view config reports?
In the role filter ensure that Resource type -> Config reports, view config reports is enabled for that user role.

Here is the output.

https://gist.github.com/csschwe/ce6024a107fd6f6844cb

This configuration has no proxy servers. Foreman is just being used as a reporting backend at this time.

Could you try running foreman-rake fix_db_cache to rebuild the DB cache of users versus their roles?

Strange that the menu is visible but the page isn't working, but it's possible the former doesn't use the DB cache and that's causing it. The two should obviously be consistent.

Did you provide the view_config_reports permission by adding it to an existing role, adding another role to the user or how exactly?

foreman-rake fix_db_cache did not change anything.

The issue I see is that (permissions.resource_type = 'Report') and it should be (permissions.resource_type = 'ConfigReport')

2016-02-29 14:46:10 [sql] [D]   Filter Load (1.8ms)  SELECT "filters".* FROM "filters" INNER JOIN "filterings" ON "filterings"."filter_id" = "filters"."id" INNER JOIN "permissions" ON "permissions"."id" = "filterings"."permission_id" INNER JOIN "roles" ON "filters"."role_id" = "roles"."id" INNER JOIN "cached_user_roles" ON "roles"."id" = "cached_user_roles"."role_id" WHERE "cached_user_roles"."user_id" = $1 AND (permissions.resource_type = 'Report') AND (permissions.name = 'view_config_reports')  ORDER BY filters.role_id, filters.id  [["user_id", 65]]

Here is the example output by changing Report to ConfigReport

foreman=# SELECT "filters".* FROM "filters" INNER JOIN "filterings" ON "filterings"."filter_id" = "filters"."id" INNER JOIN "permissions" ON "permissions"."id" = "filterings"."permission_id" INNER JOIN "roles" ON "filters"."role_id" = "roles"."id" INNER JOIN "cached_user_roles" ON "roles"."id" = "cached_user_roles"."role_id" WHERE "cached_user_roles"."user_id" = '65' AND (permissions.resource_type = 'Report') AND (permissions.name = 'view_config_reports')  ORDER BY filters.role_id, filters.id ;
 id | search | role_id | created_at | updated_at | taxonomy_search 
----+--------+---------+------------+------------+-----------------
(0 rows)

foreman=# SELECT "filters".* FROM "filters" INNER JOIN "filterings" ON "filterings"."filter_id" = "filters"."id" INNER JOIN "permissions" ON "permissions"."id" = "filterings"."permission_id" INNER JOIN "roles" ON "filters"."role_id" = "roles"."id" INNER JOIN "cached_user_roles" ON "roles"."id" = "cached_user_roles"."role_id" WHERE "cached_user_roles"."user_id" = '65' AND (permissions.resource_type = 'ConfigReport') AND (permissions.name = 'view_config_reports')  ORDER BY filters.role_id, filters.id ;
 id  | search | role_id |        created_at         |        updated_at         | taxonomy_search 
-----+--------+---------+---------------------------+---------------------------+-----------------
 121 |        |      10 | 2016-02-29 14:01:04.56838 | 2016-02-29 14:01:04.56838 | 
(1 row)

The fix for #13545 fixes this too, leaving this open for now.

I confirmed this fixes the issue on my foreman server. Thanks,