Project

General

Profile

Actions

Bug #15599

closed

Unattended controller can't access host parameters in kickstart templates

Added by Ori Rabin over 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Users, Roles and Permissions
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1351766
Description of problem:

The latest downstream Foreman release added some permissions checks to inherited parameter lookups for managed hosts. This breaks our (QCI) deployments, as the host is not be able to find an associated activation key (inherited from the hostgroup), will not register with subscription-manager (snippet is conditional on activation key in the kickstart), and will fail to install or configure puppet. The BZ that prompted the breaking change is https://bugzilla.redhat.com/show_bug.cgi?id=1296662 . The UI shows the

Version-Release number of selected component (if applicable):
6.2.0

How reproducible:
100%

Steps to Reproduce:
1. Create a hostgroup
2. Add parameters to that hostgroup
3. Convert a discovered host to a managed host.
4. From the rails console, load up the hostgroup and host
5. Set the host's hostgroup to the newly created one and save the host
6. Check host.params

Actual results:
An empty dictionary

Expected results:
Consistent with previous behavior and the web UI, you would see the parameters that the host inherited from the hostgroup.

Additional comments:
Even though the WebUI shows the inherited parameters correctly, and checking the generated kickstart looks correct, when we actually trigger a build on the host, the kickstart it gets does not have access to any of the host's inherited parameters, consistent with the behavior on the console.


Related issues 3 (0 open3 closed)

Related to Foreman - Bug #13164: view_params is missingClosedOri Rabin01/12/2016Actions
Related to Foreman Remote Execution - Bug #13689: The ssh keys bootstrap provisioning snippet doesn't work with global proxiesClosedIvan Necas02/12/2016Actions
Related to Foreman - Bug #17395: @host.params are not interpreted when was used in ptable kickstart template.ClosedDominic Cleal11/18/2016Actions
Actions #1

Updated by Ori Rabin over 7 years ago

  • Subject changed from Can't access inherited parameters from host to Unattended controller can't access host parameters in kickstart templates
  • Category changed from Inventory to Parameters
  • Status changed from New to Assigned
  • Assignee set to Ori Rabin
Actions #2

Updated by Dominic Cleal over 7 years ago

  • Related to Bug #13164: view_params is missing added
Actions #3

Updated by Dominic Cleal over 7 years ago

  • Category changed from Parameters to Users, Roles and Permissions
  • translation missing: en.field_release set to 160
Actions #4

Updated by The Foreman Bot over 7 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/3629 added
Actions #5

Updated by Ivan Necas over 7 years ago

  • Related to Bug #13689: The ssh keys bootstrap provisioning snippet doesn't work with global proxies added
Actions #6

Updated by Ori Rabin over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #7

Updated by Dominic Cleal over 7 years ago

  • Related to Bug #17395: @host.params are not interpreted when was used in ptable kickstart template. added
Actions

Also available in: Atom PDF