INFO: =================== Thu Apr 17 01:57:54 UTC 2025 ===================
INFO: Waiting for cassandra 2/30
INFO: Waiting for cassandra 3/30
INFO: Waiting for cassandra 4/30
INFO: Waiting for cassandra 5/30
INFO: Waiting for cassandra 6/30
INFO: Waiting for cassandra 7/30
INFO: Waiting for cassandra 8/30
INFO: Waiting for cassandra 9/30
INFO: Waiting for cassandra 10/30
INFO: Cassandra is connected
/usr/local/lib/python3.6/site-packages/cfgm_common/vnc_kombu.py:10: MonkeyPatchWarning: Patching more than once will result in the union of all True parameters being patched
  gevent.monkey.patch_all()
04/17/2025 01:59:36.236 7f71ed353248 [contrail-kube-manager] [INFO]: SANDESH: CONNECT TO COLLECTOR: True
04/17/2025 01:59:36.537 7f71ed353248 [contrail-kube-manager] [INFO]: SANDESH: Logging: LEVEL: [SYS_INFO] -> [SYS_NOTICE]
2025-04-17 01:59:38.10: KubeMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 01:59:38.10: KubeMonitor - Connect Kube API result 0
2025-04-17 01:59:38.34: KubeMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/api/v1
2025-04-17 01:59:38.37: NamespaceMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/api/v1
2025-04-17 01:59:38.42: NetworkMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1
2025-04-17 01:59:38.45: PodMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/api/v1
2025-04-17 01:59:38.46: ServiceMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/api/v1
2025-04-17 01:59:38.48: NetworkPolicyMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/apis/networking.k8s.io/v1
2025-04-17 01:59:38.53: EndPointMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/api/v1
2025-04-17 01:59:38.55: IngressMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/apis/networking.k8s.io/v1
2025-04-17 01:59:38.55: VncKubernetes - vnc_connect starting
2025-04-17 01:59:38.64: VncKubernetes - vnc_connect failed: 
2025-04-17 01:59:41.66: VncKubernetes - vnc_connect failed: 
2025-04-17 01:59:44.69: VncKubernetes - vnc_connect failed: 
2025-04-17 01:59:47.73: VncKubernetes - vnc_connect failed: 
2025-04-17 01:59:50.76: VncKubernetes - vnc_connect failed: 
2025-04-17 01:59:53.77: VncKubernetes - vnc_connect failed: 
2025-04-17 01:59:56.81: VncKubernetes - vnc_connect failed: 
2025-04-17 01:59:59.93: VncKubernetes - vnc_connect failed: 
2025-04-17 02:00:02.95: VncKubernetes - vnc_connect done
2025-04-17 02:00:03.92: default-domain domain available.
2025-04-17 02:00:20.77: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:00:20.77: NamespaceMonitor - start process kube event
2025-04-17 02:00:20.77: NamespaceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-17 02:00:20.77: NamespaceMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:00:20.77: NetworkMonitor - start process kube event
2025-04-17 02:00:20.77: NetworkMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-17 02:00:20.77: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:00:20.77: PodMonitor - start process kube event
2025-04-17 02:00:20.77: PodMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-17 02:00:20.77: PodMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:00:20.77: ServiceMonitor - start process kube event
2025-04-17 02:00:20.77: ServiceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-17 02:00:20.77: ServiceMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:00:20.77: NetworkPolicyMonitor - start process kube event
2025-04-17 02:00:20.77: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-17 02:00:20.77: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:00:20.77: EndPointMonitor - start process kube event
2025-04-17 02:00:20.77: EndPointMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-17 02:00:20.77: EndPointMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:00:20.77: IngressMonitor - start process kube event
2025-04-17 02:00:20.77: IngressMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-17 02:00:20.77: IngressMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:00:20.77: IngressMonitor - Connect Kube API result 0
2025-04-17 02:00:20.77: IngressMonitor - Start init url=https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses resource_version=None
2025-04-17 02:00:20.78: EndPointMonitor - Connect Kube API result 0
2025-04-17 02:00:20.78: EndPointMonitor - Start init url=https://10.0.0.22:6443/api/v1/endpoints resource_version=None
2025-04-17 02:00:20.78: NetworkPolicyMonitor - Connect Kube API result 0
2025-04-17 02:00:20.78: NetworkPolicyMonitor - Start init url=https://10.0.0.22:6443/apis/networking.k8s.io/v1/networkpolicies resource_version=None
2025-04-17 02:00:20.78: ServiceMonitor - Connect Kube API result 0
2025-04-17 02:00:20.78: ServiceMonitor - Start init url=https://10.0.0.22:6443/api/v1/services resource_version=None
2025-04-17 02:00:20.78: PodMonitor - Connect Kube API result 0
2025-04-17 02:00:20.78: PodMonitor - Start init url=https://10.0.0.22:6443/api/v1/pods resource_version=None
2025-04-17 02:00:20.78: NetworkMonitor - Connect Kube API result 0
2025-04-17 02:00:20.78: NamespaceMonitor - Connect Kube API result 0
2025-04-17 02:00:20.78: NamespaceMonitor - Start init url=https://10.0.0.22:6443/api/v1/namespaces resource_version=None
2025-04-17 02:00:20.88: NetworkPolicyMonitor - Done init url=https://10.0.0.22:6443/apis/networking.k8s.io/v1/networkpolicies, resource_version=10075
2025-04-17 02:00:20.88: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-17 02:00:20.88: NetworkPolicyMonitor - Start Watching request https://10.0.0.22:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:00:20.88: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-17 02:00:20.88: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-17 02:00:20.89: NetworkMonitor - Start init url=https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions resource_version=None
2025-04-17 02:00:20.89: IngressMonitor - Done init url=https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses, resource_version=10075
2025-04-17 02:00:20.89: IngressMonitor - _schedule_vnc_sync
2025-04-17 02:00:20.89: IngressMonitor - Start Watching request https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:00:20.91: ServiceMonitor - Got ADDED Service default:kubernetes:b776cddd-bd4f-4a05-adc9-bc822e04b0d1
2025-04-17 02:00:20.92: PodMonitor - Skipped ADDED Pod kube-system:config-zookeeper-h8stv (hostNetwork=True)
2025-04-17 02:00:20.92: EndPointMonitor - Got ADDED Endpoints default:kubernetes:0ce181a4-cb67-4d4c-8e48-99add2293117
2025-04-17 02:00:20.93: IngressMonitor - Watches https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:00:20.93: NetworkPolicyMonitor - Watches https://10.0.0.22:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:00:20.93: NetworkMonitor - Done init url=https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions, resource_version=10080
2025-04-17 02:00:20.93: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:00:20.93: NetworkMonitor - Start Watching request https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})(timeout=120)
2025-04-17 02:00:20.93: NamespaceMonitor - Got ADDED Namespace None:default:98521e59-dae3-4425-8e8d-09cb146dee93
2025-04-17 02:00:20.94: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-17 02:00:20.94: VncKubernetes - wait event (qsize=5 timeout=120)
2025-04-17 02:00:20.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-17 02:00:20.94: VncKubernetes - vnc_sync - Ingress start
2025-04-17 02:00:20.94: VncKubernetes - vnc_sync - Ingress done
2025-04-17 02:00:20.94: VncKubernetes - wait event (qsize=4 timeout=120)
2025-04-17 02:00:20.94: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Service ns=default)
VncService - Got ADDED Service default:kubernetes:b776cddd-bd4f-4a05-adc9-bc822e04b0d1
2025-04-17 02:00:20.94: PodMonitor - Got ADDED Pod kube-system:coredns-77f7cc69db-pd4b7:21fefc99-fca7-42dd-9801-482b4c22c8fa
2025-04-17 02:00:20.95: EndPointMonitor - Got ADDED Endpoints kube-system:coredns:568cd9bd-52b9-47c4-95c3-e5c29fb70331
2025-04-17 02:00:20.95: EndPointMonitor - Done init url=https://10.0.0.22:6443/api/v1/endpoints, resource_version=10075
2025-04-17 02:00:20.95: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:00:20.95: EndPointMonitor - Start Watching request https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:00:20.95: ServiceMonitor - Got ADDED Service kube-system:coredns:40b786fd-8792-443b-8217-6cdb39950c97
2025-04-17 02:00:20.95: ServiceMonitor - Done init url=https://10.0.0.22:6443/api/v1/services, resource_version=10075
2025-04-17 02:00:20.95: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:00:20.95: ServiceMonitor - Start Watching request https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:00:20.95: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})
2025-04-17 02:00:20.96: NamespaceMonitor - Got ADDED Namespace None:kube-node-lease:2bbba99f-7072-4154-b1a1-ec464266cde5
2025-04-17 02:00:20.96: ServiceMonitor - Watches https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:00:20.96: EndPointMonitor - Watches https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:00:20.97: PodMonitor - Got ADDED Pod kube-system:dns-autoscaler-595558c478-vbj5m:b667650b-1faa-426d-93ba-cab8f597463b
2025-04-17 02:00:20.97: NamespaceMonitor - Got ADDED Namespace None:kube-public:3867ebad-8a80-4637-a716-84e3ca51fee0
2025-04-17 02:00:20.98: PodMonitor - Skipped ADDED Pod kube-system:kube-apiserver-cn-jenkins-deploy-platform-k8s-manifests-160-1 (hostNetwork=True)
2025-04-17 02:00:20.98: NamespaceMonitor - Got ADDED Namespace None:kube-system:18156adc-ce42-436f-845d-657f78dba3fb
2025-04-17 02:00:20.98: NamespaceMonitor - Done init url=https://10.0.0.22:6443/api/v1/namespaces, resource_version=10075
2025-04-17 02:00:20.98: NamespaceMonitor - _schedule_vnc_sync
2025-04-17 02:00:20.98: NamespaceMonitor - Start Watching request https://10.0.0.22:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:00:20.99: PodMonitor - Skipped ADDED Pod kube-system:kube-controller-manager-cn-jenkins-deploy-platform-k8s-manifests-160-1 (hostNetwork=True)
2025-04-17 02:00:20.99: NamespaceMonitor - Watches https://10.0.0.22:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:00:21.00: PodMonitor - Skipped ADDED Pod kube-system:kube-proxy-xvvfc (hostNetwork=True)
2025-04-17 02:00:21.01: PodMonitor - Skipped ADDED Pod kube-system:kube-scheduler-cn-jenkins-deploy-platform-k8s-manifests-160-1 (hostNetwork=True)
2025-04-17 02:00:21.01: PodMonitor - Skipped ADDED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:00:21.02: PodMonitor - Skipped ADDED Pod kube-system:opensdn-analytics-8k49p (hostNetwork=True)
2025-04-17 02:00:21.03: PodMonitor - Skipped ADDED Pod kube-system:opensdn-analytics-alarm-2wtsh (hostNetwork=True)
2025-04-17 02:00:21.03: PodMonitor - Skipped ADDED Pod kube-system:opensdn-analytics-snmp-hp9rl (hostNetwork=True)
2025-04-17 02:00:21.06: PodMonitor - Skipped ADDED Pod kube-system:opensdn-analyticsdb-wls4g (hostNetwork=True)
2025-04-17 02:00:21.07: PodMonitor - Skipped ADDED Pod kube-system:opensdn-configdb-8smxv (hostNetwork=True)
2025-04-17 02:00:21.09: PodMonitor - Skipped ADDED Pod kube-system:opensdn-controller-config-sf7tb (hostNetwork=True)
2025-04-17 02:00:21.10: PodMonitor - Skipped ADDED Pod kube-system:opensdn-controller-control-v8wjx (hostNetwork=True)
2025-04-17 02:00:21.11: PodMonitor - Skipped ADDED Pod kube-system:opensdn-controller-webui-mfzgh (hostNetwork=True)
2025-04-17 02:00:21.14: PodMonitor - Skipped ADDED Pod kube-system:opensdn-kube-manager-zr66r (hostNetwork=True)
2025-04-17 02:00:21.14: PodMonitor - Skipped ADDED Pod kube-system:rabbitmq-rhggn (hostNetwork=True)
2025-04-17 02:00:21.15: PodMonitor - Skipped ADDED Pod kube-system:redis-jpbxl (hostNetwork=True)
2025-04-17 02:00:21.15: PodMonitor - Done init url=https://10.0.0.22:6443/api/v1/pods, resource_version=10075
2025-04-17 02:00:21.15: PodMonitor - _schedule_vnc_sync
2025-04-17 02:00:21.15: PodMonitor - Start Watching request https://10.0.0.22:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:00:21.16: PodMonitor - Watches https://10.0.0.22:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:00:21.16: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:00:21.16: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:00:21.16: PodMonitor - start process kube event
2025-04-17 02:00:21.16: empty line received
2025-04-17 02:00:21.16: PodMonitor - start process kube event
2025-04-17 02:00:21.95: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:00:21.95: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:00:21.95: PodMonitor - start process kube event
2025-04-17 02:00:21.95: empty line received
2025-04-17 02:00:21.95: PodMonitor - start process kube event
2025-04-17 02:00:23.28: VncKubernetes - wait event (qsize=14 timeout=120)
2025-04-17 02:00:23.29: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Endpoints ns=default)
VncEndpoints - Got ADDED Endpoints default:kubernetes:0ce181a4-cb67-4d4c-8e48-99add2293117
2025-04-17 02:00:23.39: VncKubernetes - wait event (qsize=13 timeout=120)
2025-04-17 02:00:23.39: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:00:23.39: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:00:23.39: VncKubernetes - wait event (qsize=12 timeout=120)
2025-04-17 02:00:23.39: VncKubernetes - Process event (name=default event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace default:98521e59-dae3-4425-8e8d-09cb146dee93
2025-04-17 02:00:27.79: VncKubernetes - wait event (qsize=11 timeout=120)
2025-04-17 02:00:27.79: VncKubernetes - Process event (name=coredns-77f7cc69db-pd4b7 event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:coredns-77f7cc69db-pd4b7:21fefc99-fca7-42dd-9801-482b4c22c8fa
2025-04-17 02:00:30.08: VncKubernetes - wait event (qsize=10 timeout=120)
2025-04-17 02:00:30.09: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Endpoints ns=kube-system)
VncEndpoints - Got ADDED Endpoints kube-system:coredns:568cd9bd-52b9-47c4-95c3-e5c29fb70331
2025-04-17 02:00:30.09: PodMonitor - Received MODIFIED Pod kube-system:coredns-77f7cc69db-pd4b7:21fefc99-fca7-42dd-9801-482b4c22c8fa
2025-04-17 02:00:30.09: PodMonitor - Got MODIFIED Pod kube-system:coredns-77f7cc69db-pd4b7:21fefc99-fca7-42dd-9801-482b4c22c8fa
2025-04-17 02:00:30.09: PodMonitor - start process kube event
2025-04-17 02:00:30.09: empty line received
2025-04-17 02:00:30.09: PodMonitor - start process kube event
2025-04-17 02:00:30.14: VncKubernetes - wait event (qsize=10 timeout=120)
2025-04-17 02:00:30.14: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:00:30.14: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:00:30.14: VncKubernetes - wait event (qsize=9 timeout=120)
2025-04-17 02:00:30.14: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Service ns=kube-system)
VncService - Got ADDED Service kube-system:coredns:40b786fd-8792-443b-8217-6cdb39950c97
2025-04-17 02:00:33.49: VncKubernetes - wait event (qsize=8 timeout=120)
2025-04-17 02:00:33.49: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:00:33.49: VncKubernetes - vnc_sync - Service start
2025-04-17 02:00:33.49: VncKubernetes - vnc_sync - Service done
2025-04-17 02:00:33.49: VncKubernetes - wait event (qsize=7 timeout=120)
2025-04-17 02:00:33.49: VncKubernetes - Process event (name=kube-node-lease event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-node-lease:2bbba99f-7072-4154-b1a1-ec464266cde5
2025-04-17 02:00:36.89: VncKubernetes - wait event (qsize=6 timeout=120)
2025-04-17 02:00:36.89: VncKubernetes - Process event (name=dns-autoscaler-595558c478-vbj5m event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:dns-autoscaler-595558c478-vbj5m:b667650b-1faa-426d-93ba-cab8f597463b
2025-04-17 02:00:37.45: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:00:37.45: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:00:37.45: PodMonitor - start process kube event
2025-04-17 02:00:37.45: empty line received
2025-04-17 02:00:37.45: PodMonitor - start process kube event
2025-04-17 02:00:38.61: PodMonitor - Received MODIFIED Pod kube-system:dns-autoscaler-595558c478-vbj5m:b667650b-1faa-426d-93ba-cab8f597463b
2025-04-17 02:00:38.61: PodMonitor - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-vbj5m:b667650b-1faa-426d-93ba-cab8f597463b
2025-04-17 02:00:38.61: VncKubernetes - wait event (qsize=6 timeout=120)
2025-04-17 02:00:38.61: VncKubernetes - Process event (name=kube-public event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-public:3867ebad-8a80-4637-a716-84e3ca51fee0
2025-04-17 02:00:38.61: PodMonitor - start process kube event
2025-04-17 02:00:38.61: empty line received
2025-04-17 02:00:38.61: PodMonitor - start process kube event
2025-04-17 02:00:41.47: VncKubernetes - wait event (qsize=5 timeout=120)
2025-04-17 02:00:41.47: VncKubernetes - Process event (name=kube-system event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-system:18156adc-ce42-436f-845d-657f78dba3fb
2025-04-17 02:00:44.06: VncKubernetes - wait event (qsize=4 timeout=120)
2025-04-17 02:00:44.06: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-17 02:00:44.06: VncKubernetes - vnc_sync - Namespace start
2025-04-17 02:00:44.06: VncKubernetes - vnc_sync - Namespace done
2025-04-17 02:00:44.06: VncKubernetes - wait event (qsize=3 timeout=120)
2025-04-17 02:00:44.06: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-17 02:00:44.06: VncKubernetes - vnc_sync - Pod start
2025-04-17 02:00:44.06: VncKubernetes - vnc_sync - Pod done
2025-04-17 02:00:44.06: VncKubernetes - wait event (qsize=2 timeout=120)
2025-04-17 02:00:44.06: VncKubernetes - Process event (name=coredns-77f7cc69db-pd4b7 event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:coredns-77f7cc69db-pd4b7:21fefc99-fca7-42dd-9801-482b4c22c8fa
2025-04-17 02:00:44.16: VncKubernetes - wait event (qsize=1 timeout=120)
2025-04-17 02:00:44.16: VncKubernetes - Process event (name=dns-autoscaler-595558c478-vbj5m event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-vbj5m:b667650b-1faa-426d-93ba-cab8f597463b
2025-04-17 02:00:44.27: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:01:16.61: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:01:16.61: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:01:16.61: PodMonitor - start process kube event
2025-04-17 02:01:16.61: empty line received
2025-04-17 02:01:16.61: PodMonitor - start process kube event
2025-04-17 02:01:20.84: PodMonitor - Received BOOKMARK: oldResVer=10075 newResVer=10164
2025-04-17 02:01:20.84: PodMonitor - start process kube event
2025-04-17 02:01:20.84: empty line received
2025-04-17 02:01:20.84: PodMonitor - start process kube event
2025-04-17 02:01:21.01: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10075 newResVer=10156
2025-04-17 02:01:21.02: NetworkPolicyMonitor - start process kube event
2025-04-17 02:01:21.02: empty line received
2025-04-17 02:01:21.02: NetworkPolicyMonitor - start process kube event
2025-04-17 02:01:31.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:01:31.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:01:31.56: PodMonitor - start process kube event
2025-04-17 02:01:31.56: empty line received
2025-04-17 02:01:31.56: PodMonitor - start process kube event
2025-04-17 02:01:37.14: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:01:37.14: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:01:37.14: PodMonitor - start process kube event
2025-04-17 02:01:37.14: empty line received
2025-04-17 02:01:37.14: PodMonitor - start process kube event
2025-04-17 02:01:51.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:01:51.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:01:51.56: PodMonitor - start process kube event
2025-04-17 02:01:51.56: empty line received
2025-04-17 02:01:51.56: PodMonitor - start process kube event
2025-04-17 02:02:06.93: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:02:06.93: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:02:06.93: PodMonitor - start process kube event
2025-04-17 02:02:06.93: empty line received
2025-04-17 02:02:06.93: PodMonitor - start process kube event
2025-04-17 02:02:20.40: PodMonitor - Received BOOKMARK: oldResVer=10164 newResVer=10239
2025-04-17 02:02:20.40: PodMonitor - start process kube event
2025-04-17 02:02:20.40: empty line received
2025-04-17 02:02:20.40: PodMonitor - start process kube event
2025-04-17 02:02:20.74: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10156 newResVer=10156
2025-04-17 02:02:20.74: NetworkPolicyMonitor - start process kube event
2025-04-17 02:02:20.74: empty line received
2025-04-17 02:02:20.74: NetworkPolicyMonitor - start process kube event
2025-04-17 02:02:20.93: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:02:20.93: IngressMonitor - start process kube event
2025-04-17 02:02:20.93: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10075
2025-04-17 02:02:20.93: IngressMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:02:20.93: IngressMonitor - Connect Kube API result 0
2025-04-17 02:02:20.93: IngressMonitor - _schedule_vnc_sync
2025-04-17 02:02:20.93: IngressMonitor - Start Watching request https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:02:20.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-17 02:02:20.94: VncKubernetes - vnc_sync - Ingress start
2025-04-17 02:02:20.94: VncKubernetes - vnc_sync - Ingress done
2025-04-17 02:02:20.94: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:02:20.95: IngressMonitor - Watches https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:02:20.95: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:02:20.95: NetworkMonitor - start process kube event
2025-04-17 02:02:20.95: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10080
2025-04-17 02:02:20.95: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:02:20.95: NetworkMonitor - Connect Kube API result 0
2025-04-17 02:02:20.95: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:02:20.95: NetworkMonitor - Start Watching request https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})(timeout=120)
2025-04-17 02:02:20.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:02:20.96: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:02:20.96: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:02:20.96: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})
2025-04-17 02:02:20.97: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:02:20.97: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:02:20.97: ServiceMonitor - start process kube event
2025-04-17 02:02:20.97: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10075
2025-04-17 02:02:20.97: ServiceMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:02:20.97: EndPointMonitor - start process kube event
2025-04-17 02:02:20.97: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10075
2025-04-17 02:02:20.97: EndPointMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:02:20.97: ServiceMonitor - Connect Kube API result 0
2025-04-17 02:02:20.97: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:02:20.97: ServiceMonitor - Start Watching request https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:02:20.97: EndPointMonitor - Connect Kube API result 0
2025-04-17 02:02:20.97: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:02:20.97: EndPointMonitor - Start Watching request https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:02:20.98: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:02:20.98: VncKubernetes - vnc_sync - Service start
2025-04-17 02:02:20.98: VncKubernetes - vnc_sync - Service done
2025-04-17 02:02:20.98: VncKubernetes - wait event (qsize=1 timeout=120)
2025-04-17 02:02:20.98: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:02:20.98: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:02:20.98: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:02:20.98: ServiceMonitor - Watches https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:02:20.99: EndPointMonitor - Watches https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:02:21.00: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:02:21.00: NamespaceMonitor - start process kube event
2025-04-17 02:02:21.00: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10075
2025-04-17 02:02:21.00: NamespaceMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:02:21.00: NamespaceMonitor - Connect Kube API result 0
2025-04-17 02:02:21.00: NamespaceMonitor - _schedule_vnc_sync
2025-04-17 02:02:21.00: NamespaceMonitor - Start Watching request https://10.0.0.22:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:02:21.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-17 02:02:21.00: VncKubernetes - vnc_sync - Namespace start
2025-04-17 02:02:21.00: VncKubernetes - vnc_sync - Namespace done
2025-04-17 02:02:21.00: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:02:21.00: NamespaceMonitor - Watches https://10.0.0.22:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:03:07.40: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:03:07.40: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:03:07.40: PodMonitor - start process kube event
2025-04-17 02:03:07.40: empty line received
2025-04-17 02:03:07.40: PodMonitor - start process kube event
2025-04-17 02:03:18.57: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:03:18.57: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:03:18.57: PodMonitor - start process kube event
2025-04-17 02:03:18.57: empty line received
2025-04-17 02:03:18.57: PodMonitor - start process kube event
2025-04-17 02:03:20.77: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10156 newResVer=10156
2025-04-17 02:03:20.77: NetworkPolicyMonitor - start process kube event
2025-04-17 02:03:20.77: empty line received
2025-04-17 02:03:20.77: NetworkPolicyMonitor - start process kube event
2025-04-17 02:03:21.20: NamespaceMonitor - Received BOOKMARK: oldResVer=10075 newResVer=10218
2025-04-17 02:03:21.20: NamespaceMonitor - start process kube event
2025-04-17 02:03:21.20: empty line received
2025-04-17 02:03:21.20: NamespaceMonitor - start process kube event
2025-04-17 02:03:21.39: PodMonitor - Received BOOKMARK: oldResVer=10239 newResVer=10346
2025-04-17 02:03:21.39: PodMonitor - start process kube event
2025-04-17 02:03:21.39: empty line received
2025-04-17 02:03:21.39: PodMonitor - start process kube event
2025-04-17 02:04:01.83: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:04:01.83: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:04:01.83: PodMonitor - start process kube event
2025-04-17 02:04:01.83: empty line received
2025-04-17 02:04:01.83: PodMonitor - start process kube event
2025-04-17 02:04:16.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:04:16.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:04:16.56: PodMonitor - start process kube event
2025-04-17 02:04:16.56: empty line received
2025-04-17 02:04:16.56: PodMonitor - start process kube event
2025-04-17 02:04:20.95: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:04:20.95: IngressMonitor - start process kube event
2025-04-17 02:04:20.95: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10075
2025-04-17 02:04:20.95: IngressMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:04:20.95: IngressMonitor - Connect Kube API result 0
2025-04-17 02:04:20.95: IngressMonitor - _schedule_vnc_sync
2025-04-17 02:04:20.95: IngressMonitor - Start Watching request https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:04:20.95: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-17 02:04:20.95: VncKubernetes - vnc_sync - Ingress start
2025-04-17 02:04:20.95: VncKubernetes - vnc_sync - Ingress done
2025-04-17 02:04:20.95: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:04:20.96: IngressMonitor - Watches https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:04:20.97: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:04:20.97: NetworkMonitor - start process kube event
2025-04-17 02:04:20.97: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10080
2025-04-17 02:04:20.97: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:04:20.97: NetworkMonitor - Connect Kube API result 0
2025-04-17 02:04:20.97: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:04:20.97: NetworkMonitor - Start Watching request https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})(timeout=120)
2025-04-17 02:04:20.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:04:20.97: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:04:20.97: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:04:20.97: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})
2025-04-17 02:04:20.98: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:04:20.98: ServiceMonitor - start process kube event
2025-04-17 02:04:20.98: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10075
2025-04-17 02:04:20.98: ServiceMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:04:20.98: ServiceMonitor - Connect Kube API result 0
2025-04-17 02:04:20.98: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:04:20.98: ServiceMonitor - Start Watching request https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:04:20.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:04:20.99: VncKubernetes - vnc_sync - Service start
2025-04-17 02:04:20.99: VncKubernetes - vnc_sync - Service done
2025-04-17 02:04:20.99: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:04:20.99: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:04:20.99: EndPointMonitor - start process kube event
2025-04-17 02:04:20.99: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10075
2025-04-17 02:04:20.99: EndPointMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:04:20.99: EndPointMonitor - Connect Kube API result 0
2025-04-17 02:04:20.99: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:04:20.99: EndPointMonitor - Start Watching request https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:04:20.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:04:20.99: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:04:20.99: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:04:21.00: ServiceMonitor - Watches https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:04:21.00: EndPointMonitor - Watches https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:04:21.09: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10156 newResVer=10156
2025-04-17 02:04:21.09: NetworkPolicyMonitor - start process kube event
2025-04-17 02:04:21.10: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-17 02:04:21.10: empty line received
2025-04-17 02:04:21.10: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-17 02:04:21.10: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-17 02:04:21.10: NetworkPolicyMonitor - start process kube event
2025-04-17 02:04:21.10: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-17 02:04:21.10: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:04:21.36: NamespaceMonitor - Received BOOKMARK: oldResVer=10218 newResVer=10218
2025-04-17 02:04:21.36: NamespaceMonitor - start process kube event
2025-04-17 02:04:21.36: empty line received
2025-04-17 02:04:21.36: NamespaceMonitor - start process kube event
2025-04-17 02:04:21.60: PodMonitor - Received BOOKMARK: oldResVer=10346 newResVer=10436
2025-04-17 02:04:21.60: PodMonitor - start process kube event
2025-04-17 02:04:21.60: PodMonitor - _schedule_vnc_sync
2025-04-17 02:04:21.60: empty line received
2025-04-17 02:04:21.60: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-17 02:04:21.60: VncKubernetes - vnc_sync - Pod start
2025-04-17 02:04:21.60: VncKubernetes - vnc_sync - Pod done
2025-04-17 02:04:21.60: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:04:21.60: PodMonitor - start process kube event
2025-04-17 02:05:01.44: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:05:01.44: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:05:01.44: PodMonitor - start process kube event
2025-04-17 02:05:01.44: empty line received
2025-04-17 02:05:01.44: PodMonitor - start process kube event
2025-04-17 02:05:14.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:05:14.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:05:14.56: PodMonitor - start process kube event
2025-04-17 02:05:14.56: empty line received
2025-04-17 02:05:14.56: PodMonitor - start process kube event
2025-04-17 02:05:20.53: IngressMonitor - Received BOOKMARK: oldResVer=10075 newResVer=10511
2025-04-17 02:05:20.53: IngressMonitor - start process kube event
2025-04-17 02:05:20.53: empty line received
2025-04-17 02:05:20.53: IngressMonitor - start process kube event
2025-04-17 02:05:21.36: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10156 newResVer=10156
2025-04-17 02:05:21.36: NetworkPolicyMonitor - start process kube event
2025-04-17 02:05:21.36: empty line received
2025-04-17 02:05:21.36: NetworkPolicyMonitor - start process kube event
2025-04-17 02:05:21.57: PodMonitor - Received BOOKMARK: oldResVer=10436 newResVer=10520
2025-04-17 02:05:21.57: PodMonitor - start process kube event
2025-04-17 02:05:21.57: empty line received
2025-04-17 02:05:21.57: PodMonitor - start process kube event
2025-04-17 02:05:22.29: NamespaceMonitor - Received BOOKMARK: oldResVer=10218 newResVer=10218
2025-04-17 02:05:22.29: NamespaceMonitor - start process kube event
2025-04-17 02:05:22.29: empty line received
2025-04-17 02:05:22.29: NamespaceMonitor - start process kube event
2025-04-17 02:06:20.74: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10156 newResVer=10156
2025-04-17 02:06:20.74: NetworkPolicyMonitor - start process kube event
2025-04-17 02:06:20.74: empty line received
2025-04-17 02:06:20.74: NetworkPolicyMonitor - start process kube event
2025-04-17 02:06:20.98: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:06:20.98: NetworkMonitor - start process kube event
2025-04-17 02:06:20.98: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10080
2025-04-17 02:06:20.98: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:06:20.98: NetworkMonitor - Connect Kube API result 0
2025-04-17 02:06:20.98: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:06:20.98: NetworkMonitor - Start Watching request https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})(timeout=120)
2025-04-17 02:06:20.98: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:06:20.98: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:06:20.98: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:06:20.98: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})
2025-04-17 02:06:21.00: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:06:21.00: ServiceMonitor - start process kube event
2025-04-17 02:06:21.00: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10075
2025-04-17 02:06:21.00: ServiceMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:06:21.00: ServiceMonitor - Connect Kube API result 0
2025-04-17 02:06:21.00: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:06:21.00: ServiceMonitor - Start Watching request https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:06:21.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:06:21.00: VncKubernetes - vnc_sync - Service start
2025-04-17 02:06:21.00: VncKubernetes - vnc_sync - Service done
2025-04-17 02:06:21.00: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:06:21.00: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:06:21.00: EndPointMonitor - start process kube event
2025-04-17 02:06:21.00: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10075
2025-04-17 02:06:21.00: EndPointMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:06:21.00: EndPointMonitor - Connect Kube API result 0
2025-04-17 02:06:21.00: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:06:21.00: EndPointMonitor - Start Watching request https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:06:21.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:06:21.00: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:06:21.00: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:06:21.01: ServiceMonitor - Watches https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:06:21.01: EndPointMonitor - Watches https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:06:21.35: IngressMonitor - Received BOOKMARK: oldResVer=10511 newResVer=10511
2025-04-17 02:06:21.35: IngressMonitor - start process kube event
2025-04-17 02:06:21.35: empty line received
2025-04-17 02:06:21.35: IngressMonitor - start process kube event
2025-04-17 02:06:21.79: NamespaceMonitor - Received BOOKMARK: oldResVer=10218 newResVer=10218
2025-04-17 02:06:21.79: NamespaceMonitor - start process kube event
2025-04-17 02:06:21.79: NamespaceMonitor - _schedule_vnc_sync
2025-04-17 02:06:21.79: empty line received
2025-04-17 02:06:21.79: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-17 02:06:21.79: VncKubernetes - vnc_sync - Namespace start
2025-04-17 02:06:21.79: VncKubernetes - vnc_sync - Namespace done
2025-04-17 02:06:21.79: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:06:21.79: NamespaceMonitor - start process kube event
2025-04-17 02:06:22.10: PodMonitor - Received BOOKMARK: oldResVer=10520 newResVer=10520
2025-04-17 02:06:22.10: PodMonitor - start process kube event
2025-04-17 02:06:22.10: empty line received
2025-04-17 02:06:22.10: PodMonitor - start process kube event
2025-04-17 02:06:29.54: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:06:29.54: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:06:29.54: PodMonitor - start process kube event
2025-04-17 02:06:29.54: empty line received
2025-04-17 02:06:29.54: PodMonitor - start process kube event
2025-04-17 02:07:21.02: IngressMonitor - Received BOOKMARK: oldResVer=10511 newResVer=10511
2025-04-17 02:07:21.02: IngressMonitor - start process kube event
2025-04-17 02:07:21.02: empty line received
2025-04-17 02:07:21.02: IngressMonitor - start process kube event
2025-04-17 02:07:21.10: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10156 newResVer=10156
2025-04-17 02:07:21.10: NetworkPolicyMonitor - start process kube event
2025-04-17 02:07:21.10: empty line received
2025-04-17 02:07:21.10: NetworkPolicyMonitor - start process kube event
2025-04-17 02:07:21.41: NamespaceMonitor - Received BOOKMARK: oldResVer=10218 newResVer=10218
2025-04-17 02:07:21.41: NamespaceMonitor - start process kube event
2025-04-17 02:07:21.41: empty line received
2025-04-17 02:07:21.41: NamespaceMonitor - start process kube event
2025-04-17 02:07:21.64: PodMonitor - Received BOOKMARK: oldResVer=10520 newResVer=10632
2025-04-17 02:07:21.64: PodMonitor - start process kube event
2025-04-17 02:07:21.64: empty line received
2025-04-17 02:07:21.64: PodMonitor - start process kube event
2025-04-17 02:07:28.97: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:07:28.97: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:07:28.97: PodMonitor - start process kube event
2025-04-17 02:07:28.97: empty line received
2025-04-17 02:07:28.97: PodMonitor - start process kube event
2025-04-17 02:07:30.01: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:07:30.01: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:07:30.01: PodMonitor - start process kube event
2025-04-17 02:07:30.01: empty line received
2025-04-17 02:07:30.01: PodMonitor - start process kube event
2025-04-17 02:07:43.55: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:07:43.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:07:43.56: PodMonitor - start process kube event
2025-04-17 02:07:43.56: empty line received
2025-04-17 02:07:43.56: PodMonitor - start process kube event
2025-04-17 02:08:20.41: EndPointMonitor - Received BOOKMARK: oldResVer=10075 newResVer=10789
2025-04-17 02:08:20.41: EndPointMonitor - start process kube event
2025-04-17 02:08:20.41: empty line received
2025-04-17 02:08:20.41: EndPointMonitor - start process kube event
2025-04-17 02:08:20.61: IngressMonitor - Received BOOKMARK: oldResVer=10511 newResVer=10511
2025-04-17 02:08:20.61: IngressMonitor - start process kube event
2025-04-17 02:08:20.61: empty line received
2025-04-17 02:08:20.61: IngressMonitor - start process kube event
2025-04-17 02:08:20.98: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:08:20.99: NetworkMonitor - start process kube event
2025-04-17 02:08:20.99: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10080
2025-04-17 02:08:20.99: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:08:20.99: NetworkMonitor - Connect Kube API result 0
2025-04-17 02:08:20.99: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:08:20.99: NetworkMonitor - Start Watching request https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})(timeout=120)
2025-04-17 02:08:20.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:08:20.99: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:08:20.99: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:08:20.99: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})
2025-04-17 02:08:21.01: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:08:21.01: ServiceMonitor - start process kube event
2025-04-17 02:08:21.01: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10075
2025-04-17 02:08:21.01: ServiceMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:08:21.01: ServiceMonitor - Connect Kube API result 0
2025-04-17 02:08:21.01: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:08:21.01: ServiceMonitor - Start Watching request https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})(timeout=120)
2025-04-17 02:08:21.01: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:08:21.01: VncKubernetes - vnc_sync - Service start
2025-04-17 02:08:21.01: VncKubernetes - vnc_sync - Service done
2025-04-17 02:08:21.01: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:08:21.02: ServiceMonitor - Watches https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10075'})
2025-04-17 02:08:21.02: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10156 newResVer=10156
2025-04-17 02:08:21.02: NetworkPolicyMonitor - start process kube event
2025-04-17 02:08:21.02: empty line received
2025-04-17 02:08:21.02: NetworkPolicyMonitor - start process kube event
2025-04-17 02:08:21.46: NamespaceMonitor - Received BOOKMARK: oldResVer=10218 newResVer=10218
2025-04-17 02:08:21.46: NamespaceMonitor - start process kube event
2025-04-17 02:08:21.46: empty line received
2025-04-17 02:08:21.46: NamespaceMonitor - start process kube event
2025-04-17 02:08:21.94: PodMonitor - Received BOOKMARK: oldResVer=10632 newResVer=10742
2025-04-17 02:08:21.94: PodMonitor - start process kube event
2025-04-17 02:08:21.94: PodMonitor - _schedule_vnc_sync
2025-04-17 02:08:21.94: empty line received
2025-04-17 02:08:21.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-17 02:08:21.94: VncKubernetes - vnc_sync - Pod start
2025-04-17 02:08:21.94: VncKubernetes - vnc_sync - Pod done
2025-04-17 02:08:21.94: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:08:21.94: PodMonitor - start process kube event
2025-04-17 02:09:15.51: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:09:15.51: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:09:15.51: PodMonitor - start process kube event
2025-04-17 02:09:15.51: empty line received
2025-04-17 02:09:15.51: PodMonitor - start process kube event
2025-04-17 02:09:20.67: EndPointMonitor - Received BOOKMARK: oldResVer=10789 newResVer=10789
2025-04-17 02:09:20.67: EndPointMonitor - start process kube event
2025-04-17 02:09:20.67: empty line received
2025-04-17 02:09:20.67: EndPointMonitor - start process kube event
2025-04-17 02:09:20.92: ServiceMonitor - Received BOOKMARK: oldResVer=10075 newResVer=10876
2025-04-17 02:09:20.92: ServiceMonitor - start process kube event
2025-04-17 02:09:20.92: empty line received
2025-04-17 02:09:20.92: ServiceMonitor - start process kube event
2025-04-17 02:09:21.00: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10156 newResVer=10156
2025-04-17 02:09:21.00: NetworkPolicyMonitor - start process kube event
2025-04-17 02:09:21.00: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-17 02:09:21.00: empty line received
2025-04-17 02:09:21.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-17 02:09:21.00: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-17 02:09:21.00: NetworkPolicyMonitor - start process kube event
2025-04-17 02:09:21.01: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-17 02:09:21.01: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:09:21.64: IngressMonitor - Received BOOKMARK: oldResVer=10511 newResVer=10511
2025-04-17 02:09:21.64: IngressMonitor - start process kube event
2025-04-17 02:09:21.64: IngressMonitor - _schedule_vnc_sync
2025-04-17 02:09:21.64: empty line received
2025-04-17 02:09:21.64: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-17 02:09:21.64: VncKubernetes - vnc_sync - Ingress start
2025-04-17 02:09:21.64: VncKubernetes - vnc_sync - Ingress done
2025-04-17 02:09:21.64: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:09:21.64: IngressMonitor - start process kube event
2025-04-17 02:09:21.82: PodMonitor - Received BOOKMARK: oldResVer=10742 newResVer=10874
2025-04-17 02:09:21.82: PodMonitor - start process kube event
2025-04-17 02:09:21.82: empty line received
2025-04-17 02:09:21.82: PodMonitor - start process kube event
2025-04-17 02:09:21.86: NamespaceMonitor - Received BOOKMARK: oldResVer=10218 newResVer=10218
2025-04-17 02:09:21.86: NamespaceMonitor - start process kube event
2025-04-17 02:09:21.86: empty line received
2025-04-17 02:09:21.86: NamespaceMonitor - start process kube event
2025-04-17 02:09:28.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:09:28.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:09:28.56: PodMonitor - start process kube event
2025-04-17 02:09:28.56: empty line received
2025-04-17 02:09:28.56: PodMonitor - start process kube event
2025-04-17 02:10:11.93: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:10:11.93: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:10:11.93: PodMonitor - start process kube event
2025-04-17 02:10:11.93: empty line received
2025-04-17 02:10:11.93: PodMonitor - start process kube event
2025-04-17 02:10:21.00: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-17 02:10:21.00: NetworkMonitor - start process kube event
2025-04-17 02:10:21.00: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10080
2025-04-17 02:10:21.00: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:10:21.00: NetworkMonitor - Connect Kube API result 0
2025-04-17 02:10:21.00: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:10:21.00: NetworkMonitor - Start Watching request https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})(timeout=120)
2025-04-17 02:10:21.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:10:21.00: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:10:21.00: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:10:21.00: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10080'})
2025-04-17 02:10:21.14: ServiceMonitor - Received BOOKMARK: oldResVer=10876 newResVer=10876
2025-04-17 02:10:21.14: ServiceMonitor - start process kube event
2025-04-17 02:10:21.14: empty line received
2025-04-17 02:10:21.14: ServiceMonitor - start process kube event
2025-04-17 02:10:21.19: EndPointMonitor - Received BOOKMARK: oldResVer=10789 newResVer=10789
2025-04-17 02:10:21.19: EndPointMonitor - start process kube event
2025-04-17 02:10:21.19: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:10:21.19: empty line received
2025-04-17 02:10:21.19: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:10:21.19: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:10:21.19: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:10:21.19: EndPointMonitor - start process kube event
2025-04-17 02:10:21.62: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10156 newResVer=10156
2025-04-17 02:10:21.62: NetworkPolicyMonitor - start process kube event
2025-04-17 02:10:21.62: empty line received
2025-04-17 02:10:21.62: NetworkPolicyMonitor - start process kube event
2025-04-17 02:10:22.12: NamespaceMonitor - Received BOOKMARK: oldResVer=10218 newResVer=10218
2025-04-17 02:10:22.12: NamespaceMonitor - start process kube event
2025-04-17 02:10:22.12: NamespaceMonitor - _schedule_vnc_sync
2025-04-17 02:10:22.12: empty line received
2025-04-17 02:10:22.12: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-17 02:10:22.12: VncKubernetes - vnc_sync - Namespace start
2025-04-17 02:10:22.12: VncKubernetes - vnc_sync - Namespace done
2025-04-17 02:10:22.12: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:10:22.12: NamespaceMonitor - start process kube event
2025-04-17 02:10:22.40: PodMonitor - Received BOOKMARK: oldResVer=10874 newResVer=10963
2025-04-17 02:10:22.40: PodMonitor - start process kube event
2025-04-17 02:10:22.40: empty line received
2025-04-17 02:10:22.40: PodMonitor - start process kube event
2025-04-17 02:10:22.42: IngressMonitor - Received BOOKMARK: oldResVer=10511 newResVer=10511
2025-04-17 02:10:22.42: IngressMonitor - start process kube event
2025-04-17 02:10:22.42: empty line received
2025-04-17 02:10:22.42: IngressMonitor - start process kube event
2025-04-17 02:11:11.37: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:11:11.37: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:11:11.37: PodMonitor - start process kube event
2025-04-17 02:11:11.37: empty line received
2025-04-17 02:11:11.37: PodMonitor - start process kube event
2025-04-17 02:11:21.20: EndPointMonitor - Received BOOKMARK: oldResVer=10789 newResVer=10789
2025-04-17 02:11:21.20: EndPointMonitor - start process kube event
2025-04-17 02:11:21.20: empty line received
2025-04-17 02:11:21.20: EndPointMonitor - start process kube event
2025-04-17 02:11:21.24: ServiceMonitor - Received BOOKMARK: oldResVer=10876 newResVer=10876
2025-04-17 02:11:21.24: ServiceMonitor - start process kube event
2025-04-17 02:11:21.24: empty line received
2025-04-17 02:11:21.24: ServiceMonitor - start process kube event
2025-04-17 02:11:21.29: NetworkMonitor - Received BOOKMARK: oldResVer=10080 newResVer=11062
2025-04-17 02:11:21.29: NetworkMonitor - start process kube event
2025-04-17 02:11:21.29: empty line received
2025-04-17 02:11:21.29: NetworkMonitor - start process kube event
2025-04-17 02:11:21.46: NamespaceMonitor - Received BOOKMARK: oldResVer=10218 newResVer=10218
2025-04-17 02:11:21.46: NamespaceMonitor - start process kube event
2025-04-17 02:11:21.46: empty line received
2025-04-17 02:11:21.46: NamespaceMonitor - start process kube event
2025-04-17 02:11:21.75: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10156 newResVer=10156
2025-04-17 02:11:21.75: NetworkPolicyMonitor - start process kube event
2025-04-17 02:11:21.75: empty line received
2025-04-17 02:11:21.75: NetworkPolicyMonitor - start process kube event
2025-04-17 02:11:22.23: IngressMonitor - Received BOOKMARK: oldResVer=10511 newResVer=10511
2025-04-17 02:11:22.23: IngressMonitor - start process kube event
2025-04-17 02:11:22.23: empty line received
2025-04-17 02:11:22.23: IngressMonitor - start process kube event
2025-04-17 02:11:22.38: PodMonitor - Received BOOKMARK: oldResVer=10963 newResVer=11051
2025-04-17 02:11:22.38: PodMonitor - start process kube event
2025-04-17 02:11:22.38: empty line received
2025-04-17 02:11:22.38: PodMonitor - start process kube event
2025-04-17 02:11:23.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:11:23.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:11:23.56: PodMonitor - start process kube event
2025-04-17 02:11:23.56: empty line received
2025-04-17 02:11:23.56: PodMonitor - start process kube event
2025-04-17 02:12:20.59: EndPointMonitor - Received BOOKMARK: oldResVer=10789 newResVer=10789
2025-04-17 02:12:20.59: EndPointMonitor - start process kube event
2025-04-17 02:12:20.59: empty line received
2025-04-17 02:12:20.59: EndPointMonitor - start process kube event
2025-04-17 02:12:20.62: ServiceMonitor - Received BOOKMARK: oldResVer=10876 newResVer=10876
2025-04-17 02:12:20.62: ServiceMonitor - start process kube event
2025-04-17 02:12:20.62: empty line received
2025-04-17 02:12:20.62: ServiceMonitor - start process kube event
2025-04-17 02:12:20.99: NetworkMonitor - Received BOOKMARK: oldResVer=11062 newResVer=11062
2025-04-17 02:12:20.99: NetworkMonitor - start process kube event
2025-04-17 02:12:20.99: empty line received
2025-04-17 02:12:20.99: NetworkMonitor - start process kube event
2025-04-17 02:12:21.98: NamespaceMonitor - Received BOOKMARK: oldResVer=10218 newResVer=11130
2025-04-17 02:12:21.98: NamespaceMonitor - start process kube event
2025-04-17 02:12:21.98: empty line received
2025-04-17 02:12:21.98: NamespaceMonitor - start process kube event
2025-04-17 02:12:22.12: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:12:22.22: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10156 newResVer=11066
2025-04-17 02:12:22.22: NetworkPolicyMonitor - start process kube event
2025-04-17 02:12:22.22: empty line received
2025-04-17 02:12:22.22: NetworkPolicyMonitor - start process kube event
2025-04-17 02:12:22.34: IngressMonitor - Received BOOKMARK: oldResVer=10511 newResVer=10511
2025-04-17 02:12:22.34: IngressMonitor - start process kube event
2025-04-17 02:12:22.34: empty line received
2025-04-17 02:12:22.34: IngressMonitor - start process kube event
2025-04-17 02:12:22.47: PodMonitor - Received BOOKMARK: oldResVer=11051 newResVer=11069
2025-04-17 02:12:22.47: PodMonitor - start process kube event
2025-04-17 02:12:22.47: PodMonitor - _schedule_vnc_sync
2025-04-17 02:12:22.47: empty line received
2025-04-17 02:12:22.47: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-17 02:12:22.47: VncKubernetes - vnc_sync - Pod start
2025-04-17 02:12:22.47: VncKubernetes - vnc_sync - Pod done
2025-04-17 02:12:22.47: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:12:22.47: PodMonitor - start process kube event
2025-04-17 02:13:20.48: ServiceMonitor - Received BOOKMARK: oldResVer=10876 newResVer=10876
2025-04-17 02:13:20.48: ServiceMonitor - start process kube event
2025-04-17 02:13:20.48: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:13:20.48: empty line received
2025-04-17 02:13:20.48: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:13:20.48: VncKubernetes - vnc_sync - Service start
2025-04-17 02:13:20.48: VncKubernetes - vnc_sync - Service done
2025-04-17 02:13:20.48: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:13:20.48: ServiceMonitor - start process kube event
2025-04-17 02:13:20.62: EndPointMonitor - Received BOOKMARK: oldResVer=10789 newResVer=10789
2025-04-17 02:13:20.62: EndPointMonitor - start process kube event
2025-04-17 02:13:20.62: empty line received
2025-04-17 02:13:20.62: EndPointMonitor - start process kube event
2025-04-17 02:13:21.17: NetworkMonitor - Received BOOKMARK: oldResVer=11062 newResVer=11062
2025-04-17 02:13:21.17: NetworkMonitor - start process kube event
2025-04-17 02:13:21.17: empty line received
2025-04-17 02:13:21.17: NetworkMonitor - start process kube event
2025-04-17 02:13:21.92: NamespaceMonitor - Received BOOKMARK: oldResVer=11130 newResVer=11130
2025-04-17 02:13:21.92: NamespaceMonitor - start process kube event
2025-04-17 02:13:21.92: empty line received
2025-04-17 02:13:21.92: NamespaceMonitor - start process kube event
2025-04-17 02:13:21.95: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11066 newResVer=11066
2025-04-17 02:13:21.95: NetworkPolicyMonitor - start process kube event
2025-04-17 02:13:21.95: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-17 02:13:21.95: empty line received
2025-04-17 02:13:21.95: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-17 02:13:21.95: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-17 02:13:21.96: NetworkPolicyMonitor - start process kube event
2025-04-17 02:13:21.96: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-17 02:13:21.96: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:13:22.40: IngressMonitor - Received BOOKMARK: oldResVer=10511 newResVer=10511
2025-04-17 02:13:22.40: IngressMonitor - start process kube event
2025-04-17 02:13:22.40: IngressMonitor - _schedule_vnc_sync
2025-04-17 02:13:22.40: empty line received
2025-04-17 02:13:22.40: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-17 02:13:22.40: VncKubernetes - vnc_sync - Ingress start
2025-04-17 02:13:22.40: VncKubernetes - vnc_sync - Ingress done
2025-04-17 02:13:22.40: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:13:22.40: IngressMonitor - start process kube event
2025-04-17 02:13:22.65: PodMonitor - Received BOOKMARK: oldResVer=11069 newResVer=11069
2025-04-17 02:13:22.65: PodMonitor - start process kube event
2025-04-17 02:13:22.65: empty line received
2025-04-17 02:13:22.65: PodMonitor - start process kube event
2025-04-17 02:14:20.58: EndPointMonitor - Received BOOKMARK: oldResVer=10789 newResVer=10789
2025-04-17 02:14:20.58: EndPointMonitor - start process kube event
2025-04-17 02:14:20.58: empty line received
2025-04-17 02:14:20.58: EndPointMonitor - start process kube event
2025-04-17 02:14:20.96: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:14:20.96: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:14:20.96: PodMonitor - start process kube event
2025-04-17 02:14:20.96: empty line received
2025-04-17 02:14:20.96: PodMonitor - start process kube event
2025-04-17 02:14:21.33: ServiceMonitor - Received BOOKMARK: oldResVer=10876 newResVer=10876
2025-04-17 02:14:21.34: ServiceMonitor - start process kube event
2025-04-17 02:14:21.34: empty line received
2025-04-17 02:14:21.34: ServiceMonitor - start process kube event
2025-04-17 02:14:21.57: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11066 newResVer=11066
2025-04-17 02:14:21.57: NetworkPolicyMonitor - start process kube event
2025-04-17 02:14:21.57: empty line received
2025-04-17 02:14:21.57: NetworkPolicyMonitor - start process kube event
2025-04-17 02:14:21.64: IngressMonitor - Received BOOKMARK: oldResVer=10511 newResVer=10511
2025-04-17 02:14:21.64: IngressMonitor - start process kube event
2025-04-17 02:14:21.64: empty line received
2025-04-17 02:14:21.64: IngressMonitor - start process kube event
2025-04-17 02:14:21.86: NetworkMonitor - Received BOOKMARK: oldResVer=11062 newResVer=11062
2025-04-17 02:14:21.86: NetworkMonitor - start process kube event
2025-04-17 02:14:21.86: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:14:21.86: empty line received
2025-04-17 02:14:21.86: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:14:21.86: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:14:21.86: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:14:21.86: NetworkMonitor - start process kube event
2025-04-17 02:14:22.02: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:14:22.02: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:14:22.02: PodMonitor - start process kube event
2025-04-17 02:14:22.02: empty line received
2025-04-17 02:14:22.02: PodMonitor - start process kube event
2025-04-17 02:14:22.16: NamespaceMonitor - Received BOOKMARK: oldResVer=11130 newResVer=11130
2025-04-17 02:14:22.16: NamespaceMonitor - start process kube event
2025-04-17 02:14:22.16: NamespaceMonitor - _schedule_vnc_sync
2025-04-17 02:14:22.16: empty line received
2025-04-17 02:14:22.16: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-17 02:14:22.16: VncKubernetes - vnc_sync - Namespace start
2025-04-17 02:14:22.16: VncKubernetes - vnc_sync - Namespace done
2025-04-17 02:14:22.16: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:14:22.16: NamespaceMonitor - start process kube event
2025-04-17 02:14:23.20: PodMonitor - Received BOOKMARK: oldResVer=11069 newResVer=11330
2025-04-17 02:14:23.20: PodMonitor - start process kube event
2025-04-17 02:14:23.20: empty line received
2025-04-17 02:14:23.20: PodMonitor - start process kube event
2025-04-17 02:14:33.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:14:33.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:14:33.56: PodMonitor - start process kube event
2025-04-17 02:14:33.56: empty line received
2025-04-17 02:14:33.56: PodMonitor - start process kube event
2025-04-17 02:15:21.17: EndPointMonitor - Received BOOKMARK: oldResVer=10789 newResVer=10789
2025-04-17 02:15:21.17: EndPointMonitor - start process kube event
2025-04-17 02:15:21.17: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:15:21.17: empty line received
2025-04-17 02:15:21.17: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:15:21.17: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:15:21.17: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:15:21.17: EndPointMonitor - start process kube event
2025-04-17 02:15:21.24: ServiceMonitor - Received BOOKMARK: oldResVer=10876 newResVer=10876
2025-04-17 02:15:21.24: ServiceMonitor - start process kube event
2025-04-17 02:15:21.24: empty line received
2025-04-17 02:15:21.24: ServiceMonitor - start process kube event
2025-04-17 02:15:21.61: NetworkMonitor - Received BOOKMARK: oldResVer=11062 newResVer=11062
2025-04-17 02:15:21.61: NetworkMonitor - start process kube event
2025-04-17 02:15:21.61: empty line received
2025-04-17 02:15:21.61: NetworkMonitor - start process kube event
2025-04-17 02:15:22.39: NamespaceMonitor - Received BOOKMARK: oldResVer=11130 newResVer=11130
2025-04-17 02:15:22.39: NamespaceMonitor - start process kube event
2025-04-17 02:15:22.39: empty line received
2025-04-17 02:15:22.39: NamespaceMonitor - start process kube event
2025-04-17 02:15:22.53: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11066 newResVer=11066
2025-04-17 02:15:22.53: NetworkPolicyMonitor - start process kube event
2025-04-17 02:15:22.54: empty line received
2025-04-17 02:15:22.54: NetworkPolicyMonitor - start process kube event
2025-04-17 02:15:22.60: IngressMonitor - Received BOOKMARK: oldResVer=10511 newResVer=10511
2025-04-17 02:15:22.60: IngressMonitor - start process kube event
2025-04-17 02:15:22.60: empty line received
2025-04-17 02:15:22.60: IngressMonitor - start process kube event
2025-04-17 02:15:23.09: PodMonitor - Received BOOKMARK: oldResVer=11330 newResVer=11346
2025-04-17 02:15:23.09: PodMonitor - start process kube event
2025-04-17 02:15:23.09: empty line received
2025-04-17 02:15:23.09: PodMonitor - start process kube event
2025-04-17 02:16:20.93: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:16:20.93: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:16:20.93: PodMonitor - start process kube event
2025-04-17 02:16:20.93: empty line received
2025-04-17 02:16:20.93: PodMonitor - start process kube event
2025-04-17 02:16:20.96: ServiceMonitor - Received BOOKMARK: oldResVer=10876 newResVer=10876
2025-04-17 02:16:20.96: ServiceMonitor - start process kube event
2025-04-17 02:16:20.96: empty line received
2025-04-17 02:16:20.96: ServiceMonitor - start process kube event
2025-04-17 02:16:21.36: EndPointMonitor - Received BOOKMARK: oldResVer=10789 newResVer=10789
2025-04-17 02:16:21.36: EndPointMonitor - start process kube event
2025-04-17 02:16:21.36: empty line received
2025-04-17 02:16:21.36: EndPointMonitor - start process kube event
2025-04-17 02:16:22.00: NetworkMonitor - Received BOOKMARK: oldResVer=11062 newResVer=11062
2025-04-17 02:16:22.00: NetworkMonitor - start process kube event
2025-04-17 02:16:22.00: empty line received
2025-04-17 02:16:22.00: NetworkMonitor - start process kube event
2025-04-17 02:16:22.55: NamespaceMonitor - Received BOOKMARK: oldResVer=11130 newResVer=11130
2025-04-17 02:16:22.55: NamespaceMonitor - start process kube event
2025-04-17 02:16:22.55: empty line received
2025-04-17 02:16:22.55: NamespaceMonitor - start process kube event
2025-04-17 02:16:22.94: PodMonitor - Received BOOKMARK: oldResVer=11346 newResVer=11506
2025-04-17 02:16:22.94: PodMonitor - start process kube event
2025-04-17 02:16:22.94: PodMonitor - _schedule_vnc_sync
2025-04-17 02:16:22.94: empty line received
2025-04-17 02:16:22.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-17 02:16:22.94: VncKubernetes - vnc_sync - Pod start
2025-04-17 02:16:22.94: VncKubernetes - vnc_sync - Pod done
2025-04-17 02:16:22.94: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:16:22.94: PodMonitor - start process kube event
2025-04-17 02:16:23.41: IngressMonitor - Received BOOKMARK: oldResVer=10511 newResVer=11444
2025-04-17 02:16:23.41: IngressMonitor - start process kube event
2025-04-17 02:16:23.41: empty line received
2025-04-17 02:16:23.41: IngressMonitor - start process kube event
2025-04-17 02:16:23.58: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11066 newResVer=11066
2025-04-17 02:16:23.58: NetworkPolicyMonitor - start process kube event
2025-04-17 02:16:23.58: empty line received
2025-04-17 02:16:23.58: NetworkPolicyMonitor - start process kube event
2025-04-17 02:17:20.54: ServiceMonitor - Received BOOKMARK: oldResVer=10876 newResVer=10876
2025-04-17 02:17:20.54: ServiceMonitor - start process kube event
2025-04-17 02:17:20.54: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:17:20.54: empty line received
2025-04-17 02:17:20.54: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:17:20.54: VncKubernetes - vnc_sync - Service start
2025-04-17 02:17:20.54: VncKubernetes - vnc_sync - Service done
2025-04-17 02:17:20.54: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:17:20.54: ServiceMonitor - start process kube event
2025-04-17 02:17:21.42: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:17:21.42: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:17:21.42: PodMonitor - start process kube event
2025-04-17 02:17:21.42: empty line received
2025-04-17 02:17:21.42: PodMonitor - start process kube event
2025-04-17 02:17:21.61: EndPointMonitor - Received BOOKMARK: oldResVer=10789 newResVer=10789
2025-04-17 02:17:21.61: EndPointMonitor - start process kube event
2025-04-17 02:17:21.61: empty line received
2025-04-17 02:17:21.61: EndPointMonitor - start process kube event
2025-04-17 02:17:22.23: NetworkMonitor - Received BOOKMARK: oldResVer=11062 newResVer=11062
2025-04-17 02:17:22.23: NetworkMonitor - start process kube event
2025-04-17 02:17:22.23: empty line received
2025-04-17 02:17:22.23: NetworkMonitor - start process kube event
2025-04-17 02:17:22.45: PodMonitor - Received BOOKMARK: oldResVer=11506 newResVer=11591
2025-04-17 02:17:22.45: PodMonitor - start process kube event
2025-04-17 02:17:22.45: empty line received
2025-04-17 02:17:22.46: PodMonitor - start process kube event
2025-04-17 02:17:23.32: IngressMonitor - Received BOOKMARK: oldResVer=11444 newResVer=11444
2025-04-17 02:17:23.32: IngressMonitor - start process kube event
2025-04-17 02:17:23.32: IngressMonitor - _schedule_vnc_sync
2025-04-17 02:17:23.32: empty line received
2025-04-17 02:17:23.32: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-17 02:17:23.32: VncKubernetes - vnc_sync - Ingress start
2025-04-17 02:17:23.32: VncKubernetes - vnc_sync - Ingress done
2025-04-17 02:17:23.32: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:17:23.32: IngressMonitor - start process kube event
2025-04-17 02:17:23.43: NamespaceMonitor - Received BOOKMARK: oldResVer=11130 newResVer=11130
2025-04-17 02:17:23.43: NamespaceMonitor - start process kube event
2025-04-17 02:17:23.43: empty line received
2025-04-17 02:17:23.43: NamespaceMonitor - start process kube event
2025-04-17 02:17:24.53: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11066 newResVer=11066
2025-04-17 02:17:24.53: NetworkPolicyMonitor - start process kube event
2025-04-17 02:17:24.53: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-17 02:17:24.53: empty line received
2025-04-17 02:17:24.53: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-17 02:17:24.53: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-17 02:17:24.53: NetworkPolicyMonitor - start process kube event
2025-04-17 02:17:24.53: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-17 02:17:24.53: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:17:34.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:17:34.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:17:34.56: PodMonitor - start process kube event
2025-04-17 02:17:34.56: empty line received
2025-04-17 02:17:34.56: PodMonitor - start process kube event
2025-04-17 02:18:21.41: ServiceMonitor - Received BOOKMARK: oldResVer=10876 newResVer=10876
2025-04-17 02:18:21.41: ServiceMonitor - start process kube event
2025-04-17 02:18:21.41: empty line received
2025-04-17 02:18:21.41: ServiceMonitor - start process kube event
2025-04-17 02:18:21.97: NetworkMonitor - Received BOOKMARK: oldResVer=11062 newResVer=11062
2025-04-17 02:18:21.97: NetworkMonitor - start process kube event
2025-04-17 02:18:21.97: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:18:21.97: empty line received
2025-04-17 02:18:21.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:18:21.97: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:18:21.97: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:18:21.97: NetworkMonitor - start process kube event
2025-04-17 02:18:22.47: EndPointMonitor - Received BOOKMARK: oldResVer=10789 newResVer=10789
2025-04-17 02:18:22.47: EndPointMonitor - start process kube event
2025-04-17 02:18:22.47: empty line received
2025-04-17 02:18:22.47: EndPointMonitor - start process kube event
2025-04-17 02:18:22.65: IngressMonitor - Received BOOKMARK: oldResVer=11444 newResVer=11444
2025-04-17 02:18:22.65: IngressMonitor - start process kube event
2025-04-17 02:18:22.65: empty line received
2025-04-17 02:18:22.65: IngressMonitor - start process kube event
2025-04-17 02:18:23.34: NamespaceMonitor - Received BOOKMARK: oldResVer=11130 newResVer=11130
2025-04-17 02:18:23.34: NamespaceMonitor - start process kube event
2025-04-17 02:18:23.34: NamespaceMonitor - _schedule_vnc_sync
2025-04-17 02:18:23.34: empty line received
2025-04-17 02:18:23.34: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-17 02:18:23.34: VncKubernetes - vnc_sync - Namespace start
2025-04-17 02:18:23.34: VncKubernetes - vnc_sync - Namespace done
2025-04-17 02:18:23.34: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:18:23.34: NamespaceMonitor - start process kube event
2025-04-17 02:18:23.54: PodMonitor - Received BOOKMARK: oldResVer=11591 newResVer=11610
2025-04-17 02:18:23.54: PodMonitor - start process kube event
2025-04-17 02:18:23.54: empty line received
2025-04-17 02:18:23.54: PodMonitor - start process kube event
2025-04-17 02:18:25.33: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11066 newResVer=11066
2025-04-17 02:18:25.33: NetworkPolicyMonitor - start process kube event
2025-04-17 02:18:25.33: empty line received
2025-04-17 02:18:25.33: NetworkPolicyMonitor - start process kube event
2025-04-17 02:19:22.28: ServiceMonitor - Received BOOKMARK: oldResVer=10876 newResVer=11752
2025-04-17 02:19:22.28: ServiceMonitor - start process kube event
2025-04-17 02:19:22.28: empty line received
2025-04-17 02:19:22.28: ServiceMonitor - start process kube event
2025-04-17 02:19:22.39: EndPointMonitor - Received BOOKMARK: oldResVer=10789 newResVer=11739
2025-04-17 02:19:22.39: EndPointMonitor - start process kube event
2025-04-17 02:19:22.39: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:19:22.39: empty line received
2025-04-17 02:19:22.39: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:19:22.39: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:19:22.39: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:19:22.39: EndPointMonitor - start process kube event
2025-04-17 02:19:22.58: NetworkMonitor - Received BOOKMARK: oldResVer=11062 newResVer=11062
2025-04-17 02:19:22.58: NetworkMonitor - start process kube event
2025-04-17 02:19:22.58: empty line received
2025-04-17 02:19:22.58: NetworkMonitor - start process kube event
2025-04-17 02:19:23.12: IngressMonitor - Received BOOKMARK: oldResVer=11444 newResVer=11444
2025-04-17 02:19:23.12: IngressMonitor - start process kube event
2025-04-17 02:19:23.12: empty line received
2025-04-17 02:19:23.12: IngressMonitor - start process kube event
2025-04-17 02:19:23.54: NamespaceMonitor - Received BOOKMARK: oldResVer=11130 newResVer=11130
2025-04-17 02:19:23.54: NamespaceMonitor - start process kube event
2025-04-17 02:19:23.54: empty line received
2025-04-17 02:19:23.54: NamespaceMonitor - start process kube event
2025-04-17 02:19:23.64: PodMonitor - Received BOOKMARK: oldResVer=11610 newResVer=11610
2025-04-17 02:19:23.64: PodMonitor - start process kube event
2025-04-17 02:19:23.64: empty line received
2025-04-17 02:19:23.64: PodMonitor - start process kube event
2025-04-17 02:19:24.98: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11066 newResVer=11066
2025-04-17 02:19:24.98: NetworkPolicyMonitor - start process kube event
2025-04-17 02:19:24.98: empty line received
2025-04-17 02:19:24.98: NetworkPolicyMonitor - start process kube event
2025-04-17 02:19:31.45: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:19:31.46: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:19:31.46: PodMonitor - start process kube event
2025-04-17 02:19:31.46: empty line received
2025-04-17 02:19:31.46: PodMonitor - start process kube event
2025-04-17 02:19:46.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:19:46.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:19:46.56: PodMonitor - start process kube event
2025-04-17 02:19:46.56: empty line received
2025-04-17 02:19:46.56: PodMonitor - start process kube event
2025-04-17 02:20:21.72: ServiceMonitor - Received BOOKMARK: oldResVer=11752 newResVer=11752
2025-04-17 02:20:21.72: ServiceMonitor - start process kube event
2025-04-17 02:20:21.72: empty line received
2025-04-17 02:20:21.72: ServiceMonitor - start process kube event
2025-04-17 02:20:21.91: NetworkMonitor - Received BOOKMARK: oldResVer=11062 newResVer=11062
2025-04-17 02:20:21.91: NetworkMonitor - start process kube event
2025-04-17 02:20:21.91: empty line received
2025-04-17 02:20:21.91: NetworkMonitor - start process kube event
2025-04-17 02:20:22.73: EndPointMonitor - Received BOOKMARK: oldResVer=11739 newResVer=11739
2025-04-17 02:20:22.73: EndPointMonitor - start process kube event
2025-04-17 02:20:22.73: empty line received
2025-04-17 02:20:22.73: EndPointMonitor - start process kube event
2025-04-17 02:20:22.95: IngressMonitor - Received BOOKMARK: oldResVer=11444 newResVer=11444
2025-04-17 02:20:22.95: IngressMonitor - start process kube event
2025-04-17 02:20:22.95: empty line received
2025-04-17 02:20:22.95: IngressMonitor - start process kube event
2025-04-17 02:20:23.40: PodMonitor - Received BOOKMARK: oldResVer=11610 newResVer=11797
2025-04-17 02:20:23.40: PodMonitor - start process kube event
2025-04-17 02:20:23.40: PodMonitor - _schedule_vnc_sync
2025-04-17 02:20:23.40: empty line received
2025-04-17 02:20:23.40: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-17 02:20:23.40: VncKubernetes - vnc_sync - Pod start
2025-04-17 02:20:23.40: VncKubernetes - vnc_sync - Pod done
2025-04-17 02:20:23.40: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:20:23.40: PodMonitor - start process kube event
2025-04-17 02:20:23.45: NamespaceMonitor - Received BOOKMARK: oldResVer=11130 newResVer=11130
2025-04-17 02:20:23.45: NamespaceMonitor - start process kube event
2025-04-17 02:20:23.45: empty line received
2025-04-17 02:20:23.45: NamespaceMonitor - start process kube event
2025-04-17 02:20:24.93: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11066 newResVer=11066
2025-04-17 02:20:24.93: NetworkPolicyMonitor - start process kube event
2025-04-17 02:20:24.93: empty line received
2025-04-17 02:20:24.93: NetworkPolicyMonitor - start process kube event
2025-04-17 02:21:21.69: ServiceMonitor - Received BOOKMARK: oldResVer=11752 newResVer=11752
2025-04-17 02:21:21.69: ServiceMonitor - start process kube event
2025-04-17 02:21:21.69: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:21:21.69: empty line received
2025-04-17 02:21:21.69: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:21:21.69: VncKubernetes - vnc_sync - Service start
2025-04-17 02:21:21.69: VncKubernetes - vnc_sync - Service done
2025-04-17 02:21:21.69: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:21:21.69: ServiceMonitor - start process kube event
2025-04-17 02:21:22.91: NetworkMonitor - Received BOOKMARK: oldResVer=11062 newResVer=11062
2025-04-17 02:21:22.91: NetworkMonitor - start process kube event
2025-04-17 02:21:22.91: empty line received
2025-04-17 02:21:22.91: NetworkMonitor - start process kube event
2025-04-17 02:21:23.11: IngressMonitor - Received BOOKMARK: oldResVer=11444 newResVer=11444
2025-04-17 02:21:23.11: IngressMonitor - start process kube event
2025-04-17 02:21:23.11: empty line received
2025-04-17 02:21:23.11: IngressMonitor - start process kube event
2025-04-17 02:21:23.33: NamespaceMonitor - Received BOOKMARK: oldResVer=11130 newResVer=11130
2025-04-17 02:21:23.33: NamespaceMonitor - start process kube event
2025-04-17 02:21:23.33: empty line received
2025-04-17 02:21:23.33: NamespaceMonitor - start process kube event
2025-04-17 02:21:23.41: EndPointMonitor - Received BOOKMARK: oldResVer=11739 newResVer=11739
2025-04-17 02:21:23.41: EndPointMonitor - start process kube event
2025-04-17 02:21:23.41: empty line received
2025-04-17 02:21:23.41: EndPointMonitor - start process kube event
2025-04-17 02:21:24.34: PodMonitor - Received BOOKMARK: oldResVer=11797 newResVer=11797
2025-04-17 02:21:24.34: PodMonitor - start process kube event
2025-04-17 02:21:24.34: empty line received
2025-04-17 02:21:24.34: PodMonitor - start process kube event
2025-04-17 02:21:24.82: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11066 newResVer=11066
2025-04-17 02:21:24.82: NetworkPolicyMonitor - start process kube event
2025-04-17 02:21:24.82: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-17 02:21:24.82: empty line received
2025-04-17 02:21:24.82: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-17 02:21:24.82: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-17 02:21:24.82: NetworkPolicyMonitor - start process kube event
2025-04-17 02:21:24.82: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-17 02:21:24.82: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:22:21.40: ServiceMonitor - Received BOOKMARK: oldResVer=11752 newResVer=11752
2025-04-17 02:22:21.40: ServiceMonitor - start process kube event
2025-04-17 02:22:21.40: empty line received
2025-04-17 02:22:21.40: ServiceMonitor - start process kube event
2025-04-17 02:22:22.04: NetworkMonitor - Received BOOKMARK: oldResVer=11062 newResVer=12005
2025-04-17 02:22:22.04: NetworkMonitor - start process kube event
2025-04-17 02:22:22.05: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:22:22.05: empty line received
2025-04-17 02:22:22.05: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:22:22.05: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:22:22.05: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:22:22.05: NetworkMonitor - start process kube event
2025-04-17 02:22:23.43: NamespaceMonitor - Received BOOKMARK: oldResVer=11130 newResVer=12014
2025-04-17 02:22:23.43: NamespaceMonitor - start process kube event
2025-04-17 02:22:23.43: NamespaceMonitor - _schedule_vnc_sync
2025-04-17 02:22:23.43: empty line received
2025-04-17 02:22:23.43: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-17 02:22:23.43: VncKubernetes - vnc_sync - Namespace start
2025-04-17 02:22:23.43: VncKubernetes - vnc_sync - Namespace done
2025-04-17 02:22:23.43: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:22:23.43: NamespaceMonitor - start process kube event
2025-04-17 02:22:23.55: IngressMonitor - Received BOOKMARK: oldResVer=11444 newResVer=11444
2025-04-17 02:22:23.55: IngressMonitor - start process kube event
2025-04-17 02:22:23.55: IngressMonitor - _schedule_vnc_sync
2025-04-17 02:22:23.55: empty line received
2025-04-17 02:22:23.55: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-17 02:22:23.55: VncKubernetes - vnc_sync - Ingress start
2025-04-17 02:22:23.55: VncKubernetes - vnc_sync - Ingress done
2025-04-17 02:22:23.55: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:22:23.55: IngressMonitor - start process kube event
2025-04-17 02:22:24.06: PodMonitor - Received BOOKMARK: oldResVer=11797 newResVer=11797
2025-04-17 02:22:24.06: PodMonitor - start process kube event
2025-04-17 02:22:24.06: empty line received
2025-04-17 02:22:24.06: PodMonitor - start process kube event
2025-04-17 02:22:24.20: EndPointMonitor - Received BOOKMARK: oldResVer=11739 newResVer=11739
2025-04-17 02:22:24.20: EndPointMonitor - start process kube event
2025-04-17 02:22:24.20: empty line received
2025-04-17 02:22:24.20: EndPointMonitor - start process kube event
2025-04-17 02:22:24.58: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11066 newResVer=11946
2025-04-17 02:22:24.59: NetworkPolicyMonitor - start process kube event
2025-04-17 02:22:24.59: empty line received
2025-04-17 02:22:24.59: NetworkPolicyMonitor - start process kube event
2025-04-17 02:22:26.77: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:22:26.77: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:22:26.77: PodMonitor - start process kube event
2025-04-17 02:22:26.77: empty line received
2025-04-17 02:22:26.77: PodMonitor - start process kube event
2025-04-17 02:23:21.78: ServiceMonitor - Received BOOKMARK: oldResVer=11752 newResVer=11752
2025-04-17 02:23:21.78: ServiceMonitor - start process kube event
2025-04-17 02:23:21.78: empty line received
2025-04-17 02:23:21.78: ServiceMonitor - start process kube event
2025-04-17 02:23:22.13: NetworkMonitor - Received BOOKMARK: oldResVer=12005 newResVer=12005
2025-04-17 02:23:22.13: NetworkMonitor - start process kube event
2025-04-17 02:23:22.13: empty line received
2025-04-17 02:23:22.13: NetworkMonitor - start process kube event
2025-04-17 02:23:23.39: PodMonitor - Received BOOKMARK: oldResVer=11797 newResVer=12022
2025-04-17 02:23:23.39: PodMonitor - start process kube event
2025-04-17 02:23:23.39: empty line received
2025-04-17 02:23:23.39: PodMonitor - start process kube event
2025-04-17 02:23:23.42: NamespaceMonitor - Received BOOKMARK: oldResVer=12014 newResVer=12014
2025-04-17 02:23:23.42: NamespaceMonitor - start process kube event
2025-04-17 02:23:23.42: empty line received
2025-04-17 02:23:23.42: NamespaceMonitor - start process kube event
2025-04-17 02:23:24.15: EndPointMonitor - Received BOOKMARK: oldResVer=11739 newResVer=11739
2025-04-17 02:23:24.15: EndPointMonitor - start process kube event
2025-04-17 02:23:24.15: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:23:24.15: empty line received
2025-04-17 02:23:24.15: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:23:24.15: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:23:24.15: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:23:24.15: EndPointMonitor - start process kube event
2025-04-17 02:23:24.42: IngressMonitor - Received BOOKMARK: oldResVer=11444 newResVer=11444
2025-04-17 02:23:24.42: IngressMonitor - start process kube event
2025-04-17 02:23:24.42: empty line received
2025-04-17 02:23:24.42: IngressMonitor - start process kube event
2025-04-17 02:23:24.62: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11946 newResVer=11946
2025-04-17 02:23:24.62: NetworkPolicyMonitor - start process kube event
2025-04-17 02:23:24.62: empty line received
2025-04-17 02:23:24.62: NetworkPolicyMonitor - start process kube event
2025-04-17 02:23:27.24: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:23:27.24: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:23:27.24: PodMonitor - start process kube event
2025-04-17 02:23:27.24: empty line received
2025-04-17 02:23:27.24: PodMonitor - start process kube event
2025-04-17 02:23:41.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:23:41.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:23:41.56: PodMonitor - start process kube event
2025-04-17 02:23:41.56: empty line received
2025-04-17 02:23:41.56: PodMonitor - start process kube event
2025-04-17 02:24:22.40: NetworkMonitor - Received BOOKMARK: oldResVer=12005 newResVer=12005
2025-04-17 02:24:22.40: NetworkMonitor - start process kube event
2025-04-17 02:24:22.40: empty line received
2025-04-17 02:24:22.40: NetworkMonitor - start process kube event
2025-04-17 02:24:22.45: ServiceMonitor - Received BOOKMARK: oldResVer=11752 newResVer=11752
2025-04-17 02:24:22.45: ServiceMonitor - start process kube event
2025-04-17 02:24:22.45: empty line received
2025-04-17 02:24:22.45: ServiceMonitor - start process kube event
2025-04-17 02:24:23.89: PodMonitor - Received BOOKMARK: oldResVer=12022 newResVer=12130
2025-04-17 02:24:23.89: PodMonitor - start process kube event
2025-04-17 02:24:23.89: PodMonitor - _schedule_vnc_sync
2025-04-17 02:24:23.89: empty line received
2025-04-17 02:24:23.89: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-17 02:24:23.89: VncKubernetes - vnc_sync - Pod start
2025-04-17 02:24:23.89: VncKubernetes - vnc_sync - Pod done
2025-04-17 02:24:23.89: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:24:23.89: PodMonitor - start process kube event
2025-04-17 02:24:23.98: NamespaceMonitor - Received BOOKMARK: oldResVer=12014 newResVer=12014
2025-04-17 02:24:23.99: NamespaceMonitor - start process kube event
2025-04-17 02:24:23.99: empty line received
2025-04-17 02:24:23.99: NamespaceMonitor - start process kube event
2025-04-17 02:24:24.01: IngressMonitor - Received BOOKMARK: oldResVer=11444 newResVer=11444
2025-04-17 02:24:24.01: IngressMonitor - start process kube event
2025-04-17 02:24:24.01: empty line received
2025-04-17 02:24:24.01: IngressMonitor - start process kube event
2025-04-17 02:24:24.34: EndPointMonitor - Received BOOKMARK: oldResVer=11739 newResVer=11739
2025-04-17 02:24:24.34: EndPointMonitor - start process kube event
2025-04-17 02:24:24.34: empty line received
2025-04-17 02:24:24.34: EndPointMonitor - start process kube event
2025-04-17 02:24:25.14: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11946 newResVer=11946
2025-04-17 02:24:25.14: NetworkPolicyMonitor - start process kube event
2025-04-17 02:24:25.14: empty line received
2025-04-17 02:24:25.14: NetworkPolicyMonitor - start process kube event
2025-04-17 02:24:37.22: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:24:37.22: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:24:37.22: PodMonitor - start process kube event
2025-04-17 02:24:37.23: empty line received
2025-04-17 02:24:37.23: PodMonitor - start process kube event
2025-04-17 02:24:38.26: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:24:38.26: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:24:38.26: PodMonitor - start process kube event
2025-04-17 02:24:38.26: empty line received
2025-04-17 02:24:38.26: PodMonitor - start process kube event
2025-04-17 02:24:50.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:24:50.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:24:50.56: PodMonitor - start process kube event
2025-04-17 02:24:50.56: empty line received
2025-04-17 02:24:50.56: PodMonitor - start process kube event
2025-04-17 02:25:22.50: ServiceMonitor - Received BOOKMARK: oldResVer=11752 newResVer=11752
2025-04-17 02:25:22.50: ServiceMonitor - start process kube event
2025-04-17 02:25:22.50: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:25:22.50: empty line received
2025-04-17 02:25:22.50: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:25:22.50: VncKubernetes - vnc_sync - Service start
2025-04-17 02:25:22.50: VncKubernetes - vnc_sync - Service done
2025-04-17 02:25:22.50: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:25:22.50: ServiceMonitor - start process kube event
2025-04-17 02:25:23.10: NetworkMonitor - Received BOOKMARK: oldResVer=12005 newResVer=12005
2025-04-17 02:25:23.10: NetworkMonitor - start process kube event
2025-04-17 02:25:23.10: empty line received
2025-04-17 02:25:23.10: NetworkMonitor - start process kube event
2025-04-17 02:25:23.50: NamespaceMonitor - Received BOOKMARK: oldResVer=12014 newResVer=12014
2025-04-17 02:25:23.50: NamespaceMonitor - start process kube event
2025-04-17 02:25:23.50: empty line received
2025-04-17 02:25:23.50: NamespaceMonitor - start process kube event
2025-04-17 02:25:23.66: EndPointMonitor - Received BOOKMARK: oldResVer=11739 newResVer=11739
2025-04-17 02:25:23.66: EndPointMonitor - start process kube event
2025-04-17 02:25:23.66: empty line received
2025-04-17 02:25:23.66: EndPointMonitor - start process kube event
2025-04-17 02:25:23.76: PodMonitor - Received BOOKMARK: oldResVer=12130 newResVer=12230
2025-04-17 02:25:23.76: PodMonitor - start process kube event
2025-04-17 02:25:23.76: empty line received
2025-04-17 02:25:23.76: PodMonitor - start process kube event
2025-04-17 02:25:23.81: IngressMonitor - Received BOOKMARK: oldResVer=11444 newResVer=11444
2025-04-17 02:25:23.81: IngressMonitor - start process kube event
2025-04-17 02:25:23.81: empty line received
2025-04-17 02:25:23.81: IngressMonitor - start process kube event
2025-04-17 02:25:25.49: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11946 newResVer=11946
2025-04-17 02:25:25.49: NetworkPolicyMonitor - start process kube event
2025-04-17 02:25:25.49: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-17 02:25:25.49: empty line received
2025-04-17 02:25:25.49: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-17 02:25:25.49: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-17 02:25:25.49: NetworkPolicyMonitor - start process kube event
2025-04-17 02:25:25.50: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-17 02:25:25.50: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:26:23.40: EndPointMonitor - Received BOOKMARK: oldResVer=11739 newResVer=11739
2025-04-17 02:26:23.40: EndPointMonitor - start process kube event
2025-04-17 02:26:23.40: empty line received
2025-04-17 02:26:23.40: EndPointMonitor - start process kube event
2025-04-17 02:26:23.42: ServiceMonitor - Received BOOKMARK: oldResVer=11752 newResVer=11752
2025-04-17 02:26:23.42: ServiceMonitor - start process kube event
2025-04-17 02:26:23.42: empty line received
2025-04-17 02:26:23.42: ServiceMonitor - start process kube event
2025-04-17 02:26:23.44: NetworkMonitor - Received BOOKMARK: oldResVer=12005 newResVer=12005
2025-04-17 02:26:23.44: NetworkMonitor - start process kube event
2025-04-17 02:26:23.44: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:26:23.44: empty line received
2025-04-17 02:26:23.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:26:23.44: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:26:23.44: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:26:23.44: NetworkMonitor - start process kube event
2025-04-17 02:26:23.66: NamespaceMonitor - Received BOOKMARK: oldResVer=12014 newResVer=12014
2025-04-17 02:26:23.66: NamespaceMonitor - start process kube event
2025-04-17 02:26:23.66: NamespaceMonitor - _schedule_vnc_sync
2025-04-17 02:26:23.66: empty line received
2025-04-17 02:26:23.66: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-17 02:26:23.66: VncKubernetes - vnc_sync - Namespace start
2025-04-17 02:26:23.66: VncKubernetes - vnc_sync - Namespace done
2025-04-17 02:26:23.66: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:26:23.66: NamespaceMonitor - start process kube event
2025-04-17 02:26:23.98: IngressMonitor - Received BOOKMARK: oldResVer=11444 newResVer=12343
2025-04-17 02:26:23.98: IngressMonitor - start process kube event
2025-04-17 02:26:23.98: IngressMonitor - _schedule_vnc_sync
2025-04-17 02:26:23.98: empty line received
2025-04-17 02:26:23.98: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-17 02:26:23.98: VncKubernetes - vnc_sync - Ingress start
2025-04-17 02:26:23.98: VncKubernetes - vnc_sync - Ingress done
2025-04-17 02:26:23.98: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:26:23.98: IngressMonitor - start process kube event
2025-04-17 02:26:24.10: PodMonitor - Received BOOKMARK: oldResVer=12230 newResVer=12230
2025-04-17 02:26:24.10: PodMonitor - start process kube event
2025-04-17 02:26:24.10: empty line received
2025-04-17 02:26:24.10: PodMonitor - start process kube event
2025-04-17 02:26:26.30: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11946 newResVer=11946
2025-04-17 02:26:26.30: NetworkPolicyMonitor - start process kube event
2025-04-17 02:26:26.30: empty line received
2025-04-17 02:26:26.30: NetworkPolicyMonitor - start process kube event
2025-04-17 02:27:23.00: NetworkMonitor - Received BOOKMARK: oldResVer=12005 newResVer=12005
2025-04-17 02:27:23.00: NetworkMonitor - start process kube event
2025-04-17 02:27:23.00: empty line received
2025-04-17 02:27:23.00: NetworkMonitor - start process kube event
2025-04-17 02:27:23.40: PodMonitor - Received BOOKMARK: oldResVer=12230 newResVer=12230
2025-04-17 02:27:23.40: PodMonitor - start process kube event
2025-04-17 02:27:23.40: empty line received
2025-04-17 02:27:23.40: PodMonitor - start process kube event
2025-04-17 02:27:23.54: ServiceMonitor - Received BOOKMARK: oldResVer=11752 newResVer=11752
2025-04-17 02:27:23.54: ServiceMonitor - start process kube event
2025-04-17 02:27:23.54: empty line received
2025-04-17 02:27:23.54: ServiceMonitor - start process kube event
2025-04-17 02:27:23.61: EndPointMonitor - Received BOOKMARK: oldResVer=11739 newResVer=11739
2025-04-17 02:27:23.61: EndPointMonitor - start process kube event
2025-04-17 02:27:23.61: empty line received
2025-04-17 02:27:23.61: EndPointMonitor - start process kube event
2025-04-17 02:27:23.80: NamespaceMonitor - Received BOOKMARK: oldResVer=12014 newResVer=12014
2025-04-17 02:27:23.80: NamespaceMonitor - start process kube event
2025-04-17 02:27:23.80: empty line received
2025-04-17 02:27:23.80: NamespaceMonitor - start process kube event
2025-04-17 02:27:24.60: IngressMonitor - Received BOOKMARK: oldResVer=12343 newResVer=12343
2025-04-17 02:27:24.60: IngressMonitor - start process kube event
2025-04-17 02:27:24.60: empty line received
2025-04-17 02:27:24.60: IngressMonitor - start process kube event
2025-04-17 02:27:25.92: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11946 newResVer=11946
2025-04-17 02:27:25.93: NetworkPolicyMonitor - start process kube event
2025-04-17 02:27:25.93: empty line received
2025-04-17 02:27:25.93: NetworkPolicyMonitor - start process kube event
2025-04-17 02:28:23.06: NetworkMonitor - Received BOOKMARK: oldResVer=12005 newResVer=12005
2025-04-17 02:28:23.06: NetworkMonitor - start process kube event
2025-04-17 02:28:23.06: empty line received
2025-04-17 02:28:23.06: NetworkMonitor - start process kube event
2025-04-17 02:28:23.47: EndPointMonitor - Received BOOKMARK: oldResVer=11739 newResVer=11739
2025-04-17 02:28:23.47: EndPointMonitor - start process kube event
2025-04-17 02:28:23.47: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:28:23.47: empty line received
2025-04-17 02:28:23.47: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:28:23.47: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:28:23.47: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:28:23.47: EndPointMonitor - start process kube event
2025-04-17 02:28:23.88: ServiceMonitor - Received BOOKMARK: oldResVer=11752 newResVer=11752
2025-04-17 02:28:23.88: ServiceMonitor - start process kube event
2025-04-17 02:28:23.88: empty line received
2025-04-17 02:28:23.88: ServiceMonitor - start process kube event
2025-04-17 02:28:23.92: PodMonitor - Received BOOKMARK: oldResVer=12230 newResVer=12230
2025-04-17 02:28:23.92: PodMonitor - start process kube event
2025-04-17 02:28:23.92: PodMonitor - _schedule_vnc_sync
2025-04-17 02:28:23.92: empty line received
2025-04-17 02:28:23.92: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-17 02:28:23.92: VncKubernetes - vnc_sync - Pod start
2025-04-17 02:28:23.92: VncKubernetes - vnc_sync - Pod done
2025-04-17 02:28:23.92: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:28:23.92: PodMonitor - start process kube event
2025-04-17 02:28:24.13: NamespaceMonitor - Received BOOKMARK: oldResVer=12014 newResVer=12014
2025-04-17 02:28:24.13: NamespaceMonitor - start process kube event
2025-04-17 02:28:24.13: empty line received
2025-04-17 02:28:24.13: NamespaceMonitor - start process kube event
2025-04-17 02:28:25.43: IngressMonitor - Received BOOKMARK: oldResVer=12343 newResVer=12343
2025-04-17 02:28:25.43: IngressMonitor - start process kube event
2025-04-17 02:28:25.43: empty line received
2025-04-17 02:28:25.43: IngressMonitor - start process kube event
2025-04-17 02:28:25.50: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11946 newResVer=11946
2025-04-17 02:28:25.50: NetworkPolicyMonitor - start process kube event
2025-04-17 02:28:25.50: empty line received
2025-04-17 02:28:25.50: NetworkPolicyMonitor - start process kube event
2025-04-17 02:28:27.39: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:28:27.39: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:28:27.39: PodMonitor - start process kube event
2025-04-17 02:28:27.39: empty line received
2025-04-17 02:28:27.39: PodMonitor - start process kube event
2025-04-17 02:29:23.34: NamespaceMonitor - Received BOOKMARK: oldResVer=12014 newResVer=12014
2025-04-17 02:29:23.34: NamespaceMonitor - start process kube event
2025-04-17 02:29:23.34: empty line received
2025-04-17 02:29:23.34: NamespaceMonitor - start process kube event
2025-04-17 02:29:23.85: EndPointMonitor - Received BOOKMARK: oldResVer=11739 newResVer=11739
2025-04-17 02:29:23.85: EndPointMonitor - start process kube event
2025-04-17 02:29:23.85: empty line received
2025-04-17 02:29:23.85: EndPointMonitor - start process kube event
2025-04-17 02:29:23.87: NetworkMonitor - Received BOOKMARK: oldResVer=12005 newResVer=12005
2025-04-17 02:29:23.87: NetworkMonitor - start process kube event
2025-04-17 02:29:23.87: empty line received
2025-04-17 02:29:23.87: NetworkMonitor - start process kube event
2025-04-17 02:29:24.32: ServiceMonitor - Received BOOKMARK: oldResVer=11752 newResVer=12603
2025-04-17 02:29:24.32: ServiceMonitor - start process kube event
2025-04-17 02:29:24.32: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:29:24.33: empty line received
2025-04-17 02:29:24.33: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:29:24.33: VncKubernetes - vnc_sync - Service start
2025-04-17 02:29:24.33: VncKubernetes - vnc_sync - Service done
2025-04-17 02:29:24.33: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:29:24.33: ServiceMonitor - start process kube event
2025-04-17 02:29:24.36: PodMonitor - Received BOOKMARK: oldResVer=12230 newResVer=12535
2025-04-17 02:29:24.36: PodMonitor - start process kube event
2025-04-17 02:29:24.36: empty line received
2025-04-17 02:29:24.36: PodMonitor - start process kube event
2025-04-17 02:29:24.64: IngressMonitor - Received BOOKMARK: oldResVer=12343 newResVer=12343
2025-04-17 02:29:24.64: IngressMonitor - start process kube event
2025-04-17 02:29:24.64: empty line received
2025-04-17 02:29:24.64: IngressMonitor - start process kube event
2025-04-17 02:29:25.77: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11946 newResVer=11946
2025-04-17 02:29:25.77: NetworkPolicyMonitor - start process kube event
2025-04-17 02:29:25.77: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-17 02:29:25.77: empty line received
2025-04-17 02:29:25.77: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-17 02:29:25.77: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-17 02:29:25.77: NetworkPolicyMonitor - start process kube event
2025-04-17 02:29:25.78: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-17 02:29:25.78: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:29:28.06: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:29:28.06: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:29:28.06: PodMonitor - start process kube event
2025-04-17 02:29:28.06: empty line received
2025-04-17 02:29:28.06: PodMonitor - start process kube event
2025-04-17 02:29:39.57: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:29:39.57: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:29:39.57: PodMonitor - start process kube event
2025-04-17 02:29:39.57: empty line received
2025-04-17 02:29:39.57: PodMonitor - start process kube event
2025-04-17 02:29:40.53: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:29:40.53: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:29:40.53: PodMonitor - start process kube event
2025-04-17 02:29:40.53: empty line received
2025-04-17 02:29:40.53: PodMonitor - start process kube event
2025-04-17 02:29:54.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:29:54.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:29:54.56: PodMonitor - start process kube event
2025-04-17 02:29:54.56: empty line received
2025-04-17 02:29:54.56: PodMonitor - start process kube event
2025-04-17 02:30:23.29: NetworkMonitor - Received BOOKMARK: oldResVer=12005 newResVer=12005
2025-04-17 02:30:23.29: NetworkMonitor - start process kube event
2025-04-17 02:30:23.29: empty line received
2025-04-17 02:30:23.29: NetworkMonitor - start process kube event
2025-04-17 02:30:23.38: NamespaceMonitor - Received BOOKMARK: oldResVer=12014 newResVer=12014
2025-04-17 02:30:23.38: NamespaceMonitor - start process kube event
2025-04-17 02:30:23.38: empty line received
2025-04-17 02:30:23.38: NamespaceMonitor - start process kube event
2025-04-17 02:30:24.29: ServiceMonitor - Received BOOKMARK: oldResVer=12603 newResVer=12603
2025-04-17 02:30:24.29: ServiceMonitor - start process kube event
2025-04-17 02:30:24.29: empty line received
2025-04-17 02:30:24.29: ServiceMonitor - start process kube event
2025-04-17 02:30:24.44: EndPointMonitor - Received BOOKMARK: oldResVer=11739 newResVer=12664
2025-04-17 02:30:24.44: EndPointMonitor - start process kube event
2025-04-17 02:30:24.44: empty line received
2025-04-17 02:30:24.44: EndPointMonitor - start process kube event
2025-04-17 02:30:24.51: PodMonitor - Received BOOKMARK: oldResVer=12535 newResVer=12660
2025-04-17 02:30:24.51: PodMonitor - start process kube event
2025-04-17 02:30:24.51: empty line received
2025-04-17 02:30:24.51: PodMonitor - start process kube event
2025-04-17 02:30:25.12: IngressMonitor - Received BOOKMARK: oldResVer=12343 newResVer=12343
2025-04-17 02:30:25.12: IngressMonitor - start process kube event
2025-04-17 02:30:25.12: IngressMonitor - _schedule_vnc_sync
2025-04-17 02:30:25.12: empty line received
2025-04-17 02:30:25.12: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-17 02:30:25.12: VncKubernetes - vnc_sync - Ingress start
2025-04-17 02:30:25.12: VncKubernetes - vnc_sync - Ingress done
2025-04-17 02:30:25.12: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:30:25.12: IngressMonitor - start process kube event
2025-04-17 02:30:26.37: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11946 newResVer=11946
2025-04-17 02:30:26.37: NetworkPolicyMonitor - start process kube event
2025-04-17 02:30:26.37: empty line received
2025-04-17 02:30:26.37: NetworkPolicyMonitor - start process kube event
2025-04-17 02:31:23.59: NetworkMonitor - Received BOOKMARK: oldResVer=12005 newResVer=12005
2025-04-17 02:31:23.59: NetworkMonitor - start process kube event
2025-04-17 02:31:23.59: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:31:23.59: empty line received
2025-04-17 02:31:23.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:31:23.59: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:31:23.59: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:31:23.59: NetworkMonitor - start process kube event
2025-04-17 02:31:24.07: NamespaceMonitor - Received BOOKMARK: oldResVer=12014 newResVer=12014
2025-04-17 02:31:24.07: NamespaceMonitor - start process kube event
2025-04-17 02:31:24.07: NamespaceMonitor - _schedule_vnc_sync
2025-04-17 02:31:24.07: empty line received
2025-04-17 02:31:24.07: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-17 02:31:24.07: VncKubernetes - vnc_sync - Namespace start
2025-04-17 02:31:24.07: VncKubernetes - vnc_sync - Namespace done
2025-04-17 02:31:24.07: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:31:24.07: NamespaceMonitor - start process kube event
2025-04-17 02:31:24.26: ServiceMonitor - Received BOOKMARK: oldResVer=12603 newResVer=12603
2025-04-17 02:31:24.26: ServiceMonitor - start process kube event
2025-04-17 02:31:24.26: empty line received
2025-04-17 02:31:24.26: ServiceMonitor - start process kube event
2025-04-17 02:31:24.91: PodMonitor - Received BOOKMARK: oldResVer=12660 newResVer=12660
2025-04-17 02:31:24.91: PodMonitor - start process kube event
2025-04-17 02:31:24.91: empty line received
2025-04-17 02:31:24.91: PodMonitor - start process kube event
2025-04-17 02:31:25.20: EndPointMonitor - Received BOOKMARK: oldResVer=12664 newResVer=12664
2025-04-17 02:31:25.20: EndPointMonitor - start process kube event
2025-04-17 02:31:25.20: empty line received
2025-04-17 02:31:25.20: EndPointMonitor - start process kube event
2025-04-17 02:31:25.40: IngressMonitor - Received BOOKMARK: oldResVer=12343 newResVer=12343
2025-04-17 02:31:25.40: IngressMonitor - start process kube event
2025-04-17 02:31:25.40: empty line received
2025-04-17 02:31:25.40: IngressMonitor - start process kube event
2025-04-17 02:31:25.70: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11946 newResVer=11946
2025-04-17 02:31:25.70: NetworkPolicyMonitor - start process kube event
2025-04-17 02:31:25.70: empty line received
2025-04-17 02:31:25.70: NetworkPolicyMonitor - start process kube event
2025-04-17 02:32:23.56: ServiceMonitor - Received BOOKMARK: oldResVer=12603 newResVer=12603
2025-04-17 02:32:23.56: ServiceMonitor - start process kube event
2025-04-17 02:32:23.56: empty line received
2025-04-17 02:32:23.56: ServiceMonitor - start process kube event
2025-04-17 02:32:23.56: NetworkMonitor - Received BOOKMARK: oldResVer=12005 newResVer=12005
2025-04-17 02:32:23.56: NetworkMonitor - start process kube event
2025-04-17 02:32:23.56: empty line received
2025-04-17 02:32:23.56: NetworkMonitor - start process kube event
2025-04-17 02:32:24.38: NamespaceMonitor - Received BOOKMARK: oldResVer=12014 newResVer=12014
2025-04-17 02:32:24.38: NamespaceMonitor - start process kube event
2025-04-17 02:32:24.38: empty line received
2025-04-17 02:32:24.38: NamespaceMonitor - start process kube event
2025-04-17 02:32:24.50: PodMonitor - Received BOOKMARK: oldResVer=12660 newResVer=12660
2025-04-17 02:32:24.50: PodMonitor - start process kube event
2025-04-17 02:32:24.50: PodMonitor - _schedule_vnc_sync
2025-04-17 02:32:24.50: empty line received
2025-04-17 02:32:24.50: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-17 02:32:24.50: VncKubernetes - vnc_sync - Pod start
2025-04-17 02:32:24.50: VncKubernetes - vnc_sync - Pod done
2025-04-17 02:32:24.50: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:32:24.50: PodMonitor - start process kube event
2025-04-17 02:32:24.64: EndPointMonitor - Received BOOKMARK: oldResVer=12664 newResVer=12664
2025-04-17 02:32:24.64: EndPointMonitor - start process kube event
2025-04-17 02:32:24.64: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:32:24.64: empty line received
2025-04-17 02:32:24.64: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:32:24.64: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:32:24.64: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:32:24.64: EndPointMonitor - start process kube event
2025-04-17 02:32:25.12: IngressMonitor - Received BOOKMARK: oldResVer=12343 newResVer=12343
2025-04-17 02:32:25.12: IngressMonitor - start process kube event
2025-04-17 02:32:25.12: empty line received
2025-04-17 02:32:25.12: IngressMonitor - start process kube event
2025-04-17 02:32:26.49: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11946 newResVer=12814
2025-04-17 02:32:26.49: NetworkPolicyMonitor - start process kube event
2025-04-17 02:32:26.49: empty line received
2025-04-17 02:32:26.49: NetworkPolicyMonitor - start process kube event
2025-04-17 02:33:23.61: NetworkMonitor - Received BOOKMARK: oldResVer=12005 newResVer=12940
2025-04-17 02:33:23.61: NetworkMonitor - start process kube event
2025-04-17 02:33:23.61: empty line received
2025-04-17 02:33:23.61: NetworkMonitor - start process kube event
2025-04-17 02:33:24.29: ServiceMonitor - Received BOOKMARK: oldResVer=12603 newResVer=12603
2025-04-17 02:33:24.29: ServiceMonitor - start process kube event
2025-04-17 02:33:24.29: empty line received
2025-04-17 02:33:24.29: ServiceMonitor - start process kube event
2025-04-17 02:33:24.40: PodMonitor - Received BOOKMARK: oldResVer=12660 newResVer=12660
2025-04-17 02:33:24.40: PodMonitor - start process kube event
2025-04-17 02:33:24.40: empty line received
2025-04-17 02:33:24.40: PodMonitor - start process kube event
2025-04-17 02:33:24.91: IngressMonitor - Received BOOKMARK: oldResVer=12343 newResVer=12343
2025-04-17 02:33:24.91: IngressMonitor - start process kube event
2025-04-17 02:33:24.91: empty line received
2025-04-17 02:33:24.91: IngressMonitor - start process kube event
2025-04-17 02:33:25.13: NamespaceMonitor - Received BOOKMARK: oldResVer=12014 newResVer=12886
2025-04-17 02:33:25.13: NamespaceMonitor - start process kube event
2025-04-17 02:33:25.13: empty line received
2025-04-17 02:33:25.13: NamespaceMonitor - start process kube event
2025-04-17 02:33:25.43: EndPointMonitor - Received BOOKMARK: oldResVer=12664 newResVer=12664
2025-04-17 02:33:25.43: EndPointMonitor - start process kube event
2025-04-17 02:33:25.43: empty line received
2025-04-17 02:33:25.43: EndPointMonitor - start process kube event
2025-04-17 02:33:26.66: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12814 newResVer=12814
2025-04-17 02:33:26.66: NetworkPolicyMonitor - start process kube event
2025-04-17 02:33:26.66: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-17 02:33:26.66: empty line received
2025-04-17 02:33:26.66: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-17 02:33:26.66: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-17 02:33:26.66: NetworkPolicyMonitor - start process kube event
2025-04-17 02:33:26.66: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-17 02:33:26.66: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:34:23.32: NetworkMonitor - Received BOOKMARK: oldResVer=12940 newResVer=12940
2025-04-17 02:34:23.32: NetworkMonitor - start process kube event
2025-04-17 02:34:23.32: empty line received
2025-04-17 02:34:23.32: NetworkMonitor - start process kube event
2025-04-17 02:34:24.40: ServiceMonitor - Received BOOKMARK: oldResVer=12603 newResVer=12603
2025-04-17 02:34:24.40: ServiceMonitor - start process kube event
2025-04-17 02:34:24.40: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:34:24.40: empty line received
2025-04-17 02:34:24.40: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:34:24.40: VncKubernetes - vnc_sync - Service start
2025-04-17 02:34:24.40: VncKubernetes - vnc_sync - Service done
2025-04-17 02:34:24.40: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:34:24.40: ServiceMonitor - start process kube event
2025-04-17 02:34:24.58: NamespaceMonitor - Received BOOKMARK: oldResVer=12886 newResVer=12886
2025-04-17 02:34:24.58: NamespaceMonitor - start process kube event
2025-04-17 02:34:24.58: empty line received
2025-04-17 02:34:24.58: NamespaceMonitor - start process kube event
2025-04-17 02:34:24.86: IngressMonitor - Received BOOKMARK: oldResVer=12343 newResVer=12343
2025-04-17 02:34:24.86: IngressMonitor - start process kube event
2025-04-17 02:34:24.86: empty line received
2025-04-17 02:34:24.86: IngressMonitor - start process kube event
2025-04-17 02:34:25.55: PodMonitor - Received BOOKMARK: oldResVer=12660 newResVer=12660
2025-04-17 02:34:25.55: PodMonitor - start process kube event
2025-04-17 02:34:25.55: empty line received
2025-04-17 02:34:25.55: PodMonitor - start process kube event
2025-04-17 02:34:25.80: EndPointMonitor - Received BOOKMARK: oldResVer=12664 newResVer=12664
2025-04-17 02:34:25.80: EndPointMonitor - start process kube event
2025-04-17 02:34:25.80: empty line received
2025-04-17 02:34:25.80: EndPointMonitor - start process kube event
2025-04-17 02:34:27.51: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12814 newResVer=12814
2025-04-17 02:34:27.51: NetworkPolicyMonitor - start process kube event
2025-04-17 02:34:27.51: empty line received
2025-04-17 02:34:27.51: NetworkPolicyMonitor - start process kube event
2025-04-17 02:34:28.10: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:34:28.10: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:34:28.10: PodMonitor - start process kube event
2025-04-17 02:34:28.10: empty line received
2025-04-17 02:34:28.10: PodMonitor - start process kube event
2025-04-17 02:34:52.78: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:34:52.78: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:34:52.78: PodMonitor - start process kube event
2025-04-17 02:34:52.78: empty line received
2025-04-17 02:34:52.78: PodMonitor - start process kube event
2025-04-17 02:34:53.85: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:34:53.85: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:34:53.85: PodMonitor - start process kube event
2025-04-17 02:34:53.85: empty line received
2025-04-17 02:34:53.85: PodMonitor - start process kube event
2025-04-17 02:35:07.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:35:07.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:35:07.56: PodMonitor - start process kube event
2025-04-17 02:35:07.56: empty line received
2025-04-17 02:35:07.56: PodMonitor - start process kube event
2025-04-17 02:35:23.10: NetworkMonitor - Received BOOKMARK: oldResVer=12940 newResVer=12940
2025-04-17 02:35:23.10: NetworkMonitor - start process kube event
2025-04-17 02:35:23.10: empty line received
2025-04-17 02:35:23.10: NetworkMonitor - start process kube event
2025-04-17 02:35:24.91: ServiceMonitor - Received BOOKMARK: oldResVer=12603 newResVer=12603
2025-04-17 02:35:24.91: ServiceMonitor - start process kube event
2025-04-17 02:35:24.91: empty line received
2025-04-17 02:35:24.91: ServiceMonitor - start process kube event
2025-04-17 02:35:25.22: NamespaceMonitor - Received BOOKMARK: oldResVer=12886 newResVer=12886
2025-04-17 02:35:25.22: NamespaceMonitor - start process kube event
2025-04-17 02:35:25.22: NamespaceMonitor - _schedule_vnc_sync
2025-04-17 02:35:25.22: empty line received
2025-04-17 02:35:25.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-17 02:35:25.22: VncKubernetes - vnc_sync - Namespace start
2025-04-17 02:35:25.22: VncKubernetes - vnc_sync - Namespace done
2025-04-17 02:35:25.22: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:35:25.22: NamespaceMonitor - start process kube event
2025-04-17 02:35:25.41: IngressMonitor - Received BOOKMARK: oldResVer=12343 newResVer=12343
2025-04-17 02:35:25.41: IngressMonitor - start process kube event
2025-04-17 02:35:25.41: IngressMonitor - _schedule_vnc_sync
2025-04-17 02:35:25.41: empty line received
2025-04-17 02:35:25.41: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-17 02:35:25.41: VncKubernetes - vnc_sync - Ingress start
2025-04-17 02:35:25.41: VncKubernetes - vnc_sync - Ingress done
2025-04-17 02:35:25.41: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:35:25.41: IngressMonitor - start process kube event
2025-04-17 02:35:25.88: EndPointMonitor - Received BOOKMARK: oldResVer=12664 newResVer=12664
2025-04-17 02:35:25.88: EndPointMonitor - start process kube event
2025-04-17 02:35:25.88: empty line received
2025-04-17 02:35:25.88: EndPointMonitor - start process kube event
2025-04-17 02:35:26.30: PodMonitor - Received BOOKMARK: oldResVer=12660 newResVer=13107
2025-04-17 02:35:26.30: PodMonitor - start process kube event
2025-04-17 02:35:26.30: empty line received
2025-04-17 02:35:26.30: PodMonitor - start process kube event
2025-04-17 02:35:27.51: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12814 newResVer=12814
2025-04-17 02:35:27.51: NetworkPolicyMonitor - start process kube event
2025-04-17 02:35:27.51: empty line received
2025-04-17 02:35:27.51: NetworkPolicyMonitor - start process kube event
2025-04-17 02:35:28.85: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:35:28.85: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:35:28.85: PodMonitor - start process kube event
2025-04-17 02:35:28.85: empty line received
2025-04-17 02:35:28.85: PodMonitor - start process kube event
2025-04-17 02:35:41.56: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:35:41.56: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:35:41.56: PodMonitor - start process kube event
2025-04-17 02:35:41.56: empty line received
2025-04-17 02:35:41.56: PodMonitor - start process kube event
2025-04-17 02:36:23.24: NetworkMonitor - Received BOOKMARK: oldResVer=12940 newResVer=12940
2025-04-17 02:36:23.24: NetworkMonitor - start process kube event
2025-04-17 02:36:23.24: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:36:23.24: empty line received
2025-04-17 02:36:23.24: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:36:23.24: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:36:23.24: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:36:23.24: NetworkMonitor - start process kube event
2025-04-17 02:36:24.50: ServiceMonitor - Received BOOKMARK: oldResVer=12603 newResVer=12603
2025-04-17 02:36:24.50: ServiceMonitor - start process kube event
2025-04-17 02:36:24.50: empty line received
2025-04-17 02:36:24.50: ServiceMonitor - start process kube event
2025-04-17 02:36:24.66: NamespaceMonitor - Received BOOKMARK: oldResVer=12886 newResVer=12886
2025-04-17 02:36:24.66: NamespaceMonitor - start process kube event
2025-04-17 02:36:24.66: empty line received
2025-04-17 02:36:24.66: NamespaceMonitor - start process kube event
2025-04-17 02:36:25.08: IngressMonitor - Received BOOKMARK: oldResVer=12343 newResVer=12343
2025-04-17 02:36:25.08: IngressMonitor - start process kube event
2025-04-17 02:36:25.08: empty line received
2025-04-17 02:36:25.08: IngressMonitor - start process kube event
2025-04-17 02:36:25.63: EndPointMonitor - Received BOOKMARK: oldResVer=12664 newResVer=12664
2025-04-17 02:36:25.63: EndPointMonitor - start process kube event
2025-04-17 02:36:25.63: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:36:25.63: empty line received
2025-04-17 02:36:25.63: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:36:25.63: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:36:25.63: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:36:25.63: EndPointMonitor - start process kube event
2025-04-17 02:36:26.05: PodMonitor - Received BOOKMARK: oldResVer=13107 newResVer=13156
2025-04-17 02:36:26.05: PodMonitor - start process kube event
2025-04-17 02:36:26.05: PodMonitor - _schedule_vnc_sync
2025-04-17 02:36:26.05: empty line received
2025-04-17 02:36:26.05: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-17 02:36:26.05: VncKubernetes - vnc_sync - Pod start
2025-04-17 02:36:26.05: VncKubernetes - vnc_sync - Pod done
2025-04-17 02:36:26.05: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:36:26.05: PodMonitor - start process kube event
2025-04-17 02:36:28.40: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12814 newResVer=12814
2025-04-17 02:36:28.40: NetworkPolicyMonitor - start process kube event
2025-04-17 02:36:28.40: empty line received
2025-04-17 02:36:28.40: NetworkPolicyMonitor - start process kube event
2025-04-17 02:37:23.81: NetworkMonitor - Received BOOKMARK: oldResVer=12940 newResVer=12940
2025-04-17 02:37:23.81: NetworkMonitor - start process kube event
2025-04-17 02:37:23.82: empty line received
2025-04-17 02:37:23.82: NetworkMonitor - start process kube event
2025-04-17 02:37:24.58: NamespaceMonitor - Received BOOKMARK: oldResVer=12886 newResVer=12886
2025-04-17 02:37:24.58: NamespaceMonitor - start process kube event
2025-04-17 02:37:24.58: empty line received
2025-04-17 02:37:24.58: NamespaceMonitor - start process kube event
2025-04-17 02:37:24.85: IngressMonitor - Received BOOKMARK: oldResVer=12343 newResVer=13243
2025-04-17 02:37:24.85: IngressMonitor - start process kube event
2025-04-17 02:37:24.85: empty line received
2025-04-17 02:37:24.85: IngressMonitor - start process kube event
2025-04-17 02:37:25.05: ServiceMonitor - Received BOOKMARK: oldResVer=12603 newResVer=12603
2025-04-17 02:37:25.05: ServiceMonitor - start process kube event
2025-04-17 02:37:25.05: empty line received
2025-04-17 02:37:25.05: ServiceMonitor - start process kube event
2025-04-17 02:37:25.76: PodMonitor - Received BOOKMARK: oldResVer=13156 newResVer=13156
2025-04-17 02:37:25.76: PodMonitor - start process kube event
2025-04-17 02:37:25.76: empty line received
2025-04-17 02:37:25.76: PodMonitor - start process kube event
2025-04-17 02:37:26.47: EndPointMonitor - Received BOOKMARK: oldResVer=12664 newResVer=12664
2025-04-17 02:37:26.47: EndPointMonitor - start process kube event
2025-04-17 02:37:26.47: empty line received
2025-04-17 02:37:26.47: EndPointMonitor - start process kube event
2025-04-17 02:37:28.16: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12814 newResVer=12814
2025-04-17 02:37:28.16: NetworkPolicyMonitor - start process kube event
2025-04-17 02:37:28.16: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-17 02:37:28.16: empty line received
2025-04-17 02:37:28.16: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-17 02:37:28.16: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-17 02:37:28.16: NetworkPolicyMonitor - start process kube event
2025-04-17 02:37:28.16: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-17 02:37:28.16: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:38:22.94: NetworkMonitor - Received BOOKMARK: oldResVer=12940 newResVer=12940
2025-04-17 02:38:22.94: NetworkMonitor - start process kube event
2025-04-17 02:38:22.94: empty line received
2025-04-17 02:38:22.94: NetworkMonitor - start process kube event
2025-04-17 02:38:24.57: NamespaceMonitor - Received BOOKMARK: oldResVer=12886 newResVer=12886
2025-04-17 02:38:24.57: NamespaceMonitor - start process kube event
2025-04-17 02:38:24.57: empty line received
2025-04-17 02:38:24.57: NamespaceMonitor - start process kube event
2025-04-17 02:38:25.18: ServiceMonitor - Received BOOKMARK: oldResVer=12603 newResVer=12603
2025-04-17 02:38:25.18: ServiceMonitor - start process kube event
2025-04-17 02:38:25.18: ServiceMonitor - _schedule_vnc_sync
2025-04-17 02:38:25.18: empty line received
2025-04-17 02:38:25.18: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-17 02:38:25.18: VncKubernetes - vnc_sync - Service start
2025-04-17 02:38:25.18: VncKubernetes - vnc_sync - Service done
2025-04-17 02:38:25.18: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:38:25.18: ServiceMonitor - start process kube event
2025-04-17 02:38:25.26: IngressMonitor - Received BOOKMARK: oldResVer=13243 newResVer=13243
2025-04-17 02:38:25.26: IngressMonitor - start process kube event
2025-04-17 02:38:25.26: empty line received
2025-04-17 02:38:25.26: IngressMonitor - start process kube event
2025-04-17 02:38:25.95: PodMonitor - Received BOOKMARK: oldResVer=13156 newResVer=13156
2025-04-17 02:38:25.95: PodMonitor - start process kube event
2025-04-17 02:38:25.95: empty line received
2025-04-17 02:38:25.95: PodMonitor - start process kube event
2025-04-17 02:38:27.07: EndPointMonitor - Received BOOKMARK: oldResVer=12664 newResVer=12664
2025-04-17 02:38:27.07: EndPointMonitor - start process kube event
2025-04-17 02:38:27.07: empty line received
2025-04-17 02:38:27.07: EndPointMonitor - start process kube event
2025-04-17 02:38:28.08: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12814 newResVer=12814
2025-04-17 02:38:28.08: NetworkPolicyMonitor - start process kube event
2025-04-17 02:38:28.08: empty line received
2025-04-17 02:38:28.08: NetworkPolicyMonitor - start process kube event
2025-04-17 02:39:23.45: NetworkMonitor - Received BOOKMARK: oldResVer=12940 newResVer=12940
2025-04-17 02:39:23.45: NetworkMonitor - start process kube event
2025-04-17 02:39:23.45: empty line received
2025-04-17 02:39:23.45: NetworkMonitor - start process kube event
2025-04-17 02:39:24.50: IngressMonitor - Received BOOKMARK: oldResVer=13243 newResVer=13243
2025-04-17 02:39:24.50: IngressMonitor - start process kube event
2025-04-17 02:39:24.50: empty line received
2025-04-17 02:39:24.50: IngressMonitor - start process kube event
2025-04-17 02:39:24.61: NamespaceMonitor - Received BOOKMARK: oldResVer=12886 newResVer=12886
2025-04-17 02:39:24.61: NamespaceMonitor - start process kube event
2025-04-17 02:39:24.61: empty line received
2025-04-17 02:39:24.61: NamespaceMonitor - start process kube event
2025-04-17 02:39:24.76: ServiceMonitor - Received BOOKMARK: oldResVer=12603 newResVer=13455
2025-04-17 02:39:24.76: ServiceMonitor - start process kube event
2025-04-17 02:39:24.76: empty line received
2025-04-17 02:39:24.76: ServiceMonitor - start process kube event
2025-04-17 02:39:25.54: PodMonitor - Received BOOKMARK: oldResVer=13156 newResVer=13156
2025-04-17 02:39:25.54: PodMonitor - start process kube event
2025-04-17 02:39:25.54: empty line received
2025-04-17 02:39:25.54: PodMonitor - start process kube event
2025-04-17 02:39:27.23: EndPointMonitor - Received BOOKMARK: oldResVer=12664 newResVer=12664
2025-04-17 02:39:27.23: EndPointMonitor - start process kube event
2025-04-17 02:39:27.23: empty line received
2025-04-17 02:39:27.24: EndPointMonitor - start process kube event
2025-04-17 02:39:27.77: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12814 newResVer=12814
2025-04-17 02:39:27.77: NetworkPolicyMonitor - start process kube event
2025-04-17 02:39:27.77: empty line received
2025-04-17 02:39:27.77: NetworkPolicyMonitor - start process kube event
2025-04-17 02:40:01.96: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:40:01.96: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:40:01.96: PodMonitor - start process kube event
2025-04-17 02:40:01.96: empty line received
2025-04-17 02:40:01.96: PodMonitor - start process kube event
2025-04-17 02:40:03.01: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:40:03.01: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:40:03.01: PodMonitor - start process kube event
2025-04-17 02:40:03.01: empty line received
2025-04-17 02:40:03.01: PodMonitor - start process kube event
2025-04-17 02:40:17.57: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:40:17.57: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:40:17.57: PodMonitor - start process kube event
2025-04-17 02:40:17.57: empty line received
2025-04-17 02:40:17.57: PodMonitor - start process kube event
2025-04-17 02:40:23.51: NetworkMonitor - Received BOOKMARK: oldResVer=12940 newResVer=12940
2025-04-17 02:40:23.51: NetworkMonitor - start process kube event
2025-04-17 02:40:23.51: NetworkMonitor - _schedule_vnc_sync
2025-04-17 02:40:23.51: empty line received
2025-04-17 02:40:23.51: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-17 02:40:23.51: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-17 02:40:23.51: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:40:23.51: NetworkMonitor - start process kube event
2025-04-17 02:40:24.67: IngressMonitor - Received BOOKMARK: oldResVer=13243 newResVer=13243
2025-04-17 02:40:24.67: IngressMonitor - start process kube event
2025-04-17 02:40:24.67: IngressMonitor - _schedule_vnc_sync
2025-04-17 02:40:24.67: empty line received
2025-04-17 02:40:24.67: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-17 02:40:24.67: VncKubernetes - vnc_sync - Ingress start
2025-04-17 02:40:24.67: VncKubernetes - vnc_sync - Ingress done
2025-04-17 02:40:24.67: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:40:24.67: IngressMonitor - start process kube event
2025-04-17 02:40:24.85: ServiceMonitor - Received BOOKMARK: oldResVer=13455 newResVer=13455
2025-04-17 02:40:24.85: ServiceMonitor - start process kube event
2025-04-17 02:40:24.85: empty line received
2025-04-17 02:40:24.85: ServiceMonitor - start process kube event
2025-04-17 02:40:25.04: NamespaceMonitor - Received BOOKMARK: oldResVer=12886 newResVer=12886
2025-04-17 02:40:25.04: NamespaceMonitor - start process kube event
2025-04-17 02:40:25.04: NamespaceMonitor - _schedule_vnc_sync
2025-04-17 02:40:25.04: empty line received
2025-04-17 02:40:25.04: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-17 02:40:25.04: VncKubernetes - vnc_sync - Namespace start
2025-04-17 02:40:25.04: VncKubernetes - vnc_sync - Namespace done
2025-04-17 02:40:25.04: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:40:25.04: NamespaceMonitor - start process kube event
2025-04-17 02:40:26.29: PodMonitor - Received BOOKMARK: oldResVer=13156 newResVer=13547
2025-04-17 02:40:26.29: PodMonitor - start process kube event
2025-04-17 02:40:26.29: PodMonitor - _schedule_vnc_sync
2025-04-17 02:40:26.29: empty line received
2025-04-17 02:40:26.29: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-17 02:40:26.29: VncKubernetes - vnc_sync - Pod start
2025-04-17 02:40:26.29: VncKubernetes - vnc_sync - Pod done
2025-04-17 02:40:26.29: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:40:26.29: PodMonitor - start process kube event
2025-04-17 02:40:26.43: EndPointMonitor - Received BOOKMARK: oldResVer=12664 newResVer=12664
2025-04-17 02:40:26.43: EndPointMonitor - start process kube event
2025-04-17 02:40:26.43: EndPointMonitor - _schedule_vnc_sync
2025-04-17 02:40:26.43: empty line received
2025-04-17 02:40:26.43: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-17 02:40:26.43: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-17 02:40:26.43: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:40:26.43: EndPointMonitor - start process kube event
2025-04-17 02:40:28.07: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12814 newResVer=12814
2025-04-17 02:40:28.07: NetworkPolicyMonitor - start process kube event
2025-04-17 02:40:28.07: empty line received
2025-04-17 02:40:28.07: NetworkPolicyMonitor - start process kube event
2025-04-17 02:40:30.82: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-4b8sr:1daf4f7c-bd59-4aee-9f86-589d65abcbcb
2025-04-17 02:40:30.82: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-4b8sr (hostNetwork=True)
2025-04-17 02:40:30.82: PodMonitor - start process kube event
2025-04-17 02:40:30.82: empty line received
2025-04-17 02:40:30.82: PodMonitor - start process kube event
2025-04-17 02:41:11.28: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12814 newResVer=12814
2025-04-17 02:41:11.28: NetworkPolicyMonitor - start process kube event
2025-04-17 02:41:11.28: empty line received
2025-04-17 02:41:11.28: NetworkPolicyMonitor - start process kube event
2025-04-17 02:41:12.78: stop iteration NetworkPolicyMonitor
2025-04-17 02:41:12.78: NetworkPolicyMonitor - start process kube event
2025-04-17 02:41:12.78: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12814
2025-04-17 02:41:12.78: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-17 02:41:12.78: NetworkPolicyMonitor - Connect Kube API result 0
2025-04-17 02:41:12.78: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-17 02:41:12.78: NetworkPolicyMonitor - Start Watching request https://10.0.0.22:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12814'})(timeout=120)
2025-04-17 02:41:12.79: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-17 02:41:12.79: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-17 02:41:12.79: NetworkPolicyMonitor - Watches https://10.0.0.22:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12814'})
2025-04-17 02:41:12.79: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-17 02:41:12.79: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-17 02:41:23.47: NetworkMonitor - Received BOOKMARK: oldResVer=12940 newResVer=12940
2025-04-17 02:41:23.47: NetworkMonitor - start process kube event
2025-04-17 02:41:23.47: empty line received
2025-04-17 02:41:23.47: NetworkMonitor - start process kube event
2025-04-17 02:41:25.19: NamespaceMonitor - Received BOOKMARK: oldResVer=12886 newResVer=12886
2025-04-17 02:41:25.19: NamespaceMonitor - start process kube event