Project

General

Profile

Actions

Bug #39374

open

Specifying organization_id/location_id in hammer host boot causes ERF42-5227 unknown parent permission error

Added by Yusuke Hirota 19 days ago. Updated 12 days ago.

Status:
Ready For Testing
Priority:
Normal
Assignee:
Category:
BMC
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

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:

  1. Prepare a host with BMC available (e.g. host id 3).
  2. Run with taxonomy parameters:
    hammer host boot --id 3 --device bios --organization-id 1 --location-id 2
    
  3. For comparison, run without taxonomy parameters:
    hammer host boot --id 3 --device bios
    
  4. 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:

ERF42-5227 [Foreman::Exception]: unknown parent permission for api/v2/hosts#ipmi_boot

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.

Actions #1

Updated by Yusuke Hirota 17 days ago

  • Description updated (diff)
Actions #2

Updated by The Foreman Bot 12 days ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/11012 added
Actions

Also available in: Atom PDF