Bug 1395570

Summary: [platformmanagement_public_479] StartingDeadlineSeconds was skipped by ScheduledJob
Product: OpenShift Container Platform Reporter: Chuan Yu <chuyu>
Component: MasterAssignee: Maciej Szulik <maszulik>
Status: CLOSED CURRENTRELEASE QA Contact: Chuan Yu <chuyu>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.4.0CC: aos-bugs, dma, jokerman, mfojtik, mmccomas
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
QA mistake, no change happened, no doc update required.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-08 18:39:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Chuan Yu 2016-11-16 09:01:52 UTC
Description of problem:
StartingDeadlineSeconds was skipped by ScheduledJob when create or edit 

Version-Release number of selected component (if applicable):
openshift v3.4.0.26+f7e109e
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0

How reproducible:
always

Steps to Reproduce:
1.run command 'oc create -f scheduledjob.yaml', scheduledjob.yaml:
apiVersion: batch/v2alpha1
kind: ScheduledJob
metadata:
  labels:
    run: sj3
  name: sj3
spec:
  concurrencyPolicy: Allow
  jobTemplate:
    metadata:
      name: sj3
    spec:
      completion: 5
      Parallelism: 1
      activeDeadlineSeconds: 300
      template:
        metadata:
          labels:
            run: sj3
        spec:
          containers:
          - args:
            - sleep
            - "10"
            image: busybox
            imagePullPolicy: Always
            name: sj3
            resources: {}
          restartPolicy: Never
  schedule: '*/1 * * * *'
  suspend: false
  StartingDeadlineSeconds: 300
2.
3.

Actual results:
1.when create scheduledjobs, the log show no StartingDeadlineSeconds in Response Body, see the log in additional info.
2.when get the scheduledjob by yaml, no StartingDeadlineSeconds parameter in the spec.
3.try to edit scheduledjob, and add StartingDeadlineSeconds to the spec, was skipped.

Expected results:
The StartingDeadlineSeconds should take effective by scheduledjob.

Additional info:
I1116 15:24:36.080710   28621 decoder.go:206] decoding stream as YAML
I1116 15:24:36.082081   28621 request.go:558] Request Body: "{\"apiVersion\":\"batch/v2alpha1\",\"kind\":\"ScheduledJob\",\"metadata\":{\"labels\":{\"run\":\"sj3\"},\"name\":\"sj3\",\"namespace\":\"chuyu\"},\"spec\":{\"StartingDeadlineSeconds\":300,\"concurrencyPolicy\":\"Allow\",\"jobTemplate\":{\"metadata\":{\"name\":\"sj3\"},\"spec\":{\"Parallelism\":1,\"activeDeadlineSeconds\":300,\"completion\":5,\"template\":{\"metadata\":{\"labels\":{\"run\":\"sj3\"}},\"spec\":{\"containers\":[{\"args\":[\"sleep\",\"10\"],\"image\":\"busybox\",\"imagePullPolicy\":\"Always\",\"name\":\"sj3\",\"resources\":{}}],\"restartPolicy\":\"Never\"}}}},\"schedule\":\"*/1 * * * *\",\"suspend\":false}}\n"
...
I1116 15:24:36.397547   28621 request.go:908] Response Body: {"kind":"ScheduledJob","apiVersion":"batch/v2alpha1","metadata":{"name":"sj3","namespace":"chuyu","selfLink":"/apis/batch/v2alpha1/namespaces/chuyu/scheduledjobs/sj3","uid":"ba3a941f-abcd-11e6-9ef7-0e91effc2ebe","resourceVersion":"18593","creationTimestamp":"2016-11-16T07:24:36Z","labels":{"run":"sj3"}},"spec":{"schedule":"*/1 * * * *","concurrencyPolicy":"Allow","suspend":false,"jobTemplate":{"metadata":{"name":"sj3","creationTimestamp":null},"spec":{"activeDeadlineSeconds":300,"template":{"metadata":{"creationTimestamp":null,"labels":{"run":"sj3"}},"spec":{"containers":[{"name":"sj3","image":"busybox","args":["sleep","10"],"resources":{},"terminationMessagePath":"/dev/termination-log","imagePullPolicy":"Always"}],"restartPolicy":"Never","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","securityContext":{}}}}}},"status":{}}

Comment 1 Maciej Szulik 2016-11-24 10:08:18 UTC
You have a typo in your spec, startingDeadlineSeconds needs to start with lowercase, not uppercase.

Comment 2 Chuan Yu 2016-11-24 11:10:22 UTC
Sorry, my mistake, after modify it to the lowercase started with, the startingDeadlineSeconds take effective.

version:
openshift v3.4.0.29+ca980ba
kubernetes v1.4.0+776c994
etcd 3.1.0-rc.0