Bug 1533806
| Summary: | Rebuild cns-deploy to get new rhgs-server-container image built with glusterd memory-leak fixes | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Raghavendra Talur <rtalur> |
| Component: | cns-deploy-tool | Assignee: | Raghavendra Talur <rtalur> |
| Status: | CLOSED ERRATA | QA Contact: | Prasanth <pprakash> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | cns-3.6 | CC: | bmohanra, hchiramm, jarrpa, knarra, kramdoss, rcyriac, rhs-bugs |
| Target Milestone: | --- | ||
| Target Release: | CNS 3.6 Async | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cns-deploy-5.0.0-57.el7rhgs | Doc Type: | Bug Fix |
| Doc Text: |
This version of cns-deploy has updated template files which reference the rhgs-server-container image that includes memory leak fixes for glusterd process.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-01-30 08:36:36 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
Raghavendra Talur
2018-01-12 09:43:27 UTC
cns-deploy-5.0.0-57.el7rhgs.x86_64 pulls the correct rhgs image - brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhgs3/rhgs-server-rhel7:3.3.1-1 with image id: 3e1f512a0a6b sh-4.2# rpm -qa | grep 'gluster' glusterfs-libs-3.8.4-54.el7rhgs.x86_64 glusterfs-3.8.4-54.el7rhgs.x86_64 glusterfs-api-3.8.4-54.el7rhgs.x86_64 glusterfs-cli-3.8.4-54.el7rhgs.x86_64 glusterfs-fuse-3.8.4-54.el7rhgs.x86_64 glusterfs-geo-replication-3.8.4-54.el7rhgs.x86_64 glusterfs-client-xlators-3.8.4-54.el7rhgs.x86_64 glusterfs-server-3.8.4-54.el7rhgs.x86_64 gluster-block-0.2.1-14.el7rhgs.x86_64 Moving the bug to 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/RHBA-2018:0234 |