Project

General

Profile

Actions

Bug #9837

closed

power_compute_resources_vms permission is listed twice

Added by Tomer Brisker about 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1198731
Description of problem:
To the best of my knowledge, each permission should be uniquely named. Unfortunately, there are two permissions named "power_compute_resources_vms". For example:

>>> from robottelo import entities
>>> entities.Permission(name='power_compute_resources_vms').search()
[ {
u'name': u'power_compute_resources_vms',
u'resource_type': u'ComputeResource',
u'id': 26,
}, {
u'name': u'power_compute_resources_vms',
u'resource_type': None,
u'id': 166,
},
]

Version-Release number of selected component (if applicable):
Tested against Version 1.9.0-develop and Satellite-6.1.0-RHEL-7-20150303.0.

How reproducible:
100%

Steps to Reproduce:
1. Search for a permission named 'power_compute_resources_vms'

Actual results:
Two permissions.

Expected results:
One permission.

Additional info:


Related issues 1 (0 open1 closed)

Related to Docker - Bug #9338: Cannot create a filter with container permissionsClosed02/11/2015Actions
Actions #1

Updated by Tomer Brisker about 9 years ago

Docker plugin registers it's permissions without setting resource_type for them.
One of the permissions, power_compute_resources_vms, also appears in foreman-core with resource_type = "ComputeResource".

Actions #2

Updated by Tomer Brisker about 9 years ago

  • Related to Bug #9338: Cannot create a filter with container permissions added
Actions #3

Updated by Tomer Brisker about 9 years ago

  • Status changed from New to Resolved

Fixed by #9338.

Actions

Also available in: Atom PDF