-
Notifications
You must be signed in to change notification settings - Fork 82
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
Local strategy fails on port forwarding in our case of cross-cluster migration (error upgrading connection: Unauthorized) #236
Comments
Thanks for the detailed report. Can you retry with the args |
Sure. I don't see any extra info in it unfortunately.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Generally, port forwarding fails while using local strategy.
Digging more into the problem, it seems like the Dialer object (in portforward.go, after calling forwarder.ForwardPorts()) throws back an error, stating
error upgrading connection: Unauthorized
. The strange thing is, that pv-migrate is easily able to make a connection to the cluster, because the pods are created properly. Port forwarding withkubectl
also works without an issue, with the same kube config files (and yes, I have tried to explicitly give the context files to pv-migrate as well). Comparing the source code of pv-migrate with kubectl, the used RestConfig is a bit different, but the BearerToken is the same in both cases, so that shouldn't be the issue. Other than that, the port forwarding code is (at first glance) identical with the one used in kubectl.To Reproduce
Steps to reproduce the behavior:
pv-migrate migrate --log-level trace -s local -i -c cluster1 -C cluster2 -N testns -n testns vol-claim1 vol-claim2
Expected behavior
Port forward should not fail.
Console output
Version
pv-migrate
version and architecture: v1.2.0 - linux_x86_64Additional context
Rancher clusters. Probably not reproducible in every cluster, since I'm the first reporter of this issue.
The text was updated successfully, but these errors were encountered: