-
Notifications
You must be signed in to change notification settings - Fork 177
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
Add an e2e test for retryable NodeConfig mount units #2253
base: master
Are you sure you want to change the base?
Conversation
@rzetelskik: GitHub didn't allow me to request PR reviews from the following users: rzetelskik. Note that only scylladb members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
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-sigs/prow repository. |
23d1880
to
752ef07
Compare
752ef07
to
51e7c47
Compare
/cc zimnx tnozicka |
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.
lgtm
/assign tnozicka
ping @tnozicka |
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.
/approve
please
/hold
for #1955 (conflicts)
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rzetelskik, tnozicka, zimnx 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 |
Description of your changes: It seems that the scenario described in #1559 has been covered by #2134. I wasn't able to find a scenario that would differentiate the case where a mount unit would require a restart to end up in an active state (as opposed to just starting it again as we do now), so this PR only adds an e2e covering the scenario described in the issue. We can go back to discussing the restarts if an actual scenario comes up.
Which issue is resolved by this Pull Request:
Resolves #1559
/kind feature
/priority important-longterm
/cc