Bug 2056496 - If image does not exists for builder image then upload jar form crashes
Summary: If image does not exists for builder image then upload jar form crashes
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Jaivardhan Kumar
QA Contact: spathak@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2022-02-21 11:19 UTC by Jaivardhan Kumar
Modified: 2022-08-10 10:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-08-10 10:50:27 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11099 0 None open Bug 2056496: update upload jar flow for no builder image 2022-02-24 15:21:31 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:51:03 UTC

Description Jaivardhan Kumar 2022-02-21 11:19:34 UTC
Description of problem: If the image does not exists for the builder image then upload jar form crashes, this may happen if the user does not have console-operator installed.

Currently, UI fetches builder images just with the name java, we can even make sure these are valid images.

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

How reproducible: Always

Steps to Reproduce:
1. remove the existing builder images for java / get a fresh cluster that does not have a console operator in it
2. Go to add -> upload jar

Actual results: UI Crashes

Expected results: UI should not crash

Additional info: Can even check with UXD/PM on what should be shown in UI in this scenario as if builder images are not present either way then user can't proceed with creation from the upload jar form

Comment 3 Christoph Jerolimov 2022-03-17 08:40:38 UTC
Verified it on 4.11.0-0.nightly-2022-03-16-103946 by blocking this URLs:


Comment 5 errata-xmlrpc 2022-08-10 10:50:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 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.


Note You need to log in before you can comment on or make changes to this bug.