Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
We have are using a fact called "foreman_hostgroup" that determines to which hostgroup a server has to be provisioned. Currently the facts map matching in the default_hostgroup plugin can allow such looking for a custom fact name. But it does not support to replace fact values inside the hostgroup key.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Install and configure the foreman_hostgroup plugin to match foreman_hostgroup
---
:default_hostgroup:
:facts_map:
"%{foreman_hostgroup}":
"foreman_hostgroup": ".*"
2. Client: Create a fact foreman_hostgroup "Dummy"
3. Client: Run puppet on the client
Actual results:
Hostgroup will be called %{foreman_hostgroup} instead Dummy
Expected results:
Client registered to Hostgroup called Dummy
Additional info:
See BZ1127164 and Foreman #6952 for the original request in the core foreman code.
Comment 1RHEL Program Management
2015-03-03 20:19:20 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Description of problem: We have are using a fact called "foreman_hostgroup" that determines to which hostgroup a server has to be provisioned. Currently the facts map matching in the default_hostgroup plugin can allow such looking for a custom fact name. But it does not support to replace fact values inside the hostgroup key. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install and configure the foreman_hostgroup plugin to match foreman_hostgroup --- :default_hostgroup: :facts_map: "%{foreman_hostgroup}": "foreman_hostgroup": ".*" 2. Client: Create a fact foreman_hostgroup "Dummy" 3. Client: Run puppet on the client Actual results: Hostgroup will be called %{foreman_hostgroup} instead Dummy Expected results: Client registered to Hostgroup called Dummy Additional info: See BZ1127164 and Foreman #6952 for the original request in the core foreman code.