Bug 2070020 - InContext doesn't work for Event Sources
Summary: InContext doesn't work for Event Sources
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.11.0
Assignee: Sahil Budhwar
QA Contact: spathak@redhat.com
Olivia Payne
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-30 09:54 UTC by Sahil Budhwar
Modified: 2022-08-10 11:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: apiVersion in correct format was not passed to resource dropdown in Event source Creation Form. Consequence: Knative Service from InContext is not selected on Resource dropdown in EventSource creation form. Fix: apiVersion in the correct format is passed to the Resource dropdown Result: Resource from InContext is selected in the Resource dropdown.
Clone Of:
Environment:
Last Closed: 2022-08-10 11:02:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 11260 0 None open Bug 2070020: create correct apiversion: group/version for creating custom resource key for Resource Dropdown 2022-03-30 13:13:53 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:03:01 UTC

Description Sahil Budhwar 2022-03-30 09:54:08 UTC 
Description of problem:
when connector is dragged from KSVC and EventSource is selected, Incontext doesn't work

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


How reproducible:
Always

Steps to Reproduce:
1. Install Serverless Operator
2. Create Knative Service
3. Drag Knative service connector and select Event source option

Actual results: Knative Service is not selected on Resource dropdown in EventSource creation form


Expected results: Knative Service from Incontext should be selected in EventSource creation form


Additional info:
Comment 3 Vikram Raj 2022-04-22 11:50:39 UTC 
Verified it on 4.11.0-0.nightly-2022-04-22-002610. And it works as expected.
Comment 6 errata-xmlrpc 2022-08-10 11:02:42 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.

https://access.redhat.com/errata/RHSA-2022:5069
Note You need to log in before you can comment on or make changes to this bug.