Bug #39374
Updated by Yusuke Hirota about 1 month ago
*Summary:* hammer host boot fails with unknown parent permission error when organization_id/location_id is specified *Description:* When running hammer host boot with taxonomy context (organization_id / location_id), the authorization process enters a taxonomy-scoped path and attempts to resolve the parent permission for api/v2/hosts#ipmi_boot. This fails due to a missing or inconsistent parent permission mapping, causing the request to abort before reaching normal processing. A fix is being prepared and will be submitted as a separate PR. *Steps to Reproduce:* # Prepare a host with BMC available (e.g. host id 3). # Run with taxonomy parameters: <pre><code class="shell"> hammer host boot --id 3 --device bios --organization-id 1 --location-id 2 </code></pre> # For comparison, run without taxonomy parameters: <pre><code class="shell"> hammer host boot --id 3 --device bios </code></pre> # Confirm that step 2 fails with a permission error and step 3 succeeds. *Actual Behavior:* When organization_id / location_id is specified, the command fails with: <pre> ERF42-5227 [Foreman::Exception]: unknown parent permission for api/v2/hosts#ipmi_boot </pre> *Expected Behavior:* hammer host boot should succeed regardless of whether taxonomy parameters are provided, as long as the user has the necessary permissions and BMC is configured correctly.