Description of problem: The UI doesn't show updated traffic distribution, despite accepting the form. For now, we have one evidence of this - failed OCP 4.6.43 run: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.6-e2e-aws-ocp-46-continuous/1436117460133613568 screenshot: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.6-e2e-aws-ocp-46-continuous/1436117460133613568/artifacts/e2e-aws-ocp-46-continuous/serverless-e2e/artifacts/build-jmUzaF/j/ui/screenshots/serving.spec.js/OCP%20UI%20for%20Serverless%20--%20can%20route%20traffic%20to%20multiple%20revisions%20(failed).png This is for sure flaky. Version-Release number of selected component (if applicable): 4.6.43 How reproducible: Flaky Steps to Reproduce: 1. Try applying the knative service traffic distribution form?!? Actual results: The UI should show traffic distribution between two revisions, rev.1 and rev.2. The routing should have 49% and 51% chances respectively. Expected results: The UI shows 100% traffic to rev.1, and you could see the rev.2 just started to terminate.
JS error: 1) OCP UI for Serverless can route traffic to multiple revisions: AssertionError: Timed out retrying after 60000ms: Expected to find content: '51%' but never did.
We've observed the same behavior also on OCP 4.7.29. Here's a screenshot of this: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.7-e2e-aws-ocp-47-continuous/1436479866768723968/artifacts/e2e-aws-ocp-47-continuous/serverless-e2e/artifacts/build-y2Sc8l2d/ui/screenshots/serving.spec.js/OCP%20UI%20for%20Serverless%20--%20can%20route%20traffic%20to%20multiple%20revisions%20(failed).png A build link - https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.7-e2e-aws-ocp-47-continuous/1436479866768723968
Seen also today, here (the first fail, before retries, line 5447 on log): https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.6-e2e-aws-ocp-46-continuous/1440284825670914048#1:build-log.txt%3A5447 Screenshot: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.6-e2e-aws-ocp-46-continuous/1440284825670914048/artifacts/e2e-aws-ocp-46-continuous/serverless-e2e/artifacts/build-We3H/rtw/ui/screenshots/serving.spec.js/OCP%20UI%20for%20Serverless%20--%20can%20route%20traffic%20to%20multiple%20revisions%20(failed).png
The issue occurred due to filtered revisions being calculated using a function inside the component which caused it to use stale data, it was fixed by memoizing the revisions data. The fix is in 4.10 (master). Sidebar should now update traffic distributions as soon as the resource is changed, although there is still a small delay since the UI waits for the resource to be updated rather than immediately showing the changed values on form submit. Please let us know if there are further issues.
Hey Chris @ksuszyns, happy new year. :) Can you verify that this flaky issue doesn't exist on a nightly build any more or is it okay if we verify this issue on our own? Thanks
Please verify it on your end. Hopefully, the issue will be resolved.
Verified on build version: 4.10.0-0.nightly-2022-02-23-193238 Browser: Google Chrome 98`
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.10.3 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-2022:0056