Cherry-pick bot failing with pushToNamedFork is not implemented in the v2 client
#30937
Comments
|
There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:
Please see the group list for a listing of the SIGs, working groups, and committees available. 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
added
the
needs-sig
|
Maybe related to #30924 |
|
/cc |
|
@cjwagner just in case you have some idea if that change could have this impact. |
|
/cc |
|
Yeah that PR is definitely the cause of this. I didn't realize there was an unimplemented method in the v2 client. I'll push a fix ASAP (by tomorrow). |
|
this is not fixed yet, I could still get the same error. |
|
/reopen |
|
@andyzhangx: Reopened this issue. In response to this:
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. |
|
The code should be fixed, it just needs to be deployed: #30981 |
What happened:
k8s-infra-cherrypick-robot is failing to do cherry-picks with the error
failed to push cherry-picked changes in GitHub: pushToNamedFork is not implemented in the v2 clientAn example of this error occurring is
What you expected to happen:
Cherry-pick PR to be opened against correct branch
How to reproduce it (as minimally and precisely as possible):
Comment the
/cherry-pick release-1.8on PR https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/pull/2397
Please provide links to example occurrences, if any:
https://github.com/kubernetes-sigs/cluster-api-provider-vsphere
/pull/2397#issuecomment-1746652732
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: