-
Notifications
You must be signed in to change notification settings - Fork 4.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
Limit fail-on-swap override to cluster-up #17385
Conversation
/assign @mfojtik |
@liggitt fyi I had to cherry pick the helper.go change into my PR to get cluster up to work post-rebase. Not sure why since I see how you're hardcoding the setting to false, but it seems like something in cluster up wasn't picking up that false value until it was set explicitly in the config. |
fyi my PR is here: #17338 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, liggitt The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue (batch tested with PRs 17395, 17385). |
@liggitt: The following tests 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. |
nodeCfg.KubeletArguments["cgroup-driver"] = []string{cgroupDriver} | ||
} | ||
nodeCfg.KubeletArguments["fail-swap-on"] = []string{"false"} |
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.
this appears to have broken backwards compatibility for cluster up.
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.
error: Invalid NodeConfig /var/lib/origin/openshift.local.config/node-localhost/node-config.yaml
flag: Invalid value: "fail-swap-on": is not a valid flag
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.
will update with a version gated check
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.
sadly it's going to have to be something like "greater than 3.8.0-alpha.0".
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.
oh, I know. and I'm sad
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.
Follow up from rebase. Ansible disables swap, so we only need to prevent the "crash on start" behavior for cluster-up