-
Notifications
You must be signed in to change notification settings - Fork 366
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
getting 400 bad request #17
Comments
…on properties and doesnt ignore them like openstack does
@guy-mograbi-at-gigaspaces thanks for reporting the issue. I actually didn't have an HP account so I created one to find the issue. I have deployed the new 1.0.2 snapshots to Maven and updated the downloadable snapshot jars for 1.0.2 on the website. One thing I did notice about HP is if your using a scoped tenant (at least in my case) it was expecting the tenantId vs tenantName. The Factory builder now offers a tenantName(tenantName) and tenantId(tenantId) when authenticating. You may need to use the tenantId. Let me know if this works. |
@gondor - thanks for the response, however I am unable to reference the 1.0.2 version. using the snippet from your site
and I get
|
Try running a mvn compile -U The -U will force dependency updates. We publish to maven central so I'm not sure why your seeing this. You could also download source and then run a "mvn install" which will deploy the artifact locally for your dependent projects. |
You can always clone openstack4j and then do a "mvn install" to build and deploy the artifact locally. Closing issue as workarounds have been provided. Re-open if needed. |
1.compute:ContainX#17 getImageId() 2.image:#1 out of range of int,should use Long 3.image:#2 “result” in GlanceTask should be a Map 4.image:#3 imageStatus in GlanceImage should be status
Deprecate domain objects and builders for deprecated services
I keep getting
when I try to authenticate.
I simply copy pasted code from your homepage
I am sure my details are correct because when I do an HTTP request myself, It succeeds.
The text was updated successfully, but these errors were encountered: