diff options
| author | Suren A. Chilingaryan <csa@suren.me> | 2018-07-05 06:29:09 +0200 |
|---|---|---|
| committer | Suren A. Chilingaryan <csa@suren.me> | 2018-07-05 06:29:09 +0200 |
| commit | 2c3f1522274c09f7cfdb6309adc0719f05c188e9 (patch) | |
| tree | e54e0c26f581543f48e945f186734e4bd9a8f15a /docs/consistency.txt | |
| parent | 8af0865a3a3ef783b36016c17598adc9d932981d (diff) | |
| download | ands-2c3f1522274c09f7cfdb6309adc0719f05c188e9.tar.gz ands-2c3f1522274c09f7cfdb6309adc0719f05c188e9.tar.bz2 ands-2c3f1522274c09f7cfdb6309adc0719f05c188e9.tar.xz ands-2c3f1522274c09f7cfdb6309adc0719f05c188e9.zip | |
Update monitoring scripts to track leftover OpenVSwitch 'veth' interfaces and clean them up pereodically to avoid performance degradation, split kickstart
Diffstat (limited to 'docs/consistency.txt')
| -rw-r--r-- | docs/consistency.txt | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/docs/consistency.txt b/docs/consistency.txt index caaaf36..dcf311a 100644 --- a/docs/consistency.txt +++ b/docs/consistency.txt @@ -39,7 +39,17 @@ Networking - Ensure, we don't have override of cluster_name to first master (which we do during the provisioning of OpenShift plays) - + + - Sometimes OpenShift fails to clean-up after terminated pod properly. This causes rogue + network interfaces to remain in OpenVSwitch fabric. This can be determined by errors like: + could not open network device vethb9de241f (No such device) + reported by 'ovs-vsctl show' or present in the log '/var/log/openvswitch/ovs-vswitchd.log' + which may quickly grow over 100MB quickly. If number of rogue interfaces grows too much, + the pod scheduling will start time-out on the affected node. + * The work-around is to delete rogue interfaces with + ovs-vsctl del-port br0 <iface> + This does not solve the problem, however. The new interfaces will get abandoned by OpenShift. + ADEI ==== |