[JIRA] [openstack-cloud-plugin] (JENKINS-35347) unable to test connection when using keystone V3 API

2016-06-10 Thread jjfig...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Juan Jose Figueredo commented on  JENKINS-35347 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unable to test connection when using keystone V3 API  
 
 
 
 
 
 
 
 
 
 
I have been checking again openstack-cloud-2.9-SNAPSHOT.hpi and I have the same response as Yufen Kuo, my fault was that I had in End Point URL the /domain. This is because I tried configuring the domain somewhere (I also tried in the user identity…) and when I replied the jira I forgot to remove it from the End Point URL and I copied the wrong response. I´m sorry. Testing with curl, I have also the same response as Yufen Kuo. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [openstack-cloud-plugin] (JENKINS-35347) unable to test connection when using keystone V3 API

2016-06-10 Thread y...@mvista.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yufen Kuo commented on  JENKINS-35347 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unable to test connection when using keystone V3 API  
 
 
 
 
 
 
 
 
 
 
Using curl to test the V3 APIs with and without domain: 
With domain: 

 

curl -i \
  -H "Content-Type: application/json" \
  -d '
{ "auth": {
"identity": {
  "methods": ["password"],
  "password": {
"user": {
  "name": "admin",
  "domain": { "name": "default" },
  "password": "admin"
}
  }
}
  }
}' \
  http://ostackcon12:35357/v3/auth/tokens ; echo

 

 
Would get token successfully 

 

HTTP/1.1 201 Created
Date: Fri, 10 Jun 2016 20:37:55 GMT
Server: Apache/2.4.6 (CentOS) mod_wsgi/3.4 Python/2.7.5
X-Subject-Token: gABXWyUjs8sxqZ0NwNtsdco65iNXieAVRHlXlhSUFaCQKKxmtgIewl1HwR-G9CJlkKQFHHDTYgo9e6-DWSSqWybnT4HIMH0gMH_peO6FIOylM8uWLYNQIplI5kDIc1pKi4_A9Mnitgwu3Y3n3Frj5CpKJ6fzRQ
Vary: X-Auth-Token
x-openstack-request-id: req-c15a17f5-cda7-4a0b-bead-9055a71100a9
Content-Length: 308
Content-Type: application/json

{"token": {"issued_at": "2016-06-10T20:37:55.00Z", "audit_ids": ["U4kTyl8JTnmDsG5NwryZWA"], "methods": ["password"], "expires_at": "2016-06-10T21:37:55.592538Z", "user": {"domain": {"id": "3bed6fb34c1a4bd687e7ece65eca05cd", "name": "default"}, "id": "87f5a285fd404520bdccd05756235ff8", "name": "admin"}}}

 

 
Remove domain line: 

 

HTTP/1.1 400 Bad Request
Date: Fri, 10 Jun 2016 20:40:01 GMT
Server: Apache/2.4.6 (CentOS) mod_wsgi/3.4 Python/2.7.5
Vary: X-Auth-Token
x-openstack-request-id: req-6e41d558-dec5-4abf-8355-c9b91e2f1daa
Content-Length: 233
Connection: close
Content-Type: application/json

{"error": {"message": "Expecting to find domain in user - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error.", "code": 400, "title": "Bad Request"}}

 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 

[JIRA] [openstack-cloud-plugin] (JENKINS-35347) unable to test connection when using keystone V3 API

2016-06-10 Thread y...@mvista.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yufen Kuo commented on  JENKINS-35347 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unable to test connection when using keystone V3 API  
 
 
 
 
 
 
 
 
 
 
I am getting a different error message/stacktrace when I tried  https://jenkins.ci.cloudbees.com/job/plugins/job/openstack-cloud-plugin/215/org.jenkins-ci.plugins$openstack-cloud/artifact/org.jenkins-ci.plugins/openstack-cloud/2.9-SNAPSHOT/openstack-cloud-2.9-SNAPSHOT.hpi 

 




Cannot connect to specified cloud, please check the identity and credentials: Bad Request

ClientResponseException{message=Bad Request, status=400, status-code=BAD_REQUEST}
	at org.openstack4j.core.transport.HttpExceptionHandler.mapException(HttpExceptionHandler.java:38)
	at org.openstack4j.core.transport.HttpExceptionHandler.mapException(HttpExceptionHandler.java:23)
	at org.openstack4j.openstack.internal.OSAuthenticator.authenticateV3(OSAuthenticator.java:158)
	at org.openstack4j.openstack.internal.OSAuthenticator.invoke(OSAuthenticator.java:70)
	at org.openstack4j.openstack.client.OSClientBuilder$ClientV3.authenticate(OSClientBuilder.java:165)
	at org.openstack4j.openstack.client.OSClientBuilder$ClientV3.authenticate(OSClientBuilder.java:128)
	at jenkins.plugins.openstack.compute.internal.Openstack.getClient(Openstack.java:110)
	at jenkins.plugins.openstack.compute.internal.Openstack.(Openstack.java:97)
	at jenkins.plugins.openstack.compute.internal.Openstack$Factory.getOpenstack(Openstack.java:485)
	at jenkins.plugins.openstack.compute.internal.Openstack$FactoryEP.get(Openstack.java:469)
	at jenkins.plugins.openstack.compute.JCloudsCloud$DescriptorImpl.doTestConnection(JCloudsCloud.java:478)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178)
	at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85)
	at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
	at

[JIRA] [openstack-cloud-plugin] (JENKINS-35347) unable to test connection when using keystone V3 API

2016-06-09 Thread jjfig...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Juan Jose Figueredo commented on  JENKINS-35347 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unable to test connection when using keystone V3 API  
 
 
 
 
 
 
 
 
 
 
Hello Oliver, I have just installed and tested but it still not working, the error is the same as in the summary of this jira but here you have the complete trace: 

 

Cannot connect to specified cloud, please check the identity and credentials: Not Found
ClientResponseException{message=Not Found, status=404, status-code=NOT_FOUND}
	at org.openstack4j.core.transport.HttpExceptionHandler.mapException(HttpExceptionHandler.java:38)
	at org.openstack4j.core.transport.HttpExceptionHandler.mapException(HttpExceptionHandler.java:23)
	at org.openstack4j.openstack.internal.OSAuthenticator.authenticateV3(OSAuthenticator.java:158)
	at org.openstack4j.openstack.internal.OSAuthenticator.invoke(OSAuthenticator.java:70)
	at org.openstack4j.openstack.client.OSClientBuilder$ClientV3.authenticate(OSClientBuilder.java:165)
	at org.openstack4j.openstack.client.OSClientBuilder$ClientV3.authenticate(OSClientBuilder.java:128)
	at jenkins.plugins.openstack.compute.internal.Openstack.getClient(Openstack.java:110)
	at jenkins.plugins.openstack.compute.internal.Openstack.(Openstack.java:97)
	at jenkins.plugins.openstack.compute.internal.Openstack$Factory.getOpenstack(Openstack.java:485)
	at jenkins.plugins.openstack.compute.internal.Openstack$FactoryEP.get(Openstack.java:469)
	at jenkins.plugins.openstack.compute.JCloudsCloud$DescriptorImpl.doTestConnection(JCloudsCloud.java:478)
	at sun.reflect.GeneratedMethodAccessor273.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at

[JIRA] [openstack-cloud-plugin] (JENKINS-35347) unable to test connection when using keystone V3 API

2016-06-09 Thread ogon...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-35347 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unable to test connection when using keystone V3 API  
 
 
 
 
 
 
 
 
 
 
I have done some initial steps to bring keystone v3 support: https://github.com/jenkinsci/openstack-cloud-plugin/pull/83. Please, let me know if ti works or not. Build: https://jenkins.ci.cloudbees.com/job/plugins/job/openstack-cloud-plugin/215/org.jenkins-ci.plugins$openstack-cloud/artifact/org.jenkins-ci.plugins/openstack-cloud/2.9-SNAPSHOT/openstack-cloud-2.9-SNAPSHOT.hpi 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [openstack-cloud-plugin] (JENKINS-35347) unable to test connection when using keystone V3 API

2016-06-08 Thread ogon...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-35347 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unable to test connection when using keystone V3 API  
 
 
 
 
 
 
 
 
 
 
Currently used version of openstack4j does not support keystone v3. openstack4j 3.0 does but it require JDK 8 while I need the plugin to support JDK 7 for the time being. We have done some progress in os4j upstream and I expect 3.1 will support JDK 7 and keystone v3. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [openstack-cloud-plugin] (JENKINS-35347) unable to test connection when using keystone V3 API

2016-06-08 Thread jjfig...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Juan Jose Figueredo commented on  JENKINS-35347 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: unable to test connection when using keystone V3 API  
 
 
 
 
 
 
 
 
 
 
Hello! I´m experiencing this issue also. In my case I´m using Keystone V3 and domains in the OpenStack instance. It would be grateful a lot the resolution of this issue. 
Thanks you!! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [openstack-cloud-plugin] (JENKINS-35347) unable to test connection when using keystone V3 API

2016-06-03 Thread y...@mvista.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yufen Kuo created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35347 
 
 
 
  unable to test connection when using keystone V3 API  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 openstack-cloud-plugin 
 
 
 

Created:
 

 2016/Jun/03 7:21 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Yufen Kuo 
 
 
 
 
 
 
 
 
 
 
Cannot connect to specified cloud, please check the identity and credentials: Not Found 
ClientResponseException {message=Not Found, status=404, status-code=NOT_FOUND} 
 at org.openstack4j.core.transport.HttpExceptionHandler.mapException(HttpExceptionHandler.java:38) at org.openstack4j.core.transport.HttpExceptionHandler.mapException(HttpExceptionHandler.java:23) at org.openstack4j.openstack.internal.OSAuthenticator.authenticateV2(OSAuthenticator.java:120) at org.openstack4j.openstack.internal.OSAuthenticator.invoke(OSAuthenticator.java:50) at org.openstack4j.openstack.client.OSClientBuilder$ClientV2.authenticate(OSClientBuilder.java:117) at org.openstack4j.openstack.client.OSClientBuilder$ClientV2.authenticate(OSClientBuilder.java:81) at jenkins.plugins.openstack.compute.internal.Openstack.(Openstack.java:95) at jenkins.plugins.openstack.compute.internal.Openstack$Factory.getOpenstack(Openstack.java:466) at jenkins.plugins.openstack.compute.internal.Openstack$FactoryEP.get(Openstack.java:450) at jenkins.plugins.openstack.compute.JCloudsCloud$DescriptorImpl.doTestConnection(JCloudsCloud.java:478)