Bug 2024262 - Sample catalog is not displayed when one API call to the backend fails
Summary: Sample catalog is not displayed when one API call to the backend fails
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Nico Finkernagel
QA Contact: spathak@redhat.com
Depends On:
Blocks: 2068203
TreeView+ depends on / blocked
Reported: 2021-11-17 17:39 UTC by Nico Finkernagel
Modified: 2022-05-31 19:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:28:46 UTC
Target Upstream Version:

Attachments (Terms of Use)
Screenshot 1 (44.92 KB, image/png)
2021-11-17 17:40 UTC, Nico Finkernagel
no flags Details
Screenshot 2 (151.75 KB, image/png)
2021-11-17 17:42 UTC, Nico Finkernagel
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10569 0 None open Bug 2024262: Sample catalog is not displayed when one API call to the backend fails 2021-11-29 10:05:22 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:29:08 UTC

Description Nico Finkernagel 2021-11-17 17:39:19 UTC
Description of problem:
On the samples page when you try to add an application from a sample the catalog gets not rendered when one API Call fails but the catalog placeholder is rendered instead. I assume that there are multiple sources for those entries on the samples page.

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

How reproducible:

Steps to Reproduce:
1. Switch to the dev console
2. Create a new project
3. Click on "+Add" or "View all samples"

Actual results:
There is a second bug open at this time which ensures that the devfiles cannot be loaded from the server (see additional info). Instead of showing an error message, the page goes into a state where the catalog placeholder is shown forever.

Expected results:
There can always be a network problem that is outside the scope of the ODC, but we should somehow inform the user that the request failed.

Additional info:

Comment 1 Nico Finkernagel 2021-11-17 17:40:27 UTC
Created attachment 1842396 [details]
Screenshot 1

Comment 2 Nico Finkernagel 2021-11-17 17:42:16 UTC
Created attachment 1842410 [details]
Screenshot 2

Comment 5 Christoph Jerolimov 2022-01-04 07:30:07 UTC
Verified on 4.10.0-0.nightly-2021-12-23-153012

Comment 8 errata-xmlrpc 2022-03-10 16:28:46 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 (Moderate: OpenShift Container Platform 4.10.3 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.