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:
QE's test suite should be updated with a reference to this bug shortly. See: https://github.com/SatelliteQE/robottelo/pull/1966
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
In fact permissions are only limited to have unique names per resource_type. What you found here is one of several permissions added by foreman-docker plugin without setting resource_type - note that the second permission has resource_type: None.
Created redmine issue http://projects.theforeman.org/issues/9837 from this bug
This has been fixed upstream in foreman_docker by https://github.com/theforeman/foreman-docker/pull/88 Moving to POST.
VERIFIED : rpm -qa | grep foreman ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.9-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.3-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el7sat.noarch foreman-debug-1.7.2.17-1.el7sat.noarch foreman-libvirt-1.7.2.17-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.10-1.el7sat.noarch foreman-compute-1.7.2.17-1.el7sat.noarch foreman-ovirt-1.7.2.17-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el7sat.noarch foreman-postgresql-1.7.2.17-1.el7sat.noarch qe-sat6-rhel71.usersys.redhat.com-foreman-client-1.0-1.noarch qe-sat6-rhel71.usersys.redhat.com-foreman-proxy-1.0-1.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch foreman-1.7.2.17-1.el7sat.noarch foreman-gce-1.7.2.17-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.9-1.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.9-1.el7sat.noarch foreman-vmware-1.7.2.17-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.7-1.el7sat.noarch foreman-proxy-1.7.2.4-1.el7sat.noarch qe-sat6-rhel71.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch steps: 1. Search for a permission named 'power_compute_resources_vms' >>> 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}]
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.