Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionStephen Wadeley
2020-01-17 14:28:02 UTC
Description of problem:
In 6.7 snap 8, "hammer role create" now assigns "Default Location" by default. It does not do that in Sat6.6.1
Attempting to create a filter for a role fails with error:
Could not create the permission filter:
Location ids You can't assign locations to this resource
Version-Release number of selected component (if applicable):
[root@dhcp-3-165 ~]# rpm -q tfm-rubygem-hammer_cli_katello
tfm-rubygem-hammer_cli_katello-0.20.2.1-1.el7sat.noarch
[root@dhcp-3-165 ~]# rpm -q satellite
satellite-6.7.0-5.beta.el7sat.noarch
[root@dhcp-3-165 ~]#
How reproducible:
every time
Steps to Reproduce:
[root@dhcp-3-165 ~]# hammer role create --name test
~]# hammer filter create --permissions="view_activation_keys,create_activation_keys,edit_activation_keys,destroy_activation_keys" --role-id=32
Could not create the permission filter:
Location ids You can't assign locations to this resource
[root@dhcp-3-165 ~]# hammer role info --name test
Id: 32
Name: test
Builtin: no
Description:
Locations:
Default Location
[root@dhcp-3-165 ~]# hammer role create --name test2
User role [test2] created.
[root@dhcp-3-165 ~]# hammer role info --name test2
Id: 33
Name: test2
Builtin: no
Description:
Locations:
Default Location
Actual results:
Could not create the permission filter
Expected results:
hammer filter can be created
Additional info:
Bug 1778945 - Hammer filter create fails if default organization is set.
Tested on Satellite 6.7 Snap 16 (foreman-1.24.1.19-1) using the reproducer script from the original report.
./roles_permission_locations_bug.sh
Organization created.
User role [NonAdminSubscriptionViewer] created.
Permission filter for [Organization] created.
See the attached file hammer-ok.out for the hammer debug output.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:1454
Description of problem: In 6.7 snap 8, "hammer role create" now assigns "Default Location" by default. It does not do that in Sat6.6.1 Attempting to create a filter for a role fails with error: Could not create the permission filter: Location ids You can't assign locations to this resource Version-Release number of selected component (if applicable): [root@dhcp-3-165 ~]# rpm -q tfm-rubygem-hammer_cli_katello tfm-rubygem-hammer_cli_katello-0.20.2.1-1.el7sat.noarch [root@dhcp-3-165 ~]# rpm -q satellite satellite-6.7.0-5.beta.el7sat.noarch [root@dhcp-3-165 ~]# How reproducible: every time Steps to Reproduce: [root@dhcp-3-165 ~]# hammer role create --name test ~]# hammer filter create --permissions="view_activation_keys,create_activation_keys,edit_activation_keys,destroy_activation_keys" --role-id=32 Could not create the permission filter: Location ids You can't assign locations to this resource [root@dhcp-3-165 ~]# hammer role info --name test Id: 32 Name: test Builtin: no Description: Locations: Default Location [root@dhcp-3-165 ~]# hammer role create --name test2 User role [test2] created. [root@dhcp-3-165 ~]# hammer role info --name test2 Id: 33 Name: test2 Builtin: no Description: Locations: Default Location Actual results: Could not create the permission filter Expected results: hammer filter can be created Additional info: Bug 1778945 - Hammer filter create fails if default organization is set.