Bug 1501347
| Summary: | [RHEL6] Build RHGS 3.3.1 gdeploy rpms for RHEL6 | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sunil Kumar Acharya <sheggodu> |
| Component: | gdeploy | Assignee: | Sachidananda Urs <surs> |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.3 | CC: | amukherj, pmulay, rcyriac, rhinduja, rhs-bugs, smohan, storage-qa-internal, surs |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gdeploy-2.0.2-16 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the permission bits on the glusterfs.ca certificate file was restricted only to the owner to read the certificate. As a result, virtual machines did not start using libgfapi as the self signed certificates were generated using gdeploy. With this fix, the permissions of glusterfs.ca file must be changed to 644 before setting up SSL using the following command: chmod 644 /etc/ssl/glusterfs.ca. With the change in permissions, the virtual machines start as expected.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-11-29 03:25:10 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: | 1475686 | ||
|
Description
Sunil Kumar Acharya
2017-10-12 12:14:25 UTC
Reusing Doc Text from https://bugzilla.redhat.com/show_bug.cgi?id=1482987 basis my discussion with sac. Hi Sachidananda, Request you to review the same and let me know in case of any concerns. If no changes are required, request you to provide your approval for the same. 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-2017:3273 |