search

google-code-export / typica

Automatically exported from code.google.com/p/typica
Apache License 2.0
1 stars 1 forks source link

Detachment of a volume without specifying a device does not work (at least with Eucalyptus) #93

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. call Jec2.detachVolume with device parameter set to null

What is the expected output? What do you see instead?
The volume should be detached from the instance. However, Eucalyptus
returns with an internal server error because it can not process the request.
The problem is: in the GET request, Typica includes the device parameter,
but does not set a value.
Solution: when no device is specified, device parameter should not be
contained in the request.

What version of the product are you using? On what operating system?
Typica r323 with Eucalyptus 1.6.2

Please provide any additional information below.
See attached patch for a fix :)

Original issue reported on code.google.com by frank.bi...@gmail.com on 5 May 2010 at 5:03

Attachments:

GoogleCodeExporter commented 9 years ago 
It could be successful to attach the volume but fail to deatch.

In Jec2,I give the same parameter to attach and deatch function,there's only 
one difference which is the additional field "force" .

But I don't know why I could attach but fail to deatch

Original comment by kevinwan...@gmail.com on 6 Jul 2010 at 7:47

GoogleCodeExporter commented 9 years ago 
The thing with this and another issue was that I intended the user to pass 
null, not an empty string. I have no problem making the test for empty string 
also.

I tested attach/detach on EC2 just now and it worked fine. Will try with Euca 
ECC next.

Original comment by dkavan...@gmail.com on 8 Jul 2010 at 11:00

GoogleCodeExporter commented 9 years ago 
That's right. 
I just use this function in the Euca ECC environment and it fails to detach.

That throws the exception "com.xerox.amazonws.ec2.EC2Exception: Client error : 
Volume is not attached to instance: i-43FE07EA"

But I'm sure that the instance has been attached to the volume.

Thanks for replying.

Original comment by kevinwan...@gmail.com on 9 Jul 2010 at 1:21

GoogleCodeExporter commented 9 years ago 
I'm getting a 500 error from the ECC. Will try to solve with those folks first.

Original comment by dkavan...@gmail.com on 9 Jul 2010 at 6:43

GoogleCodeExporter commented 9 years ago 
I could detach now with just the volume and instance id specified. I'm seeing a 
problem with deleting the volume, but I'll close this issue.

Original comment by dkavan...@gmail.com on 9 Jul 2010 at 7:00

GoogleCodeExporter commented 9 years ago

Original comment by dkavan...@gmail.com on 9 Jul 2010 at 7:01