Loading...
Loading...
When the LNNs are changed on the cluster, the auditing service doesn't use the new assignments. New audit event logs will not be created in /ifs/.ifsvar/audit/logs/ for the new Node LNN assignments. The auditing will continue to use old Node LNN directories, for writing events to audit event logs in the /ifs/.ifsvar/audit/logs/ directory. If a new node is added to the cluster, and it inherits a LNN that was previously assigned to another node, it will append new events to existing audit event logs in /ifs/.ifsvar/audit/logs/ directory for the LNN it was assigned. If the auditing doesn't get refreshed to use the new LNN assignments, and a new node is added and uses the LNN that still being used by the old node, both nodes will append new audit event entries to the log in /ifs/.ifsvar/audit/logs/.
This is currently tied to the sensitive nature of the audit service. If the audit service is improperly interrupted, it can cause workflow disruptions to the node(s) in question, resulting in users losing access to SMB and/or NFS access on the node(s).
Please reach out to PowerScale support for assistance with resolution quoting this KB.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.