Skip to content
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

kubeadm: move duplicated code into enforceRequirements() #74511

Merged

Conversation

rojkov
Copy link

@rojkov rojkov commented Feb 25, 2019

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Move duplicated code into enforceRequirements() and to a new function getK8sVersionFromUserInput().

Also drop applyPlanFlags.ignorePreflightErrorsSet field which is not a command line option.

Special notes for your reviewer:
This is a part of the PR series splitting #73135.

XXX: This PR increases code coverage, but the new tests reveal some unexpected behaviour. The current logic of handling user input is that if a user specifies a ClusterConfiguration file without KubernetesVersion specified in it and no version is given as an argument then there's no failure. Because the function LoadInitConfigurationFromFile() returns a config with some default version already defined which is taken from the release server and is not known at test time.
Thus when a new release of K8s is finalized the tests will start to fail.

Does this PR introduce a user-facing change?:

NONE

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. release-note-none Denotes a PR that doesn't merit a release note. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Feb 25, 2019
@k8s-ci-robot
Copy link
Contributor

Hi @rojkov. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Feb 25, 2019
@k8s-ci-robot k8s-ci-robot added area/kubeadm sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 25, 2019
@bart0sh
Copy link
Contributor

bart0sh commented Feb 25, 2019

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 25, 2019
@rojkov rojkov force-pushed the kubeadm-refactor-enforceRequirements branch from f780c2b to b11b7f7 Compare February 25, 2019 09:56
@bart0sh
Copy link
Contributor

bart0sh commented Feb 25, 2019

/test pull-kubernetes-integration

Copy link
Contributor

@rosti rosti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @rojkov !
We need to remove the flaky tests though.

}

// Ensure the user is root
klog.V(1).Infof("running preflight checks")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/Infof/Info

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

name: "Valid config, but no version specified",
isVersionMandatory: true,
flags: &applyPlanFlags{
cfgPath: "testdata/cluster_config_with_version.yaml",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not a big a fan of using testdata files. In fact I was planning on nuking those at some point. Trouble is, that these occasionally get recycled by other tests, the actual test data is far apart from the test code and the test data itself does not mention what it's used to test.
I'd rather keep the content of the config in a const in this file (or even test case), write it out in a temp file and supply the temp file path to cfgPath.
But that's just me, I am fine if you choose to keep the testdata files.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rewrote to create temp files with configs.

// XXX: This is possibly wrong. The current logic is that if version is omitted
// from both the config and arguments then take the latest version
// from the release server. Which is unknown at test time.
expectedVersion: "v1.13.3",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a flaky test, it requires internet connection and changing every time we release a new version. Please, don't add this case.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added this test case to illustrate a possible problem. I wasn't sure If it's expected that a user could use apply without providing any version and still get away with it.

Removed now.

// XXX: This is possibly wrong. The current logic is that if version is omitted
// from both the config and arguments then take the latest version
// from the release server. Which is unknown at test time.
expectedVersion: "v1.13.3",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again a flaky test case to be removed.

return "", err
}

if cfg.KubernetesVersion != "" {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The if statement does not make any difference if cfg.KubernetesVersion == "", because userVersion should be empty at that moment. Just leave userVersion = cfg.KubernetesVersion.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Fixed.

Copy link
Member

@yagonobre yagonobre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @rojkov
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Feb 25, 2019
and to a new function getK8sVersionFromUserInput().

Also drop applyPlanFlags.ignorePreflightErrorsSet field which is not
a command line option.
@rojkov rojkov force-pushed the kubeadm-refactor-enforceRequirements branch from b11b7f7 to 226843f Compare February 25, 2019 14:28
Copy link
Member

@neolit123 neolit123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

thanks seems like a clean change.
leaving the LGTM to others.

we also need to start auditing 1.13 -> 1.14 upgrades...

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neolit123, rojkov

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 27, 2019
@bart0sh
Copy link
Contributor

bart0sh commented Feb 28, 2019

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 28, 2019
@k8s-ci-robot k8s-ci-robot merged commit 83fc13e into kubernetes:master Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/kubeadm cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. release-note-none Denotes a PR that doesn't merit a release note. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants