Bug 2231091 - Mention of steps on how to utilize the "Leapp preupgrade report" cloned template in the documentation.
Summary: Mention of steps on how to utilize the "Leapp preupgrade report" cloned templ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.14.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-10 14:31 UTC by Arzoo Singh
Modified: 2023-08-14 15:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19487 0 None None None 2023-08-10 14:32:34 UTC

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!


Note You need to log in before you can comment on or make changes to this bug.