Bug 1228554

Summary:	28 role resource types could not be submitted
Product:	Red Hat Satellite	Reporter:	Dirk Herrmann <dherrman>
Component:	Users & Roles	Assignee:	Shimon Shtein <sshtein>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tazim Kolhar <tkolhar>
Severity:	high	Docs Contact:
Priority:	high
Version:	Unspecified	CC:	bbuckingham, bkearney, cwelton, katello-qa-list, mtaru, ohadlevy, tkolhar
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-12 13:56:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dirk Herrmann 2015-06-05 07:43:29 UTC

Description of problem:

If you select one of them and then select one or more permissions and click submit nothing happens. The following resource types are affected:

Miscellaneous
Bookmark
Foreman tasks/task
Parameter
Puppet class
Report 
Trend
Architecture
Audited/adapters/active record/audit
Auth Source ldap
User Groups
Report
Operating System
Common Parameter
E-Mail Notification
External Usergroups
Fact Value
Host Class
Image
Config Groups
Model
Organization
Partition Table
Compute Profile
Role
Location
Lookup Key
Trend


Version-Release number of selected component (if applicable):

Satellite 6.1 Beta

How reproducible:

Go to Administer, Role, create a new role and add filters of the resource types mentioned above.

Steps to Reproduce:
1.
2.
3.

Actual results:

Nothing happens if I click submit, permission sets not applied to this role.

Expected results:

After clicking submit the permissions are added to this role.

Additional info:

Comment 1 RHEL Program Management 2015-06-05 07:48:24 UTC

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.

Comment 10 Tazim Kolhar 2015-06-11 10:26:18 UTC

VERIFIED:
 rpm -qa  | grep foreman
ruby193-rubygem-foreman_discovery-2.0.0.15-1.el7sat.noarch
foreman-libvirt-1.7.2.27-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
hp-ml150g6-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
ruby193-rubygem-foreman_docker-1.2.0.14-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
foreman-compute-1.7.2.27-1.el7sat.noarch
foreman-gce-1.7.2.27-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.2.0-8.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch
foreman-debug-1.7.2.27-1.el7sat.noarch
foreman-vmware-1.7.2.27-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.8-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.7-1.el7sat.noarch
foreman-proxy-1.7.2.5-1.el7sat.noarch
hp-ml150g6-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
hp-ml150g6-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch
foreman-ovirt-1.7.2.27-1.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-1.7.2.27-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
foreman-postgresql-1.7.2.27-1.el7sat.noarch



steps:
1. Administer -> Roles -> New Role
2. Filters tab says I have to save it first.
3. Clicked Submit
4. Found the new role, and clicked Filters.
5. Click New filter
6. Selected resource type "puppet class"
7. clicked on edit_puppetclasses, destroy_puppetclasses, import_puppetclasses
8. the items moved to the right list
9. Clicked Submit
10. Selected the role again
11. all filters appear in the table.

Comment 11 Dirk Herrmann 2015-06-11 16:27:49 UTC

Tested today again using Snap8 and all my roles are working and are documented. I will open new BZs for hammer (only IDs work) and filter (regexp works with ~ but not ^).

Comment 12 Bryan Kearney 2015-08-11 13:20:14 UTC

This bug is slated to be released with Satellite 6.1.

Comment 13 Bryan Kearney 2015-08-12 13:56:25 UTC

This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.