search

kubernetes-sigs / cluster-api-provider-azure

Cluster API implementation for Microsoft Azure
https://capz.sigs.k8s.io/
Apache License 2.0
287 stars 414 forks source link

e2e -aks job fails with GitHub API rate limiting #3133

Open mboersma opened 1 year ago

mboersma commented 1 year ago

Which jobs are failing:

pull-cluster-api-provider-azure-e2e-aks

Which tests are failing:

SynchronizedBeforeSuite, the prelude to actual testing, where we're trying to fetch cert-manager.yaml from the cert-manager GH repo.

Since when has it been failing:

At least since 1/31/2023.

Testgrid link:

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/directory/pull-cluster-api-provider-azure-e2e-aks/1620461725285355520

Reason for failure (if possible):

STEP: Initializing the bootstrap cluster @ 01/31/23 16:47:54.736
  INFO: clusterctl init --core cluster-api --bootstrap kubeadm --control-plane kubeadm --infrastructure azure --ipam  --runtime-extension  --config /logs/artifacts/repository/clusterctl-config.yaml --kubeconfig /tmp/e2e-kind3895625533
  [FAILED] in [SynchronizedBeforeSuite] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/clusterctl/client.go:94 @ 01/31/23 16:47:55.946
  << Timeline
  [FAILED] failed to run clusterctl init
  Unexpected error:
      <*errors.withStack | 0xc00224d0e0>: {
          error: <*errors.withMessage | 0xc0008c5380>{
              cause: <*errors.withStack | 0xc00224d0b0>{
                  error: <*errors.withMessage | 0xc0008c5360>{
                      cause: <*errors.fundamental | 0xc00224d080>{
                          msg: "rate limit for github api has been reached. Please wait one hour or get a personal API token and assign it to the GITHUB_TOKEN environment variable",
                          stack: [0x2ccf906, 0x2cce87a, 0x22bd6db, 0x22bd7b7, 0x22be538, 0x22be30a, 0x22be290, 0x2cce651, 0x2ccd4bf, 0x2ccbf27, 0x2ccb737, 0x2f8add6, 0x2f894ce, 0x2f89325, 0x2fe40c3, 0x2feb378, 0x2fef892, 0x36[577](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/directory/pull-cluster-api-provider-azure-e2e-aks/1620461725285355520#1:build-log.txt%3A577)10, 0x365620a, 0x154e085, 0x154d57c, 0x1947827, 0x19[580](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/directory/pull-cluster-api-provider-azure-e2e-aks/1620461725285355520#1:build-log.txt%3A580)54, 0x195b958, 0x14db741],
                      },
                      msg: "failed to get GitHub release v1.10.1",
                  },
                  stack: [0x2ccd5c8, 0x2ccbf27, 0x2ccb737, 0x2f8add6, 0x2f894ce, 0x2f89325, 0x2fe40c3, 0x2feb378, 0x2fef892, 0x3657710, 0x365620a, 0x154e085, 0x154d57c, 0x1947827, 0x1958054, 0x195b958, 0x14db741],
              },
              msg: "failed to read \"cert-manager.yaml\" from provider's repository \"cert-manager\"",
          },
          stack: [0x2ccc005, 0x2ccb737, 0x2f8add6, 0x2f894ce, 0x2f89325, 0x2fe40c3, 0x2feb378, 0x2fef892, 0x3657710, 0x365620a, 0x154e085, 0x154d57c, 0x1947827, 0x1958054, 0x195b958, 0x14db741],
      }
      failed to read "cert-manager.yaml" from provider's repository "cert-manager": failed to get GitHub release v1.10.1: rate limit for github api has been reached. Please wait one hour or get a personal API token and assign it to the GITHUB_TOKEN environment variable
  occurred

Setting up cert-manager requires fetching some resources from their repo, which we're doing anonymously. Apparently we need to set a GITHUB_TOKEN.

Anything else we need to know:

/kind failing-test

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

mboersma commented 1 year ago

/remove-lifecycle stale

Here's another example of a test that failed today due to GitHub rate limiting: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/periodic-cluster-api-provider-azure-e2e-main/1653646765460557824

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 4 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

nawazkh commented 4 months ago

/remove-lifecycle rotten

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 week ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten