Bug 2224093

Summary:	Missing "Leapp preupgrade report" section when running the clone of "Run preupgrade via Leapp " job template.
Product:	Red Hat Satellite	Reporter:	Arzoo Singh <arsingh>
Component:	Leapp integration	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.14.0	CC:	aruzicka, lstejska
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-20 10:24:09 UTC	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 Arzoo Singh 2023-07-19 18:41:00 UTC

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

Comment 2 Adam Ruzicka 2023-07-20 08:46:11 UTC

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

Comment 3 Leos Stejskal 2023-07-20 10:24:09 UTC

Agree with Adam, this is expected behavior. Closing as not a bug.