Description of problem: activeDeadlineSeconds warning is repeated and incorrect while set activeDeadlineSeconds value to a minus Version-Release number of selected component (if applicable): openshift v3.6.65 kubernetes v1.6.1+5115d708d7 How reproducible: always Steps to Reproduce: 1. create a run-once pod oc run run-once-pod --command=true sleep 2000s --restart=Never 2. patch the pod oc patch pod run-once-pod -p \{\"spec\":\{\"activeDeadlineSeconds\":-5\}\} Actual results: [root@ymsun cucushift-test]# oc patch pod run-once-pod -p \{\"spec\":\{\"activeDeadlineSeconds\":-5\}\} The Pod "run-once-pod" is invalid: * spec.activeDeadlineSeconds: Invalid value: -5: must be greater than 0 * spec.activeDeadlineSeconds: Invalid value: -5: must be greater than or equal to 0 Expected results: The line "spec.activeDeadlineSeconds: Invalid value: -5: must be greater than or equal to 0" is a repeated warning. And due to 0 can not be used, it is an incorrect warning too. Additional info:
The issue exist in dev-preview-stg too.
the issue is that on pod update we call: ValidatePod ValidatePodUpdate https://github.com/kubernetes/kubernetes/blob/master/pkg/registry/core/pod/strategy.go#L93 The differing values are because the allowed value set for the field differ on create versus update.
*** Bug 1466113 has been marked as a duplicate of this bug. ***
No movement on this in 2 years. If issues still persist, please open a new bug.