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

Console: Cannot Edit Shipwright Build

XMLWordPrintable

    • Moderate
    • No
    • ODC Sprint 3248
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

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

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

      Description of problem:

      
      Unable to edit Shipwright Builds with the upcoming builds for Red Hat OpenShift release (based on Shipwright v0.12.0) in the developer and admin consoles.
      
      Workaround is to use `oc edit build.shipwright.io ...`
      
      

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

      
      OCP 4.14
      builds for OpenShift v1.0.0
      
      

      How reproducible:

      
      Always
      
      

      Steps to Reproduce:

      
      1. Deploy the builds for Red Hat OpenShift release candidate operator
      2. Create a Build using the shp command line: `shp build create ...`
      3. Open the Dev or Admin console for Shipwright Builds
      4. Attempt to edit the Build object
      
      

      Actual results:

      
      Page appears to "freeze", does not let you edit.
      
      

      Expected results:

      
      Shipwright Build objects can be edited.
      
      

      Additional info:

      
      Can be reproduced by deploying the following "test catalog" - quay.io/adambkaplan/shipwright-io/operator-catalog:v0.13.0-rc7, then creating a subscription for the Shipwright operator.
      
      Will likely be easier to reproduce once we have the downstream operator in the Red Hat OperatorHub catalog.
      
      

              avik6028 Avik Kundu
              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: