Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 868711

Summary:	Include "gluster volume geo-replication status" in the gluster sos plugin
Product:	Red Hat Enterprise Linux 6	Reporter:	Brad Hubbard <bhubbard>
Component:	sos	Assignee:	Bryn M. Reeves <bmr>
Status:	CLOSED ERRATA	QA Contact:	Filip Holec <fholec>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.3	CC:	agk, bmr, fholec, gavin, mhradile, psplicha, sos-team
Target Milestone:	rc
Target Release:	6.5
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	sos-2.2-43.el6	Doc Type:	Enhancement
Doc Text:	Feature: The gluster plug-in now collects the output of the "gluster volume geo-replication-status" command by default. Reason: This diagnostic output may be important for debugging problems related to Gluster geographic replication. Result (if any):	Story Points:	---
Clone Of:
Clones:	1036752 (view as bug list)		Environment:
Last Closed:	2013-11-21 22:35:26 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:	1036752

Description Brad Hubbard 2012-10-21 22:16:52 UTC

Description of problem:

The sos gluster plugin should capture the output of the "gluster volume geo-replication status" command.

Comment 1 Bryn M. Reeves 2012-10-22 09:46:20 UTC

Can you file or clone this against the RHS component? Gluster folks want to retain control of the gluster module so this needs to be reviewed by them first (we just removed all the volume status stuff at their request).

Comment 2 Brad Hubbard 2012-10-22 20:52:29 UTC

Hey Bryn,

Already done, 868712.

Comment 3 Bryn M. Reeves 2013-06-03 12:54:24 UTC

Setting devel_ack based on RHS acceptance of this change in bug 868712.

Comment 4 Bryn M. Reeves 2013-08-12 19:03:35 UTC

Patches do not apply cleanly to the rhel-6 branch; looks like other changes have been made in the downstream (RHS) package.

I need to look into this before I can include this in 6.5.

If there are further differences then it may be preferable for us to just re-sync the gluster.py with the version in RHS - I don't want these two to diverge over time.

Comment 10 errata-xmlrpc 2013-11-21 22:35:26 UTC

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-1688.html