CI Management、またはContainer Managementの状態異常

■事象

CI Management、またはContainer Managementの更新に失敗します。

TASK [get_status/container_mng : Show k8s other component status] **************
ok: [172.16.0.11] => (item=fj-nginx-ingress-controller-689c9468cd-22ctm                       1/1       Running    0          2d) => {
    "msg": "fj-nginx-ingress-controller-689c9468cd-22ctm                       1/1       Running    0          2d"
}
ok: [172.16.0.11] => (item=fj-nginx-ingress-controller-689c9468cd-fcw47                       1/1       Running    0          2d) => {
    "msg": "fj-nginx-ingress-controller-689c9468cd-fcw47                       1/1       Running    0          2d"
}
ok: [172.16.0.11] => (item=fj-nginx-ingress-default-backend-598d54d4c7-q98pz                  1/1       Running    0          2d) => {
    "msg": "fj-nginx-ingress-default-backend-598d54d4c7-q98pz                  1/1       Running    0          2d"
}
ok: [172.16.0.11] => (item=fj-nginx-ingress-default-backend-598d54d4c7-sb476                  1/1       Running    0          2d) => {
    "msg": "fj-nginx-ingress-default-backend-598d54d4c7-sb476                  1/1       Running    0          2d"
}
ok: [172.16.0.11] => (item=kube-dns-86f4d74b45-h4r4d                                          3/3       Running    0          1d) => {
    "msg": "kube-dns-86f4d74b45-h4r4d                                          3/3       Running    0          1d"
}
ok: [172.16.0.11] => (item=kube-flannel-ds-9swvz                                              1/1       Running    1          1d) => {
    "msg": "kube-flannel-ds-9swvz                                              1/1       Running    1          1d"
}
failed: [172.16.0.11] (item=kube-flannel-ds-hvtms                                              0/1       Error      1          1d) => {
    "msg": "kube-flannel-ds-hvtms                                              0/1       Error      1          1d"
}
ok: [172.16.0.11] => (item=kube-flannel-ds-lk4kr                                              1/1       Running    0          1d) => {
    "msg": "kube-flannel-ds-lk4kr                                              1/1       Running    0          1d"
}
failed: [172.16.0.11] (item=kube-proxy-9hhkh                                                   1/1       NodeLost   3          1d) => {
    "msg": "kube-proxy-9hhkh                                                   1/1       NodeLost   3          1d"
}
ok: [172.16.0.11] => (item=kube-proxy-m27gt                                                   1/1       Running    0          1d) => {
    "msg": "kube-proxy-m27gt                                                   1/1       Running    0          1d"
}
ok: [172.16.0.11] => (item=kube-proxy-vsfmb                                                   1/1       Running    0          1d) => {
    "msg": "kube-proxy-vsfmb                                                   1/1       Running    0          1d"
}
ok: [172.16.0.11] => (item=tiller-deploy-5db96f7b4b-9zkht                                     1/1       Running    0          2d) => {
    "msg": "tiller-deploy-5db96f7b4b-9zkht                                     1/1       Running    0          2d"
}
fatal: [172.16.0.11]: FAILED! => {"msg": "All items completed"}

■原因

CI Management、またはContainer Managementが不正な状態です。

上記の例では、Container Managementを更新する際に、STATUSが「Running」以外の状態のコンポーネントを検出したため失敗しています。

■対処方法

「運用ガイド」のCI Managementの復旧、またはContainer Managementの復旧の手順を実施してください。復旧が正常に完了した後、更新操作を再実行してください。

1.10.1 CI Management、またはContainer Managementの状態異常

■事象

■原因

■対処方法