Bug 1476186 - New permission on upgraded setup and not on freshly installed box
New permission on upgraded setup and not on freshly installed box
Status: NEW
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Upgrades (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: Unspecified
: --
Assigned To: satellite6-bugs
Katello QA List
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-07-28 04:31 EDT by Sanket Jagtap
Modified: 2018-06-24 01:21 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sanket Jagtap 2017-07-28 04:31:16 EDT
Description of problem:

Version-Release number of selected component (if applicable):
Satellite 6.1.12 was upgraded to satellite 6.2.11 snap2

2017-07-25 17:56:14 - robottelo.ssh - INFO - >>> rpm -qa | grep rubygem-foreman_openscap
2017-07-25 17:56:17 - robottelo.ssh - INFO - <<< stdout

How reproducible:

nailgun.client - DEBUG - Making HTTP GET request to https://satellite.com/api/v2/permissions with options {'verify': False, 'data': '{"per_page": 1000}', 'auth': ('admin', 'changeme'), 'headers': {'content-type': 'application/json'}} and no data.
2017-07-24 11:20:07 - nailgun.client - DEBUG - Received HTTP 200 response: {
  "total": 272,
  "subtotal": 272,
  "page": 1,
  "per_page": 1000,
  "search": null,
  "sort": {
    "by": null,
    "order": null
  "results": [{"name":"edit_compliance","id":238,"resource_type":null}.......,..,.,.

There is no such permission on the freshly installed box.

Actual results:
E   AssertionError: {
E    "added_names": [
E     "edit_compliance"
E    ]
E   }

Expected results:
This should also be exposed on freshly installed box 

Additional info:

Note You need to log in before you can comment on or make changes to this bug.