Skip to content

Bump rancher/local-path-provisioner to latest release #5050

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
Open
eks-distro-pr-bot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump rancher/local-path-provisioner to latest release #5050

eks-distro-pr-bot wants to merge 1 commit into from

Conversation

@eks-distro-pr-bot
Copy link
Contributor

@eks-distro-pr-bot eks-distro-pr-bot commented Dec 26, 2025 •
edited
Loading

This PR bumps rancher/local-path-provisioner 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

eks-distro-pr-bot commented Dec 26, 2025

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

@eks-distro-bot
Copy link
Collaborator

eks-distro-bot commented Dec 26, 2025

[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 pokearu for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@eks-distro-bot
Copy link
Collaborator

eks-distro-bot commented Dec 26, 2025

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.

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.

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

eks-distro-pr-bot commented Dec 27, 2025

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-rancher-local-path-provisioner-main branch 2 times, most recently from 9be0287 to c5acc6f Compare December 28, 2025 08:09
@eks-distro-pr-bot
Copy link
Contributor Author

eks-distro-pr-bot commented Dec 28, 2025

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

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

eks-distro-pr-bot commented Dec 29, 2025

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-rancher-local-path-provisioner-main branch 2 times, most recently from 1af0538 to e8cd6a9 Compare December 30, 2025 08:09
@eks-distro-pr-bot
Copy link
Contributor Author

eks-distro-pr-bot commented Dec 30, 2025

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

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

eks-distro-pr-bot commented Dec 31, 2025

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-rancher-local-path-provisioner-main branch 2 times, most recently from b95b862 to 3b62da8 Compare January 1, 2026 08:09
@eks-distro-pr-bot
Copy link
Contributor Author

eks-distro-pr-bot commented Jan 1, 2026

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-rancher-local-path-provisioner-main branch from 3b62da8 to b3a7d70 Compare January 2, 2026 08:09
@eks-distro-pr-bot
Copy link
Contributor Author

eks-distro-pr-bot commented Jan 2, 2026

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

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

eks-distro-pr-bot commented Jan 3, 2026

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-rancher-local-path-provisioner-main branch 2 times, most recently from 691d568 to 9bc9f09 Compare January 4, 2026 08:09
@eks-distro-pr-bot
Copy link
Contributor Author

eks-distro-pr-bot commented Jan 4, 2026

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

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

eks-distro-pr-bot commented Jan 5, 2026

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-rancher-local-path-provisioner-main branch from 9bc9f09 to f792916 Compare January 5, 2026 08:08
@eks-distro-pr-bot
Copy link
Contributor Author

eks-distro-pr-bot commented Jan 6, 2026

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-rancher-local-path-provisioner-main branch 2 times, most recently from 9a6c22a to d967fe5 Compare January 7, 2026 08:09
@eks-distro-pr-bot
Copy link
Contributor Author

eks-distro-pr-bot commented Jan 7, 2026

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

@eks-distro-pr-bot eks-distro-pr-bot force-pushed the update-rancher-local-path-provisioner-main branch from d967fe5 to 414d07b Compare January 8, 2026 08:09
@eks-distro-pr-bot
Copy link
Contributor Author

eks-distro-pr-bot commented Jan 8, 2026

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

The following steps in the upgrade flow failed:

  • Checksums and attribution generation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@eks-distro-pr-bot @eks-distro-bot