Skip to content
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.

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

Bump tinkerbell/cluster-api-provider-tinkerbell to latest release #4099

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

eks-distro-pr-bot
Copy link
Contributor

@eks-distro-pr-bot eks-distro-pr-bot commented Nov 26, 2024

This PR bumps tinkerbell/cluster-api-provider-tinkerbell to the latest Git revision.

Compare changes
Release notes

/hold
/area dependencies

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

@eks-distro-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ahreehong for approval. For more information see the Kubernetes Code Review Process.

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

@eks-distro-bot
Copy link
Collaborator

Hi @eks-distro-pr-bot. Thanks for your PR.

I'm waiting for a aws member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@eks-distro-bot eks-distro-bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Nov 26, 2024
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-tinkerbell-cluster-api-provider-tinkerbell-main branch 2 times, most recently from debcdc6 to dc3a87b Compare November 28, 2024 08:08
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

1 similar comment
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-tinkerbell-cluster-api-provider-tinkerbell-main branch 2 times, most recently from 462ee1e to 0294dc8 Compare November 30, 2024 08:06
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-tinkerbell-cluster-api-provider-tinkerbell-main branch from 0294dc8 to 31d63bb Compare December 1, 2024 08:07
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

1 similar comment
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-tinkerbell-cluster-api-provider-tinkerbell-main branch 2 times, most recently from 3020c96 to 162d04d Compare December 3, 2024 08:08
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

1 similar comment
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-tinkerbell-cluster-api-provider-tinkerbell-main branch from 162d04d to 1b69dac Compare December 4, 2024 08:08
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-tinkerbell-cluster-api-provider-tinkerbell-main branch from 1b69dac to 5503138 Compare December 5, 2024 08:07
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-tinkerbell-cluster-api-provider-tinkerbell-main branch 2 times, most recently from ba2b23f to fbbad9c Compare December 7, 2024 08:08
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

1 similar comment
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-tinkerbell-cluster-api-provider-tinkerbell-main branch 2 times, most recently from fbb55c5 to 4c3d3af Compare December 9, 2024 08:06
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

1 similar comment
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-tinkerbell-cluster-api-provider-tinkerbell-main branch from 4c3d3af to ca891cb Compare December 10, 2024 08:09
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-tinkerbell-cluster-api-provider-tinkerbell-main branch from ca891cb to 375c2a9 Compare December 11, 2024 08:08
@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-tinkerbell-cluster-api-provider-tinkerbell-main branch from 375c2a9 to ae29906 Compare December 12, 2024 08:08
@eks-distro-pr-bot
Copy link
Contributor Author

This pull request is incomplete and requires manual intervention from a team member!

The following steps in the upgrade flow failed:

  • Patch application

Failed patch details

Only 0/1 patches were applied!
Patch failed at 0001 Allow inUse and provisioned to be used to check hardware ready
The following files in the above patch did not apply successfully:
controllers/machine_reconcile_scope.go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependencies do-not-merge/hold needs-ok-to-test size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants