Bug 1261004
Summary: | [New] - status and status information for geo-replication volume status service is not shown correctly when all the geo-rep sessions are deleted. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | RamaKasturi <knarra> | ||||||
Component: | nagios-server-addons | Assignee: | Sahina Bose <sabose> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Triveni Rao <trao> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | rhgs-3.1 | CC: | asrivast, sabose, sashinde, trao | ||||||
Target Milestone: | --- | Keywords: | Regression, ZStream | ||||||
Target Release: | RHGS 3.1.2 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | gluster-nagios-common-0.2.3-1 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2016-03-01 06:11:17 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: | |||||||||
Bug Blocks: | 1260783 | ||||||||
Attachments: |
|
Description
RamaKasturi
2015-09-08 12:05:08 UTC
Created attachment 1071322 [details]
screenshot for status and status infromation when all the geo-rep sessions are deleted
http://review.gluster.org/#/c/12441/ - posted to handle case when no sessions are present. Created attachment 1096692 [details]
geo-rep status screen shot
This bug is verified with buil no 67: Steps followed: 1. created geo-rep session between master and slave vols. 2. Started the session. 3. checked the status 4. Stopped the geo-rep session. 5. Deleted the geo-rep session. 6. On UI found that status of the session shows as no active sessions found which is expected. Attached the screen shot. 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. https://rhn.redhat.com/errata/RHBA-2016-0310.html |