Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1807258

Description of problem:

When the customer assigns the Viewer role to a non-admin user, that user can browse to Monitor > Facts to view a list of facts in Foreman. However, when the customer removes the Viewer role from that non-admin user, clones the Viewer role and assigns the new (ostensibly identical) role to that same non-admin user and then logs into Foreman with that user, that user is unable to browse to Monitor > Facts to view a list of facts in Foreman.

Furthermore, simply adding the "view_facts" permission to a new role also fails to grant this access. The built-in Viewer role appears to be the only way to grant non-admin users access to Monitor > Facts in the Foreman web UI.

How reproducible:

100% of the time

Steps to Reproduce:
method 1:
1. clone the viewer role
2. assign the new role to a new user
3. log into satellite as the new user
4. browse to monitor > facts

method 2 (failed workaround):
1. create a new role with permission view_facts
2. assign that role to a new user
3. log into satellite as the new user
4. browse to monitor > facts

Actual results:

The list of facts is empty.

Expected results:

The list of facts should appear the same for the non-admin user with these permissions as it does for an admin user.