CONTAP-812069: SnapLock Compliance Clock reinitialization fails on MetroCluster
Issue
- On MetroCluster, snaplock compliance-clock initialize / compliance-clock initialize -node * fails even when data volumes are online
- The error reports that Compliance Clock re-initialization requires all volumes to be online (and the usual SnapLock / snapshot-locking / S3 object-locking checks)
- After an extended outage, the System Compliance Clock can remain behind wall-clock time and does not catch up automatically
- Absolute -snaplock-expiry-time retention then lasts longer than wall-clock time by about the Compliance Clock skew
