Export to GitHub

typica - issue #93

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


Posted on May 5, 2010 by Helpful Hippo

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 :)

Attachments

Comment #1

Posted on Jul 6, 2010 by Happy Bear

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

Comment #2

Posted on Jul 8, 2010 by Massive Kangaroo

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.

Comment #3

Posted on Jul 9, 2010 by Happy Bear

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.

Comment #4

Posted on Jul 9, 2010 by Massive Kangaroo

I'm getting a 500 error from the ECC. Will try to solve with those folks first.

Comment #5

Posted on Jul 9, 2010 by Massive Kangaroo

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.

Comment #6

Posted on Jul 9, 2010 by Massive Kangaroo

(No comment was entered for this change.)

Status: Fixed