PhanLe1010

> Probably longhorn should refresh list of those endpoints and remove those invalid. Could you point me to how to refesh the list of iscsi sessions/tagets ?

Hi @dominch Could you please send us [a support bundle](https://longhorn.io/docs/1.5.3/advanced-resources/support-bundle/) to `[email protected]`? I would like to double check if this is something we can enhance from Longhorn side. What is...

> I found out that they come from instance manager and probably there is yet another config that is managed and synced with node iscsid, Sorry, could you give more...

From the code flow, I see this issue might potentially happen in theory when engine fail to logout and clean up the session (i.e.,when this function failed https://github.com/longhorn/longhorn-engine/blob/5ac6eec696db9b18ec90cac3d0aec090798ea23a/vendor/github.com/longhorn/go-iscsi-helper/iscsidev/iscsi.go#L258-L328) during engine...

Update: I am able to see a similar (but not quite the same error logs) by: 1. Create a volume and attach it to node-1 1. exec into the instance-manager...

TODO: Longhorn team needs to document a workaround to get rid of the annoying logs

@serhiynovos @Freundschaft @dominch Can you try this workaround: 1. Identify the IP from the log. For example, `10.42.82.31` from this log. Confirm that this IP is not the IP of...

I think the goal of this ticket should be to document a KB article workaround to get rid of the annoying logs. To automatically cleanup, I think we would have...

Any update @dominch and @serhiynovos ?

## Test plan: No specific test plan is needed for this ticket. Just make sure @dominch and @serhiynovos are happy with the workaround