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.

Sign up for GitHub

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

Jump to bottom

kubeadm alpha phase preflight master fails #924

Closed
fabriziopandini opened this issue Jun 15, 2018 · 6 comments · Fixed by kubernetes/kubernetes#68446
Closed

kubeadm alpha phase preflight master fails #924

fabriziopandini opened this issue Jun 15, 2018 · 6 comments · Fixed by kubernetes/kubernetes#68446
Assignees
@neolit123 @fabriziopandini
Labels
area/UX kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Milestone
v1.12

Comments

@fabriziopandini
Copy link
Member

Is this a BUG REPORT or FEATURE REQUEST?

BUG REPORT

Versions

v1.11 (.debs, kubeadm binary e docker images build from master)

What happened?

sudo kubeadm alpha phase preflight master failed with:

I0615 12:04:11.687738    7245 kernel_validator.go:81] Validating kernel version
I0615 12:04:11.687816    7245 kernel_validator.go:96] Validating kernel config
	[WARNING Hostname]: hostname "" could not be reached
	[WARNING Hostname]: hostname "" lookup : no such host
[preflight] Some fatal errors occurred:
	[ERROR KubernetesVersion]: couldn't parse kubernetes version "": could not parse "" as version
	[ERROR CRI]: unable to find command crictl: exec: "crictl": executable file not found in $PATH
	[ERROR Hostname]: hostname "" a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`

What you expected to happen?

sudo kubeadm alpha phase preflight master to works; probably, we should change the command to require --config parameter instead of using an empty config map
@fabriziopandini fabriziopandini added kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/UX sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels Jun 15, 2018
@seh
Copy link

seh commented Jun 16, 2018

Potentially related, as a subset of this complaint: #835.

@luxas
Copy link
Member

luxas commented Jun 17, 2018

Yeah solving #835 fixed this a bit, but there is still the bug that this phase should require config to be functional (create the --config flag and make it mandatory)

/assign @fabriziopandini

@luxas luxas added this to the v1.12 milestone Jun 17, 2018
@miry
Copy link

miry commented Jun 23, 2018

@luxas btw in v1.11-beta.2 we had only warning message if there are no cri tools.
[WARNING FileExisting-crictl]: crictl not found in system path
In version v1.11-rc.1 it is error, that related to this exception. Do you know why it becomes important?

@timothysc
Copy link
Member

@fabriziopandini could you post an update on this please.

@fabriziopandini
Copy link
Member Author

@timothysc the error is confirmed i v1.12.0-beta.1 as well (even if slightly changed)

$ sudo kubeadm alpha phase preflight master
	[WARNING Hostname]: hostname "" could not be reached
	[WARNING Hostname]: hostname "" lookup : no such host
[preflight] Some fatal errors occurred:
	[ERROR KubernetesVersion]: couldn't parse kubernetes version "": could not parse "" as version
	[ERROR CRI]: container runtime is not running: output: NAME:
   crictl info - Display information of the container runtime

USAGE:
   crictl info [command options] [arguments...]

OPTIONS:
   --output value, -o value  Output format, One of: json|yaml (default: "json")

time="2018-09-07T15:10:23Z" level=fatal msg="failed to connect: --runtime-endpoint is not set"
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`

@fabriziopandini fabriziopandini changed the title kubeadm alpha phase preflight master fails in v1.11 kubeadm alpha phase preflight master fails Sep 9, 2018
@neolit123
Copy link
Member

/assign @neolit123
/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Sep 9, 2018
@neolit123 neolit123 mentioned this issue Sep 9, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@neolit123 neolit123

@fabriziopandini fabriziopandini

Labels
area/UX kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Milestone
v1.12
Development

Successfully merging a pull request may close this issue.

kubeadm: add mandatory configuration to "phase preflight" neolit123/kubernetes
7 participants
@miry @timothysc @seh @neolit123 @fabriziopandini @luxas @k8s-ci-robot