diff options
| author | Suren A. Chilingaryan <csa@suren.me> | 2020-01-22 03:16:06 +0100 |
|---|---|---|
| committer | Suren A. Chilingaryan <csa@suren.me> | 2020-01-22 03:16:06 +0100 |
| commit | 1e8153c2af051ce48d5aa08d3dbdc0d0970ea532 (patch) | |
| tree | 7bb1441a87521aa8c3c5524f95fa645850a6826e /docs/logs.txt | |
| parent | e0b1b53f21095707af87a095934e971d788a90c7 (diff) | |
| download | ands-1e8153c2af051ce48d5aa08d3dbdc0d0970ea532.tar.gz ands-1e8153c2af051ce48d5aa08d3dbdc0d0970ea532.tar.bz2 ands-1e8153c2af051ce48d5aa08d3dbdc0d0970ea532.tar.xz ands-1e8153c2af051ce48d5aa08d3dbdc0d0970ea532.zip | |
Document another problem with lost IPs and exhausting of SDN IP range
Diffstat (limited to 'docs/logs.txt')
| -rw-r--r-- | docs/logs.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/logs.txt b/docs/logs.txt index d33ef0a..0a3b269 100644 --- a/docs/logs.txt +++ b/docs/logs.txt @@ -11,6 +11,11 @@ Despite the errror, the containers are actually killed and pods destroyed. However, this error likely triggers problem with rogue interfaces staying on the OpenVSwitch bridge. + - RunPodSandbox from runtime service failed: rpc error: code = 2 desc = NetworkPlugin cni failed to set up pod "kdb-server-testing-180-build_katrin" network: CNI request failed with status 400: 'failed to run IPAM for 4b56e403e2757d38dca67831ce09e10bc3b3f442b6699c20dcd89556763e2d5d: failed to run CNI IPAM ADD: no IP addresses available in network: openshift-sdn + CreatePodSandbox for pod "kdb-server-testing-180-build_katrin(65640902-3bd6-11ea-bbd6-0cc47adef0e6)" failed: rpc error: code = 2 desc = NetworkPlugin cni failed to set up pod "kdb-server-testing-180-build_katrin" network: CNI request failed with status 400: 'failed to run IPAM for 4b56e403e2757d38dca67831ce09e10bc3b3f442b6699c20dcd89556763e2d5d: failed to run CNI IPAM ADD: no IP addresses available in network: openshift-sdn + Indicates exhaustion of the IP range of the pod network on the node. This also seems triggered by problems with resource management and + pereodic manual clean-up is required. + - containerd: unable to save f7c3e6c02cdbb951670bc7ff925ddd7efd75a3bb5ed60669d4b182e5337dec23:d5b9394468235f7c9caca8ad4d97e7064cc49cd59cadd155eceae84545dc472a starttime: read /proc/81994/stat: no such process containerd: f7c3e6c02cdbb951670bc7ff925ddd7efd75a3bb5ed60669d4b182e5337dec23:d5b9394468235f7c9caca8ad4d97e7064cc49cd59cadd155eceae84545dc472a (pid 81994) has become an orphan, killing it Seems a bug in docker 1.12* which is resolved in 1.13.0rc2. No side effects according to the issue. |