[MESOS-9492] Persist CNI working directory across reboot.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.3, 1.5.3, 1.6.2, 1.7.1, 1.8.0
• Component/s: cni
• Assignee: Deepak Goel
• Reporter: Deepak Goel
• Shepherd: Jie Yu
• Created: 18/Dec/18 23:10
• Updated: 16/Jan/19 00:45
• Resolved: 19/Dec/18 19:20

Description

Currently, CNI working directory doesn't persist across reboot due to which CNI isolator loses the network related information and skips doing a proper cleanup. However, this breaks certain CNI network providers that depend on CNI_DEL call to do the necessary cleanup. The fix would be to move the CNI working directory to a location that persists across reboot such as /var/lib/mesos. 

This would be a breaking change from a backward compatibility standpoint and so should be protected by a flag

Issue Links

• is related to: MESOS-9518 CNI_NETNS should not be set for orphan containers that do not have network namespace.