Bug 2059807
| Summary: | Services other than knative service also shows as KSVC in add subscription/trigger modal | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
| Component: | Dev Console | Assignee: | Jaivardhan Kumar <jakumar> |
| Status: | CLOSED ERRATA | QA Contact: | spathak <spathak> |
| Severity: | medium | Docs Contact: | Rishu Mehra <rmehra> |
| Priority: | medium | ||
| Version: | 4.10 | CC: | aos-bugs, nmukherj |
| Target Milestone: | --- | ||
| Target Release: | 4.10.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the sink for event sources in the `Trigger/Subscription` modal in the *Topology* UI showed all resources, irrespective of whether they were created as a standalone or an underlying resource included with back KSVC, Broker, or KameletBinding. Consequently, users could sink to the underlying addressable resources as they showed up in the sink drop-down menu. With this update, a resource filter has been added to show only standalone resource sink events. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2059807[BZ#2059807])
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-28 12:03:18 UTC | Type: | --- |
| 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: | 2054285 | ||
| Bug Blocks: | |||
|
Comment 7
spathak@redhat.com
2022-03-24 12:35:48 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 (OpenShift Container Platform 4.10.6 bug fix 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/RHBA-2022:1026 |