Bug 1781193

Summary: Error in topology if knative service created via CLI
Product: OpenShift Container Platform Reporter: Karthik Jeeyar <kjeeyar>
Component: Dev ConsoleAssignee: cvogt
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: high Docs Contact:
Priority: high    
Version: 4.3.0CC: aos-bugs, cvogt, nmukherj, rgarg, viraj
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1781188 Environment:
Last Closed: 2020-01-23 11:18:16 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: 1781188    
Bug Blocks:    
Attachments:
Description Flags
Error in topology if knative service created via CLI none

Description Karthik Jeeyar 2019-12-09 14:17:39 UTC 
+++ This bug was initially created as a clone of Bug #1781188 +++

Description of problem:


Error in topology if knative service created via CLI. The error says `can't read traffic of undefined.`

Steps to reproduce:

1. Open topology view select a project
2. Via CLI create a kn service in same projectActual results:

Actual results
It throws an error in the user is in the topology page and creates a knative service via CLI

Expected results:
It should not throw error if knative service is created via CLI
Comment 2 Ruchir Garg 2020-01-07 09:57:05 UTC 
Assigning defect to Gajanan More for verification.
Comment 3 spathak@redhat.com 2020-01-07 21:25:01 UTC 
Verified on build version:4.3.0-0.ci-2020-01-06-064249
Comment 4 spathak@redhat.com 2020-01-07 21:26:20 UTC 
Created attachment 1650513 [details]
Error in topology if knative service created via CLI
Comment 6 errata-xmlrpc 2020-01-23 11:18:16 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, 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:0062