Bug 1656955
Summary: | hammer host stop results in unknown parent permission | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Ryan Kimbrell <ryan.e.kimbrell> |
Component: | Hosts | Assignee: | Marek Hulan <mhulan> |
Status: | CLOSED ERRATA | QA Contact: | tstrych |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4.0 | CC: | abakshi, apatel, egolov, inecas, mhulan, pdragun |
Target Milestone: | 6.6.0 | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | foreman-1.21.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-22 19:48:05 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
Ryan Kimbrell
2018-12-06 18:03:20 UTC
Created redmine issue https://projects.theforeman.org/issues/25745 from this bug This happens for any compute resource. The reason is that hammer has default org set, so it uses /organization/x/host/y route and we don't have mapping between power action permission and parent resource permission. The fix is to add mapping to check "view_organizations" on org x for such call. Workaround is to use admin account or don't specify org id at all (remove hammer defaults) Upstream bug assigned to mhulan Upstream bug assigned to mhulan I wanted to add that we are executing the hammer commands as the default Satellite admin, but we do have a default org set. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25745 has been resolved. Verified Verified on: Satellite 6.6.0 snap 7 Steps: 1. Use VMware ESXi 6.7 as a compute resource 2. Create a VM as a managed host. 3. Execute `hammer host stop --id <ID>` Observation: Host Powered Off successfully Terminal Output: -bash-4.2# hammer host list ---|------------------------------------------|------------------|------------|-----------------|-------------------|---------------|--------------|---------------------- ID | NAME | OPERATING SYSTEM | HOST GROUP | IP | MAC | GLOBAL STATUS | CONTENT VIEW | LIFECYCLE ENVIRONMENT ---|------------------------------------------|------------------|------------|-----------------|-------------------|---------------|--------------|---------------------- 4 | cloud-qe-04.idmqe.lab.eng.bos.redhat.com | RedHat 7.5 | | 10.19.34.31 | 34:40:b5:89:06:16 | Error | RHEL 7 CV | DEV 3 | demohost | RHEL Server 7.6 | | | | Error | RHEL 7 CV | DEV 1 | lenovo-st550-01.ml3.eng.bos.redhat.com | RHEL Server 7.6 | | 10.19.176.55 | f0:76:1c:9d:92:94 | OK | | 5 | otto-abedi.ml3.eng.bos.redhat.com | RHEL Server 7.6 | test | 192.168.100.185 | 00:50:56:be:e6:2c | OK | RHEL 7 CV | Library 2 | test1.ml3.eng.bos.redhat.com | RHEL Server 7.6 | | 192.168.100.120 | f0:76:1c:9d:92:90 | Error | | ---|------------------------------------------|------------------|------------|-----------------|-------------------|---------------|--------------|---------------------- -bash-4.2# hammer host stop --id 5 Powering the host off 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-2019:3172 |