FlexClone creation failure due to node offline in VLDB
Applies to
- ONTAP v9.12.1P11
- AFF-A900
- Cluster Mode
Issue
- FlexClone creation via API fails with the following error:
ErrorDetail(string='Server Error: STATUS=failed, REASON=Volume created successfully but not mounted. Reason: Failed to create junction record for volume <volume-name> on Vserver <vserver-name>. Reason: Node \"<node-name>\" on ring \"VLDB\" is offline. Check the health of the cluster using the \"cluster show\" command. For further assistance, contact technical support.
ServerError: STATUS=failed, REASON=Volume created successfully but not mounted. Reason: Failed to create junction record for volume on Vserver . Reason: Node "<node-name>" on ring "VLDB" is offline. Check the health of the cluster using the "cluster show" command. For further assistance, contact technical support.
- When reviewing the Autosupport (ASUP) logs, the following error is logged:
Tue Jul 22 04:26:30-0700 [<node-name>:wafl_junkd_vldbcache:wafl.mp.vldb.update.failed:error]: Updating the VLDB "granular-data" property of volume "" failed. Reason: Node "<node-name>" on ring "VLDB" is offline.
Tue Jul 22 2025 04:26:30 -07:00 [kern_mgwd:info:3599] W [src/rdb/TM.cc 5249 (0x82af0dc00)]: handleCoordBeginTranStatus: beginTran status UNIT_OFFLINE, txn request epoch 39
Tue Jul 22 2025 04:26:30 -07:00 [kern_mgwd:info:3599] 0x82af0dc00: 8604000004a0bd82: ERR: rdb_tran_glue: create: tid=0x82af0dc00 failed to create transaction for label='QoS autovolume create transaction': UNIT_OFFLINE
Tue Jul 22 2025 04:26:30 -07:00 [kern_mgwd:info:3599] 0x82af0dc00: 8604000004a0bd82: ERR: VOPL::volCloneCreate: Node "<node-name>" on ring "Management" is offline. Check the health of the cluster using the "cluster show" command. For further assistance, contact technical support.
- The Management Gateway Daemon (MGWD) goes offline and back online in about (<20) seconds
Note: What services does MGWD handle?
Mgwd is a process running on every node in the cluster which:
- Provides Clustershell command line access
- Handles external ZAPI and REST API calls to the node
- Manages authenticated access to Systemshell
- A core file is not automatically generated and confirmed by running this command from the cluster shell:
system node coredump show