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
Created redmine issue http://projects.theforeman.org/issues/19036 from this bug
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.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19036 has been resolved.
11405401
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