Bug 1410502
Summary: | Host group selection on a discovery host should work without "edit_hosts" permission. | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Sean O'Keeffe <sokeeffe> |
Component: | Discovery Plugin | Assignee: | Lukas Zapletal <lzap> |
Status: | CLOSED ERRATA | QA Contact: | Daniel Lobato Garcia <dlobatog> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2.6 | CC: | bbuckingham, bkearney, dlobatog, ehelms, jcallaha |
Target Milestone: | Unspecified | Keywords: | Reopened, Triaged, ZStream |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://projects.theforeman.org/issues/17943 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 16:51:07 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
Sean O'Keeffe
2017-01-05 15:48:43 UTC
Sean, Discovery manager role is what you need. Permissions are fine-grained objects that are atteched to specific resources. Discovery provisioning is a complex task with many resources involved. I am going to close this. Note in both 6.2 and 6.3 we had fixes around Discovery roles, latest stable version should work ok. Ok now I understand. Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17943 has been resolved. Verified. Version Tested: Satellite-6.3 Snap 12 I created an user with the "Discovery manager" role exclusively, then tried to provision a discovered host using this user. In the form, I chose a host group which triggered the process_hostgroup action without any permission errors. The fields were filled according to the Host group information. 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-2018:0336
|