-
Notifications
You must be signed in to change notification settings - Fork 418
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
Disk and File CI jobs fail to configure management cluster fully #1596
Comments
This should be fixed by kubernetes-sigs/cluster-api#4989 once we pull in a newer CAPI version which will make sure the webhook is ready before marking the deployment as ready (we already wait for the deployment to be ready before proceeding) |
Any ideas on why it is only occurring in the Disk and File jobs only? |
The conformance jobs create the cluster resource set for the CNI per cluster, when each workload cluster is created. This probably gives it a few more seconds for the webhook to become ready which is why we don't run into this error. The ci-entrypoint script installs the calico resource set right after creating the management cluster, as soon as the deployments are "available". |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
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. |
/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
During the Management cluster configuration steps, the system doesn't seem to be fully online. I noticed this only happens with the disk and file CI jobs. The error messages aren't the same but it looks to may be related (if not we can split them out)
The Disk and File jobs have a different entry point from the conformance jobs. There could be a difference in the scripts?
Disk and File: https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/master/scripts/ci-entrypoint.sh
Conformance jobs: https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/master/scripts/ci-conformance.sh
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/capz-azure-disk-vmss-master/1423754824020660224
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/capz-azure-file-1-22/1424062353263038464
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/capz-azure-disk-1-21/1424189442528120832
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/capz-azure-file-vmss-1-20/1422249304768122880
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/capz-azure-disk-vmss-1-19/1424061850206605312
What did you expect to happen:
Management cluster to come online
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: