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

clusterctl init does not wait for providers to be ready #3720

Closed
benmoss opened this issue Sep 30, 2020 · 10 comments
Closed

clusterctl init does not wait for providers to be ready #3720

benmoss opened this issue Sep 30, 2020 · 10 comments
Assignees
@wfernandes
Labels
area/clusterctl Issues or PRs related to clusterctl 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.
Milestone
v0.4

Comments

@benmoss
Copy link

benmoss commented Sep 30, 2020

What steps did you take and what happened:

$ clusterctl init --infrastructure aws
Fetching providers
Installing cert-manager Version="v0.16.1"
Waiting for cert-manager to be available...
Installing Provider="cluster-api" Version="v0.3.9" TargetNamespace="capi-system"
Installing Provider="bootstrap-kubeadm" Version="v0.3.9" TargetNamespace="capi-kubeadm-bootstrap-system"
Installing Provider="control-plane-kubeadm" Version="v0.3.9" TargetNamespace="capi-kubeadm-control-plane-system"
Installing Provider="infrastructure-aws" Version="v0.6.0" TargetNamespace="capa-system"

Your management cluster has been initialized successfully!

You can now create your first workload cluster by running the following:

  clusterctl config cluster [name] --kubernetes-version [version] | kubectl apply -f -

$ clusterctl config cluster bmo --kubernetes-version v1.17.3 --control-plane-machine-count=1 | k apply -f-
kubeadmcontrolplane.controlplane.cluster.x-k8s.io/bmo-control-plane created
kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/bmo-md-0 created
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "default.cluster.cluster.x-k8s.io": Post "https://capi-webhook-service.capi-webhook-system.svc:443/mutate-cluster-x-k8s-io-v1alpha3-cluster?timeout=30s": dial tcp 10.105.38.110:443: connect: connection
refused
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "default.awscluster.infrastructure.cluster.x-k8s.io": Post "https://capa-webhook-service.capi-webhook-system.svc:443/mutate-infrastructure-cluster-x-k8s-io-v1alpha3-awscluster?timeout=30s": dial tcp 10.101.166.65:443: connect: connection refused
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "validation.awsmachinetemplate.infrastructure.x-k8s.io": Post "https://capa-webhook-service.capi-webhook-system.svc:443/validate-infrastructure-cluster-x-k8s-io-v1alpha3-awsmachinetemplate?timeout=30s": dial tcp 10.101.166.65:443: connect: connection refused
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "default.machinedeployment.cluster.x-k8s.io": Post "https://capi-webhook-service.capi-webhook-system.svc:443/mutate-cluster-x-k8s-io-v1alpha3-machinedeployment?timeout=30s": dial tcp 10.105.38.110:443:
connect: connection refused
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "validation.awsmachinetemplate.infrastructure.x-k8s.io": Post "https://capa-webhook-service.capi-webhook-system.svc:443/validate-infrastructure-cluster-x-k8s-io-v1alpha3-awsmachinetemplate?timeout=30s": dial tcp 10.101.166.65:443: connect: connection refused

What did you expect to happen:
The commands should work sequentially without the user needing to wait or check to make sure pods have started.

Anything else you would like to add:

$ clusterctl version
clusterctl version: &version.Info{Major:"0", Minor:"3", GitVersion:"v0.3.9", GitCommit:"e1f67d8ceb1d5b30ef967035f7a0d1b1ee088b37", GitTreeState:"clean", BuildDate:"2020-09-01T02:44:58Z", GoVersion:"go1.13.14", Compiler:"gc", Platform:"linux/amd64"}
$ kind version
kind v0.9.0 go1.15 linux/amd64

/kind bug
/area clusterctl
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. area/clusterctl Issues or PRs related to clusterctl labels Sep 30, 2020
@k8s-ci-robot
Copy link
Contributor

@benmoss: The label(s) area/ cannot be applied, because the repository doesn't have them

In response to this:

What steps did you take and what happened:

$ clusterctl init --infrastructure aws
Fetching providers
Installing cert-manager Version="v0.16.1"
Waiting for cert-manager to be available...
Installing Provider="cluster-api" Version="v0.3.9" TargetNamespace="capi-system"
Installing Provider="bootstrap-kubeadm" Version="v0.3.9" TargetNamespace="capi-kubeadm-bootstrap-system"
Installing Provider="control-plane-kubeadm" Version="v0.3.9" TargetNamespace="capi-kubeadm-control-plane-system"
Installing Provider="infrastructure-aws" Version="v0.6.0" TargetNamespace="capa-system"

Your management cluster has been initialized successfully!

You can now create your first workload cluster by running the following:

 clusterctl config cluster [name] --kubernetes-version [version] | kubectl apply -f -

$ clusterctl config cluster bmo --kubernetes-version v1.17.3 --control-plane-machine-count=1 | k apply -f-
kubeadmcontrolplane.controlplane.cluster.x-k8s.io/bmo-control-plane created
kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/bmo-md-0 created
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "default.cluster.cluster.x-k8s.io": Post "https://capi-webhook-service.capi-webhook-system.svc:443/mutate-cluster-x-k8s-io-v1alpha3-cluster?timeout=30s": dial tcp 10.105.38.110:443: connect: connection
refused
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "default.awscluster.infrastructure.cluster.x-k8s.io": Post "https://capa-webhook-service.capi-webhook-system.svc:443/mutate-infrastructure-cluster-x-k8s-io-v1alpha3-awscluster?timeout=30s": dial tcp 10.101.166.65:443: connect: connection refused
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "validation.awsmachinetemplate.infrastructure.x-k8s.io": Post "https://capa-webhook-service.capi-webhook-system.svc:443/validate-infrastructure-cluster-x-k8s-io-v1alpha3-awsmachinetemplate?timeout=30s": dial tcp 10.101.166.65:443: connect: connection refused
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "default.machinedeployment.cluster.x-k8s.io": Post "https://capi-webhook-service.capi-webhook-system.svc:443/mutate-cluster-x-k8s-io-v1alpha3-machinedeployment?timeout=30s": dial tcp 10.105.38.110:443:
connect: connection refused
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "validation.awsmachinetemplate.infrastructure.x-k8s.io": Post "https://capa-webhook-service.capi-webhook-system.svc:443/validate-infrastructure-cluster-x-k8s-io-v1alpha3-awsmachinetemplate?timeout=30s": dial tcp 10.101.166.65:443: connect: connection refused

What did you expect to happen:
The commands should work sequentially without the user needing to wait or check to make sure pods have started.

Anything else you would like to add:

$ clusterctl version
clusterctl version: &version.Info{Major:"0", Minor:"3", GitVersion:"v0.3.9", GitCommit:"e1f67d8ceb1d5b30ef967035f7a0d1b1ee088b37", GitTreeState:"clean", BuildDate:"2020-09-01T02:44:58Z", GoVersion:"go1.13.14", Compiler:"gc", Platform:"linux/amd64"}
$ kind version
kind v0.9.0 go1.15 linux/amd64

/kind bug
/area clusterctl

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.

@benmoss benmoss mentioned this issue Sep 30, 2020
Closed
@vincepri
Copy link
Member

@wfernandes @fabriziopandini

@wfernandes
Copy link
Contributor

I can take a look into this.
/assign

@wfernandes
Copy link
Contributor

Just an update.
I haven't gotten started on this yet. Will try to start working on it next week.

@wfernandes
Copy link
Contributor

/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 Oct 13, 2020
@wfernandes wfernandes mentioned this issue Oct 16, 2020
Closed
@vincepri
Copy link
Member

/milestone v0.3.11

@k8s-ci-robot k8s-ci-robot added this to the v0.3.11 milestone Oct 16, 2020
@vincepri
Copy link
Member

/milestone v0.4.0

@k8s-ci-robot k8s-ci-robot modified the milestones: v0.3.11, v0.4.0 Oct 16, 2020
@wfernandes wfernandes mentioned this issue Oct 19, 2020
Closed
@vincepri
Copy link
Member

Closing, see #3825 (comment)

@vincepri
Copy link
Member

/close

@k8s-ci-robot
Copy link
Contributor

@vincepri: Closing this issue.

In response to this:

/close

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.

@fabriziopandini fabriziopandini mentioned this issue Apr 14, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wfernandes wfernandes

Labels
area/clusterctl Issues or PRs related to clusterctl 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.
Projects
None yet
Milestone
v0.4
4 participants
@benmoss @wfernandes @vincepri @k8s-ci-robot