[BUG]cronjob-controller Cannot determine if job needs to be started
amaheshwari21 opened this issue · comments
Describe the bug
Cronjob to release free ips are not getting executed on scheduled interval.
Expected behavior
Cronjob to clear free ips into the pool must have executed as per the schedule
To Reproduce
Steps to reproduce the behavior:
- setup whereabouts v0.5.3 on k8s 1.20
- create and delete multiple multus pods to see IPs are freed up or not.
Environment:
- Whereabouts version : 0.5.3
- Kubernetes version (use
kubectl version): 1.20 - Network-attachment-definition: N/A
- Whereabouts configuration (on the host): N/A
- OS (e.g. from /etc/os-release): Amazon Linux2
- Kernel (e.g.
uname -a): - Others:
Additional info / context
Log message
Type Reason Age From Message │
---- ------ ---- ---- ------- │
Warning FailedNeedsStart 2m49s (x14839 over 41h) cronjob-controller Cannot determine if job needs to be started: too many missed start time (> 100). Set or decrease .spec.startingDeadlineSeconds or check clock skew
Does this issue reproduce with a supported Kubernetes version (1.22 / 1.23 / 1.24) ?