Project

General

Profile

Actions
Copy link

Bug #14592

closed

Reports not viewable altought permissions granted

Added by Robert Heinzmann over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Users, Roles and Permissions
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hello,

a role with the permissions:

  • destroy_reports
  • view_reports
  • upload_reports

Has no permissions to view reports of a host:

See screenshot attached

Version: 1.11.1

Files

screenshot 01.png View screenshot 01.png 4.26 KB Robert Heinzmann, 04/12/2016 08:34 AM
Actions
Copy link
 #1

Updated by Dominic Cleal over 8 years ago

  • Category set to Users, Roles and Permissions
  • Status changed from New to Need more information

Please confirm the version of Foreman you are using, we haven't released 1.11.1. There was a similar issue fixed during the release candidates, so ensure you are on 1.11.0.

I can't reproduce it at the moment on develop, so please attach production.log with permissions and SQL debugging enabled: http://theforeman.org/manuals/1.11/index.html#7.2Debugging

Actions
Copy link
 #2

Updated by Dominic Cleal over 8 years ago

Oh, something else - the permissions should be called view_config_reports, not view_reports. Please check the list of available permissions, and try running foreman-rake db:migrate and foreman-rake db:seed again.

Actions
Copy link
 #3

Updated by Robert Heinzmann over 8 years ago

We are running Foreman 1.11

I added the following permissions of group "ConfigReport" and now it works. 

163 | view_config_reports            | ConfigReport
  164 | destroy_config_reports         | ConfigReport
  165 | upload_config_reports          | ConfigReport

However, is "ConfigReport" a replacement for "Report" ?

It seems ConfigReport is a new config option in 1.11, is that right ?

So, using the right permissions solved the issue.

Actions
Copy link
 #4

Updated by Dominic Cleal over 8 years ago

  • Status changed from Need more information to Resolved

Yes, ConfigReport replaces Report, however it should have been renamed during the DB migration from 1.10 to 1.11, so something went wrong. The old Report/view_reports permissions should no longer exist.

The logs from the DB migration may show, if they happened to be stored somewhere - the 20150728122736 (Change report permissions) migration should have changed it.

Glad it's sorted anyway, I'll close this for now.

Actions
Copy link

Also available in: Atom PDF