Skip to content

Test flake: integration #1835

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
Closed
ncdc opened this issue Dec 4, 2019 · 0 comments · Fixed by #1836
Closed

Test flake: integration #1835

ncdc opened this issue Dec 4, 2019 · 0 comments · Fixed by #1836
Assignees
@ncdc
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. 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.
Milestone
v0.3.0

Comments

@ncdc
Copy link
Contributor

ncdc commented Dec 4, 2019

The integration tests are flakey because cert-manager might not be fully initialized by the time we try to install CAPI. An example flake is here: https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api/1826/pull-cluster-api-integration/1202351416828497920

service/cert-manager created
service/cert-manager-webhook created
deployment.apps/cert-manager-cainjector created
deployment.apps/cert-manager created
deployment.apps/cert-manager-webhook created
apiservice.apiregistration.k8s.io/v1beta1.webhook.cert-manager.io created
mutatingwebhookconfiguration.admissionregistration.k8s.io/cert-manager-webhook created
validatingwebhookconfiguration.admissionregistration.k8s.io/cert-manager-webhook created
Replicas:               1 desired | 1 updated | 1 total | 1 available | 0 unavailable
namespace/capi-system created
customresourcedefinition.apiextensions.k8s.io/clusters.cluster.x-k8s.io created
customresourcedefinition.apiextensions.k8s.io/kubeadmconfigs.bootstrap.cluster.x-k8s.io created
customresourcedefinition.apiextensions.k8s.io/kubeadmconfigtemplates.bootstrap.cluster.x-k8s.io created
customresourcedefinition.apiextensions.k8s.io/kubeadmcontrolplanes.cluster.x-k8s.io created
customresourcedefinition.apiextensions.k8s.io/machinedeployments.cluster.x-k8s.io created
customresourcedefinition.apiextensions.k8s.io/machines.cluster.x-k8s.io created
customresourcedefinition.apiextensions.k8s.io/machinesets.cluster.x-k8s.io created
mutatingwebhookconfiguration.admissionregistration.k8s.io/capi-mutating-webhook-configuration created
role.rbac.authorization.k8s.io/capi-leader-election-role created
clusterrole.rbac.authorization.k8s.io/capi-manager-role created
rolebinding.rbac.authorization.k8s.io/capi-leader-election-rolebinding created
clusterrolebinding.rbac.authorization.k8s.io/capi-manager-rolebinding created
service/capi-webhook-service created
deployment.apps/capi-controller-manager created
validatingwebhookconfiguration.admissionregistration.k8s.io/capi-validating-webhook-configuration created
namespace/provider-system created
role.rbac.authorization.k8s.io/provider-leader-election-role created
clusterrole.rbac.authorization.k8s.io/provider-manager-role created
rolebinding.rbac.authorization.k8s.io/provider-leader-election-rolebinding created
clusterrolebinding.rbac.authorization.k8s.io/provider-manager-rolebinding created
deployment.apps/provider-controller-manager created
Error from server (InternalError): error when creating "crd.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": the server is currently unable to handle the request
Error from server (InternalError): error when creating "crd.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": the server is currently unable to handle the request
+ EXIT_VALUE=1

We should be able to instead wait for the cert-manager apiservice to be available.

/kind failing-test
/kind flake
/priority important-soon
/milestone v0.3.0
/assign
/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 Dec 4, 2019
@k8s-ci-robot k8s-ci-robot added this to the v0.3.0 milestone Dec 4, 2019
@k8s-ci-robot k8s-ci-robot added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Dec 4, 2019
@ncdc ncdc mentioned this issue Dec 4, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ncdc ncdc

Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. kind/flake Categorizes issue or PR as related to a flaky test. 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.
Projects
None yet
Milestone
v0.3.0
Development

Successfully merging a pull request may close this issue.

🏃 integration test: better cert-manager wait ncdc/cluster-api
2 participants
@ncdc @k8s-ci-robot