When maximum volume size is exceeded, the system should report a more helpful error

[Neil Soman]

Current error message:

<Exception>org.apache.axis2.AxisFault: SERVICE: Volume PROBLEM: Error calling CreateStorageVolume:vol-325A049B MSG-TYPE: CreateVolumeType
 at edu.ucsb.eucalyptus.transport.Axis2InOutMessageReceiver.checkException(Axis2InOutMessageReceiver.java:200)
 at edu.ucsb.eucalyptus.transport.Axis2InOutMessageReceiver.invokeBusinessLogic(Axis2InOutMessageReceiver.java:115)
 at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
 at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
 at edu.ucsb.eucalyptus.transport.http.Axis2HttpWorker.processURLRequest(Axis2HttpWorker.java:224)
 at edu.ucsb.eucalyptus.transport.http.Axis2HttpWorker.handleGet(Axis2HttpWorker.java:199)
 at edu.ucsb.eucalyptus.transport.http.Axis2HttpWorker.service(Axis2HttpWorker.java:113)
 at org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281)
 at org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187)
 at org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82)
 at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
 at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
 at java.lang.Thread.run(Thread.java:619)

[Dustin Kirkland  (kirkland)]

Neil-

What's the status of this issue upstream? I see it marked against 1.5... Is this solved for 1.6?

:-Dustin

[Neil Soman (neilsoman)]

The current status for this is that the Storage Controller reports this as an EntityTooLargeException (which is better than the cryptic error that it used to), but the front end reports this as,

com.eucalyptus.util.EucalyptusCloudException: Error communicating with Storage Controller: CreateStorageVolume:Internal Error

which is the general purpose exception thrown on any exceptions it gets from the Storage Controller.

This needs to be reported sanely. Unfortunately, the Amazon API only allows a return value of true or false to the user since the operation is asynchronous. The user only gets to know whether the request suceeded or failed, so the cloud admin has to actually dig through the logs to figure out why.

In any case, it should not be dumped to the logs as an "Internal Error"

I'm leaving this one open.

[Dustin Kirkland  (kirkland)]

Bug still present in Lucid. Should be fixed in 1.7, though, according to Dan.

[Dave Walker (davewalker)]

Would upstream Eucalyptus be able to update if/when this was resolved? Has it been resolved for 1.6.2 and 2.0, as the last comment suggests?

[Andy Grimm (agrimm)]

This issue is now being tracked upstream at http://eucalyptus.atlassian.net/browse/EUCA-2640

Please watch that issue for further updates.