MCC SnapLock Compliance Clock re-initialization fails
Applies to
- ONTAP 9.16.1x
- SnapLock
- Metro Cluster (MCC)
Issue
SnapLock Compliance Clock re-initialization fails on Metro Cluster (MCC) with the following error:
Cluster::> compliance-clock initialize -node *
Warning: You are about to initialize the secure ComplianceClock of the node "cluster-01" to the current value of the node's system clock. ComplianceClock re-initialization requires all nodes in the cluster to be healthy, all volumes are in online state, no volumes are present in the volume recovery queue and there are no SnapLock volumes or volumes with "snapshot-locking-enabled" set to true or S3 buckets with object locking enabled. Ensure that the system time is set correctly before proceeding. The current node's system clock is: Mon Jan 1 12:22:17 CET 2026
Error: command failed on node "cluster-01": ComplianceClock re-initialization failed. ComplianceClock re-initialization requires all nodes in the cluster to be healthy, all volumes are in online state, no volumes are present in the volume recovery queue and there are no SnapLock volumes or volumes with "snapshot-locking-enabled" set to true or S3 buckets with object locking enabled 