Bug 1640135
| Summary: | Wrong version number in /etc/redhat-storage-release | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Filip Balák <fbalak> |
| Component: | redhat-storage-server | Assignee: | Milind Changire <mchangir> |
| Status: | CLOSED ERRATA | QA Contact: | Rahul Hinduja <rhinduja> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.4 | CC: | amukherj, apaladug, dahorak, mbukatov, mchangir, rcyriac, rhs-bugs, sanandpa, sankarshan, sheggodu, storage-qa-internal, ubansal, vbellur, vmalkoti |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.4.z Batch Update 1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | redhat-storage-server-3.4.1.0-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-31 08:46:58 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: | |||
|
Description
Filip Balák
2018-10-17 12:13:09 UTC
Note that, glusterfs RPMs doesn't change /etc/redhat-storage-release file. Should be part of build/distribution! Are there other ways to identify the version / release ? I guess it is important to understand whether it is 3.4.1 or 3.4.2 etc . right ? As per the bug updates and patch see that the changes has been implemented On previous build - glusterfs-server-3.12.2-23.el6rhs.x86_64 ============================================================ [root@dhcp37-150 ~]# cat /etc/redhat-storage-release Red Hat Gluster Storage Server 3.4.0 Build - glusterfs-server-3.12.2-25.el6rhs.x86_64 ================================================= [root@dhcp37-150 yum.repos.d]# cat /etc/redhat-storage-release Red Hat Gluster Storage Server 3.4 Hence closing the 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. https://access.redhat.com/errata/RHSA-2018:3432 |