Endpoint becomes unresponsive after several hours

[hickeng]

The following is seen in journalctl output:

Mar 20 08:32:11 Linux systemd[1]: vic-init.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 20 08:32:11 Linux systemd[1]: vic-init.service: Unit entered failed state.
Mar 20 08:32:11 Linux systemd[1]: vic-init.service: Failed with result 'exit-code'.

Current speculation is that this is related to DHCP lease failure on the management network, but no clarity on why this would result in vic-init exit.

Speculative fix is to use --asymmetric-routes but that's pure speculation due to martian packets being logged.

Bug2084707 tracks this and contains the original details and logs.

[hickeng]

@dbarkelew Opened this issue for tracking. If you manage a recreate please let me know.

[hickeng]

Added to the release as we've had several customers run into this. We need a least a root cause and documentation covering it for 1.4 if not a code fix.