Bug 983966
Summary: | cli crashes when setting diagnostics.client-log-level is set to trace | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Ravishankar N <ravishankar> |
Component: | glusterfs | Assignee: | Ravishankar N <ravishankar> |
Status: | CLOSED ERRATA | QA Contact: | Gowrishankar Rajaiyan <grajaiya> |
Severity: | low | Docs Contact: | |
Priority: | high | ||
Version: | 2.1 | CC: | amarts, gluster-bugs, grajaiya, rhs-bugs, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.4.0.12rhs.beta5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 982174 | Environment: | |
Last Closed: | 2013-09-23 22:35:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 982174 | ||
Bug Blocks: |
Description
Ravishankar N
2013-07-12 12:10:50 UTC
Downstream review at https://code.engineering.redhat.com/gerrit/#/c/10189/ Moving priority to 'high' as it would crash the process. Patch merged into 'rhs-2.1' branch. [root@dhcp201-183 ~]# for i in debug warning error info critical none trace; do gluster volume set fsync diagnostics.client-log-level $i; done volume set: failed: option log-level debug: 'debug' is not valid (possible options are DEBUG, WARNING, ERROR, INFO, CRITICAL, NONE, TRACE.) volume set: failed: option log-level warning: 'warning' is not valid (possible options are DEBUG, WARNING, ERROR, INFO, CRITICAL, NONE, TRACE.) volume set: failed: option log-level error: 'error' is not valid (possible options are DEBUG, WARNING, ERROR, INFO, CRITICAL, NONE, TRACE.) volume set: failed: option log-level info: 'info' is not valid (possible options are DEBUG, WARNING, ERROR, INFO, CRITICAL, NONE, TRACE.) volume set: failed: option log-level critical: 'critical' is not valid (possible options are DEBUG, WARNING, ERROR, INFO, CRITICAL, NONE, TRACE.) volume set: failed: option log-level none: 'none' is not valid (possible options are DEBUG, WARNING, ERROR, INFO, CRITICAL, NONE, TRACE.) volume set: failed: option log-level trace: 'trace' is not valid (possible options are DEBUG, WARNING, ERROR, INFO, CRITICAL, NONE, TRACE.) [root@dhcp201-183 ~]# No crash detected. Verified. Build: glusterfs-server-3.4.0.13rhs-1.el6rhs.x86_64 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html |