Bug 980725
| Summary: | Dist-geo-rep : 'gluster volume geo status' is not showing status of sessions which are in 'Not started' or 'Stopped' state | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rachana Patel <racpatel> |
| Component: | geo-replication | Assignee: | Avra Sengupta <asengupt> |
| Status: | CLOSED ERRATA | QA Contact: | amainkar |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.1 | CC: | aavati, amarts, asengupt, csaba, rhs-bugs, vbhat, vkoppad |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.4.0.12rhs.beta4_1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-23 22:38:42 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: | |||
Now geo-replication status shows all the session's status. But it's not ordered properly. Technically speaking the status shown is correct. But it's not ordered properly. For a user it would be good to see 'session' wise. Like in the status lines of one session should be together. Similar to volume status. Is that achievable? Or this is just fine? Or should I close this bug and open other for ordering them properly? [root@pythagoras ]# gluster v geo master status NODE MASTER SLAVE HEALTH UPTIME -------------------------------------------------------------------------------------------- pythagoras.blr.redhat.com master ssh://neumann::slave3 Initializing... N/A pythagoras.blr.redhat.com master ssh://riemann::slave2 Not Started N/A pythagoras.blr.redhat.com master ssh://euclid::slave1 Stopped N/A ramanujan.blr.redhat.com master ssh://neumann::slave3 Initializing... N/A ramanujan.blr.redhat.com master ssh://riemann::slave2 Not Started N/A ramanujan.blr.redhat.com master ssh://euclid::slave1 Stopped N/A [root@pythagoras ]# gluster v geo master status NODE MASTER SLAVE HEALTH UPTIME ------------------------------------------------------------------------------------------ pythagoras.blr.redhat.com master ssh://neumann::slave3 Stable 00:01:40 pythagoras.blr.redhat.com master ssh://riemann::slave2 Not Started N/A pythagoras.blr.redhat.com master ssh://euclid::slave1 Stopped N/A ramanujan.blr.redhat.com master ssh://neumann::slave3 Stable 00:01:41 ramanujan.blr.redhat.com master ssh://riemann::slave2 Not Started N/A ramanujan.blr.redhat.com master ssh://euclid::slave1 Stopped N/A Amar, Avra, The status shown is technically correct. But the ordering is not user friendly. Ideally I would expect it to be ordered session wise, just like volume status (where it is volume wise) Should I move this bug to verify and open another bug for proper ordering? Or that should be fixed as part of this bug itself? MSV, If you think *technical* issues reported initial bug report is fixed, please mark the bug VERIFIED. You should be opening a new bug IMO. Just found, there is already another bug opened for that. https://bugzilla.redhat.com/show_bug.cgi?id=988722 So closing this bug as VERIFIED. 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 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 |
Description of problem: Distributed-geo-rep : 'gluster volume geo session' is not showing status of sessions which are in 'Not started' or 'Stopped' state Version-Release number of selected component (if applicable): 3.4.0.12rhs.beta1-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1. Create multiple geo rep sessions between master and slave cluster 2. Keep changing status of session ('not started', 'stopped' etc) and check status using 'gluster volume geo status' and 'gluster volume geo <master_vol> <slave_ip>::<slave_vol> status. [root@hulk ~]# gluster volume geo master2 10.70.43.147::slave2 status NODE MASTER SLAVE HEALTH UPTIME ------------------------------------------------------------------------------------------- wall.blr.redhat.com master2 10.70.43.147::slave2 Not Started N/A ironman.blr.redhat.com master2 10.70.43.147::slave2 Not Started N/A lannister.blr.redhat.com master2 10.70.43.147::slave2 Not Started N/A [root@hulk ~]# gluster volume geo status NODE MASTER SLAVE HEALTH UPTIME -------------------------------------------------------------------------------------------- ironman.blr.redhat.com master1 ssh://10.70.43.147::slave1 Stable 00:07:51 wall.blr.redhat.com master1 ssh://10.70.43.147::slave1 Stable 00:07:52 lannister.blr.redhat.com master1 ssh://10.70.43.147::slave1 Stable 00:07:52 [root@hulk ~]# gluster volume geo master2 10.70.43.147::slave2 stop Stopping geo-replication session between master2 & 10.70.43.147::slave2 has been successful [root@hulk ~]# gluster volume geo master2 10.70.43.147::slave2 status NODE MASTER SLAVE HEALTH UPTIME --------------------------------------------------------------------------------------- ironman.blr.redhat.com master2 10.70.43.147::slave2 Stopped N/A wall.blr.redhat.com master2 10.70.43.147::slave2 Stopped N/A lannister.blr.redhat.com master2 10.70.43.147::slave2 Stopped N/A [root@hulk ~]# gluster volume geo status NODE MASTER SLAVE HEALTH UPTIME -------------------------------------------------------------------------------------------- lannister.blr.redhat.com master1 ssh://10.70.43.147::slave1 Stable 00:08:35 ironman.blr.redhat.com master1 ssh://10.70.43.147::slave1 Stable 00:08:34 wall.blr.redhat.com master1 ssh://10.70.43.147::slave1 Stable 00:08:34 Actual results: 'gluster volume geo session' is not showing status of sessions which are in 'Not started' or 'Stopped' state Expected results: It should show all session information Additional info: