-
Notifications
You must be signed in to change notification settings - Fork 28
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
HTTP errors using 2.2.1 #162
Comments
Opening in nodeshift repo. |
Actually I think I've found a fix. In openshift-rest-client.js add: const Request = require('kubernetes-client/backends/request') and make this change: // Current code. Doesn't work
// const client = new Client({ backend: kubeconfig || kbconfig.loadFromDefault(), spec, getNames: getNames });
// Fix per https://github.com/godaddy/kubernetes-client/blob/master/merging-with-kubernetes.md#preparing-to-upgrade-to-900
const client = new Client({ backend: new Request(kubeconfig) || kbconfig.loadFromDefault(), spec, getNames: getNames }); I'm happy to PR this. |
That's weird on how the tests passed before.
Sounds great thanks! |
A PR would be good, thanks. are you specifying your own configuration? How are you setting up the client, i guess is what i'm asking |
@lholmquist no config besides the PR opened. |
I put this in your PR, but this comment should go here @evanshortiss i reverted the changes from that other PR #160 and released a new 2.2.2 version. you should be able to get this new updated version if you remove your package-lock and do an install again This will give us more time to figure this out |
Going to close this since 2.2.2 should fix this |
Thanks! |
We noticed that since openshift-rest-client v2.2.1 was released nodeshift has stopped working for some of us.
I have a project setup on my machine using nodeshift to deploy and test on OpenShift and it was working great (thank you 🙏)
A colleague cloned the project and tried to use nodeshift, but the deploy failed with this error:
Looking at the dependency tree it seems like a new release of the openshift-rest-client was made, so it's possibly the culprit.
The original dep setup for me was:
I rm'ed my lockfile and did a reinstall and ended up with:
Adding a log in the nodeshift source allows me to get this stacktrace:
The
get()
call inbuild-config.js:84:133
triggers the error.I'm not familiar with how the swagger module and openshift-rest-client work together, but hopefully this is helpful. Maybe it's just some
The text was updated successfully, but these errors were encountered: