Bug 1501347 - [RHEL6] Build RHGS 3.3.1 gdeploy rpms for RHEL6
Summary: [RHEL6] Build RHGS 3.3.1 gdeploy rpms for RHEL6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gdeploy
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.3.1
Assignee: Sachidananda Urs
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks: 1475686
TreeView+ depends on / blocked
 
Reported: 2017-10-12 12:14 UTC by Sunil Kumar Acharya
Modified: 2017-11-29 03:25 UTC (History)
8 users (show)

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.
Clone Of:
Environment:
Last Closed: 2017-11-29 03:25:10 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3273 0 normal SHIPPED_LIVE [RHEL6] gdeploy bug fixes 2017-11-29 08:24:57 UTC

Description Sunil Kumar Acharya 2017-10-12 12:14:25 UTC 
Description of problem:

Build RHGS 3.3.1 gdeploy rpms for RHEL6
Comment 6 Pratik Mulay 2017-11-17 11:33:12 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.
Comment 10 errata-xmlrpc 2017-11-29 03:25:10 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/RHBA-2017:3273
Note You need to log in before you can comment on or make changes to this bug.