-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Do writes in init container before trying reads #73318
Conversation
eb61f6e
to
93d4d65
Compare
/retest |
1 similar comment
/retest |
/retest |
5389446
to
8d802f0
Compare
8d802f0
to
9f5a799
Compare
/test pull-kubernetes-e2e-kops-aws |
/retest |
@wongma7: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
@kubernetes/sig-storage-pr-reviews |
SecurityContext: &v1.SecurityContext{ | ||
Privileged: &privilegedSecurityContext, | ||
}, | ||
}, |
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.
Do we still need 2 regular containers in pod?
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.
nvm, looks like other test depend on them.
/lgtm cc @msau42 for approval. |
/lgtm |
/assign @msau42 |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: msau42, wongma7 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind flake
What this PR does / why we need it: In some subpath tests, it is expected that container 1 reads something container 0 writes, but there is no guarantee that container 0 starts before 1 (or vice versa). The read check is 10 seconds so if container 0 starts 10s after container 1, the test will fail. To work around this, make init versions of container 0 and 1 and always use the init version when writing.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
/sig storage