Skip to content

capz: debug failing periodic main job #26746

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
jackfrancis wants to merge 1 commit into from
Closed

capz: debug failing periodic main job #26746

jackfrancis wants to merge 1 commit into from

Conversation

@jackfrancis
Copy link
Contributor

@jackfrancis jackfrancis commented Jul 5, 2022

This PR updates the capz periodic main test job to this dedicated PR branch used for turning these flakes green:

kubernetes-sigs/cluster-api-provider-azure#2451

As of 5 July 2022 8 of the past 10 jobs have failed, so it would be defensible to consider this job (or capz @ main) unstable. Having a dedicated branch to change and observe outcomes to test configuration (or code) changes will help us triage which of those two possibilities are true, and how best to make things healthy again.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. area/config Issues or PRs related to code in /config labels Jul 5, 2022
@jackfrancis
Copy link
Contributor Author

jackfrancis commented Jul 5, 2022

cc @CecileRobertMichon @jsturtevant

@k8s-ci-robot k8s-ci-robot added area/jobs area/provider/azure Issues or PRs related to azure provider sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Jul 5, 2022
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jul 5, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jackfrancis

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

The pull request process is described here

Details 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 k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 5, 2022
CecileRobertMichon
CecileRobertMichon reviewed Jul 5, 2022
View reviewed changes
...bs/kubernetes-sigs/cluster-api-provider-azure/cluster-api-provider-azure-periodics-main.yaml
preset-azure-anonymous-pull: "true"
extra_refs:
- org: kubernetes-sigs
- org: jackfrancis
Copy link
Member

@CecileRobertMichon CecileRobertMichon Jul 5, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should be running the same tests as presubmit jobs, is there any reason we can't use CI running on a PR to investigate failures? are there flakes observed in periodic jobs that can't be reproduced in presubmit?

@CecileRobertMichon
Copy link
Member

CecileRobertMichon commented Jul 6, 2022

/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 6, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Oct 4, 2022

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 4, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Nov 3, 2022

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:

  • 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 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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 3, 2022
@jackfrancis jackfrancis closed this Nov 4, 2022
@jackfrancis jackfrancis deleted the capz-periodic-main-flakes branch November 4, 2022 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Jont828 Jont828 Awaiting requested review from Jont828

@jsturtevant jsturtevant Awaiting requested review from jsturtevant

1 more reviewer

@CecileRobertMichon CecileRobertMichon CecileRobertMichon left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/config Issues or PRs related to code in /config area/jobs area/provider/azure Issues or PRs related to azure provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@jackfrancis @k8s-ci-robot @CecileRobertMichon @k8s-triage-robot