Bug 2231091

Summary: Mention of steps on how to utilize the "Leapp preupgrade report" cloned template in the documentation.
Product: Red Hat Satellite Reporter: Arzoo Singh <arsingh>
Component: HostsAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.14.0CC: alazik, aruzicka
Target Milestone: UnspecifiedKeywords: Documentation, Triaged
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: 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-08-10 14:31:17 UTC
Document URL: https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.14/html-single/managing_hosts/index?lb_target=preview#Upgrading_Hosts_to_Next_Major_RHEL_Release_managing-hosts

Section Number and Name: Chapter 5, Procedure point no. 6

Describe the issue: With reference to this Bug 2224093 need to make recommendation to use the clone template efficiently. 

Suggestions for improvement: We can provide recommendation about clone template after point 6.
- The recommendation on how the "Leapp preupgrade report" section on the cloned job template can be achieved that is only available in the default job template.


Additional information: For the leapp_preupgrade or leapp_remediation_plan to function correctly, it is essential that they are directed towards the utilized template; otherwise, the process will not be successful.

administer > remote execution features, click on leapp_preupgrade > in the drop down select the clone template and submit

Comment 1 Marie Hornickova 2023-08-10 16:02:52 UTC
Hello,
Many thanks for reporting this suggestion for documentation improvement. 
The BZ will go through proper team triage and detailed information about the implementation will be shared in the corresponding Jira ticket.
Thank you!