[Bug 462656] [NEW] 408 (timeout) errors could be made more explicit when due to file system being full

[Nick Barcet]

Public bug reported:

Torsten reported:
When trying to access Walrus I lately get a lot of timeouts. This happens when starting an instance (e.g. it's in pending state forever) or when accessing S3 with euca-delete-bundle:

spindler at lysander:~/Work/cloud$ euca-delete-bundle -a $EC2_ACCESS_KEY -s $EC2_SECRET_KEY -U $S3_URL -b image3 -p root.img --clear
-------------------------
         4 0 8           
path=/services/Walrus/image3/?max-keys=0
Failure: 408 Request Timeout

After a bit of searching, he figured that it was due to his file system
being almost full.  I think it would be nice if Walrus was returning a
more explicit error message in this case.

** Affects: eucalyptus (Ubuntu)
     Importance: Wishlist
         Status: New

** Changed in: eucalyptus (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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
Server Team, which is subscribed to eucalyptus in ubuntu.