Bug 1098046
| Summary: | [Nagios] Status information for volume quota status service needs improvement when hard limit is reached | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shruti Sampat <ssampat> | ||||
| Component: | gluster-nagios-addons | Assignee: | Sahina Bose <sabose> | ||||
| Status: | CLOSED CANTFIX | QA Contact: | RHS-C QE <rhsc-qe-bugs> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | rhgs-3.0 | CC: | sankarshan | ||||
| Target Milestone: | --- | Keywords: | ZStream | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-01-30 11:48:11 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: | |||||||
| Attachments: |
|
||||||
|
Description
Shruti Sampat
2014-05-15 07:23:06 UTC
Hi, I have something to add, the following is the status information when soft limit is exceeded on some directories and hard limit on others - “QUOTA:hard limit exceeded on /test1: soft limit exceeded on /” The soft limit list and the hard limit list need to be separated by a comma and not by a colon. The hard limit list and soft limit list are separated by a semi-colon. The dangling semi-colon at the end has been removed. Posted - http://review.gluster.org/7798 Created attachment 900346 [details]
screenshot
Still seeing this issue. See attached screenshot. Moving to ASSIGNED. Removing it from Denali, as we agreed over e-mail -- this is not a blocker for RHSC Denali release. Removing FutureFeature keyword as this is not an RFE Thank you for your bug report. However, this bug is being closed as it's on a component where no further new development is being undertaken. |