In the unlikely event of this error occurring, schedule either a node reboot or a node rescue maintenance task.
Once the maintenance task completes and the node is online, try the command again.