Bug 1281350
Summary: | None admin users cant do bulk actions on hosts | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Kamudini Gazdikova <kshirsal> |
Component: | Provisioning | Assignee: | Katello Bug Bin <katello-bugs> |
Status: | CLOSED ERRATA | QA Contact: | Corey Welton <cwelton> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1.3 | CC: | bbuckingham, chpeters, cwelton, daobrien, tkolhar |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://projects.theforeman.org/issues/12452 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Non admin users were blocked from performing bulk actions on hosts. This restriction was removed.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-01-21 07:42:38 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: | |||
Bug Depends On: | 1215659, 1296877 | ||
Bug Blocks: |
Description
Kamudini Gazdikova
2015-11-12 11:08:56 UTC
Upstream bug component is Provisioning Moving to POST since upstream bug http://projects.theforeman.org/issues/12452 has been closed ------------- Alon Goldboim Applied in changeset commit:935bc248287083b57c1c2bdf68e59c5a0035a4af. this bz is still failing: # hammer -u admin -p changeme host create --medium-id 7 --root-pass dog8code --organization-id 1 --location-id 1 --architecture-id 1 --operatingsystem-id 2 --name test6 --environment-id 2 --compute-resource-id 1 --domain-id 1 --puppet-proxy-id 1 --partition-table-id 7 --hostgroup host_test_grp Could not create the host: Failed to create a compute comp_resource (Libvirt) instance test6.rhts.englab.brq.redhat.com: can't convert nil into String # rpm -qa | grep foreman dell-pe-sc1435-02.rhts.englab.brq.redhat.com-foreman-proxy-1.0-1.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch foreman-vmware-1.7.2.50-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.5-1.el7sat.noarch foreman-ovirt-1.7.2.50-1.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch foreman-1.7.2.50-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.24-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.15.7-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.10-1.el7sat.noarch foreman-debug-1.7.2.50-1.el7sat.noarch foreman-proxy-1.7.2.8-1.el7sat.noarch foreman-postgresql-1.7.2.50-1.el7sat.noarch dell-pe-sc1435-02.rhts.englab.brq.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-libvirt-1.7.2.50-1.el7sat.noarch foreman-gce-1.7.2.50-1.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.15-1.el7sat.noarch dell-pe-sc1435-02.rhts.englab.brq.redhat.com-foreman-client-1.0-1.noarch ruby193-rubygem-foreman_discovery-2.0.0.23-1.el7sat.noarch foreman-selinux-1.7.2.17-1.el7sat.noarch foreman-compute-1.7.2.50-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.2.4-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.14-1.el7sat.noarch I think we can mark this verified in 6.1.6 compose #5 * I created a user, 'hostuser' which has only access to view/edit hosts - this user does not have any admin rights. * In hostuser's organization, I selected a variety of systems and performed a bulk action (Select Action > Delete Hosts) result: 4 tasks, 4 success, 0 fail Subtasks: Destroy Host stopped success 2016-01-15 23:33:52 UTC 2016-01-15 23:33:53 UTC hostuser Destroy Host stopped success 2016-01-15 23:33:53 UTC 2016-01-15 23:33:53 UTC hostuser Destroy Host stopped success 2016-01-15 23:33:53 UTC 2016-01-15 23:33:53 UTC hostuser Destroy Host stopped success 2016-01-15 23:33:52 UTC 2016-01-15 23:33:53 UTC hostuser Hi, this worked for me too for sat6.1.6 compose 5: # rpm -qa | grep foreman hp-dl180g6-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch foreman-vmware-1.7.2.50-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.5-1.el7sat.noarch foreman-selinux-1.7.2.17-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.14-1.el7sat.noarch foreman-ovirt-1.7.2.50-1.el7sat.noarch foreman-1.7.2.50-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.24-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.15.7-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.10-1.el7sat.noarch foreman-debug-1.7.2.50-1.el7sat.noarch foreman-proxy-1.7.2.8-1.el7sat.noarch hp-dl180g6-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch hp-dl180g6-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-discovery-image-3.0.5-3.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch foreman-libvirt-1.7.2.50-1.el7sat.noarch foreman-gce-1.7.2.50-1.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.15-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.23-1.el7sat.noarch foreman-postgresql-1.7.2.50-1.el7sat.noarch foreman-compute-1.7.2.50-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.2.4-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch 2 tasks, 2 success, 0 fail SubTasks Action State Result Started at Ended at User Destroy Host stopped success 2016-01-16 14:45:34 UTC 2016-01-16 14:45:50 UTC testuser Destroy Host stopped success 2016-01-16 14:45:36 UTC 2016-01-16 14:45:54 UTC testuser Thanks and Regards, Tazim If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format: Cause: Consequence: Fix: Result: The documentation team will review, edit, and approve the text. If this bug does not require doc text, please set the 'requires_doc_text' flag to -. 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/RHBA-2016:0052 |