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.

Bug 1436139

Summary: [RFE] Add custom-hierra.yaml to the foreman-debug
Product: Red Hat Satellite Reporter: Marcel Gazdík <mgazdik>
Component: Foreman DebugAssignee: Lukas Zapletal <lzap>
Status: CLOSED ERRATA QA Contact: Ales Dujicek <adujicek>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.8CC: adujicek, bkearney, jcallaha
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 Marcel Gazdík 2017-03-27 09:41:42 UTC
Description of problem:
  When there are any changes in the /etc/foreman-installer/custom-hiera.yaml it should be included in foreman-debug. This will help the person analyzing the logs pinpoint changes quicker and easier way than going through each configuration file of every single service managed by installer / required by satellite.

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

Actual results:
  /etc/foreman-installer/custom-hiera.yaml is not included

Expected results:
  /etc/foreman-installer/custom-hiera.yaml will be included

Additional info:
  https://bugzilla.redhat.com/show_bug.cgi?id=1305782

Comment 1 Satellite Program 2017-03-27 13:32:59 UTC
Created redmine issue http://projects.theforeman.org/issues/19036 from this bug

Comment 2 Lukas Zapletal 2017-03-27 13:40:11 UTC
Can you attach an example file? I want to make sure we filter out passwords from it, it may contain sensitive data. Not eligible for 6.2 backport tho.

Comment 3 Satellite Program 2017-03-27 14:07:42 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19036 has been resolved.

Comment 5 Satellite Program 2017-06-01 20:35:32 UTC
11405401

Comment 7 Bryan Kearney 2018-02-21 17:33:00 UTC
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-2018:0336

Comment 8 Bryan Kearney 2018-02-21 17:33:16 UTC
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-2018:0336