Bug 1972514
| Summary: | add check for accessing traffic from status in ksvc | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jaivardhan Kumar <jakumar> | ||||
| Component: | Dev Console | Assignee: | Jaivardhan Kumar <jakumar> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | Rishu Mehra <rmehra> | ||||
| Priority: | high | ||||||
| Version: | 4.7 | CC: | aos-bugs, nmukherj, viraj | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.9.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Previously, because of some issues with serverless operators, the status of the nightly builds was not getting updated in the associated resources. So when you click on `ksvc` in the Topology and throw a null pointer exception. In the current release, this issue is fixed and now when you click on `ksvc` it shows the build information in the side panel. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1972514[*BZ#1972514*])
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 2013091 (view as bug list) | Environment: | |||||
| Last Closed: | 2021-10-18 17:34:18 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: | 2013091 | ||||||
| Attachments: |
|
||||||
Verified this on 4.9.0-0.nightly-2021-06-18-061022 and not able to reproduce it anymore. 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. https://access.redhat.com/errata/RHSA-2021:3759 |
Created attachment 1791446 [details] screenshot Description of problem: Status is usually there when any k8s resource is created, same is the case for ksvc. Though status is an optional field and good to have a check. Version-Release number of selected component (if applicable): Install serverless operator How reproducible: Only Once Steps to Reproduce: 1.go to devconsole => add => git import flow 2.select node js sample app and ksvc as resource 3.click on KSVC in topology Actual results: NPE is thrown in topology and err is shown in the error boundary Expected results: should show ksvc sidebar Additional info: This issue was observed by Vikram Raj and for this scenario, there was no status field in ksvc yaml, but we couldn't reproduce it again on the same cluster again.