Bug 1833034

Summary: Incorrect traffic splitting percentage in topology sidebar
Product: OpenShift Container Platform Reporter: Karthik Jeeyar <kjeeyar>
Component: Dev ConsoleAssignee: Karthik Jeeyar <kjeeyar>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.5CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:35:59 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:
Description Flags
traffic sidebar
traffic modal none

Description Karthik Jeeyar 2020-05-07 17:10:45 UTC
Description of problem:

When traffic is split to the same revision but with different tags, the topology and sidebar do not show the correct traffic % to the revision

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a knative service via git import flow
2. In topology page, click on the newly create service
3. In sidebar click on the set traffic distribution
4. Add new row and split the traffic for the same revision in multiple rows
5. click on save

Actual results:
On clicking the service in topology, in the sidebar newly splitted traffic and routes are not been shown.

Expected results:
On clicking the service in topology, in the sidebar newly splitted traffic and routes shoule be shown.

Comment 3 Gajanan More 2020-05-15 10:50:35 UTC
Created attachment 1688889 [details]
traffic sidebar

Comment 4 Gajanan More 2020-05-15 10:50:49 UTC
Created attachment 1688890 [details]
traffic modal

Comment 5 Gajanan More 2020-05-15 10:51:03 UTC
I have validated the bugzilla on:
Build: 4.5.0-0.ci-2020-05-14-224329
Browser: Google Chrome Version 81.0.4044.129
Please have a look at the screenshot shared
Marking this as verified.

Comment 6 errata-xmlrpc 2020-07-13 17:35:59 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.