Writing to request that the Storage Installation Guide (and possibly the Admin Guide) be updated to provide more clarity on how an end user is to apply any and all async errata for the Storage product as they are incremental and cumulative. Per VS; "On the server side, they will need to restart glusterd for applied changes to take effect. If there are any changes in NFS, either the NFS process will have to be restarted or the volume will have to be restarted (stop/start)." "On the client side, there is no action required for NFS. If it is a native client, it will require an unmount/mount for the changes to take effect." "I will just need to check if we restart glusterd in the rpm post-install. I will take an AI to coordinate this with Anjana." Per Anjana; "Currently, the RHS Installation Guide has a section - Setting Software Updates -- https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Storage/2.0/html/Installation_Guide/chap-Installation_Guide-Software_Updates.html."
Have verified that we restart glusterd in the rpm postinstall, so no specific instructions required. And with respect to restarting NFS process, this needs to be done only when there are NFS fixes in a particular errata, this is not needed when there are no NFS fixes. So this will be better handled in that specific errata text than a general update to the install/admin guide. Same applies to native client updates. Only when the client RPMs are updated, umount/mount needs to be done. Today we rebuild client RPMs anyway even if there are no updates on client side. This needs fixing so that we will know when changes are happening on client side. I believe there is a BZ for this already.
Updated the Installation Guide is available for review at http://documentation-stage-02.lab.eng.bne.redhat.com/docs/en-US/Red_Hat_Storage/2.0/html/Installation_Guide/chap-Installation_Guide-Software_Updates.html#idp10293904
Had suggested minor changes which is incorporated now. Looks good.