MountNetworkShares -umount does not unmount filesystems

Products

• CA Identity Suite

Issue/Introduction

The vAPP alias unmount option, MountNetworkShares -umount, does not unmount shares and may require a restart for the shares to be unmounted.

"MountNetworkShares -umount" could complete without producing any errors or warning messages. But the volumes might not be unmounted and could cause a .gpz patch to hang, for example. 

"MountNetworkShares -umount" does not produce any errors or timeouts if the umount is unsuccessful. 

Environment

vAPP 14.5.1 CHF01

Cause

"MountNetworkShares -umount" works in normal working scenarios. The Linux default umount command has both lazy and forced unmount options for scenarios where a file from the mounted volume is in use, but the 'MountNetworkShares -umount ' might not work if the associated share files are in use.

Resolution

Apply HF_VA-14.5.1-20260218120846-DE662140.tgz.gpg 

This patch will allow passing options for umount from the same file used to mount the file system, /opt/CA/VirtualAppliance/custom/mounts.

The fifth column will be used as the umount option, for example:

<IP_Address>:/mnt/nfsshare /mnt/nfs_clientshare nfs noexec -f                 / -f at the end is the option for umount.

                                                                                                                     /If you want to use lazy umount, use the -l option.

Additional Information