-
Notifications
You must be signed in to change notification settings - Fork 239
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
Validate MachineController/OperatingSystemManager and cloudProvider None are mutually exclusive #3369
Validate MachineController/OperatingSystemManager and cloudProvider None are mutually exclusive #3369
Conversation
@kron4eg: The following test failed, say
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. I understand the commands that are listed here. |
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.
As stated in #3366 (comment), we shouldn't forbid this, but properly handle it
…one are mutually exclusive Signed-off-by: Artiom Diomin <[email protected]>
2918dda
to
27ebcec
Compare
Since we got #3416, this PR can be merge too. |
@kron4eg Yes, we can proceed if you want. |
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
/approve
LGTM label has been added. Git tree hash: 5dc83d7859faab7b905265d18441906fd69e36d8
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: xmudrii 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 |
/remove-kind bug
|
Which issue(s) this PR fixes:
Fixes #3366
What type of PR is this?
/kind bug
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: