Description of problem: A few messages logged as errors should probably logged as warnings, as the code appears to recover and still do the right thing. Version-Release number of selected component (if applicable): RHS 2.0 How reproducible: Every time. Steps to Reproduce: 1. Delete metadata from the root Gluster account directory, AUTH_* 2. Make any Swift request to fetch a file, get a container listing, etc. 3. View logs to see that metadata errors are logged, but nothing broke Actual results: Errors logged. Expected results: Warnings logged. Additional info:
Created attachment 627532 [details] Sample patch of the changes. Seems like errors should be logged when the operation of the servers fails, rather than when they recover.
CHANGE: http://review.gluster.org/4089 (object-storage: change logging of some errors to warnings) merged in master by Anand Avati (avati)
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.5.0, please reopen this bug report. glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user