careful-truck-98666
10/24/2022, 2:55 PME1024 14:49:44.621450 1 volume_controller.go:216] fail to sync longhorn-system/pvc-336ed0a5-1889-4e0a-be69-e9cd6602b4af: fail to reconcile volume state for pvc-336ed0a5-1889-4e0a-be69-e9cd6602b4af: volume pvc-336ed0a5-1889-4e0a-be69-e9cd6602b4af has already attached to node kube-w-04, but asked to attach to node kube-w-03
time="2022-10-24T14:49:44Z" level=warning msg="Dropping Longhorn volume longhorn-system/pvc-336ed0a5-1889-4e0a-be69-e9cd6602b4af out of the queue" controller=longhorn-volume error="fail to sync longhorn-system/pvc-336ed0a5-1889-4e0a-be69-e9cd6602b4af: fail to reconcile volume state for pvc-336ed0a5-1889-4e0a-be69-e9cd6602b4af: volume pvc-336ed0a5-1889-4e0a-be69-e9cd6602b4af has already attached to node kube-w-04, but asked to attach to node kube-w-03" node=kube-w-03
How can I tell it that it's not attached to w-04?famous-journalist-11332
10/25/2022, 10:57 PMkubectl edit <http://volumes.longhorn.io|volumes.longhorn.io> pvc-336ed0a5-1889-4e0a-be69-e9cd6602b4af
and set the spec.NodeID
to ""
3. Wait for volume to be detached in Longhorn UI
4. Scale up the workload