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:
After adding a user input, header of script is not changed in the script edit textarea (or in "hammer report-template dump ..."), however, when exporting it, the new input is included there.

I would accept having to include it in the script manually in both cases but this behavior is inconsistent and doesn't seem right to me.

This bug is also true for reporting templates.

Version-Release number of selected component (if applicable):
Tested on Sat 6.5 snap 7

How reproducible:
Deterministic

Steps to Reproduce through WebUI:
1. Clone some report template
2. Edit the cloned report template, in the Inputs tab, add some input
3. After submitting, open in for editing again

Actual results:
The script doesn't contain the new input declared in its header

Expected results:
I think the script contents should be the same in the textarea and in the export

Lukáš I'm not sure whether you've seen my reply but I believe this is not a bug. The "script header" you talk about is a comment. We store metadata into it that are useful on importing the template. There's a PR pending already to actually strip it from the template content so user will not see that at all. On export you can choose one of three modes (foreman_templates plugin) that would either generate such comment for you from scratch, remove it entirely or keep it as it is. The export functionality in core always generate new metadata, so it can be reimported back (or to different Satellite instance). This is not related to report templates, this is a behavior that we have for all templates for a while.

I'm closing this as NOTABUG for now.