Flakes while running the E2E test suite

srm09 commented 2 years ago

/kind bug

What steps did you take and what happened: Observing random failures during cluster creation in the E2E test suite. The flake specifically occurs when the ClusterResourceSet tries to apply the resources but fails to initiate a connection with the remote kube-api server of the workload cluster. Error condition from the CRS object

status:
  conditions:
  - lastTransitionTime: "2022-02-09T16:13:30Z"
    message: 'error creating client and cache for remote cluster: error creating dynamic
      rest mapper for remote cluster "quick-start-psb07a/quick-start-mnb1dm": Get
      "https://192.168.6.165:6443/api?timeout=10s": x509: certificate signed by unknown
      authority (possibly because of "crypto/rsa: verification error" while trying
      to verify candidate authority certificate "kubernetes")'
    reason: RemoteClusterClientFailed
    severity: Error
    status: "False"
    type: ResourcesApplied
  observedGeneration: 1

What did you expect to happen: Cluster creation is successful in case of no errors.

Anything else you would like to add: Test failures:

Environment:

Cluster-api-provider-vsphere version: main
Kubernetes version: (use kubectl version): v1.19
OS (e.g. from /etc/os-release): photon

/priority critical-urgent /area testing

k8s-triage-robot commented 2 years ago

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:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

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

/lifecycle stale

srm09 commented 2 years ago

/close This was due to conflicting IP addresses in the CI.

k8s-ci-robot commented 2 years ago

@srm09: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/issues/1423#issuecomment-1122814424): >/close >This was due to conflicting IP addresses in the CI. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

nguyenthai0107 commented 1 year ago

Hello @srm09 Could you please explain which exactly conflicting IP addresses. Im facing this exactly issue. Thank you

kubernetes-sigs / cluster-api-provider-vsphere

Flakes while running the E2E test suite #1423