Description of problem: In Serverless -> Services list table, Age column ordering don't work Version-Release number of selected component (if applicable): serverless-operator.v1.4.0 4.4.0-0.nightly-2020-02-12-191550 How reproducible: Always Steps to Reproduce: 1. Enable OpenShift Serverless operator 2. Create several example service at Serverless -> Services page using default YAML 3. Check resources on Serverless -> Services list page and order by Age Actual results: 3. Table data didn't change when Age ordering direction is changed Expected results: 3. Table data should change accordingly when Age ordering direction is changed Additional info:
I was not able to reproduce, but lets confirm specificity: - Install OpenShift Serverless Operator from OperatorHub - Create knative-serving namespace (required by operator) - Create instances of knative-serving (operand) - View knative serving tab on the Installed Operators -> OpenShift Serverless Operator -> Operator Details page - Sort by last updated column (age?) This sorting function works.
Hi Ben, Tried to get a screenshot then it would be much clear, but failed to install OpenShift Serverless Operator today. The issue is Order by 'Age' on Serverless -> Services list page not Installed Operators page. Let me know if it's still not clear
Created attachment 1663476 [details] Serverless Services list page I installed OpenShift Serverless Operator successfully and got a screenshot of the page, it's much clear
1. Enable OpenShift Serverless operator, and create Knative Serving instance cat > serving.yaml << EOF apiVersion: v1 kind: Namespace metadata: name: knative-serving --- apiVersion: operator.knative.dev/v1alpha1 kind: KnativeServing metadata: name: knative-serving namespace: knative-serving EOF $ oc apply -f serving.yaml 2. Create several example service at Serverless -> Services page using default YAML 3. Check resources on Serverless -> Services list page and order by Age When we change ordering direction, the table row changes too Verified on 4.5.0-0.ci-2020-03-04-223611
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:2409