Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-35586 The "Leapp preupgrade report" tab on job invocations UI page disappears
  3. SAT-35675

[QE] The "Leapp preupgrade report" tab on job invocations UI page disappears

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • sat-endeavour
    • Rocket

      Reproducer steps:

      1. Clone the default "Run preupgrade via Leapp" job template:

      • Hosts --> Templates --> Job Templates --> "Run preupgrade via Leapp" --> Clone
      • Make desired modifications to the cloned template and name it "Run preupgrade via Leapp clone"

      2. Run leapp preupgrade on a host using the default template:

      • Hosts --> All Hosts --> select host --> Select Action --> Preupgrade check with Leapp --> Run on selected hosts
      • Open the job details in WebUI (https://<satellite>/job_invocations/<id>) and you will see "Leapp Preupgrade Report" tab as expected

      3. Choose the cloned template in REX features:

      • Administer --> Remote Execution Features --> leapp_preupgrade --> "Run preupgrade via Leapp clone"

      4. Run leapp preupgrade on the same host using the cloned template:

      • Hosts --> All Hosts --> select host --> Select Action --> Preupgrade check with Leapp --> Run on selected hosts
      • Open the job details in WebUI (https://<satellite>/job_invocations/<id>) and you will see "Leapp Preupgrade Report" tab as expected

      5. Open the job invocation details belonging to the first job and you will see that "Leapp Preupgrade Report" tab disappeared. Presumably as a consequence of the second job.

      Additional details:

      This happens only when the job template changes.

      QE Tracker for https://issues.redhat.com/browse/SAT-35586

              rhn-support-shwsingh Shweta Singh (Inactive)
              satellite-jira-automation@redhat.com Satellite Jira-Automation
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: