diff options
| author | Dan Williams <dcbw@redhat.com> | 2017-03-03 11:09:56 -0600 |
|---|---|---|
| committer | Dan Williams <dcbw@redhat.com> | 2017-03-03 14:49:32 -0600 |
| commit | 77d984eb94477f5e170c30318e0d3064d1c953e4 (patch) | |
| tree | 5402e3de722817c19992d53d9c694ad5b649f315 /roles/etcd/templates/etcd.docker.service | |
| parent | e2bc346fc99de637d03762b4b813b596afffc7dc (diff) | |
| download | openshift-77d984eb94477f5e170c30318e0d3064d1c953e4.tar.gz openshift-77d984eb94477f5e170c30318e0d3064d1c953e4.tar.bz2 openshift-77d984eb94477f5e170c30318e0d3064d1c953e4.tar.xz openshift-77d984eb94477f5e170c30318e0d3064d1c953e4.zip | |
node/sdn: make /var/lib/cni persistent to ensure IPAM allocations stick around across node restart
With the move to a CNI plugin, docker no longer handles IPAM, but CNI does through
openshift-sdn's usage of the 'host-local' CNI IPAM plugin. That plugin stores
IPAM allocations under /var/lib/cni/.
If the node container gets restarted, without presreving /var/lib/cni, the IPs
currently allocated to running pods get lost and on restart, openshift-sdn
may allocate those IPs to new pods causing duplicate allocations.
This never happened with docker because it has its own persistent IPAM store that
does not get removed when docker restarts. Also because (historically) when docker
restarted, all the containers died and the IP allocations were released by the
daemon.
Fix this by ensuring that IPAM allocations (which are tied to the life of the pod,
*not* the life of the openshift-node process) persist even if the openshift-node
process restarts.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1427789
Diffstat (limited to 'roles/etcd/templates/etcd.docker.service')
0 files changed, 0 insertions, 0 deletions