Bug 1810534
| Summary: | Topology filter by application throws an error when it has Operator backed nodes | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Karthik Jeeyar <kjeeyar> |
| Component: | Dev Console | Assignee: | Karthik Jeeyar <kjeeyar> |
| Status: | CLOSED ERRATA | QA Contact: | Jaivardhan Kumar <jakumar> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.4 | CC: | aos-bugs, cvogt, jakumar, nmukherj, rgarg |
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Filtering the OBS nodes based on the application in topology model is missing
Consequence: Filtering the topology nodes by application, throws an error when the topology has operator backed services in the namespace.
Fix: Add a logic to filter the OBS nodes based on the selected application group.
Result: User can now filter the Operator backed service nodes based on the application.
|
Story Points: | --- |
| Clone Of: | 1810532 | Environment: | |
| Last Closed: | 2020-05-04 11:44:56 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: | 1810532 | ||
| Bug Blocks: | |||
|
Description
Karthik Jeeyar
2020-03-05 13:00:35 UTC
Verified on 4.4 OpenShift Version 4.4.0-0.nightly-2020-03-05-205718 Kubernetes Version v1.17.1 Channel stable-4.4 Cluster ID 18833f12-279d-4b66-b83a-1772efac79ee API Server https://api.gamore44installer0603.devcluster.openshift.com:6443 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:0581 |