INFO: =================== Thu Apr 24 01:32:12 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/24/2025 01:33:50.409 7fdc1023be48 [contrail-kube-manager] [INFO]: SANDESH: CONNECT TO COLLECTOR: True
04/24/2025 01:33:50.700 7fdc1023be48 [contrail-kube-manager] [INFO]: SANDESH: Logging: LEVEL: [SYS_INFO] -> [SYS_NOTICE]
2025-04-24 01:33:52.01: KubeMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:33:52.01: KubeMonitor - Connect Kube API result 0
2025-04-24 01:33:52.07: KubeMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/api/v1
2025-04-24 01:33:52.07: NamespaceMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/api/v1
2025-04-24 01:33:52.08: NetworkMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1
2025-04-24 01:33:52.08: PodMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/api/v1
2025-04-24 01:33:52.09: ServiceMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/api/v1
2025-04-24 01:33:52.09: NetworkPolicyMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/apis/networking.k8s.io/v1
2025-04-24 01:33:52.10: EndPointMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/api/v1
2025-04-24 01:33:52.10: IngressMonitor - KubeMonitor init done: url=https://10.0.0.22:6443/apis/networking.k8s.io/v1
2025-04-24 01:33:52.10: VncKubernetes - vnc_connect starting
2025-04-24 01:33:52.11: VncKubernetes - vnc_connect failed: 
2025-04-24 01:33:55.13: VncKubernetes - vnc_connect failed: 
2025-04-24 01:33:58.15: VncKubernetes - vnc_connect failed: 
2025-04-24 01:34:01.18: VncKubernetes - vnc_connect failed: 
2025-04-24 01:34:04.20: VncKubernetes - vnc_connect failed: 
2025-04-24 01:34:07.22: VncKubernetes - vnc_connect done
2025-04-24 01:34:08.46: default-domain domain available.
2025-04-24 01:34:20.77: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:34:20.77: NamespaceMonitor - start process kube event
2025-04-24 01:34:20.77: NamespaceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-24 01:34:20.77: NamespaceMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:34:20.77: NetworkMonitor - start process kube event
2025-04-24 01:34:20.78: NetworkMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-24 01:34:20.78: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:34:20.78: PodMonitor - start process kube event
2025-04-24 01:34:20.78: PodMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-24 01:34:20.78: PodMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:34:20.78: ServiceMonitor - start process kube event
2025-04-24 01:34:20.78: ServiceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-24 01:34:20.78: ServiceMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:34:20.78: NetworkPolicyMonitor - start process kube event
2025-04-24 01:34:20.78: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-24 01:34:20.78: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:34:20.78: EndPointMonitor - start process kube event
2025-04-24 01:34:20.78: EndPointMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-24 01:34:20.78: EndPointMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:34:20.78: IngressMonitor - start process kube event
2025-04-24 01:34:20.78: IngressMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-04-24 01:34:20.78: IngressMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:34:20.78: IngressMonitor - Connect Kube API result 0
2025-04-24 01:34:20.78: IngressMonitor - Start init url=https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses resource_version=None
2025-04-24 01:34:20.78: EndPointMonitor - Connect Kube API result 0
2025-04-24 01:34:20.78: EndPointMonitor - Start init url=https://10.0.0.22:6443/api/v1/endpoints resource_version=None
2025-04-24 01:34:20.78: NetworkPolicyMonitor - Connect Kube API result 0
2025-04-24 01:34:20.78: NetworkPolicyMonitor - Start init url=https://10.0.0.22:6443/apis/networking.k8s.io/v1/networkpolicies resource_version=None
2025-04-24 01:34:20.78: ServiceMonitor - Connect Kube API result 0
2025-04-24 01:34:20.78: ServiceMonitor - Start init url=https://10.0.0.22:6443/api/v1/services resource_version=None
2025-04-24 01:34:20.78: PodMonitor - Connect Kube API result 0
2025-04-24 01:34:20.78: PodMonitor - Start init url=https://10.0.0.22:6443/api/v1/pods resource_version=None
2025-04-24 01:34:20.78: NetworkMonitor - Connect Kube API result 0
2025-04-24 01:34:20.78: NamespaceMonitor - Connect Kube API result 0
2025-04-24 01:34:20.78: NamespaceMonitor - Start init url=https://10.0.0.22:6443/api/v1/namespaces resource_version=None
2025-04-24 01:34:20.83: IngressMonitor - Done init url=https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses, resource_version=7960
2025-04-24 01:34:20.83: IngressMonitor - _schedule_vnc_sync
2025-04-24 01:34:20.83: IngressMonitor - Start Watching request https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:34:20.83: NamespaceMonitor - Got ADDED Namespace None:default:a7474640-8faf-481c-92a6-4a7bd1850c46
2025-04-24 01:34:20.83: NetworkPolicyMonitor - Done init url=https://10.0.0.22:6443/apis/networking.k8s.io/v1/networkpolicies, resource_version=7960
2025-04-24 01:34:20.83: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-24 01:34:20.83: NetworkPolicyMonitor - Start Watching request https://10.0.0.22:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:34:20.84: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-24 01:34:20.84: VncKubernetes - vnc_sync - Ingress start
2025-04-24 01:34:20.84: VncKubernetes - vnc_sync - Ingress done
2025-04-24 01:34:20.84: VncKubernetes - wait event (qsize=2 timeout=120)
2025-04-24 01:34:20.84: VncKubernetes - Process event (name=default event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace default:a7474640-8faf-481c-92a6-4a7bd1850c46
2025-04-24 01:34:20.85: IngressMonitor - Watches https://10.0.0.22:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:34:20.85: NetworkMonitor - Start init url=https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions resource_version=None
2025-04-24 01:34:20.85: NetworkPolicyMonitor - Watches https://10.0.0.22:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:34:20.86: EndPointMonitor - Got ADDED Endpoints default:kubernetes:100a409f-5ee2-4449-a498-8199a803147c
2025-04-24 01:34:20.86: ServiceMonitor - Got ADDED Service default:kubernetes:942c1427-a35c-4ebc-b1c3-5ac9c74e3c8c
2025-04-24 01:34:20.86: NamespaceMonitor - Got ADDED Namespace None:kube-node-lease:b2fdde1a-264c-4c96-bca9-89552e02f587
2025-04-24 01:34:20.87: PodMonitor - Skipped ADDED Pod kube-system:config-zookeeper-g7s4m (hostNetwork=True)
2025-04-24 01:34:20.87: NamespaceMonitor - Got ADDED Namespace None:kube-public:6050e1d0-e83f-41b2-b9ee-36b0092ad501
2025-04-24 01:34:20.88: NetworkMonitor - Done init url=https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions, resource_version=7964
2025-04-24 01:34:20.88: NetworkMonitor - _schedule_vnc_sync
2025-04-24 01:34:20.88: NetworkMonitor - Start Watching request https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7964'})(timeout=120)
2025-04-24 01:34:20.88: ServiceMonitor - Got ADDED Service kube-system:coredns:11f83fd5-45fb-4aac-b3c2-2280c9671fab
2025-04-24 01:34:20.88: ServiceMonitor - Done init url=https://10.0.0.22:6443/api/v1/services, resource_version=7960
2025-04-24 01:34:20.88: ServiceMonitor - _schedule_vnc_sync
2025-04-24 01:34:20.88: ServiceMonitor - Start Watching request https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:34:20.88: EndPointMonitor - Got ADDED Endpoints kube-system:coredns:ddb9babe-e538-42b7-9d79-27e85d569c33
2025-04-24 01:34:20.88: EndPointMonitor - Done init url=https://10.0.0.22:6443/api/v1/endpoints, resource_version=7960
2025-04-24 01:34:20.88: EndPointMonitor - _schedule_vnc_sync
2025-04-24 01:34:20.88: EndPointMonitor - Start Watching request https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:34:20.88: PodMonitor - Got ADDED Pod kube-system:coredns-77f7cc69db-7t9sf:d8d53619-1e66-4d2a-8bf7-8cb979d2b8e3
2025-04-24 01:34:20.88: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7964'})
2025-04-24 01:34:20.89: ServiceMonitor - Watches https://10.0.0.22:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:34:20.89: EndPointMonitor - Watches https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:34:20.89: NamespaceMonitor - Got ADDED Namespace None:kube-system:88e42389-3429-4b93-9b72-45f14214a87a
2025-04-24 01:34:20.89: NamespaceMonitor - Done init url=https://10.0.0.22:6443/api/v1/namespaces, resource_version=7960
2025-04-24 01:34:20.89: NamespaceMonitor - _schedule_vnc_sync
2025-04-24 01:34:20.89: NamespaceMonitor - Start Watching request https://10.0.0.22:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:34:20.89: NamespaceMonitor - Watches https://10.0.0.22:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:34:20.89: PodMonitor - Got ADDED Pod kube-system:dns-autoscaler-595558c478-c4lbx:f4f0e05b-f270-4197-b374-7c9be8301e42
2025-04-24 01:34:20.90: PodMonitor - Skipped ADDED Pod kube-system:kube-apiserver-cn-jenkins-deploy-platform-k8s-manifests-162-1 (hostNetwork=True)
2025-04-24 01:34:20.90: PodMonitor - Skipped ADDED Pod kube-system:kube-controller-manager-cn-jenkins-deploy-platform-k8s-manifests-162-1 (hostNetwork=True)
2025-04-24 01:34:20.92: PodMonitor - Skipped ADDED Pod kube-system:kube-proxy-nks2h (hostNetwork=True)
2025-04-24 01:34:20.93: PodMonitor - Skipped ADDED Pod kube-system:kube-scheduler-cn-jenkins-deploy-platform-k8s-manifests-162-1 (hostNetwork=True)
2025-04-24 01:34:20.95: PodMonitor - Skipped ADDED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:34:20.96: PodMonitor - Skipped ADDED Pod kube-system:opensdn-analytics-7qgkz (hostNetwork=True)
2025-04-24 01:34:20.98: PodMonitor - Skipped ADDED Pod kube-system:opensdn-analytics-alarm-zb56s (hostNetwork=True)
2025-04-24 01:34:20.99: PodMonitor - Skipped ADDED Pod kube-system:opensdn-analytics-snmp-r9dfw (hostNetwork=True)
2025-04-24 01:34:21.00: PodMonitor - Skipped ADDED Pod kube-system:opensdn-analyticsdb-rx979 (hostNetwork=True)
2025-04-24 01:34:21.01: PodMonitor - Skipped ADDED Pod kube-system:opensdn-configdb-zzrqs (hostNetwork=True)
2025-04-24 01:34:21.01: PodMonitor - Skipped ADDED Pod kube-system:opensdn-controller-config-zrkrs (hostNetwork=True)
2025-04-24 01:34:21.03: PodMonitor - Skipped ADDED Pod kube-system:opensdn-controller-control-g7ccl (hostNetwork=True)
2025-04-24 01:34:21.04: PodMonitor - Skipped ADDED Pod kube-system:opensdn-controller-webui-fv9sn (hostNetwork=True)
2025-04-24 01:34:21.05: PodMonitor - Skipped ADDED Pod kube-system:opensdn-kube-manager-5n4gz (hostNetwork=True)
2025-04-24 01:34:21.06: PodMonitor - Skipped ADDED Pod kube-system:rabbitmq-v77l6 (hostNetwork=True)
2025-04-24 01:34:21.07: PodMonitor - Skipped ADDED Pod kube-system:redis-jdwrv (hostNetwork=True)
2025-04-24 01:34:21.07: PodMonitor - Done init url=https://10.0.0.22:6443/api/v1/pods, resource_version=7960
2025-04-24 01:34:21.07: PodMonitor - _schedule_vnc_sync
2025-04-24 01:34:21.07: PodMonitor - Start Watching request https://10.0.0.22:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:34:21.07: PodMonitor - Watches https://10.0.0.22:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:34:25.05: VncKubernetes - wait event (qsize=15 timeout=120)
2025-04-24 01:34:25.05: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-24 01:34:25.05: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-24 01:34:25.05: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-24 01:34:25.05: VncKubernetes - wait event (qsize=14 timeout=120)
2025-04-24 01:34:25.05: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Endpoints ns=default)
VncEndpoints - Got ADDED Endpoints default:kubernetes:100a409f-5ee2-4449-a498-8199a803147c
2025-04-24 01:34:25.11: VncKubernetes - wait event (qsize=13 timeout=120)
2025-04-24 01:34:25.11: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Service ns=default)
VncService - Got ADDED Service default:kubernetes:942c1427-a35c-4ebc-b1c3-5ac9c74e3c8c
2025-04-24 01:34:27.05: VncKubernetes - wait event (qsize=12 timeout=120)
2025-04-24 01:34:27.05: VncKubernetes - Process event (name=kube-node-lease event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-node-lease:b2fdde1a-264c-4c96-bca9-89552e02f587
2025-04-24 01:34:29.80: VncKubernetes - wait event (qsize=11 timeout=120)
2025-04-24 01:34:29.80: VncKubernetes - Process event (name=kube-public event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-public:6050e1d0-e83f-41b2-b9ee-36b0092ad501
2025-04-24 01:34:32.44: VncKubernetes - wait event (qsize=10 timeout=120)
2025-04-24 01:34:32.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-24 01:34:32.44: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-24 01:34:32.44: VncKubernetes - wait event (qsize=9 timeout=120)
2025-04-24 01:34:32.44: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Service ns=kube-system)
VncService - Got ADDED Service kube-system:coredns:11f83fd5-45fb-4aac-b3c2-2280c9671fab
2025-04-24 01:34:35.33: VncKubernetes - wait event (qsize=8 timeout=120)
2025-04-24 01:34:35.33: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-24 01:34:35.33: VncKubernetes - vnc_sync - Service start
2025-04-24 01:34:35.33: VncKubernetes - vnc_sync - Service done
2025-04-24 01:34:35.33: VncKubernetes - wait event (qsize=7 timeout=120)
2025-04-24 01:34:35.33: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Endpoints ns=kube-system)
VncEndpoints - Got ADDED Endpoints kube-system:coredns:ddb9babe-e538-42b7-9d79-27e85d569c33
2025-04-24 01:34:35.44: VncKubernetes - wait event (qsize=6 timeout=120)
2025-04-24 01:34:35.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-24 01:34:35.44: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-24 01:34:35.44: VncKubernetes - wait event (qsize=5 timeout=120)
2025-04-24 01:34:35.44: VncKubernetes - Process event (name=coredns-77f7cc69db-7t9sf event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:coredns-77f7cc69db-7t9sf:d8d53619-1e66-4d2a-8bf7-8cb979d2b8e3
2025-04-24 01:34:37.05: VncKubernetes - wait event (qsize=4 timeout=120)
2025-04-24 01:34:37.05: VncKubernetes - Process event (name=kube-system event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-system:88e42389-3429-4b93-9b72-45f14214a87a
2025-04-24 01:34:37.06: PodMonitor - Received MODIFIED Pod kube-system:coredns-77f7cc69db-7t9sf:d8d53619-1e66-4d2a-8bf7-8cb979d2b8e3
2025-04-24 01:34:37.06: PodMonitor - Got MODIFIED Pod kube-system:coredns-77f7cc69db-7t9sf:d8d53619-1e66-4d2a-8bf7-8cb979d2b8e3
2025-04-24 01:34:37.06: PodMonitor - start process kube event
2025-04-24 01:34:37.06: empty line received
2025-04-24 01:34:37.06: PodMonitor - start process kube event
2025-04-24 01:34:39.52: VncKubernetes - wait event (qsize=4 timeout=120)
2025-04-24 01:34:39.52: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-24 01:34:39.52: VncKubernetes - vnc_sync - Namespace start
2025-04-24 01:34:39.52: VncKubernetes - vnc_sync - Namespace done
2025-04-24 01:34:39.52: VncKubernetes - wait event (qsize=3 timeout=120)
2025-04-24 01:34:39.52: VncKubernetes - Process event (name=dns-autoscaler-595558c478-c4lbx event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:dns-autoscaler-595558c478-c4lbx:f4f0e05b-f270-4197-b374-7c9be8301e42
2025-04-24 01:34:40.94: PodMonitor - Received MODIFIED Pod kube-system:dns-autoscaler-595558c478-c4lbx:f4f0e05b-f270-4197-b374-7c9be8301e42
2025-04-24 01:34:40.94: PodMonitor - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-c4lbx:f4f0e05b-f270-4197-b374-7c9be8301e42
2025-04-24 01:34:40.94: PodMonitor - start process kube event
2025-04-24 01:34:40.94: empty line received
2025-04-24 01:34:40.94: VncKubernetes - wait event (qsize=3 timeout=120)
2025-04-24 01:34:40.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-24 01:34:40.94: VncKubernetes - vnc_sync - Pod start
2025-04-24 01:34:40.94: VncKubernetes - vnc_sync - Pod done
2025-04-24 01:34:40.94: VncKubernetes - wait event (qsize=2 timeout=120)
2025-04-24 01:34:40.94: VncKubernetes - Process event (name=coredns-77f7cc69db-7t9sf event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:coredns-77f7cc69db-7t9sf:d8d53619-1e66-4d2a-8bf7-8cb979d2b8e3
2025-04-24 01:34:40.94: PodMonitor - start process kube event
2025-04-24 01:34:41.03: VncKubernetes - wait event (qsize=1 timeout=120)
2025-04-24 01:34:41.03: VncKubernetes - Process event (name=dns-autoscaler-595558c478-c4lbx event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-c4lbx:f4f0e05b-f270-4197-b374-7c9be8301e42
2025-04-24 01:34:41.13: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:34:44.70: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:34:44.70: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:34:44.70: PodMonitor - start process kube event
2025-04-24 01:34:44.70: empty line received
2025-04-24 01:34:44.70: PodMonitor - start process kube event
2025-04-24 01:34:58.98: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:34:58.98: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:34:58.98: PodMonitor - start process kube event
2025-04-24 01:34:58.98: empty line received
2025-04-24 01:34:58.98: PodMonitor - start process kube event
2025-04-24 01:35:00.15: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:35:00.15: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:35:00.15: PodMonitor - start process kube event
2025-04-24 01:35:00.15: empty line received
2025-04-24 01:35:00.15: PodMonitor - start process kube event
2025-04-24 01:35:20.83: IngressMonitor - Received BOOKMARK: oldResVer=7960 newResVer=8022
2025-04-24 01:35:20.83: IngressMonitor - start process kube event
2025-04-24 01:35:20.83: empty line received
2025-04-24 01:35:20.83: IngressMonitor - start process kube event
2025-04-24 01:35:21.47: PodMonitor - Received BOOKMARK: oldResVer=7960 newResVer=8025
2025-04-24 01:35:21.47: PodMonitor - start process kube event
2025-04-24 01:35:21.47: empty line received
2025-04-24 01:35:21.47: PodMonitor - start process kube event
2025-04-24 01:35:42.22: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:35:42.22: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:35:42.22: PodMonitor - start process kube event
2025-04-24 01:35:42.22: empty line received
2025-04-24 01:35:42.22: PodMonitor - start process kube event
2025-04-24 01:35:54.98: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:35:54.98: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:35:54.98: PodMonitor - start process kube event
2025-04-24 01:35:54.98: empty line received
2025-04-24 01:35:54.98: PodMonitor - start process kube event
2025-04-24 01:35:59.60: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:35:59.60: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:35:59.60: PodMonitor - start process kube event
2025-04-24 01:35:59.60: empty line received
2025-04-24 01:35:59.60: PodMonitor - start process kube event
2025-04-24 01:36:13.98: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:36:13.98: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:36:13.98: PodMonitor - start process kube event
2025-04-24 01:36:13.98: empty line received
2025-04-24 01:36:13.98: PodMonitor - start process kube event
2025-04-24 01:36:20.33: IngressMonitor - Received BOOKMARK: oldResVer=8022 newResVer=8022
2025-04-24 01:36:20.33: IngressMonitor - start process kube event
2025-04-24 01:36:20.33: empty line received
2025-04-24 01:36:20.33: IngressMonitor - start process kube event
2025-04-24 01:36:20.40: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=7960 newResVer=8069
2025-04-24 01:36:20.40: NetworkPolicyMonitor - start process kube event
2025-04-24 01:36:20.40: empty line received
2025-04-24 01:36:20.40: NetworkPolicyMonitor - start process kube event
2025-04-24 01:36:20.46: ServiceMonitor - Received BOOKMARK: oldResVer=7960 newResVer=8116
2025-04-24 01:36:20.46: ServiceMonitor - start process kube event
2025-04-24 01:36:20.46: empty line received
2025-04-24 01:36:20.46: ServiceMonitor - start process kube event
2025-04-24 01:36:20.89: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-24 01:36:20.89: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-24 01:36:20.89: NetworkMonitor - start process kube event
2025-04-24 01:36:20.89: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=7964
2025-04-24 01:36:20.89: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:36:20.89: EndPointMonitor - start process kube event
2025-04-24 01:36:20.89: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=7960
2025-04-24 01:36:20.89: EndPointMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:36:20.89: NetworkMonitor - Connect Kube API result 0
2025-04-24 01:36:20.89: NetworkMonitor - _schedule_vnc_sync
2025-04-24 01:36:20.89: NetworkMonitor - Start Watching request https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7964'})(timeout=120)
2025-04-24 01:36:20.89: EndPointMonitor - Connect Kube API result 0
2025-04-24 01:36:20.89: EndPointMonitor - _schedule_vnc_sync
2025-04-24 01:36:20.89: EndPointMonitor - Start Watching request https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:36:20.89: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-24 01:36:20.89: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-24 01:36:20.89: VncKubernetes - wait event (qsize=1 timeout=120)
2025-04-24 01:36:20.89: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-24 01:36:20.89: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-24 01:36:20.89: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:36:20.89: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-24 01:36:20.89: NamespaceMonitor - start process kube event
2025-04-24 01:36:20.89: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=7960
2025-04-24 01:36:20.89: NamespaceMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:36:20.89: NamespaceMonitor - Connect Kube API result 0
2025-04-24 01:36:20.89: NamespaceMonitor - _schedule_vnc_sync
2025-04-24 01:36:20.89: NamespaceMonitor - Start Watching request https://10.0.0.22:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:36:20.89: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-24 01:36:20.89: VncKubernetes - vnc_sync - Namespace start
2025-04-24 01:36:20.89: VncKubernetes - vnc_sync - Namespace done
2025-04-24 01:36:20.89: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:36:20.90: EndPointMonitor - Watches https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:36:20.90: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7964'})
2025-04-24 01:36:20.90: NamespaceMonitor - Watches https://10.0.0.22:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:36:21.24: PodMonitor - Received BOOKMARK: oldResVer=8025 newResVer=8134
2025-04-24 01:36:21.24: PodMonitor - start process kube event
2025-04-24 01:36:21.24: empty line received
2025-04-24 01:36:21.24: PodMonitor - start process kube event
2025-04-24 01:36:27.28: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:36:27.28: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:36:27.28: PodMonitor - start process kube event
2025-04-24 01:36:27.28: empty line received
2025-04-24 01:36:27.28: PodMonitor - start process kube event
2025-04-24 01:37:20.35: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=8069 newResVer=8069
2025-04-24 01:37:20.35: NetworkPolicyMonitor - start process kube event
2025-04-24 01:37:20.35: empty line received
2025-04-24 01:37:20.35: NetworkPolicyMonitor - start process kube event
2025-04-24 01:37:20.58: ServiceMonitor - Received BOOKMARK: oldResVer=8116 newResVer=8116
2025-04-24 01:37:20.59: ServiceMonitor - start process kube event
2025-04-24 01:37:20.59: empty line received
2025-04-24 01:37:20.59: ServiceMonitor - start process kube event
2025-04-24 01:37:20.92: IngressMonitor - Received BOOKMARK: oldResVer=8022 newResVer=8022
2025-04-24 01:37:20.92: IngressMonitor - start process kube event
2025-04-24 01:37:20.92: empty line received
2025-04-24 01:37:20.92: IngressMonitor - start process kube event
2025-04-24 01:37:21.74: PodMonitor - Received BOOKMARK: oldResVer=8134 newResVer=8159
2025-04-24 01:37:21.74: PodMonitor - start process kube event
2025-04-24 01:37:21.74: empty line received
2025-04-24 01:37:21.74: PodMonitor - start process kube event
2025-04-24 01:37:26.51: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:37:26.51: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:37:26.51: PodMonitor - start process kube event
2025-04-24 01:37:26.51: empty line received
2025-04-24 01:37:26.51: PodMonitor - start process kube event
2025-04-24 01:37:40.99: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:37:40.99: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:37:40.99: PodMonitor - start process kube event
2025-04-24 01:37:40.99: empty line received
2025-04-24 01:37:40.99: PodMonitor - start process kube event
2025-04-24 01:38:07.38: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:38:07.38: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:38:07.38: PodMonitor - start process kube event
2025-04-24 01:38:07.38: empty line received
2025-04-24 01:38:07.38: PodMonitor - start process kube event
2025-04-24 01:38:20.02: IngressMonitor - Received BOOKMARK: oldResVer=8022 newResVer=8022
2025-04-24 01:38:20.02: IngressMonitor - start process kube event
2025-04-24 01:38:20.02: empty line received
2025-04-24 01:38:20.02: IngressMonitor - start process kube event
2025-04-24 01:38:20.40: ServiceMonitor - Received BOOKMARK: oldResVer=8116 newResVer=8116
2025-04-24 01:38:20.40: ServiceMonitor - start process kube event
2025-04-24 01:38:20.40: empty line received
2025-04-24 01:38:20.40: ServiceMonitor - start process kube event
2025-04-24 01:38:20.87: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=8069 newResVer=8069
2025-04-24 01:38:20.87: NetworkPolicyMonitor - start process kube event
2025-04-24 01:38:20.87: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-24 01:38:20.87: empty line received
2025-04-24 01:38:20.87: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-24 01:38:20.87: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-24 01:38:20.87: NetworkPolicyMonitor - start process kube event
2025-04-24 01:38:20.88: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-24 01:38:20.88: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:38:20.90: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-24 01:38:20.90: EndPointMonitor - start process kube event
2025-04-24 01:38:20.90: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=7960
2025-04-24 01:38:20.90: EndPointMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:38:20.90: EndPointMonitor - Connect Kube API result 0
2025-04-24 01:38:20.90: EndPointMonitor - _schedule_vnc_sync
2025-04-24 01:38:20.90: EndPointMonitor - Start Watching request https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:38:20.90: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-24 01:38:20.90: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-24 01:38:20.91: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:38:20.91: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-24 01:38:20.91: NetworkMonitor - start process kube event
2025-04-24 01:38:20.91: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=7964
2025-04-24 01:38:20.91: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:38:20.91: NetworkMonitor - Connect Kube API result 0
2025-04-24 01:38:20.91: NetworkMonitor - _schedule_vnc_sync
2025-04-24 01:38:20.91: NetworkMonitor - Start Watching request https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7964'})(timeout=120)
2025-04-24 01:38:20.91: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-24 01:38:20.91: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-24 01:38:20.91: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:38:20.91: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-24 01:38:20.91: NamespaceMonitor - start process kube event
2025-04-24 01:38:20.91: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=7960
2025-04-24 01:38:20.91: NamespaceMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:38:20.91: NamespaceMonitor - Connect Kube API result 0
2025-04-24 01:38:20.91: NamespaceMonitor - _schedule_vnc_sync
2025-04-24 01:38:20.91: NamespaceMonitor - Start Watching request https://10.0.0.22:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:38:20.91: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-24 01:38:20.91: VncKubernetes - vnc_sync - Namespace start
2025-04-24 01:38:20.91: VncKubernetes - vnc_sync - Namespace done
2025-04-24 01:38:20.91: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:38:20.92: EndPointMonitor - Watches https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:38:20.92: NamespaceMonitor - Watches https://10.0.0.22:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:38:20.92: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7964'})
2025-04-24 01:38:21.90: PodMonitor - Received BOOKMARK: oldResVer=8159 newResVer=8305
2025-04-24 01:38:21.90: PodMonitor - start process kube event
2025-04-24 01:38:21.90: PodMonitor - _schedule_vnc_sync
2025-04-24 01:38:21.90: empty line received
2025-04-24 01:38:21.90: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-24 01:38:21.90: VncKubernetes - vnc_sync - Pod start
2025-04-24 01:38:21.90: VncKubernetes - vnc_sync - Pod done
2025-04-24 01:38:21.90: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:38:21.90: PodMonitor - start process kube event
2025-04-24 01:38:36.04: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:38:36.04: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:38:36.04: PodMonitor - start process kube event
2025-04-24 01:38:36.04: empty line received
2025-04-24 01:38:36.04: PodMonitor - start process kube event
2025-04-24 01:38:49.99: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:38:49.99: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:38:49.99: PodMonitor - start process kube event
2025-04-24 01:38:49.99: empty line received
2025-04-24 01:38:49.99: PodMonitor - start process kube event
2025-04-24 01:39:07.81: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:39:07.81: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:39:07.81: PodMonitor - start process kube event
2025-04-24 01:39:07.81: empty line received
2025-04-24 01:39:07.81: PodMonitor - start process kube event
2025-04-24 01:39:18.98: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:39:18.98: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:39:18.98: PodMonitor - start process kube event
2025-04-24 01:39:18.98: empty line received
2025-04-24 01:39:18.98: PodMonitor - start process kube event
2025-04-24 01:39:20.89: IngressMonitor - Received BOOKMARK: oldResVer=8022 newResVer=8022
2025-04-24 01:39:20.89: IngressMonitor - start process kube event
2025-04-24 01:39:20.89: IngressMonitor - _schedule_vnc_sync
2025-04-24 01:39:20.89: empty line received
2025-04-24 01:39:20.89: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-24 01:39:20.89: VncKubernetes - vnc_sync - Ingress start
2025-04-24 01:39:20.89: VncKubernetes - vnc_sync - Ingress done
2025-04-24 01:39:20.89: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:39:20.89: IngressMonitor - start process kube event
2025-04-24 01:39:20.96: ServiceMonitor - Received BOOKMARK: oldResVer=8116 newResVer=8116
2025-04-24 01:39:20.96: ServiceMonitor - start process kube event
2025-04-24 01:39:20.96: ServiceMonitor - _schedule_vnc_sync
2025-04-24 01:39:20.96: empty line received
2025-04-24 01:39:20.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-24 01:39:20.96: VncKubernetes - vnc_sync - Service start
2025-04-24 01:39:20.96: VncKubernetes - vnc_sync - Service done
2025-04-24 01:39:20.96: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:39:20.96: ServiceMonitor - start process kube event
2025-04-24 01:39:21.02: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=8069 newResVer=8069
2025-04-24 01:39:21.02: NetworkPolicyMonitor - start process kube event
2025-04-24 01:39:21.02: empty line received
2025-04-24 01:39:21.02: NetworkPolicyMonitor - start process kube event
2025-04-24 01:39:21.66: NamespaceMonitor - Received BOOKMARK: oldResVer=7960 newResVer=8368
2025-04-24 01:39:21.66: NamespaceMonitor - start process kube event
2025-04-24 01:39:21.66: empty line received
2025-04-24 01:39:21.66: NamespaceMonitor - start process kube event
2025-04-24 01:39:21.96: PodMonitor - Received BOOKMARK: oldResVer=8305 newResVer=8416
2025-04-24 01:39:21.96: PodMonitor - start process kube event
2025-04-24 01:39:21.96: empty line received
2025-04-24 01:39:21.96: PodMonitor - start process kube event
2025-04-24 01:40:20.75: IngressMonitor - Received BOOKMARK: oldResVer=8022 newResVer=8022
2025-04-24 01:40:20.75: IngressMonitor - start process kube event
2025-04-24 01:40:20.75: empty line received
2025-04-24 01:40:20.75: IngressMonitor - start process kube event
2025-04-24 01:40:20.92: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-24 01:40:20.92: EndPointMonitor - start process kube event
2025-04-24 01:40:20.92: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=7960
2025-04-24 01:40:20.92: EndPointMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:40:20.92: EndPointMonitor - Connect Kube API result 0
2025-04-24 01:40:20.92: EndPointMonitor - _schedule_vnc_sync
2025-04-24 01:40:20.92: EndPointMonitor - Start Watching request https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:40:20.92: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-24 01:40:20.92: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-24 01:40:20.92: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:40:20.92: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-24 01:40:20.92: NetworkMonitor - start process kube event
2025-04-24 01:40:20.92: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=7964
2025-04-24 01:40:20.92: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:40:20.92: NetworkMonitor - Connect Kube API result 0
2025-04-24 01:40:20.92: NetworkMonitor - _schedule_vnc_sync
2025-04-24 01:40:20.92: NetworkMonitor - Start Watching request https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7964'})(timeout=120)
2025-04-24 01:40:20.92: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-24 01:40:20.92: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-24 01:40:20.92: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:40:20.93: EndPointMonitor - Watches https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:40:20.93: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7964'})
2025-04-24 01:40:21.50: ServiceMonitor - Received BOOKMARK: oldResVer=8116 newResVer=8116
2025-04-24 01:40:21.50: ServiceMonitor - start process kube event
2025-04-24 01:40:21.50: empty line received
2025-04-24 01:40:21.50: ServiceMonitor - start process kube event
2025-04-24 01:40:21.84: NamespaceMonitor - Received BOOKMARK: oldResVer=8368 newResVer=8368
2025-04-24 01:40:21.84: NamespaceMonitor - start process kube event
2025-04-24 01:40:21.84: empty line received
2025-04-24 01:40:21.84: NamespaceMonitor - start process kube event
2025-04-24 01:40:22.03: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=8069 newResVer=8069
2025-04-24 01:40:22.03: NetworkPolicyMonitor - start process kube event
2025-04-24 01:40:22.03: empty line received
2025-04-24 01:40:22.03: NetworkPolicyMonitor - start process kube event
2025-04-24 01:40:22.47: PodMonitor - Received BOOKMARK: oldResVer=8416 newResVer=8416
2025-04-24 01:40:22.47: PodMonitor - start process kube event
2025-04-24 01:40:22.47: empty line received
2025-04-24 01:40:22.47: PodMonitor - start process kube event
2025-04-24 01:40:41.78: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:40:41.78: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:40:41.78: PodMonitor - start process kube event
2025-04-24 01:40:41.78: empty line received
2025-04-24 01:40:41.78: PodMonitor - start process kube event
2025-04-24 01:41:20.83: IngressMonitor - Received BOOKMARK: oldResVer=8022 newResVer=8022
2025-04-24 01:41:20.83: IngressMonitor - start process kube event
2025-04-24 01:41:20.83: empty line received
2025-04-24 01:41:20.83: IngressMonitor - start process kube event
2025-04-24 01:41:21.38: ServiceMonitor - Received BOOKMARK: oldResVer=8116 newResVer=8116
2025-04-24 01:41:21.38: ServiceMonitor - start process kube event
2025-04-24 01:41:21.38: empty line received
2025-04-24 01:41:21.38: ServiceMonitor - start process kube event
2025-04-24 01:41:21.92: NamespaceMonitor - Received BOOKMARK: oldResVer=8368 newResVer=8368
2025-04-24 01:41:21.92: NamespaceMonitor - start process kube event
2025-04-24 01:41:21.92: empty line received
2025-04-24 01:41:21.92: NamespaceMonitor - start process kube event
2025-04-24 01:41:22.35: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=8069 newResVer=8069
2025-04-24 01:41:22.35: NetworkPolicyMonitor - start process kube event
2025-04-24 01:41:22.35: empty line received
2025-04-24 01:41:22.35: NetworkPolicyMonitor - start process kube event
2025-04-24 01:41:22.83: PodMonitor - Received BOOKMARK: oldResVer=8416 newResVer=8536
2025-04-24 01:41:22.83: PodMonitor - start process kube event
2025-04-24 01:41:22.83: empty line received
2025-04-24 01:41:22.83: PodMonitor - start process kube event
2025-04-24 01:41:42.03: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:41:42.03: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:41:42.03: PodMonitor - start process kube event
2025-04-24 01:41:42.03: empty line received
2025-04-24 01:41:42.03: PodMonitor - start process kube event
2025-04-24 01:41:43.07: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:41:43.07: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:41:43.07: PodMonitor - start process kube event
2025-04-24 01:41:43.07: empty line received
2025-04-24 01:41:43.07: PodMonitor - start process kube event
2025-04-24 01:42:20.41: IngressMonitor - Received BOOKMARK: oldResVer=8022 newResVer=8022
2025-04-24 01:42:20.41: IngressMonitor - start process kube event
2025-04-24 01:42:20.41: empty line received
2025-04-24 01:42:20.41: IngressMonitor - start process kube event
2025-04-24 01:42:20.92: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:42:20.93: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-24 01:42:20.93: EndPointMonitor - start process kube event
2025-04-24 01:42:20.93: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=7960
2025-04-24 01:42:20.93: EndPointMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:42:20.93: EndPointMonitor - Connect Kube API result 0
2025-04-24 01:42:20.93: EndPointMonitor - _schedule_vnc_sync
2025-04-24 01:42:20.93: EndPointMonitor - Start Watching request https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})(timeout=120)
2025-04-24 01:42:20.93: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-24 01:42:20.93: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-24 01:42:20.93: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:42:20.93: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-24 01:42:20.93: NetworkMonitor - start process kube event
2025-04-24 01:42:20.93: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=7964
2025-04-24 01:42:20.93: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:42:20.93: NetworkMonitor - Connect Kube API result 0
2025-04-24 01:42:20.93: NetworkMonitor - _schedule_vnc_sync
2025-04-24 01:42: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': '7964'})(timeout=120)
2025-04-24 01:42:20.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-24 01:42:20.94: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-24 01:42:20.94: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:42:20.94: EndPointMonitor - Watches https://10.0.0.22:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7960'})
2025-04-24 01:42:20.94: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7964'})
2025-04-24 01:42:21.04: ServiceMonitor - Received BOOKMARK: oldResVer=8116 newResVer=8116
2025-04-24 01:42:21.04: ServiceMonitor - start process kube event
2025-04-24 01:42:21.04: empty line received
2025-04-24 01:42:21.04: ServiceMonitor - start process kube event
2025-04-24 01:42:21.99: PodMonitor - Received BOOKMARK: oldResVer=8536 newResVer=8628
2025-04-24 01:42:21.99: PodMonitor - start process kube event
2025-04-24 01:42:21.99: PodMonitor - _schedule_vnc_sync
2025-04-24 01:42:21.99: empty line received
2025-04-24 01:42:21.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-24 01:42:21.99: VncKubernetes - vnc_sync - Pod start
2025-04-24 01:42:21.99: VncKubernetes - vnc_sync - Pod done
2025-04-24 01:42:21.99: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:42:21.99: PodMonitor - start process kube event
2025-04-24 01:42:22.41: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=8069 newResVer=8069
2025-04-24 01:42:22.41: NetworkPolicyMonitor - start process kube event
2025-04-24 01:42:22.41: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-24 01:42:22.41: empty line received
2025-04-24 01:42:22.41: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-24 01:42:22.41: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-24 01:42:22.41: NetworkPolicyMonitor - start process kube event
2025-04-24 01:42:22.41: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-24 01:42:22.41: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:42:22.67: NamespaceMonitor - Received BOOKMARK: oldResVer=8368 newResVer=8368
2025-04-24 01:42:22.67: NamespaceMonitor - start process kube event
2025-04-24 01:42:22.67: NamespaceMonitor - _schedule_vnc_sync
2025-04-24 01:42:22.67: empty line received
2025-04-24 01:42:22.67: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-24 01:42:22.67: VncKubernetes - vnc_sync - Namespace start
2025-04-24 01:42:22.67: VncKubernetes - vnc_sync - Namespace done
2025-04-24 01:42:22.67: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:42:22.67: NamespaceMonitor - start process kube event
2025-04-24 01:43:20.98: IngressMonitor - Received BOOKMARK: oldResVer=8022 newResVer=8022
2025-04-24 01:43:20.98: IngressMonitor - start process kube event
2025-04-24 01:43:20.98: IngressMonitor - _schedule_vnc_sync
2025-04-24 01:43:20.98: empty line received
2025-04-24 01:43:20.98: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-24 01:43:20.98: VncKubernetes - vnc_sync - Ingress start
2025-04-24 01:43:20.98: VncKubernetes - vnc_sync - Ingress done
2025-04-24 01:43:20.98: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:43:20.98: IngressMonitor - start process kube event
2025-04-24 01:43:21.73: ServiceMonitor - Received BOOKMARK: oldResVer=8116 newResVer=8116
2025-04-24 01:43:21.73: ServiceMonitor - start process kube event
2025-04-24 01:43:21.73: ServiceMonitor - _schedule_vnc_sync
2025-04-24 01:43:21.73: empty line received
2025-04-24 01:43:21.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-24 01:43:21.73: VncKubernetes - vnc_sync - Service start
2025-04-24 01:43:21.73: VncKubernetes - vnc_sync - Service done
2025-04-24 01:43:21.73: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:43:21.73: ServiceMonitor - start process kube event
2025-04-24 01:43:22.06: EndPointMonitor - Received BOOKMARK: oldResVer=7960 newResVer=8621
2025-04-24 01:43:22.06: EndPointMonitor - start process kube event
2025-04-24 01:43:22.06: empty line received
2025-04-24 01:43:22.06: EndPointMonitor - start process kube event
2025-04-24 01:43:22.52: PodMonitor - Received BOOKMARK: oldResVer=8628 newResVer=8628
2025-04-24 01:43:22.52: PodMonitor - start process kube event
2025-04-24 01:43:22.52: empty line received
2025-04-24 01:43:22.52: PodMonitor - start process kube event
2025-04-24 01:43:22.77: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=8069 newResVer=8069
2025-04-24 01:43:22.77: NetworkPolicyMonitor - start process kube event
2025-04-24 01:43:22.77: empty line received
2025-04-24 01:43:22.77: NetworkPolicyMonitor - start process kube event
2025-04-24 01:43:22.78: NamespaceMonitor - Received BOOKMARK: oldResVer=8368 newResVer=8368
2025-04-24 01:43:22.78: NamespaceMonitor - start process kube event
2025-04-24 01:43:22.78: empty line received
2025-04-24 01:43:22.78: NamespaceMonitor - start process kube event
2025-04-24 01:43:37.48: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:43:37.48: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:43:37.48: PodMonitor - start process kube event
2025-04-24 01:43:37.48: empty line received
2025-04-24 01:43:37.48: PodMonitor - start process kube event
2025-04-24 01:43:52.98: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:43:52.98: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:43:52.98: PodMonitor - start process kube event
2025-04-24 01:43:52.98: empty line received
2025-04-24 01:43:52.98: PodMonitor - start process kube event
2025-04-24 01:44:20.94: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.22', port=6443): Read timed out.
2025-04-24 01:44:20.95: NetworkMonitor - start process kube event
2025-04-24 01:44:20.95: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=7964
2025-04-24 01:44:20.95: NetworkMonitor - Try to connect Kube API 10.0.0.22:6443
2025-04-24 01:44:20.95: NetworkMonitor - Connect Kube API result 0
2025-04-24 01:44:20.95: NetworkMonitor - _schedule_vnc_sync
2025-04-24 01:44: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': '7964'})(timeout=120)
2025-04-24 01:44:20.95: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-24 01:44:20.95: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-24 01:44:20.95: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:44:20.95: NetworkMonitor - Watches https://10.0.0.22:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '7964'})
2025-04-24 01:44:21.19: IngressMonitor - Received BOOKMARK: oldResVer=8022 newResVer=8022
2025-04-24 01:44:21.19: IngressMonitor - start process kube event
2025-04-24 01:44:21.19: empty line received
2025-04-24 01:44:21.19: IngressMonitor - start process kube event
2025-04-24 01:44:21.66: ServiceMonitor - Received BOOKMARK: oldResVer=8116 newResVer=8116
2025-04-24 01:44:21.66: ServiceMonitor - start process kube event
2025-04-24 01:44:21.66: empty line received
2025-04-24 01:44:21.66: ServiceMonitor - start process kube event
2025-04-24 01:44:22.22: NamespaceMonitor - Received BOOKMARK: oldResVer=8368 newResVer=8368
2025-04-24 01:44:22.22: NamespaceMonitor - start process kube event
2025-04-24 01:44:22.22: empty line received
2025-04-24 01:44:22.22: NamespaceMonitor - start process kube event
2025-04-24 01:44:22.41: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=8069 newResVer=8069
2025-04-24 01:44:22.41: NetworkPolicyMonitor - start process kube event
2025-04-24 01:44:22.41: empty line received
2025-04-24 01:44:22.41: NetworkPolicyMonitor - start process kube event
2025-04-24 01:44:22.53: PodMonitor - Received BOOKMARK: oldResVer=8628 newResVer=8815
2025-04-24 01:44:22.53: PodMonitor - start process kube event
2025-04-24 01:44:22.53: empty line received
2025-04-24 01:44:22.53: PodMonitor - start process kube event
2025-04-24 01:44:22.77: EndPointMonitor - Received BOOKMARK: oldResVer=8621 newResVer=8621
2025-04-24 01:44:22.77: EndPointMonitor - start process kube event
2025-04-24 01:44:22.77: empty line received
2025-04-24 01:44:22.77: EndPointMonitor - start process kube event
2025-04-24 01:44:30.60: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:44:30.60: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:44:30.60: PodMonitor - start process kube event
2025-04-24 01:44:30.60: empty line received
2025-04-24 01:44:30.60: PodMonitor - start process kube event
2025-04-24 01:45:21.89: NetworkMonitor - Received BOOKMARK: oldResVer=7964 newResVer=8934
2025-04-24 01:45:21.89: NetworkMonitor - start process kube event
2025-04-24 01:45:21.89: empty line received
2025-04-24 01:45:21.89: NetworkMonitor - start process kube event
2025-04-24 01:45:22.10: ServiceMonitor - Received BOOKMARK: oldResVer=8116 newResVer=8116
2025-04-24 01:45:22.10: ServiceMonitor - start process kube event
2025-04-24 01:45:22.10: empty line received
2025-04-24 01:45:22.10: ServiceMonitor - start process kube event
2025-04-24 01:45:22.12: PodMonitor - Received BOOKMARK: oldResVer=8815 newResVer=8874
2025-04-24 01:45:22.12: PodMonitor - start process kube event
2025-04-24 01:45:22.12: empty line received
2025-04-24 01:45:22.12: PodMonitor - start process kube event
2025-04-24 01:45:22.15: IngressMonitor - Received BOOKMARK: oldResVer=8022 newResVer=8022
2025-04-24 01:45:22.15: IngressMonitor - start process kube event
2025-04-24 01:45:22.15: empty line received
2025-04-24 01:45:22.15: IngressMonitor - start process kube event
2025-04-24 01:45:22.33: NamespaceMonitor - Received BOOKMARK: oldResVer=8368 newResVer=8368
2025-04-24 01:45:22.33: NamespaceMonitor - start process kube event
2025-04-24 01:45:22.33: empty line received
2025-04-24 01:45:22.33: NamespaceMonitor - start process kube event
2025-04-24 01:45:22.61: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=8069 newResVer=8069
2025-04-24 01:45:22.62: NetworkPolicyMonitor - start process kube event
2025-04-24 01:45:22.62: empty line received
2025-04-24 01:45:22.62: NetworkPolicyMonitor - start process kube event
2025-04-24 01:45:22.89: EndPointMonitor - Received BOOKMARK: oldResVer=8621 newResVer=8621
2025-04-24 01:45:22.89: EndPointMonitor - start process kube event
2025-04-24 01:45:22.89: empty line received
2025-04-24 01:45:22.89: EndPointMonitor - start process kube event
2025-04-24 01:45:30.85: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:45:30.85: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:45:30.85: PodMonitor - start process kube event
2025-04-24 01:45:30.85: empty line received
2025-04-24 01:45:30.85: PodMonitor - start process kube event
2025-04-24 01:45:43.98: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:45:43.98: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:45:43.98: PodMonitor - start process kube event
2025-04-24 01:45:43.98: empty line received
2025-04-24 01:45:43.98: PodMonitor - start process kube event
2025-04-24 01:46:20.95: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:46:22.24: NetworkMonitor - Received BOOKMARK: oldResVer=8934 newResVer=8934
2025-04-24 01:46:22.24: NetworkMonitor - start process kube event
2025-04-24 01:46:22.24: empty line received
2025-04-24 01:46:22.24: NetworkMonitor - start process kube event
2025-04-24 01:46:22.24: ServiceMonitor - Received BOOKMARK: oldResVer=8116 newResVer=8116
2025-04-24 01:46:22.24: ServiceMonitor - start process kube event
2025-04-24 01:46:22.24: empty line received
2025-04-24 01:46:22.24: ServiceMonitor - start process kube event
2025-04-24 01:46:22.34: PodMonitor - Received BOOKMARK: oldResVer=8874 newResVer=8982
2025-04-24 01:46:22.34: PodMonitor - start process kube event
2025-04-24 01:46:22.34: PodMonitor - _schedule_vnc_sync
2025-04-24 01:46:22.34: empty line received
2025-04-24 01:46:22.34: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-24 01:46:22.34: VncKubernetes - vnc_sync - Pod start
2025-04-24 01:46:22.34: VncKubernetes - vnc_sync - Pod done
2025-04-24 01:46:22.34: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:46:22.34: PodMonitor - start process kube event
2025-04-24 01:46:22.50: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=8069 newResVer=9034
2025-04-24 01:46:22.50: NetworkPolicyMonitor - start process kube event
2025-04-24 01:46:22.50: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-24 01:46:22.50: empty line received
2025-04-24 01:46:22.50: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-24 01:46:22.50: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-24 01:46:22.50: NetworkPolicyMonitor - start process kube event
2025-04-24 01:46:22.51: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-24 01:46:22.51: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:46:22.73: NamespaceMonitor - Received BOOKMARK: oldResVer=8368 newResVer=8368
2025-04-24 01:46:22.73: NamespaceMonitor - start process kube event
2025-04-24 01:46:22.73: NamespaceMonitor - _schedule_vnc_sync
2025-04-24 01:46:22.73: empty line received
2025-04-24 01:46:22.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-24 01:46:22.73: VncKubernetes - vnc_sync - Namespace start
2025-04-24 01:46:22.73: VncKubernetes - vnc_sync - Namespace done
2025-04-24 01:46:22.73: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:46:22.73: NamespaceMonitor - start process kube event
2025-04-24 01:46:22.79: EndPointMonitor - Received BOOKMARK: oldResVer=8621 newResVer=8621
2025-04-24 01:46:22.79: EndPointMonitor - start process kube event
2025-04-24 01:46:22.79: EndPointMonitor - _schedule_vnc_sync
2025-04-24 01:46:22.79: empty line received
2025-04-24 01:46:22.79: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-24 01:46:22.79: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-24 01:46:22.79: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:46:22.79: EndPointMonitor - start process kube event
2025-04-24 01:46:22.89: IngressMonitor - Received BOOKMARK: oldResVer=8022 newResVer=8988
2025-04-24 01:46:22.89: IngressMonitor - start process kube event
2025-04-24 01:46:22.89: empty line received
2025-04-24 01:46:22.89: IngressMonitor - start process kube event
2025-04-24 01:47:22.42: NamespaceMonitor - Received BOOKMARK: oldResVer=8368 newResVer=8368
2025-04-24 01:47:22.42: NamespaceMonitor - start process kube event
2025-04-24 01:47:22.42: empty line received
2025-04-24 01:47:22.42: NamespaceMonitor - start process kube event
2025-04-24 01:47:22.52: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9034 newResVer=9034
2025-04-24 01:47:22.52: NetworkPolicyMonitor - start process kube event
2025-04-24 01:47:22.52: empty line received
2025-04-24 01:47:22.52: NetworkPolicyMonitor - start process kube event
2025-04-24 01:47:22.70: PodMonitor - Received BOOKMARK: oldResVer=8982 newResVer=8982
2025-04-24 01:47:22.70: PodMonitor - start process kube event
2025-04-24 01:47:22.70: empty line received
2025-04-24 01:47:22.70: PodMonitor - start process kube event
2025-04-24 01:47:22.90: NetworkMonitor - Received BOOKMARK: oldResVer=8934 newResVer=8934
2025-04-24 01:47:22.90: NetworkMonitor - start process kube event
2025-04-24 01:47:22.90: empty line received
2025-04-24 01:47:22.90: NetworkMonitor - start process kube event
2025-04-24 01:47:22.91: EndPointMonitor - Received BOOKMARK: oldResVer=8621 newResVer=8621
2025-04-24 01:47:22.91: EndPointMonitor - start process kube event
2025-04-24 01:47:22.91: empty line received
2025-04-24 01:47:22.91: EndPointMonitor - start process kube event
2025-04-24 01:47:22.96: ServiceMonitor - Received BOOKMARK: oldResVer=8116 newResVer=9086
2025-04-24 01:47:22.96: ServiceMonitor - start process kube event
2025-04-24 01:47:22.96: ServiceMonitor - _schedule_vnc_sync
2025-04-24 01:47:22.96: empty line received
2025-04-24 01:47:22.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-24 01:47:22.96: VncKubernetes - vnc_sync - Service start
2025-04-24 01:47:22.96: VncKubernetes - vnc_sync - Service done
2025-04-24 01:47:22.96: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:47:22.96: ServiceMonitor - start process kube event
2025-04-24 01:47:23.00: IngressMonitor - Received BOOKMARK: oldResVer=8988 newResVer=8988
2025-04-24 01:47:23.00: IngressMonitor - start process kube event
2025-04-24 01:47:23.00: IngressMonitor - _schedule_vnc_sync
2025-04-24 01:47:23.00: empty line received
2025-04-24 01:47:23.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-24 01:47:23.00: VncKubernetes - vnc_sync - Ingress start
2025-04-24 01:47:23.00: VncKubernetes - vnc_sync - Ingress done
2025-04-24 01:47:23.00: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:47:23.00: IngressMonitor - start process kube event
2025-04-24 01:48:22.12: PodMonitor - Received BOOKMARK: oldResVer=8982 newResVer=8982
2025-04-24 01:48:22.12: PodMonitor - start process kube event
2025-04-24 01:48:22.12: empty line received
2025-04-24 01:48:22.12: PodMonitor - start process kube event
2025-04-24 01:48:22.12: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9034 newResVer=9034
2025-04-24 01:48:22.12: NetworkPolicyMonitor - start process kube event
2025-04-24 01:48:22.12: empty line received
2025-04-24 01:48:22.12: NetworkPolicyMonitor - start process kube event
2025-04-24 01:48:22.34: NamespaceMonitor - Received BOOKMARK: oldResVer=8368 newResVer=8368
2025-04-24 01:48:22.34: NamespaceMonitor - start process kube event
2025-04-24 01:48:22.34: empty line received
2025-04-24 01:48:22.34: NamespaceMonitor - start process kube event
2025-04-24 01:48:22.83: IngressMonitor - Received BOOKMARK: oldResVer=8988 newResVer=8988
2025-04-24 01:48:22.83: IngressMonitor - start process kube event
2025-04-24 01:48:22.83: empty line received
2025-04-24 01:48:22.83: IngressMonitor - start process kube event
2025-04-24 01:48:23.09: NetworkMonitor - Received BOOKMARK: oldResVer=8934 newResVer=8934
2025-04-24 01:48:23.09: NetworkMonitor - start process kube event
2025-04-24 01:48:23.09: NetworkMonitor - _schedule_vnc_sync
2025-04-24 01:48:23.09: empty line received
2025-04-24 01:48:23.09: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-24 01:48:23.09: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-24 01:48:23.09: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:48:23.09: NetworkMonitor - start process kube event
2025-04-24 01:48:23.21: ServiceMonitor - Received BOOKMARK: oldResVer=9086 newResVer=9086
2025-04-24 01:48:23.21: ServiceMonitor - start process kube event
2025-04-24 01:48:23.21: empty line received
2025-04-24 01:48:23.21: ServiceMonitor - start process kube event
2025-04-24 01:48:24.05: EndPointMonitor - Received BOOKMARK: oldResVer=8621 newResVer=8621
2025-04-24 01:48:24.05: EndPointMonitor - start process kube event
2025-04-24 01:48:24.05: empty line received
2025-04-24 01:48:24.05: EndPointMonitor - start process kube event
2025-04-24 01:48:48.90: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:48:48.90: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:48:48.90: PodMonitor - start process kube event
2025-04-24 01:48:48.90: empty line received
2025-04-24 01:48:48.90: PodMonitor - start process kube event
2025-04-24 01:49:03.98: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:49:03.98: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:49:03.98: PodMonitor - start process kube event
2025-04-24 01:49:03.98: empty line received
2025-04-24 01:49:03.98: PodMonitor - start process kube event
2025-04-24 01:49:22.06: IngressMonitor - Received BOOKMARK: oldResVer=8988 newResVer=8988
2025-04-24 01:49:22.06: IngressMonitor - start process kube event
2025-04-24 01:49:22.06: empty line received
2025-04-24 01:49:22.06: IngressMonitor - start process kube event
2025-04-24 01:49:22.10: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9034 newResVer=9034
2025-04-24 01:49:22.10: NetworkPolicyMonitor - start process kube event
2025-04-24 01:49:22.10: empty line received
2025-04-24 01:49:22.10: NetworkPolicyMonitor - start process kube event
2025-04-24 01:49:22.47: NamespaceMonitor - Received BOOKMARK: oldResVer=8368 newResVer=9256
2025-04-24 01:49:22.47: NamespaceMonitor - start process kube event
2025-04-24 01:49:22.47: empty line received
2025-04-24 01:49:22.47: NamespaceMonitor - start process kube event
2025-04-24 01:49:22.99: PodMonitor - Received BOOKMARK: oldResVer=8982 newResVer=9276
2025-04-24 01:49:22.99: PodMonitor - start process kube event
2025-04-24 01:49:22.99: empty line received
2025-04-24 01:49:22.99: PodMonitor - start process kube event
2025-04-24 01:49:23.71: NetworkMonitor - Received BOOKMARK: oldResVer=8934 newResVer=8934
2025-04-24 01:49:23.71: NetworkMonitor - start process kube event
2025-04-24 01:49:23.71: empty line received
2025-04-24 01:49:23.71: NetworkMonitor - start process kube event
2025-04-24 01:49:23.75: ServiceMonitor - Received BOOKMARK: oldResVer=9086 newResVer=9086
2025-04-24 01:49:23.75: ServiceMonitor - start process kube event
2025-04-24 01:49:23.75: empty line received
2025-04-24 01:49:23.75: ServiceMonitor - start process kube event
2025-04-24 01:49:23.97: EndPointMonitor - Received BOOKMARK: oldResVer=8621 newResVer=8621
2025-04-24 01:49:23.97: EndPointMonitor - start process kube event
2025-04-24 01:49:23.97: empty line received
2025-04-24 01:49:23.97: EndPointMonitor - start process kube event
2025-04-24 01:50:22.02: NamespaceMonitor - Received BOOKMARK: oldResVer=9256 newResVer=9256
2025-04-24 01:50:22.02: NamespaceMonitor - start process kube event
2025-04-24 01:50:22.02: empty line received
2025-04-24 01:50:22.02: NamespaceMonitor - start process kube event
2025-04-24 01:50:22.85: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9034 newResVer=9034
2025-04-24 01:50:22.85: NetworkPolicyMonitor - start process kube event
2025-04-24 01:50:22.85: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-24 01:50:22.85: empty line received
2025-04-24 01:50:22.85: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-24 01:50:22.85: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-24 01:50:22.85: NetworkPolicyMonitor - start process kube event
2025-04-24 01:50:22.85: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-24 01:50:22.85: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:50:23.08: IngressMonitor - Received BOOKMARK: oldResVer=8988 newResVer=8988
2025-04-24 01:50:23.08: IngressMonitor - start process kube event
2025-04-24 01:50:23.08: empty line received
2025-04-24 01:50:23.08: IngressMonitor - start process kube event
2025-04-24 01:50:23.46: NetworkMonitor - Received BOOKMARK: oldResVer=8934 newResVer=8934
2025-04-24 01:50:23.46: NetworkMonitor - start process kube event
2025-04-24 01:50:23.46: empty line received
2025-04-24 01:50:23.46: NetworkMonitor - start process kube event
2025-04-24 01:50:23.71: ServiceMonitor - Received BOOKMARK: oldResVer=9086 newResVer=9086
2025-04-24 01:50:23.71: ServiceMonitor - start process kube event
2025-04-24 01:50:23.71: empty line received
2025-04-24 01:50:23.71: ServiceMonitor - start process kube event
2025-04-24 01:50:23.85: PodMonitor - Received BOOKMARK: oldResVer=9276 newResVer=9276
2025-04-24 01:50:23.85: PodMonitor - start process kube event
2025-04-24 01:50:23.85: PodMonitor - _schedule_vnc_sync
2025-04-24 01:50:23.85: empty line received
2025-04-24 01:50:23.85: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-24 01:50:23.85: VncKubernetes - vnc_sync - Pod start
2025-04-24 01:50:23.85: VncKubernetes - vnc_sync - Pod done
2025-04-24 01:50:23.85: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:50:23.85: PodMonitor - start process kube event
2025-04-24 01:50:24.62: EndPointMonitor - Received BOOKMARK: oldResVer=8621 newResVer=8621
2025-04-24 01:50:24.62: EndPointMonitor - start process kube event
2025-04-24 01:50:24.62: EndPointMonitor - _schedule_vnc_sync
2025-04-24 01:50:24.62: empty line received
2025-04-24 01:50:24.62: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-24 01:50:24.62: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-24 01:50:24.62: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:50:24.62: EndPointMonitor - start process kube event
2025-04-24 01:50:42.25: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:50:42.25: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:50:42.25: PodMonitor - start process kube event
2025-04-24 01:50:42.25: empty line received
2025-04-24 01:50:42.25: PodMonitor - start process kube event
2025-04-24 01:51:22.24: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9034 newResVer=9034
2025-04-24 01:51:22.24: NetworkPolicyMonitor - start process kube event
2025-04-24 01:51:22.24: empty line received
2025-04-24 01:51:22.24: NetworkPolicyMonitor - start process kube event
2025-04-24 01:51:22.81: NamespaceMonitor - Received BOOKMARK: oldResVer=9256 newResVer=9256
2025-04-24 01:51:22.81: NamespaceMonitor - start process kube event
2025-04-24 01:51:22.81: NamespaceMonitor - _schedule_vnc_sync
2025-04-24 01:51:22.81: empty line received
2025-04-24 01:51:22.81: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-24 01:51:22.81: VncKubernetes - vnc_sync - Namespace start
2025-04-24 01:51:22.81: VncKubernetes - vnc_sync - Namespace done
2025-04-24 01:51:22.81: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:51:22.81: NamespaceMonitor - start process kube event
2025-04-24 01:51:23.15: IngressMonitor - Received BOOKMARK: oldResVer=8988 newResVer=8988
2025-04-24 01:51:23.15: IngressMonitor - start process kube event
2025-04-24 01:51:23.15: IngressMonitor - _schedule_vnc_sync
2025-04-24 01:51:23.15: empty line received
2025-04-24 01:51:23.15: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-24 01:51:23.15: VncKubernetes - vnc_sync - Ingress start
2025-04-24 01:51:23.15: VncKubernetes - vnc_sync - Ingress done
2025-04-24 01:51:23.15: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:51:23.15: IngressMonitor - start process kube event
2025-04-24 01:51:23.47: PodMonitor - Received BOOKMARK: oldResVer=9276 newResVer=9417
2025-04-24 01:51:23.47: PodMonitor - start process kube event
2025-04-24 01:51:23.47: empty line received
2025-04-24 01:51:23.47: PodMonitor - start process kube event
2025-04-24 01:51:23.51: NetworkMonitor - Received BOOKMARK: oldResVer=8934 newResVer=8934
2025-04-24 01:51:23.51: NetworkMonitor - start process kube event
2025-04-24 01:51:23.51: empty line received
2025-04-24 01:51:23.51: NetworkMonitor - start process kube event
2025-04-24 01:51:24.06: ServiceMonitor - Received BOOKMARK: oldResVer=9086 newResVer=9086
2025-04-24 01:51:24.06: ServiceMonitor - start process kube event
2025-04-24 01:51:24.06: ServiceMonitor - _schedule_vnc_sync
2025-04-24 01:51:24.06: empty line received
2025-04-24 01:51:24.06: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-24 01:51:24.06: VncKubernetes - vnc_sync - Service start
2025-04-24 01:51:24.06: VncKubernetes - vnc_sync - Service done
2025-04-24 01:51:24.06: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:51:24.06: ServiceMonitor - start process kube event
2025-04-24 01:51:25.03: EndPointMonitor - Received BOOKMARK: oldResVer=8621 newResVer=8621
2025-04-24 01:51:25.03: EndPointMonitor - start process kube event
2025-04-24 01:51:25.03: empty line received
2025-04-24 01:51:25.03: EndPointMonitor - start process kube event
2025-04-24 01:51:41.48: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:51:41.48: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:51:41.48: PodMonitor - start process kube event
2025-04-24 01:51:41.48: empty line received
2025-04-24 01:51:41.48: PodMonitor - start process kube event
2025-04-24 01:51:52.98: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:51:52.98: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:51:52.98: PodMonitor - start process kube event
2025-04-24 01:51:52.98: empty line received
2025-04-24 01:51:52.98: PodMonitor - start process kube event
2025-04-24 01:52:22.22: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9034 newResVer=9034
2025-04-24 01:52:22.22: NetworkPolicyMonitor - start process kube event
2025-04-24 01:52:22.22: empty line received
2025-04-24 01:52:22.22: NetworkPolicyMonitor - start process kube event
2025-04-24 01:52:22.55: NamespaceMonitor - Received BOOKMARK: oldResVer=9256 newResVer=9256
2025-04-24 01:52:22.55: NamespaceMonitor - start process kube event
2025-04-24 01:52:22.55: empty line received
2025-04-24 01:52:22.55: NamespaceMonitor - start process kube event
2025-04-24 01:52:23.35: NetworkMonitor - Received BOOKMARK: oldResVer=8934 newResVer=8934
2025-04-24 01:52:23.35: NetworkMonitor - start process kube event
2025-04-24 01:52:23.35: NetworkMonitor - _schedule_vnc_sync
2025-04-24 01:52:23.35: empty line received
2025-04-24 01:52:23.35: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-24 01:52:23.35: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-24 01:52:23.35: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:52:23.35: NetworkMonitor - start process kube event
2025-04-24 01:52:23.60: PodMonitor - Received BOOKMARK: oldResVer=9417 newResVer=9517
2025-04-24 01:52:23.60: PodMonitor - start process kube event
2025-04-24 01:52:23.60: empty line received
2025-04-24 01:52:23.60: PodMonitor - start process kube event
2025-04-24 01:52:23.69: IngressMonitor - Received BOOKMARK: oldResVer=8988 newResVer=8988
2025-04-24 01:52:23.69: IngressMonitor - start process kube event
2025-04-24 01:52:23.69: empty line received
2025-04-24 01:52:23.70: IngressMonitor - start process kube event
2025-04-24 01:52:25.03: ServiceMonitor - Received BOOKMARK: oldResVer=9086 newResVer=9086
2025-04-24 01:52:25.03: ServiceMonitor - start process kube event
2025-04-24 01:52:25.03: empty line received
2025-04-24 01:52:25.03: ServiceMonitor - start process kube event
2025-04-24 01:52:25.66: EndPointMonitor - Received BOOKMARK: oldResVer=8621 newResVer=9529
2025-04-24 01:52:25.66: EndPointMonitor - start process kube event
2025-04-24 01:52:25.66: empty line received
2025-04-24 01:52:25.66: EndPointMonitor - start process kube event
2025-04-24 01:53:22.25: NamespaceMonitor - Received BOOKMARK: oldResVer=9256 newResVer=9256
2025-04-24 01:53:22.25: NamespaceMonitor - start process kube event
2025-04-24 01:53:22.25: empty line received
2025-04-24 01:53:22.25: NamespaceMonitor - start process kube event
2025-04-24 01:53:22.59: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9034 newResVer=9034
2025-04-24 01:53:22.59: NetworkPolicyMonitor - start process kube event
2025-04-24 01:53:22.59: empty line received
2025-04-24 01:53:22.59: NetworkPolicyMonitor - start process kube event
2025-04-24 01:53:23.26: PodMonitor - Received BOOKMARK: oldResVer=9517 newResVer=9517
2025-04-24 01:53:23.26: PodMonitor - start process kube event
2025-04-24 01:53:23.26: empty line received
2025-04-24 01:53:23.26: PodMonitor - start process kube event
2025-04-24 01:53:23.31: NetworkMonitor - Received BOOKMARK: oldResVer=8934 newResVer=8934
2025-04-24 01:53:23.31: NetworkMonitor - start process kube event
2025-04-24 01:53:23.31: empty line received
2025-04-24 01:53:23.31: NetworkMonitor - start process kube event
2025-04-24 01:53:23.66: IngressMonitor - Received BOOKMARK: oldResVer=8988 newResVer=8988
2025-04-24 01:53:23.66: IngressMonitor - start process kube event
2025-04-24 01:53:23.66: empty line received
2025-04-24 01:53:23.66: IngressMonitor - start process kube event
2025-04-24 01:53:24.96: EndPointMonitor - Received BOOKMARK: oldResVer=9529 newResVer=9529
2025-04-24 01:53:24.96: EndPointMonitor - start process kube event
2025-04-24 01:53:24.96: empty line received
2025-04-24 01:53:24.96: EndPointMonitor - start process kube event
2025-04-24 01:53:24.97: ServiceMonitor - Received BOOKMARK: oldResVer=9086 newResVer=9086
2025-04-24 01:53:24.97: ServiceMonitor - start process kube event
2025-04-24 01:53:24.97: empty line received
2025-04-24 01:53:24.97: ServiceMonitor - start process kube event
2025-04-24 01:53:55.25: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:53:55.25: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:53:55.25: PodMonitor - start process kube event
2025-04-24 01:53:55.25: empty line received
2025-04-24 01:53:55.25: PodMonitor - start process kube event
2025-04-24 01:53:56.28: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:53:56.28: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:53:56.28: PodMonitor - start process kube event
2025-04-24 01:53:56.28: empty line received
2025-04-24 01:53:56.28: PodMonitor - start process kube event
2025-04-24 01:54:06.98: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:54:06.98: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:54:06.98: PodMonitor - start process kube event
2025-04-24 01:54:06.98: empty line received
2025-04-24 01:54:06.98: PodMonitor - start process kube event
2025-04-24 01:54:22.15: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9034 newResVer=9034
2025-04-24 01:54:22.15: NetworkPolicyMonitor - start process kube event
2025-04-24 01:54:22.15: empty line received
2025-04-24 01:54:22.15: NetworkPolicyMonitor - start process kube event
2025-04-24 01:54:22.51: NamespaceMonitor - Received BOOKMARK: oldResVer=9256 newResVer=9256
2025-04-24 01:54:22.51: NamespaceMonitor - start process kube event
2025-04-24 01:54:22.51: empty line received
2025-04-24 01:54:22.51: NamespaceMonitor - start process kube event
2025-04-24 01:54:22.87: NetworkMonitor - Received BOOKMARK: oldResVer=8934 newResVer=8934
2025-04-24 01:54:22.87: NetworkMonitor - start process kube event
2025-04-24 01:54:22.87: empty line received
2025-04-24 01:54:22.87: NetworkMonitor - start process kube event
2025-04-24 01:54:23.24: IngressMonitor - Received BOOKMARK: oldResVer=8988 newResVer=8988
2025-04-24 01:54:23.24: IngressMonitor - start process kube event
2025-04-24 01:54:23.24: empty line received
2025-04-24 01:54:23.24: IngressMonitor - start process kube event
2025-04-24 01:54:23.35: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:54:23.67: PodMonitor - Received BOOKMARK: oldResVer=9517 newResVer=9710
2025-04-24 01:54:23.67: PodMonitor - start process kube event
2025-04-24 01:54:23.67: empty line received
2025-04-24 01:54:23.67: PodMonitor - start process kube event
2025-04-24 01:54:25.31: EndPointMonitor - Received BOOKMARK: oldResVer=9529 newResVer=9529
2025-04-24 01:54:25.32: EndPointMonitor - start process kube event
2025-04-24 01:54:25.32: EndPointMonitor - _schedule_vnc_sync
2025-04-24 01:54:25.32: empty line received
2025-04-24 01:54:25.32: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-04-24 01:54:25.32: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-04-24 01:54:25.32: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:54:25.32: EndPointMonitor - start process kube event
2025-04-24 01:54:25.58: ServiceMonitor - Received BOOKMARK: oldResVer=9086 newResVer=9086
2025-04-24 01:54:25.58: ServiceMonitor - start process kube event
2025-04-24 01:54:25.58: empty line received
2025-04-24 01:54:25.58: ServiceMonitor - start process kube event
2025-04-24 01:55:22.43: NamespaceMonitor - Received BOOKMARK: oldResVer=9256 newResVer=9256
2025-04-24 01:55:22.43: NamespaceMonitor - start process kube event
2025-04-24 01:55:22.43: empty line received
2025-04-24 01:55:22.43: NamespaceMonitor - start process kube event
2025-04-24 01:55:22.99: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9034 newResVer=9034
2025-04-24 01:55:22.99: NetworkPolicyMonitor - start process kube event
2025-04-24 01:55:22.99: NetworkPolicyMonitor - _schedule_vnc_sync
2025-04-24 01:55:22.99: empty line received
2025-04-24 01:55:22.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-04-24 01:55:22.99: VncKubernetes - vnc_sync - NetworkPolicy start
2025-04-24 01:55:22.99: NetworkPolicyMonitor - start process kube event
2025-04-24 01:55:22.99: VncKubernetes - vnc_sync - NetworkPolicy done
2025-04-24 01:55:22.99: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:55:23.42: NetworkMonitor - Received BOOKMARK: oldResVer=8934 newResVer=8934
2025-04-24 01:55:23.42: NetworkMonitor - start process kube event
2025-04-24 01:55:23.42: empty line received
2025-04-24 01:55:23.42: NetworkMonitor - start process kube event
2025-04-24 01:55:23.48: IngressMonitor - Received BOOKMARK: oldResVer=8988 newResVer=8988
2025-04-24 01:55:23.48: IngressMonitor - start process kube event
2025-04-24 01:55:23.48: IngressMonitor - _schedule_vnc_sync
2025-04-24 01:55:23.48: empty line received
2025-04-24 01:55:23.48: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-04-24 01:55:23.48: VncKubernetes - vnc_sync - Ingress start
2025-04-24 01:55:23.48: VncKubernetes - vnc_sync - Ingress done
2025-04-24 01:55:23.48: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:55:23.48: IngressMonitor - start process kube event
2025-04-24 01:55:23.49: PodMonitor - Received BOOKMARK: oldResVer=9710 newResVer=9710
2025-04-24 01:55:23.49: PodMonitor - start process kube event
2025-04-24 01:55:23.49: PodMonitor - _schedule_vnc_sync
2025-04-24 01:55:23.49: empty line received
2025-04-24 01:55:23.49: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-04-24 01:55:23.49: VncKubernetes - vnc_sync - Pod start
2025-04-24 01:55:23.49: VncKubernetes - vnc_sync - Pod done
2025-04-24 01:55:23.49: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:55:23.49: PodMonitor - start process kube event
2025-04-24 01:55:25.46: ServiceMonitor - Received BOOKMARK: oldResVer=9086 newResVer=9086
2025-04-24 01:55:25.46: ServiceMonitor - start process kube event
2025-04-24 01:55:25.46: ServiceMonitor - _schedule_vnc_sync
2025-04-24 01:55:25.46: empty line received
2025-04-24 01:55:25.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-04-24 01:55:25.46: VncKubernetes - vnc_sync - Service start
2025-04-24 01:55:25.46: VncKubernetes - vnc_sync - Service done
2025-04-24 01:55:25.46: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:55:25.46: ServiceMonitor - start process kube event
2025-04-24 01:55:25.75: EndPointMonitor - Received BOOKMARK: oldResVer=9529 newResVer=9529
2025-04-24 01:55:25.75: EndPointMonitor - start process kube event
2025-04-24 01:55:25.75: empty line received
2025-04-24 01:55:25.75: EndPointMonitor - start process kube event
2025-04-24 01:56:22.67: NamespaceMonitor - Received BOOKMARK: oldResVer=9256 newResVer=9256
2025-04-24 01:56:22.67: NamespaceMonitor - start process kube event
2025-04-24 01:56:22.67: NamespaceMonitor - _schedule_vnc_sync
2025-04-24 01:56:22.67: empty line received
2025-04-24 01:56:22.67: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-04-24 01:56:22.67: VncKubernetes - vnc_sync - Namespace start
2025-04-24 01:56:22.67: VncKubernetes - vnc_sync - Namespace done
2025-04-24 01:56:22.67: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:56:22.67: NamespaceMonitor - start process kube event
2025-04-24 01:56:23.07: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9034 newResVer=9034
2025-04-24 01:56:23.07: NetworkPolicyMonitor - start process kube event
2025-04-24 01:56:23.07: empty line received
2025-04-24 01:56:23.07: NetworkPolicyMonitor - start process kube event
2025-04-24 01:56:23.49: IngressMonitor - Received BOOKMARK: oldResVer=8988 newResVer=8988
2025-04-24 01:56:23.49: IngressMonitor - start process kube event
2025-04-24 01:56:23.49: empty line received
2025-04-24 01:56:23.49: IngressMonitor - start process kube event
2025-04-24 01:56:23.61: NetworkMonitor - Received BOOKMARK: oldResVer=8934 newResVer=9877
2025-04-24 01:56:23.61: NetworkMonitor - start process kube event
2025-04-24 01:56:23.61: NetworkMonitor - _schedule_vnc_sync
2025-04-24 01:56:23.61: empty line received
2025-04-24 01:56:23.61: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-04-24 01:56:23.61: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-04-24 01:56:23.61: VncKubernetes - wait event (qsize=0 timeout=120)
2025-04-24 01:56:23.61: NetworkMonitor - start process kube event
2025-04-24 01:56:23.95: PodMonitor - Received BOOKMARK: oldResVer=9710 newResVer=9710
2025-04-24 01:56:23.95: PodMonitor - start process kube event
2025-04-24 01:56:23.95: empty line received
2025-04-24 01:56:23.95: PodMonitor - start process kube event
2025-04-24 01:56:25.62: EndPointMonitor - Received BOOKMARK: oldResVer=9529 newResVer=9529
2025-04-24 01:56:25.62: EndPointMonitor - start process kube event
2025-04-24 01:56:25.62: empty line received
2025-04-24 01:56:25.62: EndPointMonitor - start process kube event
2025-04-24 01:56:25.98: ServiceMonitor - Received BOOKMARK: oldResVer=9086 newResVer=9086
2025-04-24 01:56:25.98: ServiceMonitor - start process kube event
2025-04-24 01:56:25.98: empty line received
2025-04-24 01:56:25.98: ServiceMonitor - start process kube event
2025-04-24 01:56:46.76: PodMonitor - Received MODIFIED Pod kube-system:opensdn-agent-wlpj4:e530103a-3ded-40cc-be95-c6425d367dd9
2025-04-24 01:56:46.76: PodMonitor - Skipped MODIFIED Pod kube-system:opensdn-agent-wlpj4 (hostNetwork=True)
2025-04-24 01:56:46.76: PodMonitor - start process kube event