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

RHEL 7.6: cluster creation fails for Kubernetes < 1.14 #820

Closed
Hendrik-H opened this issue Aug 27, 2019 · 6 comments
Closed

RHEL 7.6: cluster creation fails for Kubernetes < 1.14 #820

Hendrik-H opened this issue Aug 27, 2019 · 6 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@Hendrik-H
Copy link

What happened:
I'm trying to create clusters using kind 0.5.1 and different node images, using the list from https://github.com/kubernetes-sigs/kind/releases/tag/v0.5.0, as there is none for 0.5.1. This works fine for kindest/node:v1.15.3@sha256:27e388752544890482a86b90d8ac50fcfa63a2e8656a96ec5337b902ec8e5157 and kindest/node:v1.14.6@sha256:464a43f5cf6ad442f100b0ca881a3acae37af069d5f96849c1d06ced2870888d but fails for the other images.

The output of the command line is:

> kind create cluster --name kind-11 --image kindest/node:v1.11.10@sha256:bb22258625199ba5e47fb17a8a8a7601e536cd03456b42c1ee32672302b1f909 --retain
Creating cluster "kind-11" ...
 ✓ Ensuring node image (kindest/node:v1.11.10) 🖼
 ✓ Preparing nodes 📦 
 ✓ Creating kubeadm config 📜 
 ✗ Starting control-plane 🕹️ 
Error: failed to create cluster: failed to init node with kubeadm: exit status 1

What you expected to happen:
That the clusters get created cleanly.

How to reproduce it (as minimally and precisely as possible):

kind create cluster --name kind-11 --image kindest/node:v1.11.10@sha256:bb22258625199ba5e47fb17a8a8a7601e536cd03456b42c1ee32672302b1f909 --retain
kind create cluster --name kind-12 --image kindest/node:v1.12.10@sha256:e43003c6714cc5a9ba7cf1137df3a3b52ada5c3f2c77f8c94a4d73c82b64f6f3 --retain
kind create cluster --name kind-13 --image kindest/node:v1.13.10@sha256:2f5f882a6d0527a2284d29042f3a6a07402e1699d792d0d5a9b9a48ef155fa2a --retain

Anything else we need to know?:
The logs for a failed cluster creation:
kind-13.zip

Environment:

  • kind version: (use kind version): v0.5.1
  • Kubernetes version: (use kubectl version): v1.15.3
  • Docker version: (use docker info): 17.05.0-ce
  • OS (e.g. from /etc/os-release): RHEL 7.6
@Hendrik-H Hendrik-H added the kind/bug Categorizes issue or PR as related to a bug. label Aug 27, 2019
@BenTheElder
Copy link
Member

/assign

FWIW on a linux box (~debian testing):

$ kind create cluster --name kind-11 --image kindest/node:v1.11.10@sha256:bb22258625199ba5e47fb17a8a8a7601e536cd03456b42c1ee32672302b1f909 --retain
Creating cluster "kind-11" ...
 ✓ Ensuring node image (kindest/node:v1.11.10) 🖼
 ✓ Preparing nodes 📦 
 ✓ Creating kubeadm config 📜 
 ✓ Starting control-plane 🕹️ 
 ✓ Installing CNI 🔌 
 ✓ Installing StorageClass 💾 
Cluster creation complete. You can now use the cluster with:

export KUBECONFIG="$(kind get kubeconfig-path --name="kind-11")"
kubectl cluster-info

@BenTheElder
Copy link
Member

BenTheElder commented Aug 27, 2019

this looks like kubernetes/kubernetes#43856 (from the logs you uploaded), I'm not sure what changed in 1.14+ yet though.

@BenTheElder BenTheElder changed the title cluster creation fails for 1.11.10, 1.12.10 and 1.13.10 RHEL 7.6: cluster creation fails for Kubernetes < 1.14 Aug 27, 2019
@BenTheElder BenTheElder added the triage/needs-information Indicates an issue needs more information in order to work on it. label Sep 7, 2019
@Hendrik-H
Copy link
Author

same result on RHEL 7.7

@aojea
Copy link
Contributor

aojea commented Sep 9, 2019

@Hendrik-H have you tried using a newer version of docker?
from the logs seems you are using Server Version: 17.05.0-ce

@Hendrik-H
Copy link
Author

no, I can only test with the version that I get with RHEL

@BenTheElder
Copy link
Member

Kubernetes 1.13 is out of support upstream now, and I'm pretty sure this docker version isn't supported upstream either. I don't have RHEL, but hopefully the next RHEL release will ship something newer or we'll figure out podman..

Given that upstream supported Kubernetes versions work, I don't think we're likely to pursue this versus other work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants