Due to the asynchronous and concurrent nature of the system, it is not
possible to readily know what is going on on the server side without
monitoring and checking logs. In this case, "euca-delete-bundle" is not
the command that is causing the disk to be filled. A timeout could be
due to a variety of reasons and not a consequence of the command that
was executed. Error reporting can be improved but not sure this
particular case be readily fixed with a simple client facing error
message. The root cause (full disk) needs to be handled more gracefully.
** Changed in: eucalyptus
Status: New => Won't Fix
--
408 (timeout) errors could be made more explicit when due to file system being
full
https://bugs.launchpad.net/bugs/462656
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
