Bug 806795
Summary: | NFS: Log - change from warning to error | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Sachidananda Urs <sac> |
Component: | nfs | Assignee: | Vinayaga Raman <vraman> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | pre-release | CC: | gluster-bugs, rwheeler, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-04-27 12:31:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sachidananda Urs
2012-03-26 09:21:10 UTC
This should be handled more appropriately by a translator at a higher level. For instance with replicate, the right behavior is to log these messages at log level WARNING in the client protocol. Only replicate will be in a position to determine whether the operation is a failure or not. Since replicate provides resiliency against these kind of errors, it is better not to confuse the user with ERRORS. |