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: When executing a clone of the job template titled "Run preupgrade via Leapp" the section for "Leapp preupgrade report" is not displayed, unlike when the original(default) template is executed.
- The cloned template remains unchanged with no modifications being made.
Version-Release number of selected component (if applicable):
How reproducible: Easily reproducible
> Navigate to Satellite WebUI > Hosts > Templates - Job Templates > Clone the "Run preupgrade via Leapp" template.> Run both the template on a host and observe the "Leapp preupgrade report" tab on both the pages.
Steps to Reproduce:
1. Navigate to Satellite WebUI > Hosts > Templates - Job Templates > Clone the "Run preupgrade via Leapp" template.
2. Run both the template on a host and observe the "Leapp preupgrade report" tab on both the pages.
Actual results: The "Leapp preupgrade report" is missing on the clone template result page.
Expected results: It is expected that the cloned template behaves similarly to the parent template and includes the missing tab.
Additional info: https://github.com/theforeman/foreman_leapp/blob/master/lib/foreman_leapp/engine.rb#L30-L39
I'd say that is expected. The leapp_preupgrade or leapp_remediation_plan needs to be pointing at the template being used otherwise it will just not work. That is the thing we use to decide "yes, this is something leapp releated, we need to do some post processing on it and show something extra". If you just clone the template and use the clone, we have nothing to go by unless you change the feature to point at the clone.
Anyway, leapp is the right component