-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scheduledjob e2e #26027
Scheduledjob e2e #26027
Conversation
err = waitForActiveJobs(f.Client, f.Namespace.Name, scheduledJob.Name, 2) | ||
Expect(err).NotTo(HaveOccurred()) | ||
|
||
By("Removing scheduledjob") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should deleting a scheduledJob delete its jobs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm... that's something I wasn't sure about, either. With current approach I've decided that at least removing the SJ will not schedule more jobs, especially that the schedule is pretty dense (new job every 5 sec.). The question is do we care about the jobs after the SJ is removed? I'm inclined to say no. Lemme check how deployments treat older RS, if removing those will also remove them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my quick skim over the DeploymentReaper
it looks like it removes all related ReplicaSet
s. In that case I'd say yes remove all.
This is blocked by #25952. |
Running all three e2e tests in #29137 gives me
|
I haven't got a chance to verify this properly at the time of writing. I'll On Aug 4, 2016 8:02 PM, "Janet Kuo" notifications@github.com wrote:
|
5c9b13f
to
ea04eb4
Compare
This relies on #30227, I've added option to set the testing group, so no more |
Yes we can enable |
) | ||
|
||
var _ = framework.KubeDescribe("ScheduledJob", func() { | ||
options := framework.FrameworkOptions{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or can we do something like:
f := framework.NewDefaultFramework("scheduledjob")
f.GroupVersion = &unversioned.GroupVersion{Group: batch.GroupName, Version: "v2alpha1"}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd propose leave this as is for now, the end goal is to entirely get rid of the unversioned client, then the problem should disappear and SJ is first on my list, but that will be not sooner than 1.5.
I found a bug in sj controller and you'll need this PR #30327 |
@kubernetes/sig-testing how can I globally enable |
ea04eb4
to
30785b4
Compare
30785b4
to
c0eded3
Compare
No reaper yet, need to write one. Will work on it tomorrow.
Done.
Done, but I aslo found a bug there, see #30442 I'll rebase this once your PR lands. |
Reading #30442 makes me think that we should verify pods created by jobs as well. Reviewed 1 of 1 files at r5. test/e2e/scheduledjob.go, line 60 [r5] (raw file):
Could there be more than two jobs? test/e2e/scheduledjob.go, line 233 [r5] (raw file):
Optional: test/e2e/scheduledjob.go, line 240 [r5] (raw file):
If there are more than 1 jobs, should we return error? Comments from Reviewable |
Review status: all files reviewed at latest revision, 5 unresolved discussions. test/e2e/scheduledjob.go, line 60 [r5] (raw file):
|
If you don't mind I'll leave it as a follow up because of that particular issue. |
c0eded3
to
783df12
Compare
GCE e2e build/test passed for commit 783df12. |
Reviewed 1 of 1 files at r6. Comments from Reviewable |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
I'm removing lgtm label, because this needs #30327 first |
GCE e2e build/test passed for commit 783df12. |
Automatic merge from submit-queue |
Apparently it was too late. |
Failure on GKE:
|
Does |
Maybe set |
The pattern I've noticed is that I set |
@erictune last element of the scheduledjob puzzle. I think we'll iterate on this once we have all the puzzles in place. This is one of those things that will be allowed to merge after code freeze.
This change is