INFO: =================== Thu Feb  6 01:49:39 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: 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()
02/06/2025 01:50:59.027 7fb9eeeb7508 [contrail-kube-manager] [INFO]: SANDESH: CONNECT TO COLLECTOR: True
02/06/2025 01:50:59.468 7fb9eeeb7508 [contrail-kube-manager] [INFO]: SANDESH: Logging: LEVEL: [SYS_INFO] -> [SYS_NOTICE]
2025-02-06 01:51:00.35: KubeMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:51:00.35: KubeMonitor - Connect Kube API result 0
2025-02-06 01:51:00.43: KubeMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/api/v1
2025-02-06 01:51:00.44: NamespaceMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/api/v1
2025-02-06 01:51:00.44: NetworkMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1
2025-02-06 01:51:00.45: PodMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/api/v1
2025-02-06 01:51:00.46: ServiceMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/api/v1
2025-02-06 01:51:00.46: NetworkPolicyMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/apis/networking.k8s.io/v1
2025-02-06 01:51:00.47: EndPointMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/api/v1
2025-02-06 01:51:00.47: IngressMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/apis/networking.k8s.io/v1
2025-02-06 01:51:00.47: VncKubernetes - vnc_connect starting
2025-02-06 01:51:00.48: VncKubernetes - vnc_connect failed: 
2025-02-06 01:51:03.50: VncKubernetes - vnc_connect failed: 
2025-02-06 01:51:06.56: VncKubernetes - vnc_connect failed: 
2025-02-06 01:51:09.57: VncKubernetes - vnc_connect failed: 
2025-02-06 01:51:12.72: VncKubernetes - vnc_connect failed: 
2025-02-06 01:51:15.77: VncKubernetes - vnc_connect failed: 
2025-02-06 01:51:18.80: VncKubernetes - vnc_connect failed: 
2025-02-06 01:51:21.88: VncKubernetes - vnc_connect failed: 
2025-02-06 01:51:24.91: VncKubernetes - vnc_connect failed: 
2025-02-06 01:51:27.99: VncKubernetes - vnc_connect failed: 
2025-02-06 01:51:31.02: VncKubernetes - vnc_connect failed: 
2025-02-06 01:51:34.07: VncKubernetes - vnc_connect done
2025-02-06 01:51:34.96: default-domain domain available.
2025-02-06 01:51:50.08: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:51:50.08: NamespaceMonitor - start process kube event
2025-02-06 01:51:50.08: NamespaceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-06 01:51:50.08: NamespaceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:51:50.08: NetworkMonitor - start process kube event
2025-02-06 01:51:50.08: NetworkMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-06 01:51:50.08: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:51:50.08: PodMonitor - start process kube event
2025-02-06 01:51:50.08: PodMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-06 01:51:50.08: PodMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:51:50.08: ServiceMonitor - start process kube event
2025-02-06 01:51:50.08: ServiceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-06 01:51:50.08: ServiceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:51:50.08: NetworkPolicyMonitor - start process kube event
2025-02-06 01:51:50.08: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-06 01:51:50.08: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:51:50.08: EndPointMonitor - start process kube event
2025-02-06 01:51:50.08: EndPointMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-06 01:51:50.08: EndPointMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:51:50.08: IngressMonitor - start process kube event
2025-02-06 01:51:50.08: IngressMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-06 01:51:50.08: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:51:50.08: IngressMonitor - Connect Kube API result 0
2025-02-06 01:51:50.08: IngressMonitor - Start init url=https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses resource_version=None
2025-02-06 01:51:50.09: EndPointMonitor - Connect Kube API result 0
2025-02-06 01:51:50.09: EndPointMonitor - Start init url=https://10.0.0.40:6443/api/v1/endpoints resource_version=None
2025-02-06 01:51:50.09: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-06 01:51:50.09: NetworkPolicyMonitor - Start init url=https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies resource_version=None
2025-02-06 01:51:50.09: ServiceMonitor - Connect Kube API result 0
2025-02-06 01:51:50.09: ServiceMonitor - Start init url=https://10.0.0.40:6443/api/v1/services resource_version=None
2025-02-06 01:51:50.09: PodMonitor - Connect Kube API result 0
2025-02-06 01:51:50.09: PodMonitor - Start init url=https://10.0.0.40:6443/api/v1/pods resource_version=None
2025-02-06 01:51:50.10: NetworkMonitor - Connect Kube API result 0
2025-02-06 01:51:50.10: NamespaceMonitor - Connect Kube API result 0
2025-02-06 01:51:50.10: NamespaceMonitor - Start init url=https://10.0.0.40:6443/api/v1/namespaces resource_version=None
2025-02-06 01:51:50.13: IngressMonitor - Done init url=https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses, resource_version=9435
2025-02-06 01:51:50.13: IngressMonitor - _schedule_vnc_sync
2025-02-06 01:51:50.13: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:51:50.13: NetworkPolicyMonitor - Done init url=https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies, resource_version=9435
2025-02-06 01:51:50.13: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 01:51:50.13: NetworkPolicyMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:51:50.14: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 01:51:50.14: VncKubernetes - vnc_sync - Ingress start
2025-02-06 01:51:50.14: VncKubernetes - vnc_sync - Ingress done
2025-02-06 01:51:50.14: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-06 01:51:50.14: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 01:51:50.14: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 01:51:50.16: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:51:50.16: NetworkPolicyMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:51:50.16: NetworkMonitor - Start init url=https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions resource_version=None
2025-02-06 01:51:50.17: ServiceMonitor - Got ADDED Service default:kubernetes:4357d288-171d-466c-814f-6a902ab7c92c
2025-02-06 01:51:50.17: EndPointMonitor - Got ADDED Endpoints default:kubernetes:56e01583-a99e-473b-97c0-72fa769ffe15
2025-02-06 01:51:50.18: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 01:51:50.18: VncKubernetes - wait event (qsize=2 timeout=120)
2025-02-06 01:51:50.18: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Service ns=default)
VncService - Got ADDED Service default:kubernetes:4357d288-171d-466c-814f-6a902ab7c92c
2025-02-06 01:51:50.19: NamespaceMonitor - Got ADDED Namespace None:default:09939591-5184-4166-a105-386034a4fa71
2025-02-06 01:51:50.19: PodMonitor - Skipped ADDED Pod kube-system:config-zookeeper-zqzdc (hostNetwork=True)
2025-02-06 01:51:50.19: EndPointMonitor - Got ADDED Endpoints kube-system:coredns:0f06f850-78b8-4589-9fcc-d914af680bc4
2025-02-06 01:51:50.19: EndPointMonitor - Done init url=https://10.0.0.40:6443/api/v1/endpoints, resource_version=9435
2025-02-06 01:51:50.19: EndPointMonitor - _schedule_vnc_sync
2025-02-06 01:51:50.19: EndPointMonitor - Start Watching request https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:51:50.20: ServiceMonitor - Got ADDED Service kube-system:coredns:dcf0a59d-9371-41d5-b182-8e117e551b9f
2025-02-06 01:51:50.20: ServiceMonitor - Done init url=https://10.0.0.40:6443/api/v1/services, resource_version=9435
2025-02-06 01:51:50.20: ServiceMonitor - _schedule_vnc_sync
2025-02-06 01:51:50.20: ServiceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:51:50.21: EndPointMonitor - Watches https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:51:50.21: NetworkMonitor - Done init url=https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions, resource_version=9439
2025-02-06 01:51:50.21: NetworkMonitor - _schedule_vnc_sync
2025-02-06 01:51:50.21: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})(timeout=120)
2025-02-06 01:51:50.21: PodMonitor - Skipped ADDED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:51:50.21: NamespaceMonitor - Got ADDED Namespace None:kube-node-lease:c6da4790-e6e2-4224-9c85-95e616d0bbec
2025-02-06 01:51:50.21: ServiceMonitor - Watches https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:51:50.21: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})
2025-02-06 01:51:50.22: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-alarm-mvwsl (hostNetwork=True)
2025-02-06 01:51:50.22: NamespaceMonitor - Got ADDED Namespace None:kube-public:d59d6055-416c-4824-a6ec-63feb9e6b02b
2025-02-06 01:51:50.22: NamespaceMonitor - Got ADDED Namespace None:kube-system:108bcf0e-cc72-4da8-aba9-9c92766cf2d4
2025-02-06 01:51:50.22: NamespaceMonitor - Done init url=https://10.0.0.40:6443/api/v1/namespaces, resource_version=9435
2025-02-06 01:51:50.22: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 01:51:50.22: NamespaceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:51:50.23: NamespaceMonitor - Watches https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:51:50.23: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-snmp-kgrmp (hostNetwork=True)
2025-02-06 01:51:50.23: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-zhpw7 (hostNetwork=True)
2025-02-06 01:51:50.24: PodMonitor - Skipped ADDED Pod kube-system:contrail-analyticsdb-bqrb9 (hostNetwork=True)
2025-02-06 01:51:50.24: PodMonitor - Skipped ADDED Pod kube-system:contrail-configdb-sv4p9 (hostNetwork=True)
2025-02-06 01:51:50.24: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-config-2ctkk (hostNetwork=True)
2025-02-06 01:51:50.25: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-control-jjrcc (hostNetwork=True)
2025-02-06 01:51:50.25: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-webui-4mdjt (hostNetwork=True)
2025-02-06 01:51:50.26: PodMonitor - Skipped ADDED Pod kube-system:contrail-kube-manager-9hxrj (hostNetwork=True)
2025-02-06 01:51:50.26: PodMonitor - Got ADDED Pod kube-system:coredns-77f7cc69db-ldnd8:d095b4c2-19c5-4b8c-966f-3fdcf1d1c0a2
2025-02-06 01:51:50.27: PodMonitor - Got ADDED Pod kube-system:dns-autoscaler-595558c478-7cdqw:df05f06b-f68f-44eb-a80b-b1d79b3df854
2025-02-06 01:51:50.27: PodMonitor - Skipped ADDED Pod kube-system:kube-apiserver-cn-jenkins-deploy-platform-k8s-manifests-133-1 (hostNetwork=True)
2025-02-06 01:51:50.28: PodMonitor - Skipped ADDED Pod kube-system:kube-controller-manager-cn-jenkins-deploy-platform-k8s-manifests-133-1 (hostNetwork=True)
2025-02-06 01:51:50.28: PodMonitor - Skipped ADDED Pod kube-system:kube-proxy-xpvq6 (hostNetwork=True)
2025-02-06 01:51:50.28: PodMonitor - Skipped ADDED Pod kube-system:kube-scheduler-cn-jenkins-deploy-platform-k8s-manifests-133-1 (hostNetwork=True)
2025-02-06 01:51:50.29: PodMonitor - Skipped ADDED Pod kube-system:rabbitmq-svgl2 (hostNetwork=True)
2025-02-06 01:51:50.29: PodMonitor - Skipped ADDED Pod kube-system:redis-kbhbr (hostNetwork=True)
2025-02-06 01:51:50.29: PodMonitor - Done init url=https://10.0.0.40:6443/api/v1/pods, resource_version=9435
2025-02-06 01:51:50.29: PodMonitor - _schedule_vnc_sync
2025-02-06 01:51:50.29: PodMonitor - Start Watching request https://10.0.0.40:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:51:50.30: PodMonitor - Watches https://10.0.0.40:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:51:52.46: VncKubernetes - wait event (qsize=14 timeout=120)
2025-02-06 01:51:52.46: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Endpoints ns=default)
VncEndpoints - Got ADDED Endpoints default:kubernetes:56e01583-a99e-473b-97c0-72fa769ffe15
2025-02-06 01:51:52.55: VncKubernetes - wait event (qsize=13 timeout=120)
2025-02-06 01:51:52.55: VncKubernetes - Process event (name=default event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace default:09939591-5184-4166-a105-386034a4fa71
2025-02-06 01:51:56.14: VncKubernetes - wait event (qsize=12 timeout=120)
2025-02-06 01:51:56.14: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Endpoints ns=kube-system)
VncEndpoints - Got ADDED Endpoints kube-system:coredns:0f06f850-78b8-4589-9fcc-d914af680bc4
2025-02-06 01:51:56.19: VncKubernetes - wait event (qsize=11 timeout=120)
2025-02-06 01:51:56.19: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 01:51:56.19: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 01:51:56.19: VncKubernetes - wait event (qsize=10 timeout=120)
2025-02-06 01:51:56.19: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Service ns=kube-system)
VncService - Got ADDED Service kube-system:coredns:dcf0a59d-9371-41d5-b182-8e117e551b9f
2025-02-06 01:51:58.82: VncKubernetes - wait event (qsize=9 timeout=120)
2025-02-06 01:51:58.82: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 01:51:58.82: VncKubernetes - vnc_sync - Service start
2025-02-06 01:51:58.82: VncKubernetes - vnc_sync - Service done
2025-02-06 01:51:58.82: VncKubernetes - wait event (qsize=8 timeout=120)
2025-02-06 01:51:58.82: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 01:51:58.82: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 01:51:58.82: VncKubernetes - wait event (qsize=7 timeout=120)
2025-02-06 01:51:58.82: VncKubernetes - Process event (name=kube-node-lease event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-node-lease:c6da4790-e6e2-4224-9c85-95e616d0bbec
2025-02-06 01:52:01.36: VncKubernetes - wait event (qsize=6 timeout=120)
2025-02-06 01:52:01.36: VncKubernetes - Process event (name=kube-public event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-public:d59d6055-416c-4824-a6ec-63feb9e6b02b
2025-02-06 01:52:03.90: VncKubernetes - wait event (qsize=5 timeout=120)
2025-02-06 01:52:03.90: VncKubernetes - Process event (name=kube-system event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-system:108bcf0e-cc72-4da8-aba9-9c92766cf2d4
2025-02-06 01:52:06.26: VncKubernetes - wait event (qsize=4 timeout=120)
2025-02-06 01:52:06.26: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 01:52:06.26: VncKubernetes - vnc_sync - Namespace start
2025-02-06 01:52:06.26: VncKubernetes - vnc_sync - Namespace done
2025-02-06 01:52:06.26: VncKubernetes - wait event (qsize=3 timeout=120)
2025-02-06 01:52:06.26: VncKubernetes - Process event (name=coredns-77f7cc69db-ldnd8 event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:coredns-77f7cc69db-ldnd8:d095b4c2-19c5-4b8c-966f-3fdcf1d1c0a2
2025-02-06 01:52:07.85: PodMonitor - Received MODIFIED Pod kube-system:coredns-77f7cc69db-ldnd8:d095b4c2-19c5-4b8c-966f-3fdcf1d1c0a2
2025-02-06 01:52:07.85: PodMonitor - Got MODIFIED Pod kube-system:coredns-77f7cc69db-ldnd8:d095b4c2-19c5-4b8c-966f-3fdcf1d1c0a2
2025-02-06 01:52:07.85: PodMonitor - start process kube event
2025-02-06 01:52:07.85: empty line received
2025-02-06 01:52:07.85: VncKubernetes - wait event (qsize=3 timeout=120)
2025-02-06 01:52:07.85: VncKubernetes - Process event (name=dns-autoscaler-595558c478-7cdqw event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:dns-autoscaler-595558c478-7cdqw:df05f06b-f68f-44eb-a80b-b1d79b3df854
2025-02-06 01:52:07.85: PodMonitor - start process kube event
2025-02-06 01:52:09.07: VncKubernetes - wait event (qsize=2 timeout=120)
2025-02-06 01:52:09.07: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 01:52:09.07: VncKubernetes - vnc_sync - Pod start
2025-02-06 01:52:09.07: VncKubernetes - vnc_sync - Pod done
2025-02-06 01:52:09.07: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-06 01:52:09.07: VncKubernetes - Process event (name=coredns-77f7cc69db-ldnd8 event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:coredns-77f7cc69db-ldnd8:d095b4c2-19c5-4b8c-966f-3fdcf1d1c0a2
2025-02-06 01:52:09.07: PodMonitor - Received MODIFIED Pod kube-system:dns-autoscaler-595558c478-7cdqw:df05f06b-f68f-44eb-a80b-b1d79b3df854
2025-02-06 01:52:09.07: PodMonitor - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-7cdqw:df05f06b-f68f-44eb-a80b-b1d79b3df854
2025-02-06 01:52:09.07: PodMonitor - start process kube event
2025-02-06 01:52:09.07: empty line received
2025-02-06 01:52:09.07: PodMonitor - start process kube event
2025-02-06 01:52:09.16: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-06 01:52:09.16: VncKubernetes - Process event (name=dns-autoscaler-595558c478-7cdqw event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-7cdqw:df05f06b-f68f-44eb-a80b-b1d79b3df854
2025-02-06 01:52:09.26: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:52:10.66: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:52:10.67: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:52:10.67: PodMonitor - start process kube event
2025-02-06 01:52:10.67: empty line received
2025-02-06 01:52:10.67: PodMonitor - start process kube event
2025-02-06 01:52:15.83: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:52:15.83: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:52:15.83: PodMonitor - start process kube event
2025-02-06 01:52:15.83: empty line received
2025-02-06 01:52:15.83: PodMonitor - start process kube event
2025-02-06 01:52:27.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:52:27.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:52:27.91: PodMonitor - start process kube event
2025-02-06 01:52:27.91: empty line received
2025-02-06 01:52:27.91: PodMonitor - start process kube event
2025-02-06 01:52:28.20: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:52:28.20: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:52:28.20: PodMonitor - start process kube event
2025-02-06 01:52:28.20: empty line received
2025-02-06 01:52:28.20: PodMonitor - start process kube event
2025-02-06 01:52:41.57: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:52:41.57: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:52:41.57: PodMonitor - start process kube event
2025-02-06 01:52:41.57: empty line received
2025-02-06 01:52:41.57: PodMonitor - start process kube event
2025-02-06 01:52:50.53: PodMonitor - Received BOOKMARK: oldResVer=9435 newResVer=9522
2025-02-06 01:52:50.53: PodMonitor - start process kube event
2025-02-06 01:52:50.53: empty line received
2025-02-06 01:52:50.53: PodMonitor - start process kube event
2025-02-06 01:52:55.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:52:55.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:52:55.91: PodMonitor - start process kube event
2025-02-06 01:52:55.91: empty line received
2025-02-06 01:52:55.91: PodMonitor - start process kube event
2025-02-06 01:52:57.11: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:52:57.11: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:52:57.11: PodMonitor - start process kube event
2025-02-06 01:52:57.11: empty line received
2025-02-06 01:52:57.11: PodMonitor - start process kube event
2025-02-06 01:53:28.93: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:53:28.93: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:53:28.93: PodMonitor - start process kube event
2025-02-06 01:53:28.93: empty line received
2025-02-06 01:53:28.93: PodMonitor - start process kube event
2025-02-06 01:53:41.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:53:41.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:53:41.91: PodMonitor - start process kube event
2025-02-06 01:53:41.91: empty line received
2025-02-06 01:53:41.91: PodMonitor - start process kube event
2025-02-06 01:53:42.37: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:53:42.37: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:53:42.37: PodMonitor - start process kube event
2025-02-06 01:53:42.37: empty line received
2025-02-06 01:53:42.37: PodMonitor - start process kube event
2025-02-06 01:53:43.42: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:53:43.42: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:53:43.42: PodMonitor - start process kube event
2025-02-06 01:53:43.42: empty line received
2025-02-06 01:53:43.42: PodMonitor - start process kube event
2025-02-06 01:53:50.17: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:53:50.17: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:53:50.17: IngressMonitor - start process kube event
2025-02-06 01:53:50.17: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:53:50.17: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:53:50.17: NetworkPolicyMonitor - start process kube event
2025-02-06 01:53:50.17: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:53:50.17: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:53:50.17: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-06 01:53:50.17: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 01:53:50.17: NetworkPolicyMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:53:50.17: IngressMonitor - Connect Kube API result 0
2025-02-06 01:53:50.17: IngressMonitor - _schedule_vnc_sync
2025-02-06 01:53:50.17: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:53:50.17: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 01:53:50.17: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 01:53:50.18: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 01:53:50.18: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-06 01:53:50.18: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 01:53:50.18: VncKubernetes - vnc_sync - Ingress start
2025-02-06 01:53:50.18: VncKubernetes - vnc_sync - Ingress done
2025-02-06 01:53:50.18: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:53:50.18: NetworkPolicyMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:53:50.18: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:53:50.21: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:53:50.21: EndPointMonitor - start process kube event
2025-02-06 01:53:50.21: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:53:50.21: EndPointMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:53:50.21: EndPointMonitor - Connect Kube API result 0
2025-02-06 01:53:50.21: EndPointMonitor - _schedule_vnc_sync
2025-02-06 01:53:50.21: EndPointMonitor - Start Watching request https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:53:50.21: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 01:53:50.21: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 01:53:50.21: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:53:50.21: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:53:50.21: ServiceMonitor - start process kube event
2025-02-06 01:53:50.21: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:53:50.21: ServiceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:53:50.21: ServiceMonitor - Connect Kube API result 0
2025-02-06 01:53:50.21: ServiceMonitor - _schedule_vnc_sync
2025-02-06 01:53:50.21: ServiceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:53:50.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 01:53:50.22: VncKubernetes - vnc_sync - Service start
2025-02-06 01:53:50.22: VncKubernetes - vnc_sync - Service done
2025-02-06 01:53:50.22: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:53:50.22: EndPointMonitor - Watches https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:53:50.22: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:53:50.22: NetworkMonitor - start process kube event
2025-02-06 01:53:50.22: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9439
2025-02-06 01:53:50.22: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:53:50.22: NetworkMonitor - Connect Kube API result 0
2025-02-06 01:53:50.22: NetworkMonitor - _schedule_vnc_sync
2025-02-06 01:53:50.22: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})(timeout=120)
2025-02-06 01:53:50.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 01:53:50.22: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 01:53:50.22: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:53:50.22: ServiceMonitor - Watches https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:53:50.23: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})
2025-02-06 01:53:50.23: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:53:50.23: NamespaceMonitor - start process kube event
2025-02-06 01:53:50.23: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:53:50.23: NamespaceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:53:50.23: NamespaceMonitor - Connect Kube API result 0
2025-02-06 01:53:50.23: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 01:53:50.23: NamespaceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:53:50.23: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 01:53:50.23: VncKubernetes - vnc_sync - Namespace start
2025-02-06 01:53:50.23: VncKubernetes - vnc_sync - Namespace done
2025-02-06 01:53:50.23: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:53:50.24: NamespaceMonitor - Watches https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:53:51.35: PodMonitor - Received BOOKMARK: oldResVer=9522 newResVer=9615
2025-02-06 01:53:51.35: PodMonitor - start process kube event
2025-02-06 01:53:51.35: empty line received
2025-02-06 01:53:51.35: PodMonitor - start process kube event
2025-02-06 01:53:56.78: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:53:56.78: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:53:56.78: PodMonitor - start process kube event
2025-02-06 01:53:56.79: empty line received
2025-02-06 01:53:56.79: PodMonitor - start process kube event
2025-02-06 01:53:57.85: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:53:57.85: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:53:57.85: PodMonitor - start process kube event
2025-02-06 01:53:57.85: empty line received
2025-02-06 01:53:57.85: PodMonitor - start process kube event
2025-02-06 01:54:28.57: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:54:28.57: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:54:28.57: PodMonitor - start process kube event
2025-02-06 01:54:28.57: empty line received
2025-02-06 01:54:28.57: PodMonitor - start process kube event
2025-02-06 01:54:50.76: PodMonitor - Received BOOKMARK: oldResVer=9615 newResVer=9684
2025-02-06 01:54:50.76: PodMonitor - start process kube event
2025-02-06 01:54:50.76: empty line received
2025-02-06 01:54:50.76: PodMonitor - start process kube event
2025-02-06 01:54:57.28: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:54:57.28: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:54:57.28: PodMonitor - start process kube event
2025-02-06 01:54:57.28: empty line received
2025-02-06 01:54:57.28: PodMonitor - start process kube event
2025-02-06 01:55:09.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:55:09.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:55:09.90: PodMonitor - start process kube event
2025-02-06 01:55:09.90: empty line received
2025-02-06 01:55:09.90: PodMonitor - start process kube event
2025-02-06 01:55:29.09: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:55:29.09: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:55:29.09: PodMonitor - start process kube event
2025-02-06 01:55:29.09: empty line received
2025-02-06 01:55:29.09: PodMonitor - start process kube event
2025-02-06 01:55:44.92: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:55:44.92: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:55:44.92: PodMonitor - start process kube event
2025-02-06 01:55:44.92: empty line received
2025-02-06 01:55:44.92: PodMonitor - start process kube event
2025-02-06 01:55:45.54: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:55:45.54: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:55:45.54: PodMonitor - start process kube event
2025-02-06 01:55:45.54: empty line received
2025-02-06 01:55:45.54: PodMonitor - start process kube event
2025-02-06 01:55:50.19: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:55:50.19: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:55:50.19: NetworkPolicyMonitor - start process kube event
2025-02-06 01:55:50.19: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:55:50.19: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:55:50.19: IngressMonitor - start process kube event
2025-02-06 01:55:50.19: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:55:50.19: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:55:50.19: IngressMonitor - Connect Kube API result 0
2025-02-06 01:55:50.19: IngressMonitor - _schedule_vnc_sync
2025-02-06 01:55:50.19: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:55:50.19: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-06 01:55:50.19: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 01:55:50.19: NetworkPolicyMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:55:50.19: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 01:55:50.19: VncKubernetes - vnc_sync - Ingress start
2025-02-06 01:55:50.19: VncKubernetes - vnc_sync - Ingress done
2025-02-06 01:55:50.19: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-06 01:55:50.19: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 01:55:50.19: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 01:55:50.19: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 01:55:50.19: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:55:50.20: NetworkPolicyMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:55:50.20: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:55:50.22: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:55:50.22: EndPointMonitor - start process kube event
2025-02-06 01:55:50.22: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:55:50.22: EndPointMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:55:50.22: EndPointMonitor - Connect Kube API result 0
2025-02-06 01:55:50.22: EndPointMonitor - _schedule_vnc_sync
2025-02-06 01:55:50.22: EndPointMonitor - Start Watching request https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:55:50.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 01:55:50.22: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 01:55:50.22: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:55:50.22: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:55:50.22: ServiceMonitor - start process kube event
2025-02-06 01:55:50.22: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:55:50.22: ServiceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:55:50.22: ServiceMonitor - Connect Kube API result 0
2025-02-06 01:55:50.22: ServiceMonitor - _schedule_vnc_sync
2025-02-06 01:55:50.22: ServiceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:55:50.23: EndPointMonitor - Watches https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:55:50.23: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 01:55:50.23: VncKubernetes - vnc_sync - Service start
2025-02-06 01:55:50.23: VncKubernetes - vnc_sync - Service done
2025-02-06 01:55:50.23: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:55:50.23: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:55:50.23: NetworkMonitor - start process kube event
2025-02-06 01:55:50.23: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9439
2025-02-06 01:55:50.23: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:55:50.23: NetworkMonitor - Connect Kube API result 0
2025-02-06 01:55:50.23: NetworkMonitor - _schedule_vnc_sync
2025-02-06 01:55:50.23: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})(timeout=120)
2025-02-06 01:55:50.23: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 01:55:50.23: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 01:55:50.23: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:55:50.23: ServiceMonitor - Watches https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:55:50.24: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:55:50.24: NamespaceMonitor - start process kube event
2025-02-06 01:55:50.24: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:55:50.24: NamespaceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:55:50.24: NamespaceMonitor - Connect Kube API result 0
2025-02-06 01:55:50.24: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 01:55:50.24: NamespaceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:55:50.24: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 01:55:50.24: VncKubernetes - vnc_sync - Namespace start
2025-02-06 01:55:50.24: VncKubernetes - vnc_sync - Namespace done
2025-02-06 01:55:50.24: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:55:50.24: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})
2025-02-06 01:55:50.24: NamespaceMonitor - Watches https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:55:50.63: PodMonitor - Received BOOKMARK: oldResVer=9684 newResVer=9802
2025-02-06 01:55:50.63: PodMonitor - start process kube event
2025-02-06 01:55:50.63: PodMonitor - _schedule_vnc_sync
2025-02-06 01:55:50.63: empty line received
2025-02-06 01:55:50.63: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 01:55:50.63: VncKubernetes - vnc_sync - Pod start
2025-02-06 01:55:50.63: VncKubernetes - vnc_sync - Pod done
2025-02-06 01:55:50.63: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:55:50.63: PodMonitor - start process kube event
2025-02-06 01:56:13.23: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:56:13.23: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:56:13.23: PodMonitor - start process kube event
2025-02-06 01:56:13.23: empty line received
2025-02-06 01:56:13.23: PodMonitor - start process kube event
2025-02-06 01:56:28.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:56:28.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:56:28.68: PodMonitor - start process kube event
2025-02-06 01:56:28.68: empty line received
2025-02-06 01:56:28.68: PodMonitor - start process kube event
2025-02-06 01:56:41.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:56:41.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:56:41.90: PodMonitor - start process kube event
2025-02-06 01:56:41.91: empty line received
2025-02-06 01:56:41.91: PodMonitor - start process kube event
2025-02-06 01:56:46.16: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:56:46.16: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:56:46.16: PodMonitor - start process kube event
2025-02-06 01:56:46.16: empty line received
2025-02-06 01:56:46.16: PodMonitor - start process kube event
2025-02-06 01:56:49.33: NamespaceMonitor - Received BOOKMARK: oldResVer=9435 newResVer=9811
2025-02-06 01:56:49.33: NamespaceMonitor - start process kube event
2025-02-06 01:56:49.33: empty line received
2025-02-06 01:56:49.33: NamespaceMonitor - start process kube event
2025-02-06 01:56:51.25: PodMonitor - Received BOOKMARK: oldResVer=9802 newResVer=9895
2025-02-06 01:56:51.25: PodMonitor - start process kube event
2025-02-06 01:56:51.25: empty line received
2025-02-06 01:56:51.25: PodMonitor - start process kube event
2025-02-06 01:56:59.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:56:59.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:56:59.90: PodMonitor - start process kube event
2025-02-06 01:56:59.90: empty line received
2025-02-06 01:56:59.90: PodMonitor - start process kube event
2025-02-06 01:57:13.87: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:57:13.87: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:57:13.87: PodMonitor - start process kube event
2025-02-06 01:57:13.87: empty line received
2025-02-06 01:57:13.87: PodMonitor - start process kube event
2025-02-06 01:57:26.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:57:26.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:57:26.91: PodMonitor - start process kube event
2025-02-06 01:57:26.91: empty line received
2025-02-06 01:57:26.91: PodMonitor - start process kube event
2025-02-06 01:57:50.18: NamespaceMonitor - Received BOOKMARK: oldResVer=9811 newResVer=9811
2025-02-06 01:57:50.19: NamespaceMonitor - start process kube event
2025-02-06 01:57:50.19: empty line received
2025-02-06 01:57:50.19: NamespaceMonitor - start process kube event
2025-02-06 01:57:50.20: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:57:50.20: NetworkPolicyMonitor - start process kube event
2025-02-06 01:57:50.20: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:57:50.20: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:57:50.20: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-06 01:57:50.20: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 01:57:50.20: NetworkPolicyMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:57:50.20: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 01:57:50.20: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 01:57:50.21: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:57:50.21: IngressMonitor - start process kube event
2025-02-06 01:57:50.21: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:57:50.21: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:57:50.21: IngressMonitor - Connect Kube API result 0
2025-02-06 01:57:50.21: IngressMonitor - _schedule_vnc_sync
2025-02-06 01:57:50.21: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:57:50.21: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 01:57:50.21: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-06 01:57:50.21: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 01:57:50.21: VncKubernetes - vnc_sync - Ingress start
2025-02-06 01:57:50.21: VncKubernetes - vnc_sync - Ingress done
2025-02-06 01:57:50.21: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:57:50.21: NetworkPolicyMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:57:50.22: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:57:50.23: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:57:50.23: EndPointMonitor - start process kube event
2025-02-06 01:57:50.23: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:57:50.23: EndPointMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:57:50.23: EndPointMonitor - Connect Kube API result 0
2025-02-06 01:57:50.23: EndPointMonitor - _schedule_vnc_sync
2025-02-06 01:57:50.23: EndPointMonitor - Start Watching request https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:57:50.23: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 01:57:50.23: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 01:57:50.23: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:57:50.24: EndPointMonitor - Watches https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:57:50.24: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:57:50.24: ServiceMonitor - start process kube event
2025-02-06 01:57:50.24: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:57:50.24: ServiceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:57:50.24: ServiceMonitor - Connect Kube API result 0
2025-02-06 01:57:50.24: ServiceMonitor - _schedule_vnc_sync
2025-02-06 01:57:50.24: ServiceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:57:50.24: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 01:57:50.24: VncKubernetes - vnc_sync - Service start
2025-02-06 01:57:50.24: VncKubernetes - vnc_sync - Service done
2025-02-06 01:57:50.24: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:57:50.24: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:57:50.24: NetworkMonitor - start process kube event
2025-02-06 01:57:50.24: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9439
2025-02-06 01:57:50.24: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:57:50.24: NetworkMonitor - Connect Kube API result 0
2025-02-06 01:57:50.24: NetworkMonitor - _schedule_vnc_sync
2025-02-06 01:57:50.24: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})(timeout=120)
2025-02-06 01:57:50.24: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 01:57:50.24: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 01:57:50.24: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:57:50.25: ServiceMonitor - Watches https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:57:50.25: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})
2025-02-06 01:57:50.38: PodMonitor - Received BOOKMARK: oldResVer=9895 newResVer=9954
2025-02-06 01:57:50.39: PodMonitor - start process kube event
2025-02-06 01:57:50.39: empty line received
2025-02-06 01:57:50.39: PodMonitor - start process kube event
2025-02-06 01:58:18.51: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:58:18.51: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:58:18.51: PodMonitor - start process kube event
2025-02-06 01:58:18.51: empty line received
2025-02-06 01:58:18.51: PodMonitor - start process kube event
2025-02-06 01:58:45.17: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:58:45.17: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:58:45.17: PodMonitor - start process kube event
2025-02-06 01:58:45.17: empty line received
2025-02-06 01:58:45.17: PodMonitor - start process kube event
2025-02-06 01:58:49.81: NamespaceMonitor - Received BOOKMARK: oldResVer=9811 newResVer=9811
2025-02-06 01:58:49.82: NamespaceMonitor - start process kube event
2025-02-06 01:58:49.82: empty line received
2025-02-06 01:58:49.82: NamespaceMonitor - start process kube event
2025-02-06 01:58:50.40: ServiceMonitor - Received BOOKMARK: oldResVer=9435 newResVer=10047
2025-02-06 01:58:50.40: ServiceMonitor - start process kube event
2025-02-06 01:58:50.40: empty line received
2025-02-06 01:58:50.40: ServiceMonitor - start process kube event
2025-02-06 01:58:51.15: PodMonitor - Received BOOKMARK: oldResVer=9954 newResVer=10068
2025-02-06 01:58:51.16: PodMonitor - start process kube event
2025-02-06 01:58:51.16: empty line received
2025-02-06 01:58:51.16: PodMonitor - start process kube event
2025-02-06 01:59:19.02: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:59:19.02: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:59:19.02: PodMonitor - start process kube event
2025-02-06 01:59:19.02: empty line received
2025-02-06 01:59:19.02: PodMonitor - start process kube event
2025-02-06 01:59:31.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:59:31.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:59:31.90: PodMonitor - start process kube event
2025-02-06 01:59:31.90: empty line received
2025-02-06 01:59:31.90: PodMonitor - start process kube event
2025-02-06 01:59:45.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:59:45.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:59:45.68: PodMonitor - start process kube event
2025-02-06 01:59:45.68: empty line received
2025-02-06 01:59:45.68: PodMonitor - start process kube event
2025-02-06 01:59:50.13: NamespaceMonitor - Received BOOKMARK: oldResVer=9811 newResVer=9811
2025-02-06 01:59:50.13: NamespaceMonitor - start process kube event
2025-02-06 01:59:50.13: empty line received
2025-02-06 01:59:50.13: NamespaceMonitor - start process kube event
2025-02-06 01:59:50.22: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:59:50.22: NetworkPolicyMonitor - start process kube event
2025-02-06 01:59:50.22: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:59:50.22: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:59:50.22: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-06 01:59:50.22: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 01:59:50.22: NetworkPolicyMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:59:50.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 01:59:50.22: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 01:59:50.22: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:59:50.22: IngressMonitor - start process kube event
2025-02-06 01:59:50.22: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:59:50.22: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:59:50.22: IngressMonitor - Connect Kube API result 0
2025-02-06 01:59:50.22: IngressMonitor - _schedule_vnc_sync
2025-02-06 01:59:50.22: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:59:50.22: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 01:59:50.22: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-06 01:59:50.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 01:59:50.22: VncKubernetes - vnc_sync - Ingress start
2025-02-06 01:59:50.22: VncKubernetes - vnc_sync - Ingress done
2025-02-06 01:59:50.22: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:59:50.23: NetworkPolicyMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:59:50.23: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:59:50.24: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:59:50.24: EndPointMonitor - start process kube event
2025-02-06 01:59:50.24: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 01:59:50.24: EndPointMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:59:50.24: EndPointMonitor - Connect Kube API result 0
2025-02-06 01:59:50.24: EndPointMonitor - _schedule_vnc_sync
2025-02-06 01:59:50.24: EndPointMonitor - Start Watching request https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 01:59:50.24: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 01:59:50.24: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 01:59:50.24: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:59:50.24: EndPointMonitor - Watches https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 01:59:50.25: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 01:59:50.25: NetworkMonitor - start process kube event
2025-02-06 01:59:50.25: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9439
2025-02-06 01:59:50.25: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 01:59:50.25: NetworkMonitor - Connect Kube API result 0
2025-02-06 01:59:50.25: NetworkMonitor - _schedule_vnc_sync
2025-02-06 01:59:50.25: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})(timeout=120)
2025-02-06 01:59:50.25: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 01:59:50.25: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 01:59:50.25: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:59:50.26: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})
2025-02-06 01:59:50.57: ServiceMonitor - Received BOOKMARK: oldResVer=10047 newResVer=10047
2025-02-06 01:59:50.57: ServiceMonitor - start process kube event
2025-02-06 01:59:50.57: empty line received
2025-02-06 01:59:50.57: ServiceMonitor - start process kube event
2025-02-06 01:59:51.53: PodMonitor - Received BOOKMARK: oldResVer=10068 newResVer=10160
2025-02-06 01:59:51.53: PodMonitor - start process kube event
2025-02-06 01:59:51.53: PodMonitor - _schedule_vnc_sync
2025-02-06 01:59:51.53: empty line received
2025-02-06 01:59:51.53: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 01:59:51.53: VncKubernetes - vnc_sync - Pod start
2025-02-06 01:59:51.53: VncKubernetes - vnc_sync - Pod done
2025-02-06 01:59:51.53: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 01:59:51.53: PodMonitor - start process kube event
2025-02-06 01:59:59.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 01:59:59.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 01:59:59.90: PodMonitor - start process kube event
2025-02-06 01:59:59.90: empty line received
2025-02-06 01:59:59.90: PodMonitor - start process kube event
2025-02-06 02:00:49.56: IngressMonitor - Received BOOKMARK: oldResVer=9435 newResVer=10205
2025-02-06 02:00:49.56: IngressMonitor - start process kube event
2025-02-06 02:00:49.56: empty line received
2025-02-06 02:00:49.56: IngressMonitor - start process kube event
2025-02-06 02:00:50.08: NamespaceMonitor - Received BOOKMARK: oldResVer=9811 newResVer=9811
2025-02-06 02:00:50.08: NamespaceMonitor - start process kube event
2025-02-06 02:00:50.08: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 02:00:50.08: empty line received
2025-02-06 02:00:50.08: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 02:00:50.08: VncKubernetes - vnc_sync - Namespace start
2025-02-06 02:00:50.08: VncKubernetes - vnc_sync - Namespace done
2025-02-06 02:00:50.08: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:00:50.08: NamespaceMonitor - start process kube event
2025-02-06 02:00:51.28: ServiceMonitor - Received BOOKMARK: oldResVer=10047 newResVer=10047
2025-02-06 02:00:51.28: ServiceMonitor - start process kube event
2025-02-06 02:00:51.28: empty line received
2025-02-06 02:00:51.28: ServiceMonitor - start process kube event
2025-02-06 02:00:52.01: PodMonitor - Received BOOKMARK: oldResVer=10160 newResVer=10182
2025-02-06 02:00:52.01: PodMonitor - start process kube event
2025-02-06 02:00:52.01: empty line received
2025-02-06 02:00:52.01: PodMonitor - start process kube event
2025-02-06 02:01:30.32: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:01:30.32: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:01:30.32: PodMonitor - start process kube event
2025-02-06 02:01:30.32: empty line received
2025-02-06 02:01:30.32: PodMonitor - start process kube event
2025-02-06 02:01:31.37: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:01:31.37: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:01:31.37: PodMonitor - start process kube event
2025-02-06 02:01:31.37: empty line received
2025-02-06 02:01:31.37: PodMonitor - start process kube event
2025-02-06 02:01:49.84: EndPointMonitor - Received BOOKMARK: oldResVer=9435 newResVer=10263
2025-02-06 02:01:49.84: EndPointMonitor - start process kube event
2025-02-06 02:01:49.84: empty line received
2025-02-06 02:01:49.84: EndPointMonitor - start process kube event
2025-02-06 02:01:49.85: NamespaceMonitor - Received BOOKMARK: oldResVer=9811 newResVer=9811
2025-02-06 02:01:49.85: NamespaceMonitor - start process kube event
2025-02-06 02:01:49.85: empty line received
2025-02-06 02:01:49.85: NamespaceMonitor - start process kube event
2025-02-06 02:01:50.23: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 02:01:50.23: NetworkPolicyMonitor - start process kube event
2025-02-06 02:01:50.23: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9435
2025-02-06 02:01:50.23: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 02:01:50.23: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-06 02:01:50.23: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 02:01:50.23: NetworkPolicyMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})(timeout=120)
2025-02-06 02:01:50.24: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 02:01:50.24: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 02:01:50.24: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 02:01:50.24: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:01:50.24: NetworkPolicyMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9435'})
2025-02-06 02:01:50.26: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-06 02:01:50.26: NetworkMonitor - start process kube event
2025-02-06 02:01:50.26: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9439
2025-02-06 02:01:50.26: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 02:01:50.26: NetworkMonitor - Connect Kube API result 0
2025-02-06 02:01:50.26: NetworkMonitor - _schedule_vnc_sync
2025-02-06 02:01:50.26: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})(timeout=120)
2025-02-06 02:01:50.26: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 02:01:50.26: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 02:01:50.26: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:01:50.27: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9439'})
2025-02-06 02:01:50.72: IngressMonitor - Received BOOKMARK: oldResVer=10205 newResVer=10205
2025-02-06 02:01:50.72: IngressMonitor - start process kube event
2025-02-06 02:01:50.72: empty line received
2025-02-06 02:01:50.72: IngressMonitor - start process kube event
2025-02-06 02:01:51.28: ServiceMonitor - Received BOOKMARK: oldResVer=10047 newResVer=10047
2025-02-06 02:01:51.28: ServiceMonitor - start process kube event
2025-02-06 02:01:51.28: ServiceMonitor - _schedule_vnc_sync
2025-02-06 02:01:51.28: empty line received
2025-02-06 02:01:51.28: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 02:01:51.28: VncKubernetes - vnc_sync - Service start
2025-02-06 02:01:51.28: VncKubernetes - vnc_sync - Service done
2025-02-06 02:01:51.28: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:01:51.28: ServiceMonitor - start process kube event
2025-02-06 02:01:52.38: PodMonitor - Received BOOKMARK: oldResVer=10182 newResVer=10320
2025-02-06 02:01:52.38: PodMonitor - start process kube event
2025-02-06 02:01:52.38: empty line received
2025-02-06 02:01:52.38: PodMonitor - start process kube event
2025-02-06 02:01:59.10: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:01:59.10: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:01:59.10: PodMonitor - start process kube event
2025-02-06 02:01:59.10: empty line received
2025-02-06 02:01:59.10: PodMonitor - start process kube event
2025-02-06 02:02:37.13: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:02:37.13: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:02:37.13: PodMonitor - start process kube event
2025-02-06 02:02:37.13: empty line received
2025-02-06 02:02:37.13: PodMonitor - start process kube event
2025-02-06 02:02:50.32: EndPointMonitor - Received BOOKMARK: oldResVer=10263 newResVer=10263
2025-02-06 02:02:50.32: EndPointMonitor - start process kube event
2025-02-06 02:02:50.32: empty line received
2025-02-06 02:02:50.32: EndPointMonitor - start process kube event
2025-02-06 02:02:50.36: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9435 newResVer=10322
2025-02-06 02:02:50.36: NetworkPolicyMonitor - start process kube event
2025-02-06 02:02:50.36: empty line received
2025-02-06 02:02:50.36: NetworkPolicyMonitor - start process kube event
2025-02-06 02:02:50.41: NamespaceMonitor - Received BOOKMARK: oldResVer=9811 newResVer=9811
2025-02-06 02:02:50.41: NamespaceMonitor - start process kube event
2025-02-06 02:02:50.41: empty line received
2025-02-06 02:02:50.41: NamespaceMonitor - start process kube event
2025-02-06 02:02:50.72: IngressMonitor - Received BOOKMARK: oldResVer=10205 newResVer=10205
2025-02-06 02:02:50.72: IngressMonitor - start process kube event
2025-02-06 02:02:50.72: empty line received
2025-02-06 02:02:50.72: IngressMonitor - start process kube event
2025-02-06 02:02:51.01: NetworkMonitor - Received BOOKMARK: oldResVer=9439 newResVer=10426
2025-02-06 02:02:51.01: NetworkMonitor - start process kube event
2025-02-06 02:02:51.01: empty line received
2025-02-06 02:02:51.01: NetworkMonitor - start process kube event
2025-02-06 02:02:51.08: ServiceMonitor - Received BOOKMARK: oldResVer=10047 newResVer=10047
2025-02-06 02:02:51.08: ServiceMonitor - start process kube event
2025-02-06 02:02:51.08: empty line received
2025-02-06 02:02:51.08: ServiceMonitor - start process kube event
2025-02-06 02:02:53.24: PodMonitor - Received BOOKMARK: oldResVer=10320 newResVer=10412
2025-02-06 02:02:53.24: PodMonitor - start process kube event
2025-02-06 02:02:53.24: empty line received
2025-02-06 02:02:53.24: PodMonitor - start process kube event
2025-02-06 02:02:59.76: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:02:59.76: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:02:59.76: PodMonitor - start process kube event
2025-02-06 02:02:59.76: empty line received
2025-02-06 02:02:59.76: PodMonitor - start process kube event
2025-02-06 02:03:10.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:03:10.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:03:10.91: PodMonitor - start process kube event
2025-02-06 02:03:10.91: empty line received
2025-02-06 02:03:10.91: PodMonitor - start process kube event
2025-02-06 02:03:36.61: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:03:36.61: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:03:36.61: PodMonitor - start process kube event
2025-02-06 02:03:36.61: empty line received
2025-02-06 02:03:36.61: PodMonitor - start process kube event
2025-02-06 02:03:47.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:03:47.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:03:47.90: PodMonitor - start process kube event
2025-02-06 02:03:47.90: empty line received
2025-02-06 02:03:47.90: PodMonitor - start process kube event
2025-02-06 02:03:49.64: EndPointMonitor - Received BOOKMARK: oldResVer=10263 newResVer=10263
2025-02-06 02:03:49.64: EndPointMonitor - start process kube event
2025-02-06 02:03:49.64: empty line received
2025-02-06 02:03:49.64: EndPointMonitor - start process kube event
2025-02-06 02:03:50.36: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10322 newResVer=10322
2025-02-06 02:03:50.36: NetworkPolicyMonitor - start process kube event
2025-02-06 02:03:50.36: empty line received
2025-02-06 02:03:50.36: NetworkPolicyMonitor - start process kube event
2025-02-06 02:03:50.42: NetworkMonitor - Received BOOKMARK: oldResVer=10426 newResVer=10426
2025-02-06 02:03:50.42: NetworkMonitor - start process kube event
2025-02-06 02:03:50.42: empty line received
2025-02-06 02:03:50.42: NetworkMonitor - start process kube event
2025-02-06 02:03:51.02: NamespaceMonitor - Received BOOKMARK: oldResVer=9811 newResVer=9811
2025-02-06 02:03:51.02: NamespaceMonitor - start process kube event
2025-02-06 02:03:51.02: empty line received
2025-02-06 02:03:51.02: NamespaceMonitor - start process kube event
2025-02-06 02:03:51.07: ServiceMonitor - Received BOOKMARK: oldResVer=10047 newResVer=10047
2025-02-06 02:03:51.07: ServiceMonitor - start process kube event
2025-02-06 02:03:51.07: empty line received
2025-02-06 02:03:51.07: ServiceMonitor - start process kube event
2025-02-06 02:03:51.12: IngressMonitor - Received BOOKMARK: oldResVer=10205 newResVer=10205
2025-02-06 02:03:51.12: IngressMonitor - start process kube event
2025-02-06 02:03:51.12: IngressMonitor - _schedule_vnc_sync
2025-02-06 02:03:51.12: empty line received
2025-02-06 02:03:51.12: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 02:03:51.12: VncKubernetes - vnc_sync - Ingress start
2025-02-06 02:03:51.12: VncKubernetes - vnc_sync - Ingress done
2025-02-06 02:03:51.12: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:03:51.12: IngressMonitor - start process kube event
2025-02-06 02:03:52.68: PodMonitor - Received BOOKMARK: oldResVer=10412 newResVer=10519
2025-02-06 02:03:52.68: PodMonitor - start process kube event
2025-02-06 02:03:52.68: PodMonitor - _schedule_vnc_sync
2025-02-06 02:03:52.68: empty line received
2025-02-06 02:03:52.68: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 02:03:52.68: VncKubernetes - vnc_sync - Pod start
2025-02-06 02:03:52.68: VncKubernetes - vnc_sync - Pod done
2025-02-06 02:03:52.68: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:03:52.68: PodMonitor - start process kube event
2025-02-06 02:04:49.79: EndPointMonitor - Received BOOKMARK: oldResVer=10263 newResVer=10263
2025-02-06 02:04:49.79: EndPointMonitor - start process kube event
2025-02-06 02:04:49.79: EndPointMonitor - _schedule_vnc_sync
2025-02-06 02:04:49.79: empty line received
2025-02-06 02:04:49.79: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 02:04:49.79: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 02:04:49.79: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:04:49.79: EndPointMonitor - start process kube event
2025-02-06 02:04:50.10: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10322 newResVer=10322
2025-02-06 02:04:50.10: NetworkPolicyMonitor - start process kube event
2025-02-06 02:04:50.10: empty line received
2025-02-06 02:04:50.10: NetworkPolicyMonitor - start process kube event
2025-02-06 02:04:50.39: NetworkMonitor - Received BOOKMARK: oldResVer=10426 newResVer=10426
2025-02-06 02:04:50.39: NetworkMonitor - start process kube event
2025-02-06 02:04:50.39: empty line received
2025-02-06 02:04:50.39: NetworkMonitor - start process kube event
2025-02-06 02:04:50.57: ServiceMonitor - Received BOOKMARK: oldResVer=10047 newResVer=10047
2025-02-06 02:04:50.57: ServiceMonitor - start process kube event
2025-02-06 02:04:50.57: empty line received
2025-02-06 02:04:50.57: ServiceMonitor - start process kube event
2025-02-06 02:04:50.68: NamespaceMonitor - Received BOOKMARK: oldResVer=9811 newResVer=9811
2025-02-06 02:04:50.68: NamespaceMonitor - start process kube event
2025-02-06 02:04:50.68: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 02:04:50.68: empty line received
2025-02-06 02:04:50.68: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 02:04:50.68: VncKubernetes - vnc_sync - Namespace start
2025-02-06 02:04:50.68: VncKubernetes - vnc_sync - Namespace done
2025-02-06 02:04:50.68: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:04:50.68: NamespaceMonitor - start process kube event
2025-02-06 02:04:51.19: IngressMonitor - Received BOOKMARK: oldResVer=10205 newResVer=10205
2025-02-06 02:04:51.19: IngressMonitor - start process kube event
2025-02-06 02:04:51.19: empty line received
2025-02-06 02:04:51.19: IngressMonitor - start process kube event
2025-02-06 02:04:53.34: PodMonitor - Received BOOKMARK: oldResVer=10519 newResVer=10519
2025-02-06 02:04:53.35: PodMonitor - start process kube event
2025-02-06 02:04:53.35: empty line received
2025-02-06 02:04:53.35: PodMonitor - start process kube event
2025-02-06 02:05:49.79: EndPointMonitor - Received BOOKMARK: oldResVer=10263 newResVer=10263
2025-02-06 02:05:49.79: EndPointMonitor - start process kube event
2025-02-06 02:05:49.79: empty line received
2025-02-06 02:05:49.79: EndPointMonitor - start process kube event
2025-02-06 02:05:49.90: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10322 newResVer=10322
2025-02-06 02:05:49.90: NetworkPolicyMonitor - start process kube event
2025-02-06 02:05:49.90: empty line received
2025-02-06 02:05:49.90: NetworkPolicyMonitor - start process kube event
2025-02-06 02:05:50.24: NetworkMonitor - Received BOOKMARK: oldResVer=10426 newResVer=10426
2025-02-06 02:05:50.24: NetworkMonitor - start process kube event
2025-02-06 02:05:50.24: empty line received
2025-02-06 02:05:50.24: NetworkMonitor - start process kube event
2025-02-06 02:05:50.38: ServiceMonitor - Received BOOKMARK: oldResVer=10047 newResVer=10047
2025-02-06 02:05:50.38: ServiceMonitor - start process kube event
2025-02-06 02:05:50.38: empty line received
2025-02-06 02:05:50.38: ServiceMonitor - start process kube event
2025-02-06 02:05:51.09: NamespaceMonitor - Received BOOKMARK: oldResVer=9811 newResVer=9811
2025-02-06 02:05:51.09: NamespaceMonitor - start process kube event
2025-02-06 02:05:51.09: empty line received
2025-02-06 02:05:51.09: NamespaceMonitor - start process kube event
2025-02-06 02:05:51.66: IngressMonitor - Received BOOKMARK: oldResVer=10205 newResVer=10205
2025-02-06 02:05:51.66: IngressMonitor - start process kube event
2025-02-06 02:05:51.66: empty line received
2025-02-06 02:05:51.66: IngressMonitor - start process kube event
2025-02-06 02:05:52.79: PodMonitor - Received BOOKMARK: oldResVer=10519 newResVer=10519
2025-02-06 02:05:52.79: PodMonitor - start process kube event
2025-02-06 02:05:52.79: empty line received
2025-02-06 02:05:52.79: PodMonitor - start process kube event
2025-02-06 02:06:35.83: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:06:35.83: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:06:35.83: PodMonitor - start process kube event
2025-02-06 02:06:35.83: empty line received
2025-02-06 02:06:35.83: PodMonitor - start process kube event
2025-02-06 02:06:48.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:06:48.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:06:48.91: PodMonitor - start process kube event
2025-02-06 02:06:48.91: empty line received
2025-02-06 02:06:48.91: PodMonitor - start process kube event
2025-02-06 02:06:49.84: EndPointMonitor - Received BOOKMARK: oldResVer=10263 newResVer=10263
2025-02-06 02:06:49.84: EndPointMonitor - start process kube event
2025-02-06 02:06:49.84: empty line received
2025-02-06 02:06:49.84: EndPointMonitor - start process kube event
2025-02-06 02:06:49.91: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10322 newResVer=10322
2025-02-06 02:06:49.91: NetworkPolicyMonitor - start process kube event
2025-02-06 02:06:49.91: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 02:06:49.91: empty line received
2025-02-06 02:06:49.91: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 02:06:49.91: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 02:06:49.91: NetworkPolicyMonitor - start process kube event
2025-02-06 02:06:49.91: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 02:06:49.91: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:06:50.82: ServiceMonitor - Received BOOKMARK: oldResVer=10047 newResVer=10047
2025-02-06 02:06:50.82: ServiceMonitor - start process kube event
2025-02-06 02:06:50.82: ServiceMonitor - _schedule_vnc_sync
2025-02-06 02:06:50.82: empty line received
2025-02-06 02:06:50.82: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 02:06:50.82: VncKubernetes - vnc_sync - Service start
2025-02-06 02:06:50.82: VncKubernetes - vnc_sync - Service done
2025-02-06 02:06:50.82: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:06:50.82: ServiceMonitor - start process kube event
2025-02-06 02:06:51.06: NamespaceMonitor - Received BOOKMARK: oldResVer=9811 newResVer=10764
2025-02-06 02:06:51.06: NamespaceMonitor - start process kube event
2025-02-06 02:06:51.06: empty line received
2025-02-06 02:06:51.06: NamespaceMonitor - start process kube event
2025-02-06 02:06:51.26: NetworkMonitor - Received BOOKMARK: oldResVer=10426 newResVer=10426
2025-02-06 02:06:51.26: NetworkMonitor - start process kube event
2025-02-06 02:06:51.26: NetworkMonitor - _schedule_vnc_sync
2025-02-06 02:06:51.26: empty line received
2025-02-06 02:06:51.26: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 02:06:51.26: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 02:06:51.26: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:06:51.26: NetworkMonitor - start process kube event
2025-02-06 02:06:52.22: IngressMonitor - Received BOOKMARK: oldResVer=10205 newResVer=10205
2025-02-06 02:06:52.22: IngressMonitor - start process kube event
2025-02-06 02:06:52.22: empty line received
2025-02-06 02:06:52.22: IngressMonitor - start process kube event
2025-02-06 02:06:52.49: PodMonitor - Received BOOKMARK: oldResVer=10519 newResVer=10787
2025-02-06 02:06:52.49: PodMonitor - start process kube event
2025-02-06 02:06:52.49: empty line received
2025-02-06 02:06:52.49: PodMonitor - start process kube event
2025-02-06 02:07:49.40: EndPointMonitor - Received BOOKMARK: oldResVer=10263 newResVer=10263
2025-02-06 02:07:49.40: EndPointMonitor - start process kube event
2025-02-06 02:07:49.40: empty line received
2025-02-06 02:07:49.40: EndPointMonitor - start process kube event
2025-02-06 02:07:49.67: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10322 newResVer=10322
2025-02-06 02:07:49.67: NetworkPolicyMonitor - start process kube event
2025-02-06 02:07:49.67: empty line received
2025-02-06 02:07:49.67: NetworkPolicyMonitor - start process kube event
2025-02-06 02:07:50.65: NamespaceMonitor - Received BOOKMARK: oldResVer=10764 newResVer=10764
2025-02-06 02:07:50.65: NamespaceMonitor - start process kube event
2025-02-06 02:07:50.65: empty line received
2025-02-06 02:07:50.65: NamespaceMonitor - start process kube event
2025-02-06 02:07:51.46: ServiceMonitor - Received BOOKMARK: oldResVer=10047 newResVer=10047
2025-02-06 02:07:51.46: ServiceMonitor - start process kube event
2025-02-06 02:07:51.46: empty line received
2025-02-06 02:07:51.46: ServiceMonitor - start process kube event
2025-02-06 02:07:52.02: IngressMonitor - Received BOOKMARK: oldResVer=10205 newResVer=10205
2025-02-06 02:07:52.02: IngressMonitor - start process kube event
2025-02-06 02:07:52.02: IngressMonitor - _schedule_vnc_sync
2025-02-06 02:07:52.02: empty line received
2025-02-06 02:07:52.02: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 02:07:52.02: VncKubernetes - vnc_sync - Ingress start
2025-02-06 02:07:52.02: VncKubernetes - vnc_sync - Ingress done
2025-02-06 02:07:52.02: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:07:52.02: IngressMonitor - start process kube event
2025-02-06 02:07:52.39: NetworkMonitor - Received BOOKMARK: oldResVer=10426 newResVer=10426
2025-02-06 02:07:52.39: NetworkMonitor - start process kube event
2025-02-06 02:07:52.39: empty line received
2025-02-06 02:07:52.39: NetworkMonitor - start process kube event
2025-02-06 02:07:52.95: PodMonitor - Received BOOKMARK: oldResVer=10787 newResVer=10787
2025-02-06 02:07:52.95: PodMonitor - start process kube event
2025-02-06 02:07:52.95: PodMonitor - _schedule_vnc_sync
2025-02-06 02:07:52.95: empty line received
2025-02-06 02:07:52.95: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 02:07:52.95: VncKubernetes - vnc_sync - Pod start
2025-02-06 02:07:52.95: VncKubernetes - vnc_sync - Pod done
2025-02-06 02:07:52.95: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:07:52.95: PodMonitor - start process kube event
2025-02-06 02:08:07.13: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:08:07.13: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:08:07.13: PodMonitor - start process kube event
2025-02-06 02:08:07.13: empty line received
2025-02-06 02:08:07.13: PodMonitor - start process kube event
2025-02-06 02:08:45.13: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:08:45.13: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:08:45.13: PodMonitor - start process kube event
2025-02-06 02:08:45.13: empty line received
2025-02-06 02:08:45.13: PodMonitor - start process kube event
2025-02-06 02:08:49.74: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10322 newResVer=10322
2025-02-06 02:08:49.74: NetworkPolicyMonitor - start process kube event
2025-02-06 02:08:49.74: empty line received
2025-02-06 02:08:49.74: NetworkPolicyMonitor - start process kube event
2025-02-06 02:08:49.97: EndPointMonitor - Received BOOKMARK: oldResVer=10263 newResVer=10263
2025-02-06 02:08:49.97: EndPointMonitor - start process kube event
2025-02-06 02:08:49.97: EndPointMonitor - _schedule_vnc_sync
2025-02-06 02:08:49.97: empty line received
2025-02-06 02:08:49.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 02:08:49.98: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 02:08:49.98: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:08:49.98: EndPointMonitor - start process kube event
2025-02-06 02:08:50.53: NamespaceMonitor - Received BOOKMARK: oldResVer=10764 newResVer=10764
2025-02-06 02:08:50.53: NamespaceMonitor - start process kube event
2025-02-06 02:08:50.53: empty line received
2025-02-06 02:08:50.53: NamespaceMonitor - start process kube event
2025-02-06 02:08:51.41: ServiceMonitor - Received BOOKMARK: oldResVer=10047 newResVer=10047
2025-02-06 02:08:51.41: ServiceMonitor - start process kube event
2025-02-06 02:08:51.41: empty line received
2025-02-06 02:08:51.41: ServiceMonitor - start process kube event
2025-02-06 02:08:51.76: IngressMonitor - Received BOOKMARK: oldResVer=10205 newResVer=10205
2025-02-06 02:08:51.76: IngressMonitor - start process kube event
2025-02-06 02:08:51.76: empty line received
2025-02-06 02:08:51.76: IngressMonitor - start process kube event
2025-02-06 02:08:52.65: NetworkMonitor - Received BOOKMARK: oldResVer=10426 newResVer=10426
2025-02-06 02:08:52.65: NetworkMonitor - start process kube event
2025-02-06 02:08:52.65: empty line received
2025-02-06 02:08:52.65: NetworkMonitor - start process kube event
2025-02-06 02:08:52.98: PodMonitor - Received BOOKMARK: oldResVer=10787 newResVer=10954
2025-02-06 02:08:52.98: PodMonitor - start process kube event
2025-02-06 02:08:52.98: empty line received
2025-02-06 02:08:52.98: PodMonitor - start process kube event
2025-02-06 02:09:06.72: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:09:06.72: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:09:06.72: PodMonitor - start process kube event
2025-02-06 02:09:06.72: empty line received
2025-02-06 02:09:06.72: PodMonitor - start process kube event
2025-02-06 02:09:18.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:09:18.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:09:18.91: PodMonitor - start process kube event
2025-02-06 02:09:18.91: empty line received
2025-02-06 02:09:18.91: PodMonitor - start process kube event
2025-02-06 02:09:44.63: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:09:44.63: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:09:44.63: PodMonitor - start process kube event
2025-02-06 02:09:44.63: empty line received
2025-02-06 02:09:44.63: PodMonitor - start process kube event
2025-02-06 02:09:49.67: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10322 newResVer=10322
2025-02-06 02:09:49.67: NetworkPolicyMonitor - start process kube event
2025-02-06 02:09:49.67: empty line received
2025-02-06 02:09:49.67: NetworkPolicyMonitor - start process kube event
2025-02-06 02:09:50.00: EndPointMonitor - Received BOOKMARK: oldResVer=10263 newResVer=10263
2025-02-06 02:09:50.00: EndPointMonitor - start process kube event
2025-02-06 02:09:50.00: empty line received
2025-02-06 02:09:50.00: EndPointMonitor - start process kube event
2025-02-06 02:09:51.11: NamespaceMonitor - Received BOOKMARK: oldResVer=10764 newResVer=10764
2025-02-06 02:09:51.11: NamespaceMonitor - start process kube event
2025-02-06 02:09:51.11: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 02:09:51.11: empty line received
2025-02-06 02:09:51.11: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 02:09:51.11: VncKubernetes - vnc_sync - Namespace start
2025-02-06 02:09:51.11: VncKubernetes - vnc_sync - Namespace done
2025-02-06 02:09:51.11: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:09:51.11: NamespaceMonitor - start process kube event
2025-02-06 02:09:51.79: ServiceMonitor - Received BOOKMARK: oldResVer=10047 newResVer=11021
2025-02-06 02:09:51.79: ServiceMonitor - start process kube event
2025-02-06 02:09:51.79: empty line received
2025-02-06 02:09:51.79: ServiceMonitor - start process kube event
2025-02-06 02:09:52.21: IngressMonitor - Received BOOKMARK: oldResVer=10205 newResVer=10205
2025-02-06 02:09:52.21: IngressMonitor - start process kube event
2025-02-06 02:09:52.21: empty line received
2025-02-06 02:09:52.21: IngressMonitor - start process kube event
2025-02-06 02:09:52.31: NetworkMonitor - Received BOOKMARK: oldResVer=10426 newResVer=10426
2025-02-06 02:09:52.31: NetworkMonitor - start process kube event
2025-02-06 02:09:52.31: empty line received
2025-02-06 02:09:52.31: NetworkMonitor - start process kube event
2025-02-06 02:09:52.83: PodMonitor - Received BOOKMARK: oldResVer=10954 newResVer=11045
2025-02-06 02:09:52.83: PodMonitor - start process kube event
2025-02-06 02:09:52.83: empty line received
2025-02-06 02:09:52.83: PodMonitor - start process kube event
2025-02-06 02:09:58.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:09:58.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:09:58.90: PodMonitor - start process kube event
2025-02-06 02:09:58.90: empty line received
2025-02-06 02:09:58.90: PodMonitor - start process kube event
2025-02-06 02:10:49.63: EndPointMonitor - Received BOOKMARK: oldResVer=10263 newResVer=10263
2025-02-06 02:10:49.63: EndPointMonitor - start process kube event
2025-02-06 02:10:49.63: empty line received
2025-02-06 02:10:49.63: EndPointMonitor - start process kube event
2025-02-06 02:10:50.26: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10322 newResVer=10322
2025-02-06 02:10:50.26: NetworkPolicyMonitor - start process kube event
2025-02-06 02:10:50.26: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 02:10:50.26: empty line received
2025-02-06 02:10:50.26: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 02:10:50.26: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 02:10:50.26: NetworkPolicyMonitor - start process kube event
2025-02-06 02:10:50.27: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 02:10:50.27: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:10:51.30: NamespaceMonitor - Received BOOKMARK: oldResVer=10764 newResVer=10764
2025-02-06 02:10:51.30: NamespaceMonitor - start process kube event
2025-02-06 02:10:51.30: empty line received
2025-02-06 02:10:51.30: NamespaceMonitor - start process kube event
2025-02-06 02:10:51.69: ServiceMonitor - Received BOOKMARK: oldResVer=11021 newResVer=11021
2025-02-06 02:10:51.69: ServiceMonitor - start process kube event
2025-02-06 02:10:51.69: ServiceMonitor - _schedule_vnc_sync
2025-02-06 02:10:51.69: empty line received
2025-02-06 02:10:51.69: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 02:10:51.69: VncKubernetes - vnc_sync - Service start
2025-02-06 02:10:51.69: VncKubernetes - vnc_sync - Service done
2025-02-06 02:10:51.69: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:10:51.69: ServiceMonitor - start process kube event
2025-02-06 02:10:52.40: IngressMonitor - Received BOOKMARK: oldResVer=10205 newResVer=11098
2025-02-06 02:10:52.40: IngressMonitor - start process kube event
2025-02-06 02:10:52.40: empty line received
2025-02-06 02:10:52.40: IngressMonitor - start process kube event
2025-02-06 02:10:52.55: NetworkMonitor - Received BOOKMARK: oldResVer=10426 newResVer=10426
2025-02-06 02:10:52.55: NetworkMonitor - start process kube event
2025-02-06 02:10:52.55: NetworkMonitor - _schedule_vnc_sync
2025-02-06 02:10:52.55: empty line received
2025-02-06 02:10:52.55: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 02:10:52.55: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 02:10:52.55: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:10:52.55: NetworkMonitor - start process kube event
2025-02-06 02:10:53.13: PodMonitor - Received BOOKMARK: oldResVer=11045 newResVer=11065
2025-02-06 02:10:53.13: PodMonitor - start process kube event
2025-02-06 02:10:53.13: empty line received
2025-02-06 02:10:53.13: PodMonitor - start process kube event
2025-02-06 02:11:40.57: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:11:40.57: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:11:40.57: PodMonitor - start process kube event
2025-02-06 02:11:40.57: empty line received
2025-02-06 02:11:40.57: PodMonitor - start process kube event
2025-02-06 02:11:49.74: EndPointMonitor - Received BOOKMARK: oldResVer=10263 newResVer=11161
2025-02-06 02:11:49.74: EndPointMonitor - start process kube event
2025-02-06 02:11:49.74: empty line received
2025-02-06 02:11:49.74: EndPointMonitor - start process kube event
2025-02-06 02:11:50.06: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10322 newResVer=11220
2025-02-06 02:11:50.06: NetworkPolicyMonitor - start process kube event
2025-02-06 02:11:50.06: empty line received
2025-02-06 02:11:50.06: NetworkPolicyMonitor - start process kube event
2025-02-06 02:11:51.75: ServiceMonitor - Received BOOKMARK: oldResVer=11021 newResVer=11021
2025-02-06 02:11:51.75: ServiceMonitor - start process kube event
2025-02-06 02:11:51.75: empty line received
2025-02-06 02:11:51.75: ServiceMonitor - start process kube event
2025-02-06 02:11:52.30: NamespaceMonitor - Received BOOKMARK: oldResVer=10764 newResVer=10764
2025-02-06 02:11:52.30: NamespaceMonitor - start process kube event
2025-02-06 02:11:52.30: empty line received
2025-02-06 02:11:52.30: NamespaceMonitor - start process kube event
2025-02-06 02:11:52.44: IngressMonitor - Received BOOKMARK: oldResVer=11098 newResVer=11098
2025-02-06 02:11:52.44: IngressMonitor - start process kube event
2025-02-06 02:11:52.44: IngressMonitor - _schedule_vnc_sync
2025-02-06 02:11:52.44: empty line received
2025-02-06 02:11:52.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 02:11:52.44: VncKubernetes - vnc_sync - Ingress start
2025-02-06 02:11:52.44: VncKubernetes - vnc_sync - Ingress done
2025-02-06 02:11:52.44: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:11:52.44: IngressMonitor - start process kube event
2025-02-06 02:11:53.02: NetworkMonitor - Received BOOKMARK: oldResVer=10426 newResVer=10426
2025-02-06 02:11:53.02: NetworkMonitor - start process kube event
2025-02-06 02:11:53.02: empty line received
2025-02-06 02:11:53.02: NetworkMonitor - start process kube event
2025-02-06 02:11:53.53: PodMonitor - Received BOOKMARK: oldResVer=11065 newResVer=11209
2025-02-06 02:11:53.53: PodMonitor - start process kube event
2025-02-06 02:11:53.53: PodMonitor - _schedule_vnc_sync
2025-02-06 02:11:53.53: empty line received
2025-02-06 02:11:53.53: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 02:11:53.53: VncKubernetes - vnc_sync - Pod start
2025-02-06 02:11:53.53: VncKubernetes - vnc_sync - Pod done
2025-02-06 02:11:53.53: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:11:53.53: PodMonitor - start process kube event
2025-02-06 02:11:55.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:11:55.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:11:55.90: PodMonitor - start process kube event
2025-02-06 02:11:55.90: empty line received
2025-02-06 02:11:55.90: PodMonitor - start process kube event
2025-02-06 02:12:50.20: EndPointMonitor - Received BOOKMARK: oldResVer=11161 newResVer=11161
2025-02-06 02:12:50.20: EndPointMonitor - start process kube event
2025-02-06 02:12:50.20: EndPointMonitor - _schedule_vnc_sync
2025-02-06 02:12:50.20: empty line received
2025-02-06 02:12:50.20: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 02:12:50.20: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 02:12:50.20: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:12:50.20: EndPointMonitor - start process kube event
2025-02-06 02:12:50.46: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11220 newResVer=11220
2025-02-06 02:12:50.46: NetworkPolicyMonitor - start process kube event
2025-02-06 02:12:50.46: empty line received
2025-02-06 02:12:50.46: NetworkPolicyMonitor - start process kube event
2025-02-06 02:12:51.61: ServiceMonitor - Received BOOKMARK: oldResVer=11021 newResVer=11021
2025-02-06 02:12:51.61: ServiceMonitor - start process kube event
2025-02-06 02:12:51.61: empty line received
2025-02-06 02:12:51.61: ServiceMonitor - start process kube event
2025-02-06 02:12:52.21: NamespaceMonitor - Received BOOKMARK: oldResVer=10764 newResVer=10764
2025-02-06 02:12:52.21: NamespaceMonitor - start process kube event
2025-02-06 02:12:52.21: empty line received
2025-02-06 02:12:52.21: NamespaceMonitor - start process kube event
2025-02-06 02:12:52.55: IngressMonitor - Received BOOKMARK: oldResVer=11098 newResVer=11098
2025-02-06 02:12:52.56: IngressMonitor - start process kube event
2025-02-06 02:12:52.56: empty line received
2025-02-06 02:12:52.56: IngressMonitor - start process kube event
2025-02-06 02:12:52.68: NetworkMonitor - Received BOOKMARK: oldResVer=10426 newResVer=10426
2025-02-06 02:12:52.68: NetworkMonitor - start process kube event
2025-02-06 02:12:52.68: empty line received
2025-02-06 02:12:52.68: NetworkMonitor - start process kube event
2025-02-06 02:12:54.44: PodMonitor - Received BOOKMARK: oldResVer=11209 newResVer=11233
2025-02-06 02:12:54.44: PodMonitor - start process kube event
2025-02-06 02:12:54.44: empty line received
2025-02-06 02:12:54.44: PodMonitor - start process kube event
2025-02-06 02:13:49.80: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11220 newResVer=11220
2025-02-06 02:13:49.80: NetworkPolicyMonitor - start process kube event
2025-02-06 02:13:49.80: empty line received
2025-02-06 02:13:49.80: NetworkPolicyMonitor - start process kube event
2025-02-06 02:13:49.99: EndPointMonitor - Received BOOKMARK: oldResVer=11161 newResVer=11161
2025-02-06 02:13:49.99: EndPointMonitor - start process kube event
2025-02-06 02:13:49.99: empty line received
2025-02-06 02:13:49.99: EndPointMonitor - start process kube event
2025-02-06 02:13:51.76: ServiceMonitor - Received BOOKMARK: oldResVer=11021 newResVer=11021
2025-02-06 02:13:51.76: ServiceMonitor - start process kube event
2025-02-06 02:13:51.76: empty line received
2025-02-06 02:13:51.76: ServiceMonitor - start process kube event
2025-02-06 02:13:52.07: NamespaceMonitor - Received BOOKMARK: oldResVer=10764 newResVer=10764
2025-02-06 02:13:52.07: NamespaceMonitor - start process kube event
2025-02-06 02:13:52.07: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 02:13:52.07: empty line received
2025-02-06 02:13:52.07: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 02:13:52.07: VncKubernetes - vnc_sync - Namespace start
2025-02-06 02:13:52.07: VncKubernetes - vnc_sync - Namespace done
2025-02-06 02:13:52.07: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:13:52.07: NamespaceMonitor - start process kube event
2025-02-06 02:13:53.19: NetworkMonitor - Received BOOKMARK: oldResVer=10426 newResVer=11372
2025-02-06 02:13:53.19: NetworkMonitor - start process kube event
2025-02-06 02:13:53.19: empty line received
2025-02-06 02:13:53.19: NetworkMonitor - start process kube event
2025-02-06 02:13:53.32: IngressMonitor - Received BOOKMARK: oldResVer=11098 newResVer=11098
2025-02-06 02:13:53.32: IngressMonitor - start process kube event
2025-02-06 02:13:53.32: empty line received
2025-02-06 02:13:53.32: IngressMonitor - start process kube event
2025-02-06 02:13:54.53: PodMonitor - Received BOOKMARK: oldResVer=11233 newResVer=11233
2025-02-06 02:13:54.53: PodMonitor - start process kube event
2025-02-06 02:13:54.53: empty line received
2025-02-06 02:13:54.53: PodMonitor - start process kube event
2025-02-06 02:14:20.45: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:14:20.45: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:14:20.45: PodMonitor - start process kube event
2025-02-06 02:14:20.45: empty line received
2025-02-06 02:14:20.45: PodMonitor - start process kube event
2025-02-06 02:14:46.17: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:14:46.17: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:14:46.17: PodMonitor - start process kube event
2025-02-06 02:14:46.17: empty line received
2025-02-06 02:14:46.17: PodMonitor - start process kube event
2025-02-06 02:14:49.74: EndPointMonitor - Received BOOKMARK: oldResVer=11161 newResVer=11161
2025-02-06 02:14:49.74: EndPointMonitor - start process kube event
2025-02-06 02:14:49.74: empty line received
2025-02-06 02:14:49.74: EndPointMonitor - start process kube event
2025-02-06 02:14:50.46: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11220 newResVer=11220
2025-02-06 02:14:50.46: NetworkPolicyMonitor - start process kube event
2025-02-06 02:14:50.46: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 02:14:50.46: empty line received
2025-02-06 02:14:50.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 02:14:50.46: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 02:14:50.46: NetworkPolicyMonitor - start process kube event
2025-02-06 02:14:50.46: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 02:14:50.46: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:14:51.79: NamespaceMonitor - Received BOOKMARK: oldResVer=10764 newResVer=10764
2025-02-06 02:14:51.79: NamespaceMonitor - start process kube event
2025-02-06 02:14:51.79: empty line received
2025-02-06 02:14:51.79: NamespaceMonitor - start process kube event
2025-02-06 02:14:52.52: ServiceMonitor - Received BOOKMARK: oldResVer=11021 newResVer=11021
2025-02-06 02:14:52.52: ServiceMonitor - start process kube event
2025-02-06 02:14:52.52: ServiceMonitor - _schedule_vnc_sync
2025-02-06 02:14:52.52: empty line received
2025-02-06 02:14:52.52: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 02:14:52.52: VncKubernetes - vnc_sync - Service start
2025-02-06 02:14:52.52: VncKubernetes - vnc_sync - Service done
2025-02-06 02:14:52.52: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:14:52.52: ServiceMonitor - start process kube event
2025-02-06 02:14:52.69: NetworkMonitor - Received BOOKMARK: oldResVer=11372 newResVer=11372
2025-02-06 02:14:52.69: NetworkMonitor - start process kube event
2025-02-06 02:14:52.69: NetworkMonitor - _schedule_vnc_sync
2025-02-06 02:14:52.69: empty line received
2025-02-06 02:14:52.69: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 02:14:52.69: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 02:14:52.69: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:14:52.69: NetworkMonitor - start process kube event
2025-02-06 02:14:53.19: IngressMonitor - Received BOOKMARK: oldResVer=11098 newResVer=11098
2025-02-06 02:14:53.19: IngressMonitor - start process kube event
2025-02-06 02:14:53.19: empty line received
2025-02-06 02:14:53.19: IngressMonitor - start process kube event
2025-02-06 02:14:54.82: PodMonitor - Received BOOKMARK: oldResVer=11233 newResVer=11473
2025-02-06 02:14:54.82: PodMonitor - start process kube event
2025-02-06 02:14:54.82: empty line received
2025-02-06 02:14:54.82: PodMonitor - start process kube event
2025-02-06 02:15:21.07: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:15:21.07: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:15:21.07: PodMonitor - start process kube event
2025-02-06 02:15:21.07: empty line received
2025-02-06 02:15:21.07: PodMonitor - start process kube event
2025-02-06 02:15:31.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:15:31.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:15:31.90: PodMonitor - start process kube event
2025-02-06 02:15:31.90: empty line received
2025-02-06 02:15:31.90: PodMonitor - start process kube event
2025-02-06 02:15:45.80: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:15:45.80: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:15:45.80: PodMonitor - start process kube event
2025-02-06 02:15:45.80: empty line received
2025-02-06 02:15:45.80: PodMonitor - start process kube event
2025-02-06 02:15:49.43: EndPointMonitor - Received BOOKMARK: oldResVer=11161 newResVer=11161
2025-02-06 02:15:49.43: EndPointMonitor - start process kube event
2025-02-06 02:15:49.43: empty line received
2025-02-06 02:15:49.43: EndPointMonitor - start process kube event
2025-02-06 02:15:50.25: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11220 newResVer=11220
2025-02-06 02:15:50.25: NetworkPolicyMonitor - start process kube event
2025-02-06 02:15:50.25: empty line received
2025-02-06 02:15:50.25: NetworkPolicyMonitor - start process kube event
2025-02-06 02:15:51.98: NamespaceMonitor - Received BOOKMARK: oldResVer=10764 newResVer=10764
2025-02-06 02:15:51.98: NamespaceMonitor - start process kube event
2025-02-06 02:15:51.98: empty line received
2025-02-06 02:15:51.98: NamespaceMonitor - start process kube event
2025-02-06 02:15:52.52: ServiceMonitor - Received BOOKMARK: oldResVer=11021 newResVer=11021
2025-02-06 02:15:52.52: ServiceMonitor - start process kube event
2025-02-06 02:15:52.52: empty line received
2025-02-06 02:15:52.52: ServiceMonitor - start process kube event
2025-02-06 02:15:52.73: IngressMonitor - Received BOOKMARK: oldResVer=11098 newResVer=11098
2025-02-06 02:15:52.73: IngressMonitor - start process kube event
2025-02-06 02:15:52.73: IngressMonitor - _schedule_vnc_sync
2025-02-06 02:15:52.73: empty line received
2025-02-06 02:15:52.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 02:15:52.73: VncKubernetes - vnc_sync - Ingress start
2025-02-06 02:15:52.73: VncKubernetes - vnc_sync - Ingress done
2025-02-06 02:15:52.73: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:15:52.73: IngressMonitor - start process kube event
2025-02-06 02:15:53.21: NetworkMonitor - Received BOOKMARK: oldResVer=11372 newResVer=11372
2025-02-06 02:15:53.21: NetworkMonitor - start process kube event
2025-02-06 02:15:53.21: empty line received
2025-02-06 02:15:53.21: NetworkMonitor - start process kube event
2025-02-06 02:15:54.53: PodMonitor - Received BOOKMARK: oldResVer=11473 newResVer=11559
2025-02-06 02:15:54.53: PodMonitor - start process kube event
2025-02-06 02:15:54.53: PodMonitor - _schedule_vnc_sync
2025-02-06 02:15:54.53: empty line received
2025-02-06 02:15:54.53: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 02:15:54.53: VncKubernetes - vnc_sync - Pod start
2025-02-06 02:15:54.53: VncKubernetes - vnc_sync - Pod done
2025-02-06 02:15:54.53: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:15:54.53: PodMonitor - start process kube event
2025-02-06 02:15:59.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:15:59.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:15:59.90: PodMonitor - start process kube event
2025-02-06 02:15:59.90: empty line received
2025-02-06 02:15:59.90: PodMonitor - start process kube event
2025-02-06 02:16:44.52: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:16:44.53: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:16:44.53: PodMonitor - start process kube event
2025-02-06 02:16:44.53: empty line received
2025-02-06 02:16:44.53: PodMonitor - start process kube event
2025-02-06 02:16:45.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:16:45.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:16:45.59: PodMonitor - start process kube event
2025-02-06 02:16:45.59: empty line received
2025-02-06 02:16:45.59: PodMonitor - start process kube event
2025-02-06 02:16:49.48: EndPointMonitor - Received BOOKMARK: oldResVer=11161 newResVer=11161
2025-02-06 02:16:49.48: EndPointMonitor - start process kube event
2025-02-06 02:16:49.48: empty line received
2025-02-06 02:16:49.48: EndPointMonitor - start process kube event
2025-02-06 02:16:49.56: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11220 newResVer=11220
2025-02-06 02:16:49.56: NetworkPolicyMonitor - start process kube event
2025-02-06 02:16:49.56: empty line received
2025-02-06 02:16:49.56: NetworkPolicyMonitor - start process kube event
2025-02-06 02:16:51.86: NamespaceMonitor - Received BOOKMARK: oldResVer=10764 newResVer=10764
2025-02-06 02:16:51.86: NamespaceMonitor - start process kube event
2025-02-06 02:16:51.86: empty line received
2025-02-06 02:16:51.86: NamespaceMonitor - start process kube event
2025-02-06 02:16:52.52: ServiceMonitor - Received BOOKMARK: oldResVer=11021 newResVer=11021
2025-02-06 02:16:52.52: ServiceMonitor - start process kube event
2025-02-06 02:16:52.52: empty line received
2025-02-06 02:16:52.52: ServiceMonitor - start process kube event
2025-02-06 02:16:53.33: NetworkMonitor - Received BOOKMARK: oldResVer=11372 newResVer=11372
2025-02-06 02:16:53.33: NetworkMonitor - start process kube event
2025-02-06 02:16:53.33: empty line received
2025-02-06 02:16:53.33: NetworkMonitor - start process kube event
2025-02-06 02:16:53.48: IngressMonitor - Received BOOKMARK: oldResVer=11098 newResVer=11098
2025-02-06 02:16:53.48: IngressMonitor - start process kube event
2025-02-06 02:16:53.48: empty line received
2025-02-06 02:16:53.48: IngressMonitor - start process kube event
2025-02-06 02:16:54.93: PodMonitor - Received BOOKMARK: oldResVer=11559 newResVer=11646
2025-02-06 02:16:54.93: PodMonitor - start process kube event
2025-02-06 02:16:54.93: empty line received
2025-02-06 02:16:54.93: PodMonitor - start process kube event
2025-02-06 02:16:59.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:16:59.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:16:59.91: PodMonitor - start process kube event
2025-02-06 02:16:59.91: empty line received
2025-02-06 02:16:59.91: PodMonitor - start process kube event
2025-02-06 02:17:50.05: EndPointMonitor - Received BOOKMARK: oldResVer=11161 newResVer=11161
2025-02-06 02:17:50.05: EndPointMonitor - start process kube event
2025-02-06 02:17:50.05: EndPointMonitor - _schedule_vnc_sync
2025-02-06 02:17:50.05: empty line received
2025-02-06 02:17:50.05: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 02:17:50.05: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 02:17:50.05: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:17:50.05: EndPointMonitor - start process kube event
2025-02-06 02:17:50.48: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11220 newResVer=11220
2025-02-06 02:17:50.48: NetworkPolicyMonitor - start process kube event
2025-02-06 02:17:50.48: empty line received
2025-02-06 02:17:50.48: NetworkPolicyMonitor - start process kube event
2025-02-06 02:17:52.09: NamespaceMonitor - Received BOOKMARK: oldResVer=10764 newResVer=11692
2025-02-06 02:17:52.09: NamespaceMonitor - start process kube event
2025-02-06 02:17:52.09: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 02:17:52.09: empty line received
2025-02-06 02:17:52.09: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 02:17:52.09: VncKubernetes - vnc_sync - Namespace start
2025-02-06 02:17:52.09: VncKubernetes - vnc_sync - Namespace done
2025-02-06 02:17:52.09: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:17:52.09: NamespaceMonitor - start process kube event
2025-02-06 02:17:53.16: IngressMonitor - Received BOOKMARK: oldResVer=11098 newResVer=11098
2025-02-06 02:17:53.16: IngressMonitor - start process kube event
2025-02-06 02:17:53.16: empty line received
2025-02-06 02:17:53.16: IngressMonitor - start process kube event
2025-02-06 02:17:53.44: ServiceMonitor - Received BOOKMARK: oldResVer=11021 newResVer=11021
2025-02-06 02:17:53.44: ServiceMonitor - start process kube event
2025-02-06 02:17:53.44: empty line received
2025-02-06 02:17:53.44: ServiceMonitor - start process kube event
2025-02-06 02:17:53.84: NetworkMonitor - Received BOOKMARK: oldResVer=11372 newResVer=11372
2025-02-06 02:17:53.84: NetworkMonitor - start process kube event
2025-02-06 02:17:53.84: empty line received
2025-02-06 02:17:53.84: NetworkMonitor - start process kube event
2025-02-06 02:17:54.68: PodMonitor - Received BOOKMARK: oldResVer=11646 newResVer=11669
2025-02-06 02:17:54.68: PodMonitor - start process kube event
2025-02-06 02:17:54.68: empty line received
2025-02-06 02:17:54.68: PodMonitor - start process kube event
2025-02-06 02:18:49.99: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11220 newResVer=11220
2025-02-06 02:18:49.99: NetworkPolicyMonitor - start process kube event
2025-02-06 02:18:49.99: empty line received
2025-02-06 02:18:49.99: NetworkPolicyMonitor - start process kube event
2025-02-06 02:18:50.33: EndPointMonitor - Received BOOKMARK: oldResVer=11161 newResVer=11161
2025-02-06 02:18:50.33: EndPointMonitor - start process kube event
2025-02-06 02:18:50.33: empty line received
2025-02-06 02:18:50.33: EndPointMonitor - start process kube event
2025-02-06 02:18:51.34: NamespaceMonitor - Received BOOKMARK: oldResVer=11692 newResVer=11692
2025-02-06 02:18:51.34: NamespaceMonitor - start process kube event
2025-02-06 02:18:51.34: empty line received
2025-02-06 02:18:51.34: NamespaceMonitor - start process kube event
2025-02-06 02:18:52.77: IngressMonitor - Received BOOKMARK: oldResVer=11098 newResVer=11098
2025-02-06 02:18:52.77: IngressMonitor - start process kube event
2025-02-06 02:18:52.77: empty line received
2025-02-06 02:18:52.77: IngressMonitor - start process kube event
2025-02-06 02:18:54.04: NetworkMonitor - Received BOOKMARK: oldResVer=11372 newResVer=11372
2025-02-06 02:18:54.04: NetworkMonitor - start process kube event
2025-02-06 02:18:54.04: NetworkMonitor - _schedule_vnc_sync
2025-02-06 02:18:54.04: empty line received
2025-02-06 02:18:54.04: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 02:18:54.04: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 02:18:54.04: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:18:54.04: NetworkMonitor - start process kube event
2025-02-06 02:18:54.32: ServiceMonitor - Received BOOKMARK: oldResVer=11021 newResVer=11021
2025-02-06 02:18:54.32: ServiceMonitor - start process kube event
2025-02-06 02:18:54.32: ServiceMonitor - _schedule_vnc_sync
2025-02-06 02:18:54.32: empty line received
2025-02-06 02:18:54.32: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 02:18:54.32: VncKubernetes - vnc_sync - Service start
2025-02-06 02:18:54.32: VncKubernetes - vnc_sync - Service done
2025-02-06 02:18:54.32: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:18:54.32: ServiceMonitor - start process kube event
2025-02-06 02:18:55.14: PodMonitor - Received BOOKMARK: oldResVer=11669 newResVer=11669
2025-02-06 02:18:55.14: PodMonitor - start process kube event
2025-02-06 02:18:55.14: empty line received
2025-02-06 02:18:55.14: PodMonitor - start process kube event
2025-02-06 02:19:49.76: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11220 newResVer=11220
2025-02-06 02:19:49.76: NetworkPolicyMonitor - start process kube event
2025-02-06 02:19:49.76: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 02:19:49.76: empty line received
2025-02-06 02:19:49.76: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 02:19:49.76: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 02:19:49.76: NetworkPolicyMonitor - start process kube event
2025-02-06 02:19:49.77: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 02:19:49.77: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:19:50.23: EndPointMonitor - Received BOOKMARK: oldResVer=11161 newResVer=11161
2025-02-06 02:19:50.23: EndPointMonitor - start process kube event
2025-02-06 02:19:50.23: empty line received
2025-02-06 02:19:50.23: EndPointMonitor - start process kube event
2025-02-06 02:19:51.94: NamespaceMonitor - Received BOOKMARK: oldResVer=11692 newResVer=11692
2025-02-06 02:19:51.94: NamespaceMonitor - start process kube event
2025-02-06 02:19:51.94: empty line received
2025-02-06 02:19:51.94: NamespaceMonitor - start process kube event
2025-02-06 02:19:52.72: IngressMonitor - Received BOOKMARK: oldResVer=11098 newResVer=11098
2025-02-06 02:19:52.72: IngressMonitor - start process kube event
2025-02-06 02:19:52.72: empty line received
2025-02-06 02:19:52.72: IngressMonitor - start process kube event
2025-02-06 02:19:54.04: ServiceMonitor - Received BOOKMARK: oldResVer=11021 newResVer=11021
2025-02-06 02:19:54.04: ServiceMonitor - start process kube event
2025-02-06 02:19:54.04: empty line received
2025-02-06 02:19:54.04: ServiceMonitor - start process kube event
2025-02-06 02:19:54.25: NetworkMonitor - Received BOOKMARK: oldResVer=11372 newResVer=11372
2025-02-06 02:19:54.25: NetworkMonitor - start process kube event
2025-02-06 02:19:54.25: empty line received
2025-02-06 02:19:54.25: NetworkMonitor - start process kube event
2025-02-06 02:19:54.91: PodMonitor - Received BOOKMARK: oldResVer=11669 newResVer=11669
2025-02-06 02:19:54.91: PodMonitor - start process kube event
2025-02-06 02:19:54.91: PodMonitor - _schedule_vnc_sync
2025-02-06 02:19:54.91: empty line received
2025-02-06 02:19:54.91: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 02:19:54.91: VncKubernetes - vnc_sync - Pod start
2025-02-06 02:19:54.91: VncKubernetes - vnc_sync - Pod done
2025-02-06 02:19:54.91: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:19:54.91: PodMonitor - start process kube event
2025-02-06 02:20:33.38: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:20:33.38: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:20:33.38: PodMonitor - start process kube event
2025-02-06 02:20:33.38: empty line received
2025-02-06 02:20:33.38: PodMonitor - start process kube event
2025-02-06 02:20:49.45: EndPointMonitor - Received BOOKMARK: oldResVer=11161 newResVer=11161
2025-02-06 02:20:49.45: EndPointMonitor - start process kube event
2025-02-06 02:20:49.45: empty line received
2025-02-06 02:20:49.45: EndPointMonitor - start process kube event
2025-02-06 02:20:49.71: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11220 newResVer=11220
2025-02-06 02:20:49.71: NetworkPolicyMonitor - start process kube event
2025-02-06 02:20:49.71: empty line received
2025-02-06 02:20:49.71: NetworkPolicyMonitor - start process kube event
2025-02-06 02:20:52.19: NamespaceMonitor - Received BOOKMARK: oldResVer=11692 newResVer=11692
2025-02-06 02:20:52.19: NamespaceMonitor - start process kube event
2025-02-06 02:20:52.19: empty line received
2025-02-06 02:20:52.19: NamespaceMonitor - start process kube event
2025-02-06 02:20:52.90: IngressMonitor - Received BOOKMARK: oldResVer=11098 newResVer=11960
2025-02-06 02:20:52.90: IngressMonitor - start process kube event
2025-02-06 02:20:52.90: IngressMonitor - _schedule_vnc_sync
2025-02-06 02:20:52.90: empty line received
2025-02-06 02:20:52.90: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 02:20:52.90: VncKubernetes - vnc_sync - Ingress start
2025-02-06 02:20:52.90: VncKubernetes - vnc_sync - Ingress done
2025-02-06 02:20:52.90: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:20:52.90: IngressMonitor - start process kube event
2025-02-06 02:20:54.14: ServiceMonitor - Received BOOKMARK: oldResVer=11021 newResVer=11959
2025-02-06 02:20:54.14: ServiceMonitor - start process kube event
2025-02-06 02:20:54.14: empty line received
2025-02-06 02:20:54.14: ServiceMonitor - start process kube event
2025-02-06 02:20:54.74: NetworkMonitor - Received BOOKMARK: oldResVer=11372 newResVer=11372
2025-02-06 02:20:54.74: NetworkMonitor - start process kube event
2025-02-06 02:20:54.74: empty line received
2025-02-06 02:20:54.74: NetworkMonitor - start process kube event
2025-02-06 02:20:55.19: PodMonitor - Received BOOKMARK: oldResVer=11669 newResVer=11968
2025-02-06 02:20:55.19: PodMonitor - start process kube event
2025-02-06 02:20:55.19: empty line received
2025-02-06 02:20:55.19: PodMonitor - start process kube event
2025-02-06 02:20:59.10: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:20:59.10: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:20:59.10: PodMonitor - start process kube event
2025-02-06 02:20:59.10: empty line received
2025-02-06 02:20:59.10: PodMonitor - start process kube event
2025-02-06 02:21:34.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:21:34.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:21:34.06: PodMonitor - start process kube event
2025-02-06 02:21:34.06: empty line received
2025-02-06 02:21:34.06: PodMonitor - start process kube event
2025-02-06 02:21:45.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:21:45.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:21:45.91: PodMonitor - start process kube event
2025-02-06 02:21:45.91: empty line received
2025-02-06 02:21:45.91: PodMonitor - start process kube event
2025-02-06 02:21:46.50: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:21:46.50: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:21:46.50: PodMonitor - start process kube event
2025-02-06 02:21:46.50: empty line received
2025-02-06 02:21:46.50: PodMonitor - start process kube event
2025-02-06 02:21:49.84: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11220 newResVer=11220
2025-02-06 02:21:49.84: NetworkPolicyMonitor - start process kube event
2025-02-06 02:21:49.84: empty line received
2025-02-06 02:21:49.84: NetworkPolicyMonitor - start process kube event
2025-02-06 02:21:50.10: EndPointMonitor - Received BOOKMARK: oldResVer=11161 newResVer=12032
2025-02-06 02:21:50.10: EndPointMonitor - start process kube event
2025-02-06 02:21:50.10: EndPointMonitor - _schedule_vnc_sync
2025-02-06 02:21:50.10: empty line received
2025-02-06 02:21:50.10: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 02:21:50.10: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 02:21:50.10: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:21:50.10: EndPointMonitor - start process kube event
2025-02-06 02:21:51.41: NamespaceMonitor - Received BOOKMARK: oldResVer=11692 newResVer=11692
2025-02-06 02:21:51.41: NamespaceMonitor - start process kube event
2025-02-06 02:21:51.41: empty line received
2025-02-06 02:21:51.41: NamespaceMonitor - start process kube event
2025-02-06 02:21:53.14: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=11960
2025-02-06 02:21:53.14: IngressMonitor - start process kube event
2025-02-06 02:21:53.14: empty line received
2025-02-06 02:21:53.14: IngressMonitor - start process kube event
2025-02-06 02:21:54.09: ServiceMonitor - Received BOOKMARK: oldResVer=11959 newResVer=11959
2025-02-06 02:21:54.09: ServiceMonitor - start process kube event
2025-02-06 02:21:54.09: empty line received
2025-02-06 02:21:54.09: ServiceMonitor - start process kube event
2025-02-06 02:21:54.93: NetworkMonitor - Received BOOKMARK: oldResVer=11372 newResVer=11372
2025-02-06 02:21:54.93: NetworkMonitor - start process kube event
2025-02-06 02:21:54.93: empty line received
2025-02-06 02:21:54.93: NetworkMonitor - start process kube event
2025-02-06 02:21:55.12: PodMonitor - Received BOOKMARK: oldResVer=11968 newResVer=12076
2025-02-06 02:21:55.12: PodMonitor - start process kube event
2025-02-06 02:21:55.12: empty line received
2025-02-06 02:21:55.12: PodMonitor - start process kube event
2025-02-06 02:21:59.87: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:21:59.87: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:21:59.87: PodMonitor - start process kube event
2025-02-06 02:21:59.87: empty line received
2025-02-06 02:21:59.87: PodMonitor - start process kube event
2025-02-06 02:22:12.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:22:12.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:22:12.91: PodMonitor - start process kube event
2025-02-06 02:22:12.91: empty line received
2025-02-06 02:22:12.91: PodMonitor - start process kube event
2025-02-06 02:22:49.63: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11220 newResVer=12099
2025-02-06 02:22:49.63: NetworkPolicyMonitor - start process kube event
2025-02-06 02:22:49.63: empty line received
2025-02-06 02:22:49.63: NetworkPolicyMonitor - start process kube event
2025-02-06 02:22:49.66: EndPointMonitor - Received BOOKMARK: oldResVer=12032 newResVer=12032
2025-02-06 02:22:49.66: EndPointMonitor - start process kube event
2025-02-06 02:22:49.66: empty line received
2025-02-06 02:22:49.66: EndPointMonitor - start process kube event
2025-02-06 02:22:52.03: NamespaceMonitor - Received BOOKMARK: oldResVer=11692 newResVer=11692
2025-02-06 02:22:52.03: NamespaceMonitor - start process kube event
2025-02-06 02:22:52.03: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 02:22:52.03: empty line received
2025-02-06 02:22:52.03: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 02:22:52.03: VncKubernetes - vnc_sync - Namespace start
2025-02-06 02:22:52.03: VncKubernetes - vnc_sync - Namespace done
2025-02-06 02:22:52.03: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:22:52.03: NamespaceMonitor - start process kube event
2025-02-06 02:22:53.38: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=11960
2025-02-06 02:22:53.38: IngressMonitor - start process kube event
2025-02-06 02:22:53.38: empty line received
2025-02-06 02:22:53.38: IngressMonitor - start process kube event
2025-02-06 02:22:53.46: ServiceMonitor - Received BOOKMARK: oldResVer=11959 newResVer=11959
2025-02-06 02:22:53.46: ServiceMonitor - start process kube event
2025-02-06 02:22:53.46: empty line received
2025-02-06 02:22:53.46: ServiceMonitor - start process kube event
2025-02-06 02:22:54.40: NetworkMonitor - Received BOOKMARK: oldResVer=11372 newResVer=11372
2025-02-06 02:22:54.40: NetworkMonitor - start process kube event
2025-02-06 02:22:54.40: NetworkMonitor - _schedule_vnc_sync
2025-02-06 02:22:54.40: empty line received
2025-02-06 02:22:54.40: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 02:22:54.40: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 02:22:54.40: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:22:54.40: NetworkMonitor - start process kube event
2025-02-06 02:22:55.21: PodMonitor - Received BOOKMARK: oldResVer=12076 newResVer=12115
2025-02-06 02:22:55.21: PodMonitor - start process kube event
2025-02-06 02:22:55.21: empty line received
2025-02-06 02:22:55.21: PodMonitor - start process kube event
2025-02-06 02:23:49.62: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12099 newResVer=12099
2025-02-06 02:23:49.62: NetworkPolicyMonitor - start process kube event
2025-02-06 02:23:49.62: empty line received
2025-02-06 02:23:49.62: NetworkPolicyMonitor - start process kube event
2025-02-06 02:23:49.88: EndPointMonitor - Received BOOKMARK: oldResVer=12032 newResVer=12032
2025-02-06 02:23:49.88: EndPointMonitor - start process kube event
2025-02-06 02:23:49.88: empty line received
2025-02-06 02:23:49.88: EndPointMonitor - start process kube event
2025-02-06 02:23:51.57: NamespaceMonitor - Received BOOKMARK: oldResVer=11692 newResVer=11692
2025-02-06 02:23:51.57: NamespaceMonitor - start process kube event
2025-02-06 02:23:51.57: empty line received
2025-02-06 02:23:51.57: NamespaceMonitor - start process kube event
2025-02-06 02:23:53.64: ServiceMonitor - Received BOOKMARK: oldResVer=11959 newResVer=11959
2025-02-06 02:23:53.64: ServiceMonitor - start process kube event
2025-02-06 02:23:53.64: ServiceMonitor - _schedule_vnc_sync
2025-02-06 02:23:53.64: empty line received
2025-02-06 02:23:53.64: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 02:23:53.64: VncKubernetes - vnc_sync - Service start
2025-02-06 02:23:53.64: VncKubernetes - vnc_sync - Service done
2025-02-06 02:23:53.64: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:23:53.64: ServiceMonitor - start process kube event
2025-02-06 02:23:53.65: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=11960
2025-02-06 02:23:53.65: IngressMonitor - start process kube event
2025-02-06 02:23:53.65: empty line received
2025-02-06 02:23:53.65: IngressMonitor - start process kube event
2025-02-06 02:23:54.78: NetworkMonitor - Received BOOKMARK: oldResVer=11372 newResVer=11372
2025-02-06 02:23:54.78: NetworkMonitor - start process kube event
2025-02-06 02:23:54.78: empty line received
2025-02-06 02:23:54.78: NetworkMonitor - start process kube event
2025-02-06 02:23:55.40: PodMonitor - Received BOOKMARK: oldResVer=12115 newResVer=12115
2025-02-06 02:23:55.40: PodMonitor - start process kube event
2025-02-06 02:23:55.40: PodMonitor - _schedule_vnc_sync
2025-02-06 02:23:55.40: empty line received
2025-02-06 02:23:55.40: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 02:23:55.40: VncKubernetes - vnc_sync - Pod start
2025-02-06 02:23:55.40: VncKubernetes - vnc_sync - Pod done
2025-02-06 02:23:55.40: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:23:55.40: PodMonitor - start process kube event
2025-02-06 02:24:49.78: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12099 newResVer=12099
2025-02-06 02:24:49.78: NetworkPolicyMonitor - start process kube event
2025-02-06 02:24:49.78: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 02:24:49.78: empty line received
2025-02-06 02:24:49.78: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 02:24:49.78: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 02:24:49.78: NetworkPolicyMonitor - start process kube event
2025-02-06 02:24:49.78: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 02:24:49.78: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:24:49.97: EndPointMonitor - Received BOOKMARK: oldResVer=12032 newResVer=12032
2025-02-06 02:24:49.97: EndPointMonitor - start process kube event
2025-02-06 02:24:49.97: empty line received
2025-02-06 02:24:49.97: EndPointMonitor - start process kube event
2025-02-06 02:24:51.96: NamespaceMonitor - Received BOOKMARK: oldResVer=11692 newResVer=11692
2025-02-06 02:24:51.96: NamespaceMonitor - start process kube event
2025-02-06 02:24:51.96: empty line received
2025-02-06 02:24:51.96: NamespaceMonitor - start process kube event
2025-02-06 02:24:53.89: ServiceMonitor - Received BOOKMARK: oldResVer=11959 newResVer=11959
2025-02-06 02:24:53.89: ServiceMonitor - start process kube event
2025-02-06 02:24:53.89: empty line received
2025-02-06 02:24:53.89: ServiceMonitor - start process kube event
2025-02-06 02:24:54.22: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=11960
2025-02-06 02:24:54.22: IngressMonitor - start process kube event
2025-02-06 02:24:54.22: IngressMonitor - _schedule_vnc_sync
2025-02-06 02:24:54.22: empty line received
2025-02-06 02:24:54.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 02:24:54.22: VncKubernetes - vnc_sync - Ingress start
2025-02-06 02:24:54.22: VncKubernetes - vnc_sync - Ingress done
2025-02-06 02:24:54.22: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:24:54.22: IngressMonitor - start process kube event
2025-02-06 02:24:54.85: NetworkMonitor - Received BOOKMARK: oldResVer=11372 newResVer=12303
2025-02-06 02:24:54.85: NetworkMonitor - start process kube event
2025-02-06 02:24:54.85: empty line received
2025-02-06 02:24:54.85: NetworkMonitor - start process kube event
2025-02-06 02:24:56.35: PodMonitor - Received BOOKMARK: oldResVer=12115 newResVer=12115
2025-02-06 02:24:56.35: PodMonitor - start process kube event
2025-02-06 02:24:56.35: empty line received
2025-02-06 02:24:56.35: PodMonitor - start process kube event
2025-02-06 02:25:50.24: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12099 newResVer=12099
2025-02-06 02:25:50.24: NetworkPolicyMonitor - start process kube event
2025-02-06 02:25:50.24: empty line received
2025-02-06 02:25:50.24: NetworkPolicyMonitor - start process kube event
2025-02-06 02:25:50.39: EndPointMonitor - Received BOOKMARK: oldResVer=12032 newResVer=12032
2025-02-06 02:25:50.39: EndPointMonitor - start process kube event
2025-02-06 02:25:50.39: EndPointMonitor - _schedule_vnc_sync
2025-02-06 02:25:50.39: empty line received
2025-02-06 02:25:50.39: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 02:25:50.39: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 02:25:50.39: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:25:50.39: EndPointMonitor - start process kube event
2025-02-06 02:25:52.00: NamespaceMonitor - Received BOOKMARK: oldResVer=11692 newResVer=11692
2025-02-06 02:25:52.01: NamespaceMonitor - start process kube event
2025-02-06 02:25:52.01: empty line received
2025-02-06 02:25:52.01: NamespaceMonitor - start process kube event
2025-02-06 02:25:53.61: ServiceMonitor - Received BOOKMARK: oldResVer=11959 newResVer=11959
2025-02-06 02:25:53.61: ServiceMonitor - start process kube event
2025-02-06 02:25:53.61: empty line received
2025-02-06 02:25:53.61: ServiceMonitor - start process kube event
2025-02-06 02:25:54.22: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=11960
2025-02-06 02:25:54.22: IngressMonitor - start process kube event
2025-02-06 02:25:54.22: empty line received
2025-02-06 02:25:54.22: IngressMonitor - start process kube event
2025-02-06 02:25:54.68: NetworkMonitor - Received BOOKMARK: oldResVer=12303 newResVer=12303
2025-02-06 02:25:54.68: NetworkMonitor - start process kube event
2025-02-06 02:25:54.68: empty line received
2025-02-06 02:25:54.68: NetworkMonitor - start process kube event
2025-02-06 02:25:55.75: PodMonitor - Received BOOKMARK: oldResVer=12115 newResVer=12115
2025-02-06 02:25:55.75: PodMonitor - start process kube event
2025-02-06 02:25:55.75: empty line received
2025-02-06 02:25:55.75: PodMonitor - start process kube event
2025-02-06 02:26:35.84: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:26:35.84: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:26:35.84: PodMonitor - start process kube event
2025-02-06 02:26:35.84: empty line received
2025-02-06 02:26:35.84: PodMonitor - start process kube event
2025-02-06 02:26:48.25: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:26:48.25: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:26:48.25: PodMonitor - start process kube event
2025-02-06 02:26:48.25: empty line received
2025-02-06 02:26:48.25: PodMonitor - start process kube event
2025-02-06 02:26:49.29: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:26:49.29: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:26:49.29: PodMonitor - start process kube event
2025-02-06 02:26:49.29: empty line received
2025-02-06 02:26:49.29: PodMonitor - start process kube event
2025-02-06 02:26:49.98: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12099 newResVer=12099
2025-02-06 02:26:49.98: NetworkPolicyMonitor - start process kube event
2025-02-06 02:26:49.98: empty line received
2025-02-06 02:26:49.98: NetworkPolicyMonitor - start process kube event
2025-02-06 02:26:50.68: EndPointMonitor - Received BOOKMARK: oldResVer=12032 newResVer=12032
2025-02-06 02:26:50.68: EndPointMonitor - start process kube event
2025-02-06 02:26:50.68: empty line received
2025-02-06 02:26:50.68: EndPointMonitor - start process kube event
2025-02-06 02:26:52.37: NamespaceMonitor - Received BOOKMARK: oldResVer=11692 newResVer=11692
2025-02-06 02:26:52.37: NamespaceMonitor - start process kube event
2025-02-06 02:26:52.37: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 02:26:52.37: empty line received
2025-02-06 02:26:52.37: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 02:26:52.37: VncKubernetes - vnc_sync - Namespace start
2025-02-06 02:26:52.37: VncKubernetes - vnc_sync - Namespace done
2025-02-06 02:26:52.37: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:26:52.37: NamespaceMonitor - start process kube event
2025-02-06 02:26:53.82: ServiceMonitor - Received BOOKMARK: oldResVer=11959 newResVer=11959
2025-02-06 02:26:53.82: ServiceMonitor - start process kube event
2025-02-06 02:26:53.82: empty line received
2025-02-06 02:26:53.82: ServiceMonitor - start process kube event
2025-02-06 02:26:54.47: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=11960
2025-02-06 02:26:54.47: IngressMonitor - start process kube event
2025-02-06 02:26:54.47: empty line received
2025-02-06 02:26:54.47: IngressMonitor - start process kube event
2025-02-06 02:26:55.12: NetworkMonitor - Received BOOKMARK: oldResVer=12303 newResVer=12303
2025-02-06 02:26:55.12: NetworkMonitor - start process kube event
2025-02-06 02:26:55.12: NetworkMonitor - _schedule_vnc_sync
2025-02-06 02:26:55.12: empty line received
2025-02-06 02:26:55.12: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 02:26:55.12: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 02:26:55.12: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:26:55.12: NetworkMonitor - start process kube event
2025-02-06 02:26:56.51: PodMonitor - Received BOOKMARK: oldResVer=12115 newResVer=12505
2025-02-06 02:26:56.51: PodMonitor - start process kube event
2025-02-06 02:26:56.51: empty line received
2025-02-06 02:26:56.51: PodMonitor - start process kube event
2025-02-06 02:27:02.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:27:02.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:27:02.90: PodMonitor - start process kube event
2025-02-06 02:27:02.90: empty line received
2025-02-06 02:27:02.90: PodMonitor - start process kube event
2025-02-06 02:27:03.48: PodMonitor - Received BOOKMARK: oldResVer=12505 newResVer=12527
2025-02-06 02:27:03.48: PodMonitor - start process kube event
2025-02-06 02:27:03.48: empty line received
2025-02-06 02:27:03.48: PodMonitor - start process kube event
2025-02-06 02:27:03.72: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:27:03.72: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:27:03.72: PodMonitor - start process kube event
2025-02-06 02:27:03.72: empty line received
2025-02-06 02:27:03.72: PodMonitor - start process kube event
2025-02-06 02:27:04.66: PodMonitor - Received BOOKMARK: oldResVer=12527 newResVer=12528
2025-02-06 02:27:04.66: PodMonitor - start process kube event
2025-02-06 02:27:04.66: empty line received
2025-02-06 02:27:04.66: PodMonitor - start process kube event
2025-02-06 02:27:06.02: stop iteration PodMonitor
2025-02-06 02:27:06.02: PodMonitor - start process kube event
2025-02-06 02:27:06.02: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12528
2025-02-06 02:27:06.02: PodMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 02:27:06.02: PodMonitor - Connect Kube API result 0
2025-02-06 02:27:06.02: PodMonitor - _schedule_vnc_sync
2025-02-06 02:27:06.02: PodMonitor - Start Watching request https://10.0.0.40:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12528'})(timeout=120)
2025-02-06 02:27:06.02: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 02:27:06.02: VncKubernetes - vnc_sync - Pod start
2025-02-06 02:27:06.02: VncKubernetes - vnc_sync - Pod done
2025-02-06 02:27:06.02: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:27:06.03: PodMonitor - Watches https://10.0.0.40:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12528'})
2025-02-06 02:27:35.51: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:27:35.51: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:27:35.51: PodMonitor - start process kube event
2025-02-06 02:27:35.51: empty line received
2025-02-06 02:27:35.51: PodMonitor - start process kube event
2025-02-06 02:27:37.10: NamespaceMonitor - Received BOOKMARK: oldResVer=11692 newResVer=11692
2025-02-06 02:27:37.10: NamespaceMonitor - start process kube event
2025-02-06 02:27:37.10: empty line received
2025-02-06 02:27:37.10: NamespaceMonitor - start process kube event
2025-02-06 02:27:39.07: stop iteration NamespaceMonitor
2025-02-06 02:27:39.07: NamespaceMonitor - start process kube event
2025-02-06 02:27:39.07: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=11692
2025-02-06 02:27:39.07: NamespaceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 02:27:39.07: NamespaceMonitor - Connect Kube API result 0
2025-02-06 02:27:39.07: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 02:27:39.07: NamespaceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '11692'})(timeout=120)
2025-02-06 02:27:39.07: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 02:27:39.07: VncKubernetes - vnc_sync - Namespace start
2025-02-06 02:27:39.07: VncKubernetes - vnc_sync - Namespace done
2025-02-06 02:27:39.07: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:27:39.07: NamespaceMonitor - Watches https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '11692'})
2025-02-06 02:27:49.49: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12099 newResVer=12099
2025-02-06 02:27:49.49: NetworkPolicyMonitor - start process kube event
2025-02-06 02:27:49.49: empty line received
2025-02-06 02:27:49.49: NetworkPolicyMonitor - start process kube event
2025-02-06 02:27:49.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:27:49.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:27:49.90: PodMonitor - start process kube event
2025-02-06 02:27:49.90: empty line received
2025-02-06 02:27:49.90: PodMonitor - start process kube event
2025-02-06 02:27:50.43: EndPointMonitor - Received BOOKMARK: oldResVer=12032 newResVer=12032
2025-02-06 02:27:50.43: EndPointMonitor - start process kube event
2025-02-06 02:27:50.43: empty line received
2025-02-06 02:27:50.43: EndPointMonitor - start process kube event
2025-02-06 02:27:54.16: ServiceMonitor - Received BOOKMARK: oldResVer=11959 newResVer=11959
2025-02-06 02:27:54.16: ServiceMonitor - start process kube event
2025-02-06 02:27:54.16: ServiceMonitor - _schedule_vnc_sync
2025-02-06 02:27:54.16: empty line received
2025-02-06 02:27:54.16: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 02:27:54.16: VncKubernetes - vnc_sync - Service start
2025-02-06 02:27:54.16: VncKubernetes - vnc_sync - Service done
2025-02-06 02:27:54.16: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:27:54.16: ServiceMonitor - start process kube event
2025-02-06 02:27:54.30: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=11960
2025-02-06 02:27:54.30: IngressMonitor - start process kube event
2025-02-06 02:27:54.30: empty line received
2025-02-06 02:27:54.30: IngressMonitor - start process kube event
2025-02-06 02:27:54.69: NetworkMonitor - Received BOOKMARK: oldResVer=12303 newResVer=12303
2025-02-06 02:27:54.69: NetworkMonitor - start process kube event
2025-02-06 02:27:54.69: empty line received
2025-02-06 02:27:54.69: NetworkMonitor - start process kube event
2025-02-06 02:28:04.29: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:28:04.29: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:28:04.29: PodMonitor - start process kube event
2025-02-06 02:28:04.29: empty line received
2025-02-06 02:28:04.29: PodMonitor - start process kube event
2025-02-06 02:28:05.84: PodMonitor - Received BOOKMARK: oldResVer=12528 newResVer=12616
2025-02-06 02:28:05.84: PodMonitor - start process kube event
2025-02-06 02:28:05.84: empty line received
2025-02-06 02:28:05.84: PodMonitor - start process kube event
2025-02-06 02:28:16.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:28:16.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:28:16.91: PodMonitor - start process kube event
2025-02-06 02:28:16.91: empty line received
2025-02-06 02:28:16.91: PodMonitor - start process kube event
2025-02-06 02:28:39.28: NamespaceMonitor - Received BOOKMARK: oldResVer=11692 newResVer=12606
2025-02-06 02:28:39.28: NamespaceMonitor - start process kube event
2025-02-06 02:28:39.28: empty line received
2025-02-06 02:28:39.28: NamespaceMonitor - start process kube event
2025-02-06 02:28:49.96: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12099 newResVer=12099
2025-02-06 02:28:49.96: NetworkPolicyMonitor - start process kube event
2025-02-06 02:28:49.96: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 02:28:49.96: empty line received
2025-02-06 02:28:49.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 02:28:49.96: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 02:28:49.96: NetworkPolicyMonitor - start process kube event
2025-02-06 02:28:49.97: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 02:28:49.97: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:28:50.73: EndPointMonitor - Received BOOKMARK: oldResVer=12032 newResVer=12032
2025-02-06 02:28:50.73: EndPointMonitor - start process kube event
2025-02-06 02:28:50.73: empty line received
2025-02-06 02:28:50.73: EndPointMonitor - start process kube event
2025-02-06 02:28:53.68: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=11960
2025-02-06 02:28:53.68: IngressMonitor - start process kube event
2025-02-06 02:28:53.68: empty line received
2025-02-06 02:28:53.68: IngressMonitor - start process kube event
2025-02-06 02:28:54.16: ServiceMonitor - Received BOOKMARK: oldResVer=11959 newResVer=11959
2025-02-06 02:28:54.17: ServiceMonitor - start process kube event
2025-02-06 02:28:54.17: empty line received
2025-02-06 02:28:54.17: ServiceMonitor - start process kube event
2025-02-06 02:28:54.59: NetworkMonitor - Received BOOKMARK: oldResVer=12303 newResVer=12303
2025-02-06 02:28:54.59: NetworkMonitor - start process kube event
2025-02-06 02:28:54.59: empty line received
2025-02-06 02:28:54.59: NetworkMonitor - start process kube event
2025-02-06 02:29:06.50: PodMonitor - Received BOOKMARK: oldResVer=12616 newResVer=12633
2025-02-06 02:29:06.50: PodMonitor - start process kube event
2025-02-06 02:29:06.50: empty line received
2025-02-06 02:29:06.50: PodMonitor - start process kube event
2025-02-06 02:29:26.20: ServiceMonitor - Received BOOKMARK: oldResVer=11959 newResVer=11959
2025-02-06 02:29:26.20: ServiceMonitor - start process kube event
2025-02-06 02:29:26.20: empty line received
2025-02-06 02:29:26.20: ServiceMonitor - start process kube event
2025-02-06 02:29:27.31: ServiceMonitor - Received BOOKMARK: oldResVer=11959 newResVer=11959
2025-02-06 02:29:27.31: ServiceMonitor - start process kube event
2025-02-06 02:29:27.31: empty line received
2025-02-06 02:29:27.31: ServiceMonitor - start process kube event
2025-02-06 02:29:28.26: stop iteration ServiceMonitor
2025-02-06 02:29:28.26: ServiceMonitor - start process kube event
2025-02-06 02:29:28.26: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=11959
2025-02-06 02:29:28.26: ServiceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 02:29:28.26: ServiceMonitor - Connect Kube API result 0
2025-02-06 02:29:28.26: ServiceMonitor - _schedule_vnc_sync
2025-02-06 02:29:28.26: ServiceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '11959'})(timeout=120)
2025-02-06 02:29:28.26: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 02:29:28.26: VncKubernetes - vnc_sync - Service start
2025-02-06 02:29:28.26: VncKubernetes - vnc_sync - Service done
2025-02-06 02:29:28.26: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:29:28.27: ServiceMonitor - Watches https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '11959'})
2025-02-06 02:29:38.44: NamespaceMonitor - Received BOOKMARK: oldResVer=12606 newResVer=12606
2025-02-06 02:29:38.44: NamespaceMonitor - start process kube event
2025-02-06 02:29:38.44: empty line received
2025-02-06 02:29:38.44: NamespaceMonitor - start process kube event
2025-02-06 02:29:50.18: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12099 newResVer=12099
2025-02-06 02:29:50.18: NetworkPolicyMonitor - start process kube event
2025-02-06 02:29:50.18: empty line received
2025-02-06 02:29:50.18: NetworkPolicyMonitor - start process kube event
2025-02-06 02:29:51.12: EndPointMonitor - Received BOOKMARK: oldResVer=12032 newResVer=12032
2025-02-06 02:29:51.12: EndPointMonitor - start process kube event
2025-02-06 02:29:51.12: EndPointMonitor - _schedule_vnc_sync
2025-02-06 02:29:51.12: empty line received
2025-02-06 02:29:51.12: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 02:29:51.12: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 02:29:51.12: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:29:51.12: EndPointMonitor - start process kube event
2025-02-06 02:29:53.52: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=11960
2025-02-06 02:29:53.52: IngressMonitor - start process kube event
2025-02-06 02:29:53.52: IngressMonitor - _schedule_vnc_sync
2025-02-06 02:29:53.52: empty line received
2025-02-06 02:29:53.52: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 02:29:53.52: VncKubernetes - vnc_sync - Ingress start
2025-02-06 02:29:53.52: VncKubernetes - vnc_sync - Ingress done
2025-02-06 02:29:53.52: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:29:53.52: IngressMonitor - start process kube event
2025-02-06 02:29:55.18: NetworkMonitor - Received BOOKMARK: oldResVer=12303 newResVer=12303
2025-02-06 02:29:55.18: NetworkMonitor - start process kube event
2025-02-06 02:29:55.18: empty line received
2025-02-06 02:29:55.18: NetworkMonitor - start process kube event
2025-02-06 02:30:06.67: PodMonitor - Received BOOKMARK: oldResVer=12633 newResVer=12633
2025-02-06 02:30:06.67: PodMonitor - start process kube event
2025-02-06 02:30:06.67: empty line received
2025-02-06 02:30:06.67: PodMonitor - start process kube event
2025-02-06 02:30:24.71: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=11960
2025-02-06 02:30:24.71: IngressMonitor - start process kube event
2025-02-06 02:30:24.71: empty line received
2025-02-06 02:30:24.71: IngressMonitor - start process kube event
2025-02-06 02:30:25.91: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=11960
2025-02-06 02:30:25.91: IngressMonitor - start process kube event
2025-02-06 02:30:25.91: empty line received
2025-02-06 02:30:25.91: IngressMonitor - start process kube event
2025-02-06 02:30:27.44: stop iteration IngressMonitor
2025-02-06 02:30:27.44: IngressMonitor - start process kube event
2025-02-06 02:30:27.44: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=11960
2025-02-06 02:30:27.44: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 02:30:27.44: IngressMonitor - Connect Kube API result 0
2025-02-06 02:30:27.44: IngressMonitor - _schedule_vnc_sync
2025-02-06 02:30:27.44: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '11960'})(timeout=120)
2025-02-06 02:30:27.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 02:30:27.44: VncKubernetes - vnc_sync - Ingress start
2025-02-06 02:30:27.44: VncKubernetes - vnc_sync - Ingress done
2025-02-06 02:30:27.44: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:30:27.44: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '11960'})
2025-02-06 02:30:38.47: NamespaceMonitor - Received BOOKMARK: oldResVer=12606 newResVer=12606
2025-02-06 02:30:38.47: NamespaceMonitor - start process kube event
2025-02-06 02:30:38.47: empty line received
2025-02-06 02:30:38.47: NamespaceMonitor - start process kube event
2025-02-06 02:30:49.74: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12099 newResVer=12099
2025-02-06 02:30:49.74: NetworkPolicyMonitor - start process kube event
2025-02-06 02:30:49.74: empty line received
2025-02-06 02:30:49.74: NetworkPolicyMonitor - start process kube event
2025-02-06 02:30:51.37: EndPointMonitor - Received BOOKMARK: oldResVer=12032 newResVer=12032
2025-02-06 02:30:51.37: EndPointMonitor - start process kube event
2025-02-06 02:30:51.37: empty line received
2025-02-06 02:30:51.37: EndPointMonitor - start process kube event
2025-02-06 02:30:55.07: NetworkMonitor - Received BOOKMARK: oldResVer=12303 newResVer=12303
2025-02-06 02:30:55.07: NetworkMonitor - start process kube event
2025-02-06 02:30:55.07: empty line received
2025-02-06 02:30:55.07: NetworkMonitor - start process kube event
2025-02-06 02:31:07.09: PodMonitor - Received BOOKMARK: oldResVer=12633 newResVer=12633
2025-02-06 02:31:07.09: PodMonitor - start process kube event
2025-02-06 02:31:07.09: PodMonitor - _schedule_vnc_sync
2025-02-06 02:31:07.09: empty line received
2025-02-06 02:31:07.09: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 02:31:07.09: VncKubernetes - vnc_sync - Pod start
2025-02-06 02:31:07.09: VncKubernetes - vnc_sync - Pod done
2025-02-06 02:31:07.09: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:31:07.09: PodMonitor - start process kube event
2025-02-06 02:31:26.80: IngressMonitor - Received BOOKMARK: oldResVer=11960 newResVer=12829
2025-02-06 02:31:26.80: IngressMonitor - start process kube event
2025-02-06 02:31:26.80: empty line received
2025-02-06 02:31:26.80: IngressMonitor - start process kube event
2025-02-06 02:31:27.58: ServiceMonitor - Received BOOKMARK: oldResVer=11959 newResVer=12898
2025-02-06 02:31:27.58: ServiceMonitor - start process kube event
2025-02-06 02:31:27.58: empty line received
2025-02-06 02:31:27.58: ServiceMonitor - start process kube event
2025-02-06 02:31:38.39: NamespaceMonitor - Received BOOKMARK: oldResVer=12606 newResVer=12606
2025-02-06 02:31:38.39: NamespaceMonitor - start process kube event
2025-02-06 02:31:38.39: empty line received
2025-02-06 02:31:38.39: NamespaceMonitor - start process kube event
2025-02-06 02:31:50.34: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12099 newResVer=12099
2025-02-06 02:31:50.34: NetworkPolicyMonitor - start process kube event
2025-02-06 02:31:50.34: empty line received
2025-02-06 02:31:50.34: NetworkPolicyMonitor - start process kube event
2025-02-06 02:31:52.16: EndPointMonitor - Received BOOKMARK: oldResVer=12032 newResVer=12904
2025-02-06 02:31:52.16: EndPointMonitor - start process kube event
2025-02-06 02:31:52.16: empty line received
2025-02-06 02:31:52.16: EndPointMonitor - start process kube event
2025-02-06 02:31:53.16: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:31:53.16: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:31:53.16: PodMonitor - start process kube event
2025-02-06 02:31:53.16: empty line received
2025-02-06 02:31:53.16: PodMonitor - start process kube event
2025-02-06 02:31:54.77: NetworkMonitor - Received BOOKMARK: oldResVer=12303 newResVer=12303
2025-02-06 02:31:54.77: NetworkMonitor - start process kube event
2025-02-06 02:31:54.77: NetworkMonitor - _schedule_vnc_sync
2025-02-06 02:31:54.77: empty line received
2025-02-06 02:31:54.77: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 02:31:54.77: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 02:31:54.77: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:31:54.77: NetworkMonitor - start process kube event
2025-02-06 02:32:03.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:32:03.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:32:03.90: PodMonitor - start process kube event
2025-02-06 02:32:03.90: empty line received
2025-02-06 02:32:03.90: PodMonitor - start process kube event
2025-02-06 02:32:06.86: PodMonitor - Received BOOKMARK: oldResVer=12633 newResVer=12955
2025-02-06 02:32:06.86: PodMonitor - start process kube event
2025-02-06 02:32:06.86: empty line received
2025-02-06 02:32:06.86: PodMonitor - start process kube event
2025-02-06 02:32:27.28: IngressMonitor - Received BOOKMARK: oldResVer=12829 newResVer=12829
2025-02-06 02:32:27.28: IngressMonitor - start process kube event
2025-02-06 02:32:27.28: empty line received
2025-02-06 02:32:27.28: IngressMonitor - start process kube event
2025-02-06 02:32:27.82: ServiceMonitor - Received BOOKMARK: oldResVer=12898 newResVer=12898
2025-02-06 02:32:27.82: ServiceMonitor - start process kube event
2025-02-06 02:32:27.82: empty line received
2025-02-06 02:32:27.82: ServiceMonitor - start process kube event
2025-02-06 02:32:38.89: NamespaceMonitor - Received BOOKMARK: oldResVer=12606 newResVer=12606
2025-02-06 02:32:38.89: NamespaceMonitor - start process kube event
2025-02-06 02:32:38.89: NamespaceMonitor - _schedule_vnc_sync
2025-02-06 02:32:38.89: empty line received
2025-02-06 02:32:38.89: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-06 02:32:38.89: VncKubernetes - vnc_sync - Namespace start
2025-02-06 02:32:38.89: VncKubernetes - vnc_sync - Namespace done
2025-02-06 02:32:38.89: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:32:38.89: NamespaceMonitor - start process kube event
2025-02-06 02:32:42.49: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:32:42.49: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:32:42.49: PodMonitor - start process kube event
2025-02-06 02:32:42.49: empty line received
2025-02-06 02:32:42.49: PodMonitor - start process kube event
2025-02-06 02:32:50.33: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12099 newResVer=12973
2025-02-06 02:32:50.33: NetworkPolicyMonitor - start process kube event
2025-02-06 02:32:50.33: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 02:32:50.33: empty line received
2025-02-06 02:32:50.33: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 02:32:50.33: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 02:32:50.34: NetworkPolicyMonitor - start process kube event
2025-02-06 02:32:50.34: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 02:32:50.34: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:32:51.78: EndPointMonitor - Received BOOKMARK: oldResVer=12904 newResVer=12904
2025-02-06 02:32:51.78: EndPointMonitor - start process kube event
2025-02-06 02:32:51.78: empty line received
2025-02-06 02:32:51.78: EndPointMonitor - start process kube event
2025-02-06 02:32:55.29: NetworkMonitor - Received BOOKMARK: oldResVer=12303 newResVer=12303
2025-02-06 02:32:55.29: NetworkMonitor - start process kube event
2025-02-06 02:32:55.29: empty line received
2025-02-06 02:32:55.29: NetworkMonitor - start process kube event
2025-02-06 02:33:06.94: PodMonitor - Received BOOKMARK: oldResVer=12955 newResVer=13010
2025-02-06 02:33:06.94: PodMonitor - start process kube event
2025-02-06 02:33:06.94: empty line received
2025-02-06 02:33:06.94: PodMonitor - start process kube event
2025-02-06 02:33:11.33: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:33:11.33: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:33:11.33: PodMonitor - start process kube event
2025-02-06 02:33:11.33: empty line received
2025-02-06 02:33:11.33: PodMonitor - start process kube event
2025-02-06 02:33:26.57: IngressMonitor - Received BOOKMARK: oldResVer=12829 newResVer=12829
2025-02-06 02:33:26.57: IngressMonitor - start process kube event
2025-02-06 02:33:26.57: empty line received
2025-02-06 02:33:26.57: IngressMonitor - start process kube event
2025-02-06 02:33:27.48: ServiceMonitor - Received BOOKMARK: oldResVer=12898 newResVer=12898
2025-02-06 02:33:27.48: ServiceMonitor - start process kube event
2025-02-06 02:33:27.48: empty line received
2025-02-06 02:33:27.48: ServiceMonitor - start process kube event
2025-02-06 02:33:38.55: NamespaceMonitor - Received BOOKMARK: oldResVer=12606 newResVer=12606
2025-02-06 02:33:38.55: NamespaceMonitor - start process kube event
2025-02-06 02:33:38.55: empty line received
2025-02-06 02:33:38.55: NamespaceMonitor - start process kube event
2025-02-06 02:33:43.24: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:33:43.24: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:33:43.24: PodMonitor - start process kube event
2025-02-06 02:33:43.24: empty line received
2025-02-06 02:33:43.24: PodMonitor - start process kube event
2025-02-06 02:33:49.73: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12973 newResVer=12973
2025-02-06 02:33:49.73: NetworkPolicyMonitor - start process kube event
2025-02-06 02:33:49.73: empty line received
2025-02-06 02:33:49.73: NetworkPolicyMonitor - start process kube event
2025-02-06 02:33:52.55: EndPointMonitor - Received BOOKMARK: oldResVer=12904 newResVer=12904
2025-02-06 02:33:52.55: EndPointMonitor - start process kube event
2025-02-06 02:33:52.55: EndPointMonitor - _schedule_vnc_sync
2025-02-06 02:33:52.55: empty line received
2025-02-06 02:33:52.55: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 02:33:52.55: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 02:33:52.55: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:33:52.55: EndPointMonitor - start process kube event
2025-02-06 02:33:55.61: NetworkMonitor - Received BOOKMARK: oldResVer=12303 newResVer=12303
2025-02-06 02:33:55.61: NetworkMonitor - start process kube event
2025-02-06 02:33:55.62: empty line received
2025-02-06 02:33:55.62: NetworkMonitor - start process kube event
2025-02-06 02:33:55.92: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:33:55.92: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:33:55.92: PodMonitor - start process kube event
2025-02-06 02:33:55.92: empty line received
2025-02-06 02:33:55.92: PodMonitor - start process kube event
2025-02-06 02:34:06.50: PodMonitor - Received BOOKMARK: oldResVer=13010 newResVer=13115
2025-02-06 02:34:06.50: PodMonitor - start process kube event
2025-02-06 02:34:06.50: empty line received
2025-02-06 02:34:06.50: PodMonitor - start process kube event
2025-02-06 02:34:11.95: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:34:11.95: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:34:11.95: PodMonitor - start process kube event
2025-02-06 02:34:11.95: empty line received
2025-02-06 02:34:11.95: PodMonitor - start process kube event
2025-02-06 02:34:23.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-sd2bf:3fababa0-4cc4-47c8-ba85-b5603c83d01a
2025-02-06 02:34:23.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-sd2bf (hostNetwork=True)
2025-02-06 02:34:23.90: PodMonitor - start process kube event
2025-02-06 02:34:23.90: empty line received
2025-02-06 02:34:23.90: PodMonitor - start process kube event
2025-02-06 02:34:27.35: IngressMonitor - Received BOOKMARK: oldResVer=12829 newResVer=12829
2025-02-06 02:34:27.35: IngressMonitor - start process kube event
2025-02-06 02:34:27.35: empty line received
2025-02-06 02:34:27.35: IngressMonitor - start process kube event
2025-02-06 02:34:27.57: ServiceMonitor - Received BOOKMARK: oldResVer=12898 newResVer=12898
2025-02-06 02:34:27.57: ServiceMonitor - start process kube event
2025-02-06 02:34:27.57: ServiceMonitor - _schedule_vnc_sync
2025-02-06 02:34:27.57: empty line received
2025-02-06 02:34:27.57: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-06 02:34:27.57: VncKubernetes - vnc_sync - Service start
2025-02-06 02:34:27.57: VncKubernetes - vnc_sync - Service done
2025-02-06 02:34:27.57: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:34:27.57: ServiceMonitor - start process kube event
2025-02-06 02:34:39.21: NamespaceMonitor - Received BOOKMARK: oldResVer=12606 newResVer=12606
2025-02-06 02:34:39.21: NamespaceMonitor - start process kube event
2025-02-06 02:34:39.21: empty line received
2025-02-06 02:34:39.21: NamespaceMonitor - start process kube event
2025-02-06 02:34:49.56: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12973 newResVer=12973
2025-02-06 02:34:49.56: NetworkPolicyMonitor - start process kube event
2025-02-06 02:34:49.56: empty line received
2025-02-06 02:34:49.56: NetworkPolicyMonitor - start process kube event
2025-02-06 02:34:53.58: EndPointMonitor - Received BOOKMARK: oldResVer=12904 newResVer=12904
2025-02-06 02:34:53.58: EndPointMonitor - start process kube event
2025-02-06 02:34:53.58: empty line received
2025-02-06 02:34:53.58: EndPointMonitor - start process kube event
2025-02-06 02:34:55.40: NetworkMonitor - Received BOOKMARK: oldResVer=12303 newResVer=12303
2025-02-06 02:34:55.40: NetworkMonitor - start process kube event
2025-02-06 02:34:55.40: empty line received
2025-02-06 02:34:55.40: NetworkMonitor - start process kube event
2025-02-06 02:35:07.21: PodMonitor - Received BOOKMARK: oldResVer=13115 newResVer=13157
2025-02-06 02:35:07.21: PodMonitor - start process kube event
2025-02-06 02:35:07.21: PodMonitor - _schedule_vnc_sync
2025-02-06 02:35:07.21: empty line received
2025-02-06 02:35:07.21: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-06 02:35:07.21: VncKubernetes - vnc_sync - Pod start
2025-02-06 02:35:07.21: VncKubernetes - vnc_sync - Pod done
2025-02-06 02:35:07.21: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:35:07.21: PodMonitor - start process kube event
2025-02-06 02:35:27.00: IngressMonitor - Received BOOKMARK: oldResVer=12829 newResVer=12829
2025-02-06 02:35:27.00: IngressMonitor - start process kube event
2025-02-06 02:35:27.00: IngressMonitor - _schedule_vnc_sync
2025-02-06 02:35:27.00: empty line received
2025-02-06 02:35:27.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-06 02:35:27.00: VncKubernetes - vnc_sync - Ingress start
2025-02-06 02:35:27.00: VncKubernetes - vnc_sync - Ingress done
2025-02-06 02:35:27.00: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:35:27.00: IngressMonitor - start process kube event
2025-02-06 02:35:27.76: ServiceMonitor - Received BOOKMARK: oldResVer=12898 newResVer=12898
2025-02-06 02:35:27.76: ServiceMonitor - start process kube event
2025-02-06 02:35:27.76: empty line received
2025-02-06 02:35:27.76: ServiceMonitor - start process kube event
2025-02-06 02:35:38.51: NamespaceMonitor - Received BOOKMARK: oldResVer=12606 newResVer=12606
2025-02-06 02:35:38.51: NamespaceMonitor - start process kube event
2025-02-06 02:35:38.51: empty line received
2025-02-06 02:35:38.51: NamespaceMonitor - start process kube event
2025-02-06 02:35:50.38: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12973 newResVer=12973
2025-02-06 02:35:50.38: NetworkPolicyMonitor - start process kube event
2025-02-06 02:35:50.38: empty line received
2025-02-06 02:35:50.38: NetworkPolicyMonitor - start process kube event
2025-02-06 02:35:53.98: EndPointMonitor - Received BOOKMARK: oldResVer=12904 newResVer=12904
2025-02-06 02:35:53.98: EndPointMonitor - start process kube event
2025-02-06 02:35:53.98: empty line received
2025-02-06 02:35:53.98: EndPointMonitor - start process kube event
2025-02-06 02:35:55.21: NetworkMonitor - Received BOOKMARK: oldResVer=12303 newResVer=13236
2025-02-06 02:35:55.21: NetworkMonitor - start process kube event
2025-02-06 02:35:55.21: NetworkMonitor - _schedule_vnc_sync
2025-02-06 02:35:55.21: empty line received
2025-02-06 02:35:55.21: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-06 02:35:55.21: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-06 02:35:55.21: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:35:55.21: NetworkMonitor - start process kube event
2025-02-06 02:36:05.41: EndPointMonitor - Received BOOKMARK: oldResVer=12904 newResVer=12904
2025-02-06 02:36:05.41: EndPointMonitor - start process kube event
2025-02-06 02:36:05.41: empty line received
2025-02-06 02:36:05.41: EndPointMonitor - start process kube event
2025-02-06 02:36:06.79: PodMonitor - Received BOOKMARK: oldResVer=13157 newResVer=13157
2025-02-06 02:36:06.79: PodMonitor - start process kube event
2025-02-06 02:36:06.79: empty line received
2025-02-06 02:36:06.79: PodMonitor - start process kube event
2025-02-06 02:36:06.87: stop iteration EndPointMonitor
2025-02-06 02:36:06.87: EndPointMonitor - start process kube event
2025-02-06 02:36:06.87: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12904
2025-02-06 02:36:06.87: EndPointMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 02:36:06.87: EndPointMonitor - Connect Kube API result 0
2025-02-06 02:36:06.87: EndPointMonitor - _schedule_vnc_sync
2025-02-06 02:36:06.87: EndPointMonitor - Start Watching request https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12904'})(timeout=120)
2025-02-06 02:36:06.87: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-06 02:36:06.87: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-06 02:36:06.87: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:36:06.87: EndPointMonitor - Watches https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12904'})
2025-02-06 02:36:10.88: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12973 newResVer=12973
2025-02-06 02:36:10.88: NetworkPolicyMonitor - start process kube event
2025-02-06 02:36:10.88: empty line received
2025-02-06 02:36:10.88: NetworkPolicyMonitor - start process kube event
2025-02-06 02:36:12.59: stop iteration NetworkPolicyMonitor
2025-02-06 02:36:12.59: NetworkPolicyMonitor - start process kube event
2025-02-06 02:36:12.59: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12973
2025-02-06 02:36:12.59: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-06 02:36:12.59: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-06 02:36:12.59: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-06 02:36:12.59: NetworkPolicyMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12973'})(timeout=120)
2025-02-06 02:36:12.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-06 02:36:12.59: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-06 02:36:12.59: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-06 02:36:12.59: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-06 02:36:12.59: NetworkPolicyMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12973'})
2025-02-06 02:36:26.53: IngressMonitor - Received BOOKMARK: oldResVer=12829 newResVer=12829
2025-02-06 02:36:26.53: IngressMonitor - start process kube event
2025-02-06 02:36:26.53: empty line received
2025-02-06 02:36:26.53: IngressMonitor - start process kube event
2025-02-06 02:36:28.36: ServiceMonitor - Received BOOKMARK: oldResVer=12898 newResVer=12898
2025-02-06 02:36:28.36: ServiceMonitor - start process kube event
2025-02-06 02:36:28.36: empty line received
2025-02-06 02:36:28.36: ServiceMonitor - start process kube event
2025-02-06 02:36:38.56: NamespaceMonitor - Received BOOKMARK: oldResVer=12606 newResVer=12606
2025-02-06 02:36:38.56: NamespaceMonitor - start process kube event
2025-02-06 02:36:38.56: empty line received
2025-02-06 02:36:38.56: NamespaceMonitor - start process kube event
2025-02-06 02:36:55.39: NetworkMonitor - Received BOOKMARK: oldResVer=13236 newResVer=13236
2025-02-06 02:36:55.39: NetworkMonitor - start process kube event
2025-02-06 02:36:55.39: empty line received