Description of problem:
When confirming the version of RHS installed, it is useful to examine the /etc/redhat-storage-release file, but this is not gathered by sosreport
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Look for /etc/redhat-storage-release file in sosreport
File gathered by sos
It's a shame there's no os-release on RHEL6 variants; this would likely be a better source for this information.
I don't have any great in-principal objections to adding this (although it's one more straw..) but I'm curious what it buys us that's not available from e.g. installed-rpms or the gluster logs, config & tool output we collect?
There are different ways to install gluster (or Red Hat Storage), and without doing a package-by-package comparison it can be difficult to discern the install method. Looking at the redhat-storage-release file helps show that the system was installed from an RHS iso/channel.
(In reply to Bryn M. Reeves from comment #2)
> It's a shame there's no os-release on RHEL6 variants; this would likely be a
> better source for this information.
> I don't have any great in-principal objections to adding this (although it's
> one more straw..) but I'm curious what it buys us that's not available from
> e.g. installed-rpms or the gluster logs, config & tool output we collect?
OK thanks for the explanation. The main reason I ask is we're trying to record the reason for collecting new pieces of data in commits so that a few years down the line when we are reviewing what's collected we can understand the rationale behind each item and assess whether it's still relevant.
Author: Bryn M. Reeves <firstname.lastname@example.org>
Date: Thu Jul 31 18:10:09 2014 +0100
[gluster] add redhat-storage-release
Signed-off-by: Bryn M. Reeves <email@example.com>
This is fixed as part of the rebase to 3.2.
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.