cluster-api-provider-vsphere icon indicating copy to clipboard operation
cluster-api-provider-vsphere copied to clipboard

Add a logging statement so that in networking blips the dissapearance…

Open jayunit100 opened this issue 3 years ago • 6 comments
trafficstars

Fixes part of seeing #1328 when it happens

jayunit100 avatar Dec 14 '21 12:12 jayunit100

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please assign randomvariable after the PR has been reviewed. You can assign the PR to them by writing /assign @randomvariable in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

k8s-ci-robot avatar Dec 14 '21 12:12 k8s-ci-robot

/retest

jayunit100 avatar Dec 14 '21 14:12 jayunit100

/retest

srm09 avatar Jan 04 '22 00:01 srm09

/retest

MaxRink avatar Jan 31 '22 22:01 MaxRink

@jayunit100: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-cluster-api-provider-vsphere-test 70dcf4b3a46fa4eaa87c5fa67ab1a356f022ba03 link true /test pull-cluster-api-provider-vsphere-test
pull-cluster-api-provider-vsphere-apidiff-main 70dcf4b3a46fa4eaa87c5fa67ab1a356f022ba03 link true /test pull-cluster-api-provider-vsphere-apidiff-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

k8s-ci-robot avatar May 10 '22 20:05 k8s-ci-robot

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

k8s-triage-robot avatar Aug 08 '22 20:08 k8s-triage-robot

/close

srm09 avatar Aug 18 '22 05:08 srm09

@srm09: Closed this PR.

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.

k8s-ci-robot avatar Aug 18 '22 05:08 k8s-ci-robot