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 see the full kickstart template in the log file. While this is potentially nice in order to debug issues, it floods the logs with usually unneeded information.

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


How reproducible: Always.


Steps to Reproduce:
1. Run unattended install/provision
2. Check the foreman logs

Actual results:
Full kickstart template in the log.


Expected results:
Kickstart template shouldn't show up in the log, unless explicitly enabled somewhere for debugging purpose.


Additional info:
Customer case will be linked.

Based upon discussion in triage, this was added based upon customer request.  Switching this one to an RFE to make it configurable.

I think this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1676302

*** This bug has been marked as a duplicate of bug 1676302 ***

Well spotted Peter.
I've closed this with DUPLICATE and attached the RHBZ#1676302 to our customer portal case, as well as to the tracker bug.

Thanks,
 Oliver