3.5. 웹 콘솔을 사용하여 OVN-Kubernetes 로그 보기

프로세스

1. OVN-Kubernetes 프로젝트의 모든 포드에 대한 자세한 정보를 얻으려면 다음 명령을 실행하세요.

   $ oc get po -o wide -n openshift-ovn-kubernetes

   출력 예

   NAME                                     READY   STATUS    RESTARTS       AGE    IP           NODE                                       NOMINATED NODE   READINESS GATES
   ovnkube-control-plane-65497d4548-9ptdr   2/2     Running   2 (128m ago)   147m   10.0.0.3     ci-ln-3njdr9b-72292-5nwkp-master-0         <none>           <none>
   ovnkube-control-plane-65497d4548-j6zfk   2/2     Running   0              147m   10.0.0.5     ci-ln-3njdr9b-72292-5nwkp-master-2         <none>           <none>
   ovnkube-node-5dx44                       8/8     Running   0              146m   10.0.0.3     ci-ln-3njdr9b-72292-5nwkp-master-0         <none>           <none>
   ovnkube-node-dpfn4                       8/8     Running   0              146m   10.0.0.4     ci-ln-3njdr9b-72292-5nwkp-master-1         <none>           <none>
   ovnkube-node-kwc9l                       8/8     Running   0              134m   10.0.128.2   ci-ln-3njdr9b-72292-5nwkp-worker-a-2fjcj   <none>           <none>
   ovnkube-node-mcrhl                       8/8     Running   0              134m   10.0.128.4   ci-ln-3njdr9b-72292-5nwkp-worker-c-v9x5v   <none>           <none>
   ovnkube-node-nsct4                       8/8     Running   0              146m   10.0.0.5     ci-ln-3njdr9b-72292-5nwkp-master-2         <none>           <none>
   ovnkube-node-zrj9f                       8/8     Running   0              134m   10.0.128.3   ci-ln-3njdr9b-72292-5nwkp-worker-b-v78h7   <none>           <none>

2. 다음 예제와 유사한 ConfigMap 파일을 만들고 env-overrides.yaml 과 같은 파일 이름을 사용합니다.

   예제 ConfigMap 파일

   kind: ConfigMap
   apiVersion: v1
   metadata:
     name: env-overrides
     namespace: openshift-ovn-kubernetes
   data:
     ci-ln-3njdr9b-72292-5nwkp-master-0: | 

   1

   
       # This sets the log level for the ovn-kubernetes node process:
       OVN_KUBE_LOG_LEVEL=5
       # You might also/instead want to enable debug logging for ovn-controller:
       OVN_LOG_LEVEL=dbg
     ci-ln-3njdr9b-72292-5nwkp-master-2: |
       # This sets the log level for the ovn-kubernetes node process:
       OVN_KUBE_LOG_LEVEL=5
       # You might also/instead want to enable debug logging for ovn-controller:
       OVN_LOG_LEVEL=dbg
     _master: | 

   2

   
       # This sets the log level for the ovn-kubernetes master process as well as the ovn-dbchecker:
       OVN_KUBE_LOG_LEVEL=5
       # You might also/instead want to enable debug logging for northd, nbdb and sbdb on all masters:
       OVN_LOG_LEVEL=dbg

   1

   디버그 로그 수준을 설정할 노드의 이름을 지정합니다.

   2

   ovnkube-master 구성 요소의 로그 수준을 설정하려면 _master를 지정하세요.

3. 다음 명령을 사용하여 ConfigMap 파일을 적용합니다.

   $ oc apply -n openshift-ovn-kubernetes -f env-overrides.yaml

   출력 예

   configmap/env-overrides.yaml created

4. 다음 명령을 사용하여 ovnkube 포드를 다시 시작하여 새 로그 수준을 적용합니다.

   $ oc delete pod -n openshift-ovn-kubernetes \
   --field-selector spec.nodeName=ci-ln-3njdr9b-72292-5nwkp-master-0 -l app=ovnkube-node

   $ oc delete pod -n openshift-ovn-kubernetes \
   --field-selector spec.nodeName=ci-ln-3njdr9b-72292-5nwkp-master-2 -l app=ovnkube-node

   $ oc delete pod -n openshift-ovn-kubernetes -l app=ovnkube-node

5. `ConfigMap` 파일이 특정 Pod의 모든 노드에 적용되었는지 확인하려면 다음 명령을 실행하세요.

   $ oc logs -n openshift-ovn-kubernetes --all-containers --prefix ovnkube-node-<xxxx> | grep -E -m 10 '(Logging config:|vconsole|DBG)'

   다음과 같습니다.

   <XXXX>

   이전 단계의 포드에 대한 무작위 문자 시퀀스를 지정합니다.

   출력 예

   [pod/ovnkube-node-2cpjc/sbdb] + exec /usr/share/ovn/scripts/ovn-ctl --no-monitor '--ovn-sb-log=-vconsole:info -vfile:off -vPATTERN:console:%D{%Y-%m-%dT%H:%M:%S.###Z}|%05N|%c%T|%p|%m' run_sb_ovsdb
   [pod/ovnkube-node-2cpjc/ovnkube-controller] I1012 14:39:59.984506   35767 config.go:2247] Logging config: {File: CNIFile:/var/log/ovn-kubernetes/ovn-k8s-cni-overlay.log LibovsdbFile:/var/log/ovnkube/libovsdb.log Level:5 LogFileMaxSize:100 LogFileMaxBackups:5 LogFileMaxAge:0 ACLLoggingRateLimit:20}
   [pod/ovnkube-node-2cpjc/northd] + exec ovn-northd --no-chdir -vconsole:info -vfile:off '-vPATTERN:console:%D{%Y-%m-%dT%H:%M:%S.###Z}|%05N|%c%T|%p|%m' --pidfile /var/run/ovn/ovn-northd.pid --n-threads=1
   [pod/ovnkube-node-2cpjc/nbdb] + exec /usr/share/ovn/scripts/ovn-ctl --no-monitor '--ovn-nb-log=-vconsole:info -vfile:off -vPATTERN:console:%D{%Y-%m-%dT%H:%M:%S.###Z}|%05N|%c%T|%p|%m' run_nb_ovsdb
   [pod/ovnkube-node-2cpjc/ovn-controller] 2023-10-12T14:39:54.552Z|00002|hmap|DBG|lib/shash.c:114: 1 bucket with 6+ nodes, including 1 bucket with 6 nodes (32 nodes total across 32 buckets)
   [pod/ovnkube-node-2cpjc/ovn-controller] 2023-10-12T14:39:54.553Z|00003|hmap|DBG|lib/shash.c:114: 1 bucket with 6+ nodes, including 1 bucket with 6 nodes (64 nodes total across 64 buckets)
   [pod/ovnkube-node-2cpjc/ovn-controller] 2023-10-12T14:39:54.553Z|00004|hmap|DBG|lib/shash.c:114: 1 bucket with 6+ nodes, including 1 bucket with 7 nodes (32 nodes total across 32 buckets)
   [pod/ovnkube-node-2cpjc/ovn-controller] 2023-10-12T14:39:54.553Z|00005|reconnect|DBG|unix:/var/run/openvswitch/db.sock: entering BACKOFF
   [pod/ovnkube-node-2cpjc/ovn-controller] 2023-10-12T14:39:54.553Z|00007|reconnect|DBG|unix:/var/run/openvswitch/db.sock: entering CONNECTING
   [pod/ovnkube-node-2cpjc/ovn-controller] 2023-10-12T14:39:54.553Z|00008|ovsdb_cs|DBG|unix:/var/run/openvswitch/db.sock: SERVER_SCHEMA_REQUESTED -> SERVER_SCHEMA_REQUESTED at lib/ovsdb-cs.c:423

6. 선택 사항: 다음 명령을 실행하여 ConfigMap 파일이 적용되었는지 확인하세요.

   for f in $(oc -n openshift-ovn-kubernetes get po -l 'app=ovnkube-node' --no-headers -o custom-columns=N:.metadata.name) ; do echo "---- $f ----" ; oc -n openshift-ovn-kubernetes exec -c ovnkube-controller $f --  pgrep -a -f  init-ovnkube-controller | grep -P -o '^.*loglevel\s+\d' ; done

   출력 예

   ---- ovnkube-node-2dt57 ----
   60981 /usr/bin/ovnkube --init-ovnkube-controller xpst8-worker-c-vmh5n.c.openshift-qe.internal --init-node xpst8-worker-c-vmh5n.c.openshift-qe.internal --config-file=/run/ovnkube-config/ovnkube.conf --ovn-empty-lb-events --loglevel 4
   ---- ovnkube-node-4zznh ----
   178034 /usr/bin/ovnkube --init-ovnkube-controller xpst8-master-2.c.openshift-qe.internal --init-node xpst8-master-2.c.openshift-qe.internal --config-file=/run/ovnkube-config/ovnkube.conf --ovn-empty-lb-events --loglevel 4
   ---- ovnkube-node-548sx ----
   77499 /usr/bin/ovnkube --init-ovnkube-controller xpst8-worker-a-fjtnb.c.openshift-qe.internal --init-node xpst8-worker-a-fjtnb.c.openshift-qe.internal --config-file=/run/ovnkube-config/ovnkube.conf --ovn-empty-lb-events --loglevel 4
   ---- ovnkube-node-6btrf ----
   73781 /usr/bin/ovnkube --init-ovnkube-controller xpst8-worker-b-p8rww.c.openshift-qe.internal --init-node xpst8-worker-b-p8rww.c.openshift-qe.internal --config-file=/run/ovnkube-config/ovnkube.conf --ovn-empty-lb-events --loglevel 4
   ---- ovnkube-node-fkc9r ----
   130707 /usr/bin/ovnkube --init-ovnkube-controller xpst8-master-0.c.openshift-qe.internal --init-node xpst8-master-0.c.openshift-qe.internal --config-file=/run/ovnkube-config/ovnkube.conf --ovn-empty-lb-events --loglevel 5
   ---- ovnkube-node-tk9l4 ----
   181328 /usr/bin/ovnkube --init-ovnkube-controller xpst8-master-1.c.openshift-qe.internal --init-node xpst8-master-1.c.openshift-qe.internal --config-file=/run/ovnkube-config/ovnkube.conf --ovn-empty-lb-events --loglevel 4