-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.18, 4.19, 4.20
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
Proposed
-
None
-
-
None
-
None
-
None
-
None
Description of problem:
CronTab list page returns error when any CronTab is missing spec fields
Version-Release number of selected component (if applicable):
4.20.0-0.nightly-2025-05-27-133818
How reproducible:
Always
Steps to Reproduce:
1. Deploy console-crontab-plugin following https://github.com/openshift/console-crontab-plugin#installing-the-helm-chart # helm upgrade -i console-crontab-plugin charts/console-crontab-plugin -n console-crontab-plugin-ns --create-namespace --set plugin.image=quay.io/yapei/console-crontab-plugin:latest 2. Create a CronTab with following YAML apiVersion: stable.example.com/v1 kind: CronTab metadata: name: my-new-cron-object namespace: default 3. Visit CronTab list page /k8s/ns/default/stable.example.com~v1~CronTab
Actual results:
3. We will see error Cannot read properties of undefined (reading 'cronSpec')
Expected results:
3. We should either make `spec` as required fields or do not show error page when spec is missing if it's optional
Additional info: