Exercise 4.3 part 5-6: activeDeadlineSeconds is in the wrong spec
Undertaking the given exercise, I have the following in cronjob.yaml:
apiVersion: batch/v1 kind: CronJob metadata: name: sleepy spec: schedule: "*/2 * * * *" jobTemplate: spec: template: spec: activeDeadlineSeconds: 10 containers: - name: resting image: busybox command: ["/bin/sleep"] args: ["30"] restartPolicy: Never
When I create this CronJob, I do not see the described behaviour for the exercise:
Ensure that if the job continues for more than 10 seconds it is terminated.
Instead, I am seeing that each two minutes, a new Job is created (as expected) but after 10 seconds, the Pod for the Job is marked DeadlineExceeded
, (and eventually Completed
), but a new Pod is created by the Job, i.e. it's retrying rather than terminated.
This is actually visible in the example output during step 6, which shows in the second-last output, a Job over 2 minutes old which has not been cleaned up.
Huh. While I was writing this up, one of the Jobs finally failed, with Job has reached the specified backoff limit
, after almost 12 minutes.
That matches the backoffLimit: 6
seen in the default Job earlier in the lesson, and I can see that in the Job docs, but it wasn't touched upon in the lesson.
I'd suggest maybe setting that to 1
or 0
in order to illustrate the point being made in a timely manner?
And now I'm in the docs, perhaps the problem is that activeDeadlineSeconds
should be in the jobTemplate.spec
, not the (PodSpec)jobTemplate.spec.template.spec
, where it was added in Step 5.
It was in the Job's spec
in Exercise 4.2 Step 11 as well, when the behaviour was correct.
Trying it that way, I now see the Jobs created by the CronJob are marked Failed and terminated after 10 seconds, per the exercise description.
And the failed Job is also deleted as soon as a newer job fails. I can see in the CronJob spec a default setting failedJobsHistoryLimit: 1
, which explains this, and highlights that seeing two Jobs older than 10 seconds meant that the exercise was not working.
So what I ended up with to get the right result from Exercise 4.3 Steps 5-6, compared to the given example, is:
apiVersion: batch/v1 kind: CronJob metadata: name: sleepy spec: schedule: "*/2 * * * *" jobTemplate: spec: activeDeadlineSeconds: 10 # <== This line has moved up two levels template: spec: containers: - name: resting image: busybox command: ["/bin/sleep"] args: ["30"] restartPolicy: Never
Categories
- All Categories
- 112 LFX Mentorship
- 112 LFX Mentorship: Linux Kernel
- 604 Linux Foundation IT Professional Programs
- 315 Cloud Engineer IT Professional Program
- 139 Advanced Cloud Engineer IT Professional Program
- 52 DevOps Engineer IT Professional Program
- 67 Cloud Native Developer IT Professional Program
- 3 Express Training Courses
- 3 Express Courses - Discussion Forum
- 5.3K Training Courses
- 17 LFC110 Class Forum - Discontinued
- 8 LFC131 Class Forum
- 30 LFD102 Class Forum
- 178 LFD103 Class Forum
- LFD110 Class Forum
- 24 LFD121 Class Forum
- LFD133 Class Forum
- 2 LFD137 Class Forum
- 62 LFD201 Class Forum
- 2 LFD210 Class Forum
- 1 LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 127 LFD232 Class Forum - Discontinued
- LFD233 Class Forum
- LFD237 Class Forum
- 22 LFD254 Class Forum
- 643 LFD259 Class Forum
- 107 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 4 LFD273 Class Forum
- 1 LFS101 Class Forum
- LFS112 Class Forum
- LFS116 Class Forum
- LFS118 Class Forum
- LFS144 Class Forum
- 2 LFS145 Class Forum
- LFS151 Class Forum
- LFS157 Class Forum
- LFS158 Class Forum
- LFS162 Class Forum
- LFS167 Class Forum
- 28 LFS200 Class Forum
- 735 LFS201 Class Forum - Discontinued
- 1 LFS201-JP クラス フォーラム
- 13 LFS203 Class Forum
- 98 LFS207 Class Forum
- 299 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 36 LFS243 Class Forum
- 12 LFS244 Class Forum
- LFS245 Class Forum
- 41 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 141 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 2 LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 109 LFS260 Class Forum
- 144 LFS261 Class Forum
- 39 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 20 LFS267 Class Forum
- 18 LFS268 Class Forum
- 26 LFS269 Class Forum
- 198 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 254 LFW211 Class Forum
- 173 LFW212 Class Forum
- 9 SKF100 Class Forum
- SKF200 Class Forum
- 781 Hardware
- 198 Drivers
- 68 I/O Devices
- 37 Monitors
- 95 Multimedia
- 174 Networking
- 87 Printers & Scanners
- 83 Storage
- 742 Linux Distributions
- 80 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 23 openSUSE
- 143 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 347 Ubuntu
- 450 Linux System Administration
- 31 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 76 Network Management
- 101 System Management
- 46 Web Management
- 51 Mobile Computing
- 18 Android
- 23 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 355 Off Topic
- 109 Introductions
- 167 Small Talk
- 18 Study Material
- 504 Programming and Development
- 283 Kernel Development
- 203 Software Development
- 844 Software
- 210 Applications
- 180 Command Line
- 3 Compiling/Installing
- 107 Games
- 308 Installation
- 51 All In Program
- 51 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)