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

Error in displaying BuildRun logs in Console

XMLWordPrintable

    • Important
    • No
    • ODC Sprint 3252
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, `BuildRun` logs were not visible in the *Logs* Tab of the BuildRun due to the recent update in the API version of the specified resources. With this update, the Logs of the `TaskRuns` were added back into the *Logs* tab of the BuildRun for both v1alpha1 as well as v1beta1 versions of the builds Operator. (link: https://issues.redhat.com/browse/OCPBUGS-29283[*OCPBUGS-29283*])
      Show
      * Previously, `BuildRun` logs were not visible in the *Logs* Tab of the BuildRun due to the recent update in the API version of the specified resources. With this update, the Logs of the `TaskRuns` were added back into the *Logs* tab of the BuildRun for both v1alpha1 as well as v1beta1 versions of the builds Operator. (link: https://issues.redhat.com/browse/OCPBUGS-29283 [* OCPBUGS-29283 *])
    • Bug Fix
    • Done

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

      Description of problem:

      BuildRun logs cannot be displayed in the console and shows the following error:

      The buildrun is created and started using the shp cli (similar behavior is observed when the build is created & started via console/yaml too):

      shp build create goapp-buildah \
    --strategy-name="buildah" \
    --source-url="https://github.com/shipwright-io/sample-go" \
    --source-context-dir="docker-build" \
    --output-image="image-registry.openshift-image-registry.svc:5000/demo/go-app"

      The issue occurs on OCP 4.14.6. Investigation showed that this works correctly on OCP 4.14.5.

              avik6028 Avik Kundu
              openshift-crt-jira-prow OpenShift Prow Bot
              Sanket Pathak Sanket Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: