Bug 1808968
| Summary: | Service binding should be through Knative Service | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jaivardhan Kumar <jakumar> | ||||||
| Component: | Dev Console | Assignee: | Jaivardhan Kumar <jakumar> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | spathak <spathak> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.3.0 | CC: | aos-bugs, cvogt, gamore, nmukherj, rgarg, spathak | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 4.3.z | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
Cause: Service binding request in topology is associated with Revisions in topology view
Consequence: no new revision will get the associated secrets
Fix: SBR should go through knative service secrets would be injected and in turn new revisions would be created
Result: SBR works as expected with Knative Service
|
Story Points: | --- | ||||||
| Clone Of: | 1798288 | Environment: | |||||||
| Last Closed: | 2020-03-24 14:34:23 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: | 1798288 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
|
Comment 3
Gajanan More
2020-03-17 07:55:44 UTC
Created attachment 1671247 [details]
Service binding should be through Knative Service-1
Created attachment 1671248 [details]
Service binding should be through Knative Service-2
Verified on build: 4.3.0-0.ci-2020-03-18-122927 Chrome browser: 76.0.3809.132 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:0858 |