Found this issue while running the console UI e2e test "tests/app/start-job-from-cronjob.cy.ts" on OCP 4.18 cluster on ppc64le arch. The test failing due unable to get start the job via "Start Job" action from the the cronjob action-list on the details page.     

 4.18

This issue is reproducing on OCP 4.18.0-ec3 cluster for ppc64le arch. When kubeadmin user create a CronJob and trying to start job from the cronjob details page, the action "Start Job" is not visible to start the job.   

Follow the below steps to reproduce the issue:    

1. Deploy a OCP cluster with 4.18.0-ec3 build for ppc64le arch
2. Create a sample cronjob with the below YAML definition from the CLI/ webconsole UI

[root@rdr-uie2e-ocp-418-bastion-0 ~]# oc get cronjob cronjob1 -n test-cron -o yaml
apiVersion: batch/v1
kind: CronJob
metadata:
  creationTimestamp: "2024-11-20T18:45:33Z"
  generation: 2
  name: cronjob1
  namespace: test-cron
  resourceVersion: "516926"
  uid: 2164b3a6-0d2d-4edb-90b0-4adc91e72abd
spec:
  concurrencyPolicy: Allow
  failedJobsHistoryLimit: 1
  jobTemplate:
    metadata:
      creationTimestamp: null
    spec:
      template:
        metadata:
          creationTimestamp: null
        spec:
          containers:
          - args:
            - /bin/sh
            - -c
            - date; echo Hello from the Kubernetes cluster
            image: busybox
            imagePullPolicy: Always
            name: hello
            resources: {}
            terminationMessagePath: /dev/termination-log
            terminationMessagePolicy: File
          dnsPolicy: ClusterFirst
          restartPolicy: OnFailure
          schedulerName: default-scheduler
          securityContext: {}
          terminationGracePeriodSeconds: 30
  schedule: '*/5 * * * *' 


3. Go to the cronjob details page for the above created cronjob and start a job with the "Start Job" action from the cronjob action-list on the cronjob details page.
    

The "Start Job" action is not visible in the action-list for the created cronjob. 

"Start Job" action should be visible in the action-list of created a CronJob as it is introduced from the OCP 4.18 version 

[root@rdr-uie2e-ocp-418-bastion-0 ~]# oc version
Client Version: 4.18.0-ec.3
Kustomize Version: v5.4.2
Server Version: 4.18.0-ec.3
Kubernetes Version: v1.31.2

[root@rdr-uie2e-ocp-418-bastion-0 ~]# oc get clusterversion
NAME      VERSION       AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.18.0-ec.3   True        False         22h     Cluster version is 4.18.0-ec.3

[root@rdr-uie2e-ocp-418-bastion-0 ~]# arch\
> ;
ppc64le