Bug 1836805
| Summary: | Update API group for eventSources | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jaivardhan Kumar <jakumar> | ||||
| Component: | Dev Console | Assignee: | Jaivardhan Kumar <jakumar> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Gajanan More <gamore> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.4 | CC: | aos-bugs, nmukherj | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.5.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Cause: Current event sources have apiGroup "sources.eventing.knative.dev" and this will be changing to "sources.knative.dev" for ApiSeverSource/Camel/Kafka Source
Consequence: Sources generated via new apiGroup maynot be recognized in topology view.
Fix: Update to latest supported apiGroup
Result: Sources generated via new apiGroup would be recognized in topology view. | Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1836807 (view as bug list) | Environment: | |||||
| Last Closed: | 2020-07-13 17:39:36 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: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1836807 | ||||||
| Attachments: | 
 | ||||||
| 
        
          Description
        
        
          Jaivardhan Kumar
        
        
        
        
        
          2020-05-18 08:27:31 UTC
        
       Associated Jira https://issues.redhat.com/browse/ODC-3000 Created attachment 1689751 [details]
API group for eventSources
I have validated the bug on the Build: 4.5.0-0.ci-2020-05-18-204038 Browser: Google Chrome Version 81.0.4044.129 Please have a look at the shared screenshot Marking this as done 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, 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/RHBA-2020:2409 |