Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-45228

ReRun of Resolver based PipelineRuns fails from UI

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.15.z, 4.17.z, 4.16.z
    • Dev Console
    • None
    • 1
    • ODC Sprint 3266, ODC Sprint 3267
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, if a `PipelineRun` was using a resolver, rerun of that `PipelineRun` was having issue. With this fix, user can rerun `PipelineRun` if it is using resolver. (link:https://issues.redhat.com/browse/OCPBUGS-45228[(*OCPBUGS-45228*)])
      Show
      * Previously, if a `PipelineRun` was using a resolver, rerun of that `PipelineRun` was having issue. With this fix, user can rerun `PipelineRun` if it is using resolver. (link: https://issues.redhat.com/browse/OCPBUGS-45228 [(* OCPBUGS-45228 *)])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-44265. The following is the description of the original issue:
      —
      Description of problem:

      As a User when we attempt to "ReRun" a resolver based pipelinerun from OpenshiftConsole, UI errors with message "Invalid PipelineRun configuration, unable to start Pipeline." Slack thread: https://redhat-internal.slack.com/archives/CG5GV6CJD/p1730876734675309  

      Version-Release number of selected component (if applicable):

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create a resolver based pipelinerun
2. Attempt to "ReRun" the same from Console    

      Actual results:

          ReRun Errors

      Expected results:

          ReRun should be triggered successfully

      Additional info:

            [OCPBUGS-45228] ReRun of Resolver based PipelineRuns fails from UI

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Important: OpenShift Container Platform 4.18.1 bug fix and security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2024:6122

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Important: OpenShift Container Platform 4.18.1 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:6122

            Shekhar Singh (Inactive) added a comment -

            verified on cluster build: 4.18.0-0.ci-2024-12-15-162004
            verified on browser : chrome Version 131.0.6778.140

            Shekhar Singh (Inactive) added a comment - verified on cluster build: 4.18.0-0.ci-2024-12-15-162004 verified on browser : chrome Version 131.0.6778.140

            OpenShift Jira Bot added a comment -

            Hi rh-ee-lprabhu,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi rh-ee-lprabhu , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

              rh-ee-lprabhu Lokananda Prabhu
              openshift-crt-jira-prow OpenShift Prow Bot
              Sanket Pathak Sanket Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: