Bug 1996566

Summary: Manually created invalid Kamelets should be skipped in the eventsources list
Product: OpenShift Container Platform Reporter: Jaivardhan Kumar <jakumar>
Component: Dev ConsoleAssignee: Jaivardhan Kumar <jakumar>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 4.9CC: aos-bugs, nmukherj, sbudhwar
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-18 17:47:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jaivardhan Kumar 2021-08-23 08:40:56 UTC
Description of problem:   
Create an invalid Kamelet of type "source" using create Kamelet button from search page. Visiting the Add flow event sources page breaks the UI with an NPE.

Prerequisites (if any, like setup, operators/versions):  
Openshift Serverless operator + Red Hat camel K Integration

Steps to Reproduce
1.Goto search page, search for Kamelet and click on create Kamlet
2.Add the below label to the metadata field in the pre-populated yaml.  
  labels: camel.apache.org/kamelet.type: "source"
3. Visit the Add -> Event sources page.

Actual results:

UI breaks with following error: 

 Uncaught TypeError: Cannot read property 'title' of undefined
 at useKameletsProvider.ts:22

Expected results:  
No errors on UI. (Invalid kamelets must be skipped in the provider list)

Reproducibility (Always/Intermittent/Only Once):

Build Details:  

Comment 5 errata-xmlrpc 2021-10-18 17:47:54 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.9.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.