Document URL: In this release (3.4) there is one minor change specific to set transport.socket.ssl-cert-depth parameter In the earlier releases to configure ssl-cert-depth user set this parameter in /etc/glusterfs/gluster.vol as below before start glusterd "option transport.socket.ssl-cert-depth <depth>" but now from this release, the same parameter user has to update in /var/lib/glusterd/sercure-access as like below "option transport.socket.ssl-cert-depth <depth>" Section Number and Name: Describe the issue: Suggestions for improvement: Additional information:
Ack for Doc Async Update 2.
Added a note regarding how to change the way to set transport.socket.ssl-cert-depth parameter Link to verify the updated doc - https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/html-single/administration_guide/#section-Enable-Management-Encryption
(In reply to Chandrakanth Pai from comment #7) > Added a note regarding how to change the way to set > transport.socket.ssl-cert-depth parameter > > Link to verify the updated doc - > https://doc-stage.usersys.redhat.com/documentation/en-us/ > red_hat_gluster_storage/3.4/html-single/administration_guide/#section-Enable- > Management-Encryption The note mentioned in the provided link captures the details to set the transport.socket.ssl-cert-depth parameter sufficiently with an example. Moving the bug to VERIFIED.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days