Bug 1787096

Summary: Sorting by 'Starting Deadlines Seconds' don't work on CronJob list page
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: David Taylor <dtaylor>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3.0CC: aos-bugs, dtaylor, eparis, jokerman, yapei
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: On CronJobs list page, sort by 'Starting Deadlines Seconds' or 'Concurrency Policy' field Consequence: Records are not sorted at all Fix: updated 'sortField' for the two fields Result: You can now sort 'Starting Deadlines Seconds' and 'Concurrency Policy' columns on CronJobs list page.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-04 11:21:35 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:
Embargoed:

Description Yadan Pei 2019-12-31 02:21:58 UTC 
Description of problem:
When try to sort by 'Starting Deadlines Seconds' on CronJobs list page, the records are not sorted at all

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-12-29-173422

How reproducible:
Always

Steps to Reproduce:
1. Create two CronJobs with different startingDeadlineSeconds
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: example1
  namespace: yapei1-project1
spec:
  schedule: '@daily'
  startingDeadlineSeconds: 100
  jobTemplate:
    spec:
      template:
        spec:
          containers:
            - name: hello
              image: busybox
              args:
                - /bin/sh
                - '-c'
                - date; echo Hello from the Kubernetes cluster
          restartPolicy: OnFailure
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: example2
  namespace: yapei1-project1
spec:
  schedule: '@daily'
  startingDeadlineSeconds: 300
  jobTemplate:
    spec:
      template:
        spec:
          containers:
            - name: hello
              image: busybox
              args:
                - /bin/sh
                - '-c'
                - date; echo Hello from the Kubernetes cluster
          restartPolicy: OnFailure
2. Goes to CronJobs list page and sort by 'Starting Deadlines Seconds' field


Actual results:
2. CronJobs are not sorted and the sequence is not changed

Expected results:
2. CronJobs should be sorted 

Additional info:
Comment 3 Yadan Pei 2020-01-13 03:00:54 UTC 
1) Create two CronJobs with different value of concurrencyPolicy && startingDeadlineSeconds
2) then goto CronJobs page and sort by 'Concurrency Policy' and 'Starting Deadline Seconds'

now the sorting on these two fields work, verified on 4.4.0-0.nightly-2020-01-12-221811
Comment 5 errata-xmlrpc 2020-05-04 11:21:35 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:0581