When you fail to delete the cluster pool using iManager, the following error message is displayed: “Error: <poolName>: Could not delete NDS objects for this pool”. As a workaround, use nssmu or nlvm commands to delete the cluster pools.
Micro Focus plans to fix this issue in the subsequent OES 2015 SP1 release.
In a mixed node cluster environment, before upgrading the NSS media to support Active Directory users or creating 64-bit pools, it is strongly recommended that you upgrade all the nodes to OES 2015 or later. This is because the upgraded NSS resources might not be accessible from cluster nodes that are not upgraded to OES 2015 or later.
Micro Focus has no current plans to change this.
In a mixed node cluster environment, before upgrading the NSS media to support Trustee Index, it is strongly recommended that you upgrade all the nodes to OES 2015 SP1 or later. This is because the upgraded NSS resources might not be accessible from cluster nodes that are not upgraded to OES 2015 SP1 or later.
Micro Focus has no current plans to change this.
When a third-party application uses FUSE infrastructure to overlay its software over the NSS file system, the rights command might fail.
Micro Focus plans to fix this issue in a future OES release.
Some issues can occur when you lose a device in an NSS software RAID 5 device, or when you expand an NSS software RAID 5 device. The following issues happen intermittently:
When a segment is missing in an NSS RAID 5 because of a device failure, the pool might hang until the device driver reports the error, and then the RAID continues. The hang time depends on the underlying device driver timeout conditions. For iSCSI devices, this includes iSCSI driver timeout. For extended hangs, the pool might also get deactivated.
Micro Focus plans to fix this issue in a future OES release.