Bug 2256213

Summary: [RFE] Add Option to specify <target_os_version> as input in the job template for Leapp upgrade
Product: Red Hat Satellite Reporter: Satyajit Das <sadas>
Component: Leapp integrationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.14.0CC: ahumbe, aruzicka, dsinglet, lstejska, rlavi, shwsingh
Target Milestone: UnspecifiedKeywords: FutureFeature, MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:40:17 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 Satyajit Das 2023-12-29 15:19:51 UTC
1. Proposed title of this feature request

Add the Option to specify <target_os_version> as input in the job template for the Leapp upgrade 


2. What is the nature and description of the request?

Based on the application requirement customer plans the in-place upgrade of the client, however, the job template used by satellite to perform the Leapp upgrade always points to the latest version and there is no option to specify <target_os_version> as input.


Template used by satellite
============================
Run upgrade via Leapp  
---
- hosts: all
  tasks:
    - name: Run Leapp Upgrade
      command: leapp upgrade
<%- if input('Reboot') == "true" -%>
    - name: Reboot the machine
      reboot:
        reboot_timeout: 1800
<%- end -%>
=====================
---
- hosts: all
  tasks:
    - name: Run Leapp Upgrade
      command: leapp upgrade

=====================

3. How would you like to achieve this? (List the functional requirements here)

Add the Option to specify <target_os_version> as input in the job template for the Leapp upgrade so that target release can be specified and the upgrade will upgrade the client till target_os_version.

Ex.

# leapp upgrade --target <target_os_version>

Comment 1 Eric Helms 2024-06-06 16:40:17 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.