-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Increase the AppArmor pod stop timeout to match the start timeout #31314
Conversation
LGTM |
@@ -146,7 +146,9 @@ func loadTestProfiles() error { | |||
|
|||
func runAppArmorTest(f *framework.Framework, profile string) api.PodStatus { | |||
pod := createPodWithAppArmor(f, profile) | |||
framework.ExpectNoError(f.WaitForPodNoLongerRunning(pod.Name)) | |||
// The pod needs to start before it stops, so wait for the longer start timeout. |
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.
Just for my own education, all apparmor tests expect the pod to fail in certain way?
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.
not necessarily fail. The pod container just runs touch and exits, and then the apparmor tests look at the container exit code to determine whether it succeeded (which should be conditional on whether the profile was applied correctly)
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 see. So the test expects the pod to terminate soon. Thanks for answering!
GCE e2e build/test passed for commit a29ad35. |
Automatic merge from submit-queue |
Fixes #30750
This change is