Job's backoffLimit not correct

[yasongxu]

What happened:

when I create a job like this :

apiVersion: batch/v1
kind: Job
metadata:
  name: demo
  namespace: default
spec:
  completions: 1
  backoffLimit: 6
  parallelism: 1
  template:
    metadata:
      name: demo
    spec:
      containers:
      - command:
        - sh
        - -c
        - exit 1
        image: nginx
        imagePullPolicy: IfNotPresent
        name: nginx
      restartPolicy: Never

job will eventually fail after it creates 5 failed pods, but it should be 6 failed pods.

status:
    conditions:
    - lastProbeTime: "2020-06-18T06:06:48Z"
      lastTransitionTime: "2020-06-18T06:06:48Z"
      message: Job has reached the specified backoff limit
      reason: BackoffLimitExceeded
      status: "True"
      type: Failed
    failed: 5
    startTime: "2020-06-18T06:01:55Z"

Events:
  Type     Reason                Age   From            Message
  ----     ------                ----  ----            -------
  Normal   SuccessfulCreate      39m   job-controller  Created pod: demo-ctvjt
  Normal   SuccessfulCreate      39m   job-controller  Created pod: demo-vjbvt
  Normal   SuccessfulCreate      38m   job-controller  Created pod: demo-5tls6
  Normal   SuccessfulCreate      38m   job-controller  Created pod: demo-6x5cz
  Normal   SuccessfulCreate      36m   job-controller  Created pod: demo-2d5mf
  Warning  BackoffLimitExceeded  34m   job-controller  Job has reached the specified backoff limit

Environment:
kubernetes version : 1.16.8 、 1.19.0

same issue

#70251
#64787

or any plan for this issue #64787 ?

[yasongxu]

/sig apps

[farah]

I'll have a look at it, thanks.

/assign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.