Bug 1680968

Summary: Collect galera mysql node status file
Product: Red Hat Enterprise Linux 8 Reporter: Jose Castillo <jcastillo>
Component: sosAssignee: Pavel Moravec <pmoravec>
Status: CLOSED ERRATA QA Contact: Miroslav HradĂ­lek <mhradile>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: agk, bmr, gavin, mhradile, plambri, sbradley
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sos-3.7-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:32:24 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: 1680691    
Bug Blocks: 1701002    

Description Jose Castillo 2019-02-25 15:24:53 UTC
This bug was found via the RHEL 8 Beta CEE Readiness initiative, so opening this BZ for tracking.


Description of problem:
Galera MySQL clusters have a file in /var/lib/mysql/grastate.dat
that contains the status of the node. This will be useful when investigating galera cluster issues.

Version-Release number of selected component (if applicable):
sos-3.6-10.el8
mariadb-10.3.11-1.module+el8+2765+cfa4f87b

How reproducible:
Always

Steps to Reproduce:
1. generate a sosreport with 'sosreport -o mysql' with a galera mysql cluster installed and configured.


Actual results:
The node state file is not captured.

Expected results:
The node state file should be captured.

Additional info:
Upstream pull request https://github.com/sosreport/sos/pull/1577

Comment 2 Pavel Moravec 2019-02-25 18:17:48 UTC
devel_ack+ for 8.1

Comment 4 Pavel Moravec 2019-03-21 12:11:59 UTC
POSTed to upstream.

Comment 8 errata-xmlrpc 2019-11-05 22:32:24 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.

https://access.redhat.com/errata/RHEA-2019:3640