Skip to content

[release-0.5] update capi references to v0.4.7#2036

Merged
k8s-ci-robot merged 1 commit into
kubernetes-sigs:release-0.5from
jackfrancis:capi-v0.4.7-release-0.5
Feb 2, 2022
Merged

[release-0.5] update capi references to v0.4.7#2036
k8s-ci-robot merged 1 commit into
kubernetes-sigs:release-0.5from
jackfrancis:capi-v0.4.7-release-0.5

Conversation

@jackfrancis
Copy link
Copy Markdown
Contributor

@jackfrancis jackfrancis commented Feb 2, 2022 •
edited
Loading

What type of PR is this?

/kind failing-test

What this PR does / why we need it:

This PR updates the release-0.5 branch to refer to a new v0.4 release of capi, enabling us to continue testing the 0.5 release branch of capz

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

  • squashed commits
  • includes documentation
  • adds unit tests

Release note:

NONE

@k8s-ci-robot k8s-ci-robot added this to the v0.5 milestone Feb 2, 2022
@k8s-ci-robot k8s-ci-robot added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 2, 2022
@k8s-ci-robot k8s-ci-robot added area/provider/azure Issues or PRs related to azure provider sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels Feb 2, 2022
@CecileRobertMichon
Copy link
Copy Markdown
Contributor

CecileRobertMichon commented Feb 2, 2022

/lgtm

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Feb 2, 2022
mboersma
mboersma approved these changes Feb 2, 2022
View reviewed changes
Copy link
Copy Markdown
Contributor

@mboersma mboersma left a comment

Choose a reason for hiding this comment

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

/lgtm

@CecileRobertMichon
Copy link
Copy Markdown
Contributor

CecileRobertMichon commented Feb 2, 2022

we can ignore the exp test until #2028 merges but ci-entrypoint should pass

/retest

@CecileRobertMichon
Copy link
Copy Markdown
Contributor

CecileRobertMichon commented Feb 2, 2022

private cluster flake, everything else looks good

/retest

@CecileRobertMichon
Copy link
Copy Markdown
Contributor

CecileRobertMichon commented Feb 2, 2022

/approve

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Feb 2, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CecileRobertMichon

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 Feb 2, 2022
@CecileRobertMichon CecileRobertMichon mentioned this pull request Feb 2, 2022
Merged
@jackfrancis
Copy link
Copy Markdown
Contributor Author

jackfrancis commented Feb 2, 2022

/retest

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Feb 2, 2022 •
edited
Loading

@jackfrancis: The following test 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-azure-e2e-exp-v1alpha4 ca73bad link false /test pull-cluster-api-provider-azure-e2e-exp-v1alpha4

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.

Details

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 k8s-ci-robot merged commit 1285592 into kubernetes-sigs:release-0.5 Feb 2, 2022
@jackfrancis jackfrancis deleted the capi-v0.4.7-release-0.5 branch February 2, 2022 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mboersma mboersma mboersma approved these changes

@cpanato cpanato Awaiting requested review from cpanato

Assignees

@mboersma mboersma

@CecileRobertMichon CecileRobertMichon

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/provider/azure Issues or PRs related to azure provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Milestone

v0.5

Development

Successfully merging this pull request may close these issues.

4 participants

@jackfrancis @CecileRobertMichon @k8s-ci-robot @mboersma