Hi Udara, I tried that option as well.
Issue here is not at volume creation level, but the attachment level. Therefore even we didn't give the ID, it gets the ID of created volume correctly and input to volumeAttach call. My guess is that doesn't pick the correct ID. Thanks. On Fri, Mar 20, 2015 at 10:28 PM, Udara Liyanage <ud...@wso2.com> wrote: > Hi Lahiru, > > There is an option to attach an already created volume. You can provide a > known volume I'd and check weather it get attached. > On 20 Mar 2015 21:49, "Lahiru Sandaruwan" <lahi...@wso2.com> wrote: > >> Hi, >> >> I have completed subscribable info support, and now it passes the >> persistence information to instance creation step correctly. >> >> But it failed to attach the volume to the instance after creating a >> volume successfully. Our code pass the instanceId and volumeId correctly >> for the volume attaching call, as per my debug session. >> >> It seems the value that is passed as volumeId doesn't get the correct >> value and send the same value always. >> >> Their rest API is, >> >> http://<host>:<port>/v2/*<volumeId>* >> /servers/<instanceId>/os-volume_attachments >> >> Error was, >> >> Caused by: org.jclouds.http.HttpResponseException: command: POST >> http://192.168.16.99:8774/v2/*cc9383d8a04f40988f2fcf8aab397551*/servers/RegionOne/33b5057b-7095-4cfc-9e2a-d811cf25051e/os-volume_attachments >> HTTP/1.1 failed with response: HTTP/1.1 404 Not Found >> >> Looking into it. Full error at [1]. >> >> Thanks. >> [1] >> >> TID: [0] [STRATOS] [2015-03-20 16:05:52,325] ERROR >> {org.apache.stratos.cloud.controller.services.impl.InstanceCreator} - >> Could not attache volume, [instance] >> RegionOne/33b5057b-7095-4cfc-9e2a-d811cf25051e [volume] Persistence >> Required: , Size: 1, device: /dev/vdb mapping path : null remove on >> termination true SnaphotId null >> org.jclouds.rest.ResourceNotFoundException: 404 Not Found >> >> The resource could not be found. >> >> >> at >> org.jclouds.openstack.nova.v2_0.handlers.NovaErrorHandler.handleError(NovaErrorHandler.java:97) >> at >> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:65) >> at >> org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:128) >> at >> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:98) >> at >> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:90) >> at >> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:73) >> at >> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:44) >> at >> org.jclouds.reflect.FunctionalReflection$FunctionalInvocationHandler.handleInvocation(FunctionalReflection.java:117) >> at >> com.google.common.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:87) >> at com.sun.proxy.$Proxy146.attachVolumeToServerAsDevice(Unknown Source) >> at >> org.apache.stratos.cloud.controller.iaases.openstack.OpenstackIaas.attachVolume(OpenstackIaas.java:476) >> at >> org.apache.stratos.cloud.controller.services.impl.InstanceCreator.attachVolumes(InstanceCreator.java:132) >> at >> org.apache.stratos.cloud.controller.services.impl.InstanceCreator.run(InstanceCreator.java:73) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> at java.lang.Thread.run(Thread.java:745) >> Caused by: org.jclouds.http.HttpResponseException: command: POST >> http://192.168.16.99:8774/v2/cc9383d8a04f40988f2fcf8aab397551/servers/RegionOne/33b5057b-7095-4cfc-9e2a-d811cf25051e/os-volume_attachments >> HTTP/1.1 failed with response: HTTP/1.1 404 Not Found; content: [404 Not >> Found >> >> The resource could not be found. >> >> ] >> at >> org.jclouds.openstack.nova.v2_0.handlers.NovaErrorHandler.handleError(NovaErrorHandler.java:78) >> ... 15 more >> >> On Wed, Mar 18, 2015 at 8:55 AM, Udara Liyanage <ud...@wso2.com> wrote: >> >>> Hi Lashiru, >>> >>> CC backend supports persistence volume. We need to add this to >>> application subscribable info. >>> >>> On Wed, Mar 18, 2015 at 7:57 AM, Lahiru Sandaruwan <lahi...@wso2.com> >>> wrote: >>> >>>> Hi devs, >>>> >>>> I'm working on $subject. We have had this feature in 4.0.0 version in >>>> cartridge definition and later moved to subscription section. But we have >>>> missed this feature when we moving subscription parameters to Application >>>> in new model. >>>> >>>> I will update this thread as i progress. >>>> >>>> Thanks. >>>> >>>> >>>> -- >>>> -- >>>> Lahiru Sandaruwan >>>> Committer and PMC member, Apache Stratos, >>>> Senior Software Engineer, >>>> WSO2 Inc., http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> phone: +94773325954 >>>> email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ >>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>>> >>>> >>> >>> >>> -- >>> >>> Udara Liyanage >>> Software Engineer >>> WSO2, Inc.: http://wso2.com >>> lean. enterprise. middleware >>> >>> web: http://udaraliyanage.wordpress.com >>> phone: +94 71 443 6897 >>> >> >> >> >> -- >> -- >> Lahiru Sandaruwan >> Committer and PMC member, Apache Stratos, >> Senior Software Engineer, >> WSO2 Inc., http://wso2.com >> lean.enterprise.middleware >> >> phone: +94773325954 >> email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ >> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> >> -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +94773325954 email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
