INFO: =================== Mon Feb  3 01:53:18 UTC 2025 ===================
INFO: Waiting for cassandra 2/30
INFO: Waiting for cassandra 3/30
INFO: Waiting for cassandra 4/30
INFO: Waiting for cassandra 5/30
INFO: Waiting for cassandra 6/30
INFO: Waiting for cassandra 7/30
INFO: Waiting for cassandra 8/30
INFO: Waiting for cassandra 9/30
INFO: 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/03/2025 01:54:48.289 7f325ff49048 [contrail-kube-manager] [INFO]: SANDESH: CONNECT TO COLLECTOR: True
02/03/2025 01:54:48.625 7f325ff49048 [contrail-kube-manager] [INFO]: SANDESH: Logging: LEVEL: [SYS_INFO] -> [SYS_NOTICE]
2025-02-03 01:54:49.53: KubeMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:54:49.54: KubeMonitor - Connect Kube API result 0
2025-02-03 01:54:49.65: KubeMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/api/v1
2025-02-03 01:54:49.67: NamespaceMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/api/v1
2025-02-03 01:54:49.68: NetworkMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1
2025-02-03 01:54:49.69: PodMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/api/v1
2025-02-03 01:54:49.69: ServiceMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/api/v1
2025-02-03 01:54:49.71: NetworkPolicyMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/apis/networking.k8s.io/v1
2025-02-03 01:54:49.71: EndPointMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/api/v1
2025-02-03 01:54:49.72: IngressMonitor - KubeMonitor init done: url=https://10.0.0.40:6443/apis/networking.k8s.io/v1
2025-02-03 01:54:49.72: VncKubernetes - vnc_connect starting
2025-02-03 01:54:49.75: VncKubernetes - vnc_connect failed: 
2025-02-03 01:54:52.77: VncKubernetes - vnc_connect failed: 
2025-02-03 01:54:55.79: VncKubernetes - vnc_connect failed: 
2025-02-03 01:54:58.80: VncKubernetes - vnc_connect failed: 
2025-02-03 01:55:01.84: VncKubernetes - vnc_connect done
2025-02-03 01:55:02.41: default-domain domain available.
2025-02-03 01:55:14.30: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 01:55:14.30: NamespaceMonitor - start process kube event
2025-02-03 01:55:14.30: NamespaceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-03 01:55:14.31: NamespaceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:55:14.31: NetworkMonitor - start process kube event
2025-02-03 01:55:14.31: NetworkMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-03 01:55:14.31: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:55:14.31: PodMonitor - start process kube event
2025-02-03 01:55:14.31: PodMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-03 01:55:14.31: PodMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:55:14.31: ServiceMonitor - start process kube event
2025-02-03 01:55:14.31: ServiceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-03 01:55:14.31: ServiceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:55:14.31: NetworkPolicyMonitor - start process kube event
2025-02-03 01:55:14.31: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-03 01:55:14.31: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:55:14.31: EndPointMonitor - start process kube event
2025-02-03 01:55:14.31: EndPointMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-03 01:55:14.31: EndPointMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:55:14.31: IngressMonitor - start process kube event
2025-02-03 01:55:14.31: IngressMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-03 01:55:14.31: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:55:14.31: IngressMonitor - Connect Kube API result 0
2025-02-03 01:55:14.31: IngressMonitor - Start init url=https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses resource_version=None
2025-02-03 01:55:14.31: EndPointMonitor - Connect Kube API result 0
2025-02-03 01:55:14.31: EndPointMonitor - Start init url=https://10.0.0.40:6443/api/v1/endpoints resource_version=None
2025-02-03 01:55:14.31: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-03 01:55:14.31: NetworkPolicyMonitor - Start init url=https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies resource_version=None
2025-02-03 01:55:14.31: ServiceMonitor - Connect Kube API result 0
2025-02-03 01:55:14.31: ServiceMonitor - Start init url=https://10.0.0.40:6443/api/v1/services resource_version=None
2025-02-03 01:55:14.31: PodMonitor - Connect Kube API result 0
2025-02-03 01:55:14.31: PodMonitor - Start init url=https://10.0.0.40:6443/api/v1/pods resource_version=None
2025-02-03 01:55:14.31: NetworkMonitor - Connect Kube API result 0
2025-02-03 01:55:14.32: NamespaceMonitor - Connect Kube API result 0
2025-02-03 01:55:14.32: NamespaceMonitor - Start init url=https://10.0.0.40:6443/api/v1/namespaces resource_version=None
2025-02-03 01:55:14.34: NetworkPolicyMonitor - Done init url=https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies, resource_version=9681
2025-02-03 01:55:14.34: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 01:55:14.34: NetworkPolicyMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:55:14.34: IngressMonitor - Done init url=https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses, resource_version=9681
2025-02-03 01:55:14.34: IngressMonitor - _schedule_vnc_sync
2025-02-03 01:55:14.34: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:55:14.35: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 01:55:14.35: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 01:55:14.36: NamespaceMonitor - Got ADDED Namespace None:default:7c18033a-1dfc-4987-83e7-1b54ab4e5cdc
2025-02-03 01:55:14.36: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:55:14.36: NetworkPolicyMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:55:14.36: ServiceMonitor - Got ADDED Service default:kubernetes:a92ac1db-5dd7-4725-8ab8-7ad1e73058d0
2025-02-03 01:55:14.37: EndPointMonitor - Got ADDED Endpoints default:kubernetes:ddd4e31f-dca6-46e2-b4e7-80aadc3ca918
2025-02-03 01:55:14.37: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 01:55:14.37: VncKubernetes - wait event (qsize=4 timeout=120)
2025-02-03 01:55:14.37: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 01:55:14.37: VncKubernetes - vnc_sync - Ingress start
2025-02-03 01:55:14.37: VncKubernetes - vnc_sync - Ingress done
2025-02-03 01:55:14.37: VncKubernetes - wait event (qsize=3 timeout=120)
2025-02-03 01:55:14.37: VncKubernetes - Process event (name=default event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace default:7c18033a-1dfc-4987-83e7-1b54ab4e5cdc
2025-02-03 01:55:14.38: NamespaceMonitor - Got ADDED Namespace None:kube-node-lease:120404f5-3308-4528-b268-2aab7b8e6487
2025-02-03 01:55:14.39: PodMonitor - Skipped ADDED Pod kube-system:config-zookeeper-fh7mc (hostNetwork=True)
2025-02-03 01:55:14.39: NetworkMonitor - Start init url=https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions resource_version=None
2025-02-03 01:55:14.39: EndPointMonitor - Got ADDED Endpoints kube-system:coredns:9ffa7868-162f-4323-81e2-4877153fa5ce
2025-02-03 01:55:14.39: EndPointMonitor - Done init url=https://10.0.0.40:6443/api/v1/endpoints, resource_version=9681
2025-02-03 01:55:14.39: EndPointMonitor - _schedule_vnc_sync
2025-02-03 01:55:14.39: EndPointMonitor - Start Watching request https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:55:14.39: ServiceMonitor - Got ADDED Service kube-system:coredns:6237c5d1-20f2-4beb-bd5a-cb46d872f2d0
2025-02-03 01:55:14.39: ServiceMonitor - Done init url=https://10.0.0.40:6443/api/v1/services, resource_version=9681
2025-02-03 01:55:14.39: ServiceMonitor - _schedule_vnc_sync
2025-02-03 01:55:14.39: ServiceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:55:14.40: PodMonitor - Skipped ADDED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:55:14.40: NamespaceMonitor - Got ADDED Namespace None:kube-public:5df42806-c9f9-4310-a457-80c286aade69
2025-02-03 01:55:14.40: ServiceMonitor - Watches https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:55:14.40: EndPointMonitor - Watches https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:55:14.40: NetworkMonitor - Done init url=https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions, resource_version=9685
2025-02-03 01:55:14.40: NetworkMonitor - _schedule_vnc_sync
2025-02-03 01:55:14.40: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})(timeout=120)
2025-02-03 01:55:14.41: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-2ts5z (hostNetwork=True)
2025-02-03 01:55:14.41: NamespaceMonitor - Got ADDED Namespace None:kube-system:e82461c2-2b2e-4717-b4cc-a979d9b2c278
2025-02-03 01:55:14.41: NamespaceMonitor - Done init url=https://10.0.0.40:6443/api/v1/namespaces, resource_version=9681
2025-02-03 01:55:14.41: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 01:55:14.41: NamespaceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:55:14.41: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})
2025-02-03 01:55:14.41: NamespaceMonitor - Watches https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:55:14.41: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-alarm-vx624 (hostNetwork=True)
2025-02-03 01:55:14.42: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-snmp-sb84v (hostNetwork=True)
2025-02-03 01:55:14.42: PodMonitor - Skipped ADDED Pod kube-system:contrail-analyticsdb-c6mls (hostNetwork=True)
2025-02-03 01:55:14.42: PodMonitor - Skipped ADDED Pod kube-system:contrail-configdb-hftpf (hostNetwork=True)
2025-02-03 01:55:14.43: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-config-n5jq2 (hostNetwork=True)
2025-02-03 01:55:14.43: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-control-zwz8r (hostNetwork=True)
2025-02-03 01:55:14.44: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-webui-xt8bs (hostNetwork=True)
2025-02-03 01:55:14.44: PodMonitor - Skipped ADDED Pod kube-system:contrail-kube-manager-grtsp (hostNetwork=True)
2025-02-03 01:55:14.45: PodMonitor - Got ADDED Pod kube-system:coredns-77f7cc69db-hvxzx:e1dc7526-a318-44e6-b117-8c3a8c882069
2025-02-03 01:55:14.46: PodMonitor - Got ADDED Pod kube-system:dns-autoscaler-595558c478-nm48t:81d88ed6-1114-46a4-bdb4-12c0c887d066
2025-02-03 01:55:14.47: PodMonitor - Skipped ADDED Pod kube-system:kube-apiserver-cn-jenkins-deploy-platform-k8s-manifests-132-1 (hostNetwork=True)
2025-02-03 01:55:14.47: PodMonitor - Skipped ADDED Pod kube-system:kube-controller-manager-cn-jenkins-deploy-platform-k8s-manifests-132-1 (hostNetwork=True)
2025-02-03 01:55:14.48: PodMonitor - Skipped ADDED Pod kube-system:kube-proxy-ckdds (hostNetwork=True)
2025-02-03 01:55:14.49: PodMonitor - Skipped ADDED Pod kube-system:kube-scheduler-cn-jenkins-deploy-platform-k8s-manifests-132-1 (hostNetwork=True)
2025-02-03 01:55:14.49: PodMonitor - Skipped ADDED Pod kube-system:rabbitmq-5trlb (hostNetwork=True)
2025-02-03 01:55:14.50: PodMonitor - Skipped ADDED Pod kube-system:redis-6rfjm (hostNetwork=True)
2025-02-03 01:55:14.50: PodMonitor - Done init url=https://10.0.0.40:6443/api/v1/pods, resource_version=9681
2025-02-03 01:55:14.50: PodMonitor - _schedule_vnc_sync
2025-02-03 01:55:14.50: PodMonitor - Start Watching request https://10.0.0.40:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:55:14.51: PodMonitor - Watches https://10.0.0.40:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:55:15.95: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:55:15.95: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:55:15.95: PodMonitor - start process kube event
2025-02-03 01:55:15.95: empty line received
2025-02-03 01:55:15.95: PodMonitor - start process kube event
2025-02-03 01:55:16.94: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:55:16.94: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:55:16.94: PodMonitor - start process kube event
2025-02-03 01:55:16.94: empty line received
2025-02-03 01:55:16.94: PodMonitor - start process kube event
2025-02-03 01:55:18.93: VncKubernetes - wait event (qsize=14 timeout=120)
2025-02-03 01:55:18.93: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Service ns=default)
VncService - Got ADDED Service default:kubernetes:a92ac1db-5dd7-4725-8ab8-7ad1e73058d0
2025-02-03 01:55:19.07: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:55:19.07: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:55:19.07: PodMonitor - start process kube event
2025-02-03 01:55:19.07: empty line received
2025-02-03 01:55:19.07: PodMonitor - start process kube event
2025-02-03 01:55:20.14: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:55:20.14: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:55:20.14: PodMonitor - start process kube event
2025-02-03 01:55:20.14: empty line received
2025-02-03 01:55:20.14: PodMonitor - start process kube event
2025-02-03 01:55:21.28: VncKubernetes - wait event (qsize=13 timeout=120)
2025-02-03 01:55:21.28: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Endpoints ns=default)
VncEndpoints - Got ADDED Endpoints default:kubernetes:ddd4e31f-dca6-46e2-b4e7-80aadc3ca918
2025-02-03 01:55:21.40: VncKubernetes - wait event (qsize=12 timeout=120)
2025-02-03 01:55:21.40: VncKubernetes - Process event (name=kube-node-lease event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-node-lease:120404f5-3308-4528-b268-2aab7b8e6487
2025-02-03 01:55:24.36: VncKubernetes - wait event (qsize=11 timeout=120)
2025-02-03 01:55:24.36: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Endpoints ns=kube-system)
VncEndpoints - Got ADDED Endpoints kube-system:coredns:9ffa7868-162f-4323-81e2-4877153fa5ce
2025-02-03 01:55:24.42: VncKubernetes - wait event (qsize=10 timeout=120)
2025-02-03 01:55:24.42: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 01:55:24.42: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 01:55:24.42: VncKubernetes - wait event (qsize=9 timeout=120)
2025-02-03 01:55:24.42: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Service ns=kube-system)
VncService - Got ADDED Service kube-system:coredns:6237c5d1-20f2-4beb-bd5a-cb46d872f2d0
2025-02-03 01:55:27.21: VncKubernetes - wait event (qsize=8 timeout=120)
2025-02-03 01:55:27.21: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 01:55:27.21: VncKubernetes - vnc_sync - Service start
2025-02-03 01:55:27.21: VncKubernetes - vnc_sync - Service done
2025-02-03 01:55:27.21: VncKubernetes - wait event (qsize=7 timeout=120)
2025-02-03 01:55:27.21: VncKubernetes - Process event (name=kube-public event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-public:5df42806-c9f9-4310-a457-80c286aade69
2025-02-03 01:55:29.88: VncKubernetes - wait event (qsize=6 timeout=120)
2025-02-03 01:55:29.88: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 01:55:29.88: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 01:55:29.88: VncKubernetes - wait event (qsize=5 timeout=120)
2025-02-03 01:55:29.88: VncKubernetes - Process event (name=kube-system event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-system:e82461c2-2b2e-4717-b4cc-a979d9b2c278
2025-02-03 01:55:32.28: VncKubernetes - wait event (qsize=4 timeout=120)
2025-02-03 01:55:32.28: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 01:55:32.28: VncKubernetes - vnc_sync - Namespace start
2025-02-03 01:55:32.28: VncKubernetes - vnc_sync - Namespace done
2025-02-03 01:55:32.28: VncKubernetes - wait event (qsize=3 timeout=120)
2025-02-03 01:55:32.28: VncKubernetes - Process event (name=coredns-77f7cc69db-hvxzx event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:coredns-77f7cc69db-hvxzx:e1dc7526-a318-44e6-b117-8c3a8c882069
2025-02-03 01:55:34.08: VncKubernetes - wait event (qsize=2 timeout=120)
2025-02-03 01:55:34.08: VncKubernetes - Process event (name=dns-autoscaler-595558c478-nm48t event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:dns-autoscaler-595558c478-nm48t:81d88ed6-1114-46a4-bdb4-12c0c887d066
2025-02-03 01:55:34.09: PodMonitor - Received MODIFIED Pod kube-system:coredns-77f7cc69db-hvxzx:e1dc7526-a318-44e6-b117-8c3a8c882069
2025-02-03 01:55:34.09: PodMonitor - Got MODIFIED Pod kube-system:coredns-77f7cc69db-hvxzx:e1dc7526-a318-44e6-b117-8c3a8c882069
2025-02-03 01:55:34.09: PodMonitor - start process kube event
2025-02-03 01:55:34.09: empty line received
2025-02-03 01:55:34.09: PodMonitor - start process kube event
2025-02-03 01:55:35.34: PodMonitor - Received MODIFIED Pod kube-system:dns-autoscaler-595558c478-nm48t:81d88ed6-1114-46a4-bdb4-12c0c887d066
2025-02-03 01:55:35.34: PodMonitor - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-nm48t:81d88ed6-1114-46a4-bdb4-12c0c887d066
2025-02-03 01:55:35.34: PodMonitor - start process kube event
2025-02-03 01:55:35.34: empty line received
2025-02-03 01:55:35.34: PodMonitor - start process kube event
2025-02-03 01:55:35.34: VncKubernetes - wait event (qsize=3 timeout=120)
2025-02-03 01:55:35.34: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 01:55:35.34: VncKubernetes - vnc_sync - Pod start
2025-02-03 01:55:35.34: VncKubernetes - vnc_sync - Pod done
2025-02-03 01:55:35.34: VncKubernetes - wait event (qsize=2 timeout=120)
2025-02-03 01:55:35.34: VncKubernetes - Process event (name=coredns-77f7cc69db-hvxzx event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:coredns-77f7cc69db-hvxzx:e1dc7526-a318-44e6-b117-8c3a8c882069
2025-02-03 01:55:35.45: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-03 01:55:35.45: VncKubernetes - Process event (name=dns-autoscaler-595558c478-nm48t event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-nm48t:81d88ed6-1114-46a4-bdb4-12c0c887d066
2025-02-03 01:55:35.54: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 01:55:44.79: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:55:44.80: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:55:44.80: PodMonitor - start process kube event
2025-02-03 01:55:44.80: empty line received
2025-02-03 01:55:44.80: PodMonitor - start process kube event
2025-02-03 01:55:55.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:55:55.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:55:55.59: PodMonitor - start process kube event
2025-02-03 01:55:55.59: empty line received
2025-02-03 01:55:55.59: PodMonitor - start process kube event
2025-02-03 01:55:56.10: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:55:56.10: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:55:56.10: PodMonitor - start process kube event
2025-02-03 01:55:56.10: empty line received
2025-02-03 01:55:56.10: PodMonitor - start process kube event
2025-02-03 01:56:09.48: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:56:09.48: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:56:09.48: PodMonitor - start process kube event
2025-02-03 01:56:09.48: empty line received
2025-02-03 01:56:09.48: PodMonitor - start process kube event
2025-02-03 01:56:14.24: PodMonitor - Received BOOKMARK: oldResVer=9681 newResVer=9774
2025-02-03 01:56:14.24: PodMonitor - start process kube event
2025-02-03 01:56:14.24: empty line received
2025-02-03 01:56:14.24: PodMonitor - start process kube event
2025-02-03 01:56:19.83: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:56:19.83: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:56:19.83: PodMonitor - start process kube event
2025-02-03 01:56:19.83: empty line received
2025-02-03 01:56:19.83: PodMonitor - start process kube event
2025-02-03 01:56:32.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:56:32.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:56:32.59: PodMonitor - start process kube event
2025-02-03 01:56:32.59: empty line received
2025-02-03 01:56:32.59: PodMonitor - start process kube event
2025-02-03 01:56:33.17: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:56:33.17: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:56:33.17: PodMonitor - start process kube event
2025-02-03 01:56:33.17: empty line received
2025-02-03 01:56:33.17: PodMonitor - start process kube event
2025-02-03 01:56:56.72: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:56:56.72: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:56:56.72: PodMonitor - start process kube event
2025-02-03 01:56:56.72: empty line received
2025-02-03 01:56:56.72: PodMonitor - start process kube event
2025-02-03 01:57:09.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:57:09.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:57:09.59: PodMonitor - start process kube event
2025-02-03 01:57:09.59: empty line received
2025-02-03 01:57:09.59: PodMonitor - start process kube event
2025-02-03 01:57:14.36: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 01:57:14.36: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 01:57:14.36: IngressMonitor - start process kube event
2025-02-03 01:57:14.36: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9681
2025-02-03 01:57:14.36: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:57:14.36: NetworkPolicyMonitor - start process kube event
2025-02-03 01:57:14.36: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9681
2025-02-03 01:57:14.36: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:57:14.36: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-03 01:57:14.36: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 01:57:14.36: NetworkPolicyMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:57:14.36: IngressMonitor - Connect Kube API result 0
2025-02-03 01:57:14.37: IngressMonitor - _schedule_vnc_sync
2025-02-03 01:57:14.37: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:57:14.37: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 01:57:14.37: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 01:57:14.37: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 01:57:14.37: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-03 01:57:14.37: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 01:57:14.37: VncKubernetes - vnc_sync - Ingress start
2025-02-03 01:57:14.37: VncKubernetes - vnc_sync - Ingress done
2025-02-03 01:57:14.37: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 01:57:14.38: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:57:14.38: NetworkPolicyMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:57:14.40: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 01:57:14.40: ServiceMonitor - start process kube event
2025-02-03 01:57:14.40: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9681
2025-02-03 01:57:14.40: ServiceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:57:14.40: ServiceMonitor - Connect Kube API result 0
2025-02-03 01:57:14.40: ServiceMonitor - _schedule_vnc_sync
2025-02-03 01:57:14.40: ServiceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:57:14.41: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 01:57:14.41: VncKubernetes - vnc_sync - Service start
2025-02-03 01:57:14.41: VncKubernetes - vnc_sync - Service done
2025-02-03 01:57:14.41: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 01:57:14.41: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 01:57:14.41: EndPointMonitor - start process kube event
2025-02-03 01:57:14.41: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9681
2025-02-03 01:57:14.41: EndPointMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:57:14.41: EndPointMonitor - Connect Kube API result 0
2025-02-03 01:57:14.41: EndPointMonitor - _schedule_vnc_sync
2025-02-03 01:57:14.41: EndPointMonitor - Start Watching request https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:57:14.41: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 01:57:14.41: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 01:57:14.41: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 01:57:14.41: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 01:57:14.41: NetworkMonitor - start process kube event
2025-02-03 01:57:14.41: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9685
2025-02-03 01:57:14.41: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:57:14.41: NetworkMonitor - Connect Kube API result 0
2025-02-03 01:57:14.41: NetworkMonitor - _schedule_vnc_sync
2025-02-03 01:57:14.41: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})(timeout=120)
2025-02-03 01:57:14.41: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 01:57:14.41: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 01:57:14.41: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 01:57:14.41: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 01:57:14.41: NamespaceMonitor - start process kube event
2025-02-03 01:57:14.41: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9681
2025-02-03 01:57:14.41: NamespaceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:57:14.41: NamespaceMonitor - Connect Kube API result 0
2025-02-03 01:57:14.42: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 01:57:14.42: NamespaceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:57:14.42: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 01:57:14.42: VncKubernetes - vnc_sync - Namespace start
2025-02-03 01:57:14.42: VncKubernetes - vnc_sync - Namespace done
2025-02-03 01:57:14.42: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 01:57:14.42: ServiceMonitor - Watches https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:57:14.42: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})
2025-02-03 01:57:14.42: EndPointMonitor - Watches https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:57:14.43: NamespaceMonitor - Watches https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:57:15.01: PodMonitor - Received BOOKMARK: oldResVer=9774 newResVer=9867
2025-02-03 01:57:15.01: PodMonitor - start process kube event
2025-02-03 01:57:15.01: empty line received
2025-02-03 01:57:15.01: PodMonitor - start process kube event
2025-02-03 01:57:21.36: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:57:21.36: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:57:21.36: PodMonitor - start process kube event
2025-02-03 01:57:21.36: empty line received
2025-02-03 01:57:21.36: PodMonitor - start process kube event
2025-02-03 01:57:34.83: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:57:34.83: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:57:34.83: PodMonitor - start process kube event
2025-02-03 01:57:34.83: empty line received
2025-02-03 01:57:34.83: PodMonitor - start process kube event
2025-02-03 01:57:35.87: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:57:35.87: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:57:35.87: PodMonitor - start process kube event
2025-02-03 01:57:35.87: empty line received
2025-02-03 01:57:35.87: PodMonitor - start process kube event
2025-02-03 01:58:01.51: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:58:01.51: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:58:01.51: PodMonitor - start process kube event
2025-02-03 01:58:01.51: empty line received
2025-02-03 01:58:01.51: PodMonitor - start process kube event
2025-02-03 01:58:14.26: EndPointMonitor - Received BOOKMARK: oldResVer=9681 newResVer=9859
2025-02-03 01:58:14.26: EndPointMonitor - start process kube event
2025-02-03 01:58:14.26: empty line received
2025-02-03 01:58:14.26: EndPointMonitor - start process kube event
2025-02-03 01:58:14.72: ServiceMonitor - Received BOOKMARK: oldResVer=9681 newResVer=9826
2025-02-03 01:58:14.72: ServiceMonitor - start process kube event
2025-02-03 01:58:14.72: empty line received
2025-02-03 01:58:14.72: ServiceMonitor - start process kube event
2025-02-03 01:58:15.49: PodMonitor - Received BOOKMARK: oldResVer=9867 newResVer=9948
2025-02-03 01:58:15.49: PodMonitor - start process kube event
2025-02-03 01:58:15.49: empty line received
2025-02-03 01:58:15.49: PodMonitor - start process kube event
2025-02-03 01:58:21.02: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:58:21.02: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:58:21.02: PodMonitor - start process kube event
2025-02-03 01:58:21.02: empty line received
2025-02-03 01:58:21.02: PodMonitor - start process kube event
2025-02-03 01:58:32.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:58:32.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:58:32.59: PodMonitor - start process kube event
2025-02-03 01:58:32.59: empty line received
2025-02-03 01:58:32.59: PodMonitor - start process kube event
2025-02-03 01:59:01.02: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:59:01.02: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:59:01.02: PodMonitor - start process kube event
2025-02-03 01:59:01.02: empty line received
2025-02-03 01:59:01.02: PodMonitor - start process kube event
2025-02-03 01:59:02.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:59:02.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:59:02.06: PodMonitor - start process kube event
2025-02-03 01:59:02.06: empty line received
2025-02-03 01:59:02.06: PodMonitor - start process kube event
2025-02-03 01:59:14.09: ServiceMonitor - Received BOOKMARK: oldResVer=9826 newResVer=9826
2025-02-03 01:59:14.09: ServiceMonitor - start process kube event
2025-02-03 01:59:14.09: empty line received
2025-02-03 01:59:14.09: ServiceMonitor - start process kube event
2025-02-03 01:59:14.28: EndPointMonitor - Received BOOKMARK: oldResVer=9859 newResVer=9859
2025-02-03 01:59:14.28: EndPointMonitor - start process kube event
2025-02-03 01:59:14.28: empty line received
2025-02-03 01:59:14.28: EndPointMonitor - start process kube event
2025-02-03 01:59:14.38: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 01:59:14.38: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 01:59:14.38: IngressMonitor - start process kube event
2025-02-03 01:59:14.38: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9681
2025-02-03 01:59:14.38: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:59:14.38: NetworkPolicyMonitor - start process kube event
2025-02-03 01:59:14.38: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9681
2025-02-03 01:59:14.38: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:59:14.38: IngressMonitor - Connect Kube API result 0
2025-02-03 01:59:14.38: IngressMonitor - _schedule_vnc_sync
2025-02-03 01:59:14.38: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:59:14.38: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-03 01:59:14.38: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 01:59:14.38: NetworkPolicyMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:59:14.39: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 01:59:14.39: VncKubernetes - vnc_sync - Ingress start
2025-02-03 01:59:14.39: VncKubernetes - vnc_sync - Ingress done
2025-02-03 01:59:14.39: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-03 01:59:14.39: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 01:59:14.39: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 01:59:14.40: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 01:59:14.40: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 01:59:14.40: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:59:14.40: NetworkPolicyMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:59:14.42: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 01:59:14.42: NetworkMonitor - start process kube event
2025-02-03 01:59:14.42: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9685
2025-02-03 01:59:14.42: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:59:14.42: NetworkMonitor - Connect Kube API result 0
2025-02-03 01:59:14.42: NetworkMonitor - _schedule_vnc_sync
2025-02-03 01:59:14.42: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})(timeout=120)
2025-02-03 01:59:14.43: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 01:59:14.43: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 01:59:14.43: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 01:59:14.43: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 01:59:14.43: NamespaceMonitor - start process kube event
2025-02-03 01:59:14.43: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9681
2025-02-03 01:59:14.43: NamespaceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 01:59:14.43: NamespaceMonitor - Connect Kube API result 0
2025-02-03 01:59:14.43: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 01:59:14.43: NamespaceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 01:59:14.43: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 01:59:14.43: VncKubernetes - vnc_sync - Namespace start
2025-02-03 01:59:14.43: VncKubernetes - vnc_sync - Namespace done
2025-02-03 01:59:14.43: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 01:59:14.43: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})
2025-02-03 01:59:14.43: NamespaceMonitor - Watches https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 01:59:15.32: PodMonitor - Received BOOKMARK: oldResVer=9948 newResVer=10042
2025-02-03 01:59:15.32: PodMonitor - start process kube event
2025-02-03 01:59:15.32: PodMonitor - _schedule_vnc_sync
2025-02-03 01:59:15.32: empty line received
2025-02-03 01:59:15.32: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 01:59:15.32: VncKubernetes - vnc_sync - Pod start
2025-02-03 01:59:15.32: VncKubernetes - vnc_sync - Pod done
2025-02-03 01:59:15.32: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 01:59:15.32: PodMonitor - start process kube event
2025-02-03 01:59:46.11: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 01:59:46.11: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 01:59:46.11: PodMonitor - start process kube event
2025-02-03 01:59:46.11: empty line received
2025-02-03 01:59:46.11: PodMonitor - start process kube event
2025-02-03 02:00:01.52: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:00:01.52: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:00:01.52: PodMonitor - start process kube event
2025-02-03 02:00:01.52: empty line received
2025-02-03 02:00:01.52: PodMonitor - start process kube event
2025-02-03 02:00:14.01: ServiceMonitor - Received BOOKMARK: oldResVer=9826 newResVer=9826
2025-02-03 02:00:14.01: ServiceMonitor - start process kube event
2025-02-03 02:00:14.01: empty line received
2025-02-03 02:00:14.01: ServiceMonitor - start process kube event
2025-02-03 02:00:14.02: EndPointMonitor - Received BOOKMARK: oldResVer=9859 newResVer=9859
2025-02-03 02:00:14.02: EndPointMonitor - start process kube event
2025-02-03 02:00:14.02: empty line received
2025-02-03 02:00:14.02: EndPointMonitor - start process kube event
2025-02-03 02:00:14.60: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:00:14.60: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:00:14.60: PodMonitor - start process kube event
2025-02-03 02:00:14.60: empty line received
2025-02-03 02:00:14.60: PodMonitor - start process kube event
2025-02-03 02:00:14.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:00:14.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:00:14.90: PodMonitor - start process kube event
2025-02-03 02:00:14.90: empty line received
2025-02-03 02:00:14.90: PodMonitor - start process kube event
2025-02-03 02:00:15.03: IngressMonitor - Received BOOKMARK: oldResVer=9681 newResVer=10063
2025-02-03 02:00:15.03: IngressMonitor - start process kube event
2025-02-03 02:00:15.03: empty line received
2025-02-03 02:00:15.03: IngressMonitor - start process kube event
2025-02-03 02:00:15.19: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9681 newResVer=10102
2025-02-03 02:00:15.19: NetworkPolicyMonitor - start process kube event
2025-02-03 02:00:15.19: empty line received
2025-02-03 02:00:15.19: NetworkPolicyMonitor - start process kube event
2025-02-03 02:00:15.53: PodMonitor - Received BOOKMARK: oldResVer=10042 newResVer=10152
2025-02-03 02:00:15.53: PodMonitor - start process kube event
2025-02-03 02:00:15.53: empty line received
2025-02-03 02:00:15.53: PodMonitor - start process kube event
2025-02-03 02:00:15.94: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:00:15.94: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:00:15.94: PodMonitor - start process kube event
2025-02-03 02:00:15.94: empty line received
2025-02-03 02:00:15.94: PodMonitor - start process kube event
2025-02-03 02:00:28.60: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:00:28.60: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:00:28.60: PodMonitor - start process kube event
2025-02-03 02:00:28.60: empty line received
2025-02-03 02:00:28.60: PodMonitor - start process kube event
2025-02-03 02:00:46.76: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:00:46.76: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:00:46.76: PodMonitor - start process kube event
2025-02-03 02:00:46.76: empty line received
2025-02-03 02:00:46.76: PodMonitor - start process kube event
2025-02-03 02:01:02.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:01:02.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:01:02.59: PodMonitor - start process kube event
2025-02-03 02:01:02.59: empty line received
2025-02-03 02:01:02.59: PodMonitor - start process kube event
2025-02-03 02:01:14.16: IngressMonitor - Received BOOKMARK: oldResVer=10063 newResVer=10063
2025-02-03 02:01:14.16: IngressMonitor - start process kube event
2025-02-03 02:01:14.16: empty line received
2025-02-03 02:01:14.16: IngressMonitor - start process kube event
2025-02-03 02:01:14.27: ServiceMonitor - Received BOOKMARK: oldResVer=9826 newResVer=9826
2025-02-03 02:01:14.27: ServiceMonitor - start process kube event
2025-02-03 02:01:14.27: empty line received
2025-02-03 02:01:14.27: ServiceMonitor - start process kube event
2025-02-03 02:01:14.43: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 02:01:14.43: NetworkMonitor - start process kube event
2025-02-03 02:01:14.43: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9685
2025-02-03 02:01:14.43: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:01:14.44: NetworkMonitor - Connect Kube API result 0
2025-02-03 02:01:14.44: NetworkMonitor - _schedule_vnc_sync
2025-02-03 02:01:14.44: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})(timeout=120)
2025-02-03 02:01:14.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 02:01:14.44: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 02:01:14.44: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:01:14.44: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 02:01:14.44: NamespaceMonitor - start process kube event
2025-02-03 02:01:14.44: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9681
2025-02-03 02:01:14.44: NamespaceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:01:14.44: NamespaceMonitor - Connect Kube API result 0
2025-02-03 02:01:14.44: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 02:01:14.44: NamespaceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 02:01:14.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 02:01:14.44: VncKubernetes - vnc_sync - Namespace start
2025-02-03 02:01:14.44: VncKubernetes - vnc_sync - Namespace done
2025-02-03 02:01:14.44: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:01:14.45: NamespaceMonitor - Watches https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 02:01:14.45: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})
2025-02-03 02:01:14.95: EndPointMonitor - Received BOOKMARK: oldResVer=9859 newResVer=9859
2025-02-03 02:01:14.95: EndPointMonitor - start process kube event
2025-02-03 02:01:14.95: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:01:14.95: empty line received
2025-02-03 02:01:14.95: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:01:14.95: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:01:14.95: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:01:14.95: EndPointMonitor - start process kube event
2025-02-03 02:01:15.12: PodMonitor - Received BOOKMARK: oldResVer=10152 newResVer=10222
2025-02-03 02:01:15.12: PodMonitor - start process kube event
2025-02-03 02:01:15.12: empty line received
2025-02-03 02:01:15.12: PodMonitor - start process kube event
2025-02-03 02:01:15.88: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10102 newResVer=10102
2025-02-03 02:01:15.88: NetworkPolicyMonitor - start process kube event
2025-02-03 02:01:15.88: empty line received
2025-02-03 02:01:15.88: NetworkPolicyMonitor - start process kube event
2025-02-03 02:01:28.87: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:01:28.87: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:01:28.87: PodMonitor - start process kube event
2025-02-03 02:01:28.87: empty line received
2025-02-03 02:01:28.87: PodMonitor - start process kube event
2025-02-03 02:02:09.86: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:02:09.86: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:02:09.86: PodMonitor - start process kube event
2025-02-03 02:02:09.86: empty line received
2025-02-03 02:02:09.86: PodMonitor - start process kube event
2025-02-03 02:02:14.44: ServiceMonitor - Received BOOKMARK: oldResVer=9826 newResVer=9826
2025-02-03 02:02:14.44: ServiceMonitor - start process kube event
2025-02-03 02:02:14.44: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:02:14.44: empty line received
2025-02-03 02:02:14.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:02:14.44: VncKubernetes - vnc_sync - Service start
2025-02-03 02:02:14.44: VncKubernetes - vnc_sync - Service done
2025-02-03 02:02:14.44: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:02:14.44: ServiceMonitor - start process kube event
2025-02-03 02:02:14.44: IngressMonitor - Received BOOKMARK: oldResVer=10063 newResVer=10063
2025-02-03 02:02:14.44: IngressMonitor - start process kube event
2025-02-03 02:02:14.44: empty line received
2025-02-03 02:02:14.44: IngressMonitor - start process kube event
2025-02-03 02:02:14.74: EndPointMonitor - Received BOOKMARK: oldResVer=9859 newResVer=9859
2025-02-03 02:02:14.74: EndPointMonitor - start process kube event
2025-02-03 02:02:14.74: empty line received
2025-02-03 02:02:14.74: EndPointMonitor - start process kube event
2025-02-03 02:02:15.78: PodMonitor - Received BOOKMARK: oldResVer=10222 newResVer=10320
2025-02-03 02:02:15.78: PodMonitor - start process kube event
2025-02-03 02:02:15.78: empty line received
2025-02-03 02:02:15.78: PodMonitor - start process kube event
2025-02-03 02:02:16.12: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10102 newResVer=10102
2025-02-03 02:02:16.12: NetworkPolicyMonitor - start process kube event
2025-02-03 02:02:16.12: empty line received
2025-02-03 02:02:16.12: NetworkPolicyMonitor - start process kube event
2025-02-03 02:02:29.38: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:02:29.38: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:02:29.38: PodMonitor - start process kube event
2025-02-03 02:02:29.38: empty line received
2025-02-03 02:02:29.38: PodMonitor - start process kube event
2025-02-03 02:02:41.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:02:41.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:02:41.59: PodMonitor - start process kube event
2025-02-03 02:02:41.59: empty line received
2025-02-03 02:02:41.59: PodMonitor - start process kube event
2025-02-03 02:03:10.42: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:03:10.42: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:03:10.42: PodMonitor - start process kube event
2025-02-03 02:03:10.42: empty line received
2025-02-03 02:03:10.42: PodMonitor - start process kube event
2025-02-03 02:03:14.24: IngressMonitor - Received BOOKMARK: oldResVer=10063 newResVer=10063
2025-02-03 02:03:14.24: IngressMonitor - start process kube event
2025-02-03 02:03:14.24: empty line received
2025-02-03 02:03:14.24: IngressMonitor - start process kube event
2025-02-03 02:03:14.45: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 02:03:14.45: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 02:03:14.45: NamespaceMonitor - start process kube event
2025-02-03 02:03:14.45: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9681
2025-02-03 02:03:14.45: NamespaceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:03:14.45: NetworkMonitor - start process kube event
2025-02-03 02:03:14.45: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9685
2025-02-03 02:03:14.45: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:03:14.45: NamespaceMonitor - Connect Kube API result 0
2025-02-03 02:03:14.45: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 02:03:14.45: NamespaceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})(timeout=120)
2025-02-03 02:03:14.46: NetworkMonitor - Connect Kube API result 0
2025-02-03 02:03:14.46: NetworkMonitor - _schedule_vnc_sync
2025-02-03 02:03:14.46: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})(timeout=120)
2025-02-03 02:03:14.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 02:03:14.46: VncKubernetes - vnc_sync - Namespace start
2025-02-03 02:03:14.46: VncKubernetes - vnc_sync - Namespace done
2025-02-03 02:03:14.46: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-03 02:03:14.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 02:03:14.46: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 02:03:14.46: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:03:14.46: NamespaceMonitor - Watches https://10.0.0.40:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9681'})
2025-02-03 02:03:14.46: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})
2025-02-03 02:03:14.64: ServiceMonitor - Received BOOKMARK: oldResVer=9826 newResVer=9826
2025-02-03 02:03:14.64: ServiceMonitor - start process kube event
2025-02-03 02:03:14.64: empty line received
2025-02-03 02:03:14.64: ServiceMonitor - start process kube event
2025-02-03 02:03:14.77: EndPointMonitor - Received BOOKMARK: oldResVer=9859 newResVer=9859
2025-02-03 02:03:14.77: EndPointMonitor - start process kube event
2025-02-03 02:03:14.77: empty line received
2025-02-03 02:03:14.77: EndPointMonitor - start process kube event
2025-02-03 02:03:15.24: PodMonitor - Received BOOKMARK: oldResVer=10320 newResVer=10413
2025-02-03 02:03:15.24: PodMonitor - start process kube event
2025-02-03 02:03:15.24: empty line received
2025-02-03 02:03:15.24: PodMonitor - start process kube event
2025-02-03 02:03:16.55: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10102 newResVer=10102
2025-02-03 02:03:16.56: NetworkPolicyMonitor - start process kube event
2025-02-03 02:03:16.56: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 02:03:16.56: empty line received
2025-02-03 02:03:16.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 02:03:16.56: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 02:03:16.56: NetworkPolicyMonitor - start process kube event
2025-02-03 02:03:16.57: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 02:03:16.57: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:03:24.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:03:24.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:03:24.59: PodMonitor - start process kube event
2025-02-03 02:03:24.59: PodMonitor - _schedule_vnc_sync
2025-02-03 02:03:24.59: empty line received
2025-02-03 02:03:24.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 02:03:24.59: VncKubernetes - vnc_sync - Pod start
2025-02-03 02:03:24.59: VncKubernetes - vnc_sync - Pod done
2025-02-03 02:03:24.59: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:03:24.59: PodMonitor - start process kube event
2025-02-03 02:04:14.75: NamespaceMonitor - Received BOOKMARK: oldResVer=9681 newResVer=10351
2025-02-03 02:04:14.75: NamespaceMonitor - start process kube event
2025-02-03 02:04:14.75: empty line received
2025-02-03 02:04:14.75: NamespaceMonitor - start process kube event
2025-02-03 02:04:14.81: ServiceMonitor - Received BOOKMARK: oldResVer=9826 newResVer=9826
2025-02-03 02:04:14.81: ServiceMonitor - start process kube event
2025-02-03 02:04:14.81: empty line received
2025-02-03 02:04:14.81: ServiceMonitor - start process kube event
2025-02-03 02:04:14.82: EndPointMonitor - Received BOOKMARK: oldResVer=9859 newResVer=9859
2025-02-03 02:04:14.82: EndPointMonitor - start process kube event
2025-02-03 02:04:14.82: empty line received
2025-02-03 02:04:14.82: EndPointMonitor - start process kube event
2025-02-03 02:04:15.01: IngressMonitor - Received BOOKMARK: oldResVer=10063 newResVer=10063
2025-02-03 02:04:15.01: IngressMonitor - start process kube event
2025-02-03 02:04:15.01: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:04:15.01: empty line received
2025-02-03 02:04:15.01: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:04:15.01: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:04:15.01: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:04:15.01: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:04:15.01: IngressMonitor - start process kube event
2025-02-03 02:04:15.42: PodMonitor - Received BOOKMARK: oldResVer=10413 newResVer=10434
2025-02-03 02:04:15.42: PodMonitor - start process kube event
2025-02-03 02:04:15.42: empty line received
2025-02-03 02:04:15.42: PodMonitor - start process kube event
2025-02-03 02:04:17.12: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10102 newResVer=10102
2025-02-03 02:04:17.12: NetworkPolicyMonitor - start process kube event
2025-02-03 02:04:17.12: empty line received
2025-02-03 02:04:17.12: NetworkPolicyMonitor - start process kube event
2025-02-03 02:05:12.43: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:05:12.43: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:05:12.43: PodMonitor - start process kube event
2025-02-03 02:05:12.43: empty line received
2025-02-03 02:05:12.43: PodMonitor - start process kube event
2025-02-03 02:05:14.15: ServiceMonitor - Received BOOKMARK: oldResVer=9826 newResVer=9826
2025-02-03 02:05:14.15: ServiceMonitor - start process kube event
2025-02-03 02:05:14.15: empty line received
2025-02-03 02:05:14.15: ServiceMonitor - start process kube event
2025-02-03 02:05:14.47: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 02:05:14.47: NetworkMonitor - start process kube event
2025-02-03 02:05:14.47: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9685
2025-02-03 02:05:14.47: NetworkMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:05:14.47: NetworkMonitor - Connect Kube API result 0
2025-02-03 02:05:14.47: NetworkMonitor - _schedule_vnc_sync
2025-02-03 02:05:14.47: NetworkMonitor - Start Watching request https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})(timeout=120)
2025-02-03 02:05:14.47: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 02:05:14.47: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 02:05:14.47: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:05:14.48: NetworkMonitor - Watches https://10.0.0.40:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9685'})
2025-02-03 02:05:14.65: NamespaceMonitor - Received BOOKMARK: oldResVer=10351 newResVer=10351
2025-02-03 02:05:14.65: NamespaceMonitor - start process kube event
2025-02-03 02:05:14.65: empty line received
2025-02-03 02:05:14.65: NamespaceMonitor - start process kube event
2025-02-03 02:05:14.98: EndPointMonitor - Received BOOKMARK: oldResVer=9859 newResVer=9859
2025-02-03 02:05:14.98: EndPointMonitor - start process kube event
2025-02-03 02:05:14.98: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:05:14.98: empty line received
2025-02-03 02:05:14.98: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:05:14.98: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:05:14.98: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:05:14.98: EndPointMonitor - start process kube event
2025-02-03 02:05:15.11: IngressMonitor - Received BOOKMARK: oldResVer=10063 newResVer=10063
2025-02-03 02:05:15.11: IngressMonitor - start process kube event
2025-02-03 02:05:15.11: empty line received
2025-02-03 02:05:15.11: IngressMonitor - start process kube event
2025-02-03 02:05:15.48: PodMonitor - Received BOOKMARK: oldResVer=10434 newResVer=10594
2025-02-03 02:05:15.48: PodMonitor - start process kube event
2025-02-03 02:05:15.48: empty line received
2025-02-03 02:05:15.48: PodMonitor - start process kube event
2025-02-03 02:05:17.31: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10102 newResVer=10102
2025-02-03 02:05:17.31: NetworkPolicyMonitor - start process kube event
2025-02-03 02:05:17.31: empty line received
2025-02-03 02:05:17.31: NetworkPolicyMonitor - start process kube event
2025-02-03 02:05:27.79: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:05:27.80: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:05:27.80: PodMonitor - start process kube event
2025-02-03 02:05:27.80: empty line received
2025-02-03 02:05:27.80: PodMonitor - start process kube event
2025-02-03 02:05:28.87: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:05:28.87: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:05:28.87: PodMonitor - start process kube event
2025-02-03 02:05:28.87: empty line received
2025-02-03 02:05:28.87: PodMonitor - start process kube event
2025-02-03 02:05:39.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:05:39.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:05:39.59: PodMonitor - start process kube event
2025-02-03 02:05:39.59: empty line received
2025-02-03 02:05:39.59: PodMonitor - start process kube event
2025-02-03 02:05:55.57: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:05:55.57: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:05:55.57: PodMonitor - start process kube event
2025-02-03 02:05:55.57: empty line received
2025-02-03 02:05:55.57: PodMonitor - start process kube event
2025-02-03 02:06:11.99: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:06:11.99: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:06:11.99: PodMonitor - start process kube event
2025-02-03 02:06:11.99: empty line received
2025-02-03 02:06:11.99: PodMonitor - start process kube event
2025-02-03 02:06:14.71: ServiceMonitor - Received BOOKMARK: oldResVer=9826 newResVer=9826
2025-02-03 02:06:14.71: ServiceMonitor - start process kube event
2025-02-03 02:06:14.72: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:06:14.72: empty line received
2025-02-03 02:06:14.72: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:06:14.72: VncKubernetes - vnc_sync - Service start
2025-02-03 02:06:14.72: VncKubernetes - vnc_sync - Service done
2025-02-03 02:06:14.72: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:06:14.72: ServiceMonitor - start process kube event
2025-02-03 02:06:14.96: NamespaceMonitor - Received BOOKMARK: oldResVer=10351 newResVer=10351
2025-02-03 02:06:14.96: NamespaceMonitor - start process kube event
2025-02-03 02:06:14.96: empty line received
2025-02-03 02:06:14.96: NamespaceMonitor - start process kube event
2025-02-03 02:06:14.99: IngressMonitor - Received BOOKMARK: oldResVer=10063 newResVer=10063
2025-02-03 02:06:14.99: IngressMonitor - start process kube event
2025-02-03 02:06:14.99: empty line received
2025-02-03 02:06:14.99: IngressMonitor - start process kube event
2025-02-03 02:06:15.31: NetworkMonitor - Received BOOKMARK: oldResVer=9685 newResVer=10655
2025-02-03 02:06:15.31: NetworkMonitor - start process kube event
2025-02-03 02:06:15.31: empty line received
2025-02-03 02:06:15.31: NetworkMonitor - start process kube event
2025-02-03 02:06:15.57: PodMonitor - Received BOOKMARK: oldResVer=10594 newResVer=10682
2025-02-03 02:06:15.57: PodMonitor - start process kube event
2025-02-03 02:06:15.57: empty line received
2025-02-03 02:06:15.57: PodMonitor - start process kube event
2025-02-03 02:06:15.60: EndPointMonitor - Received BOOKMARK: oldResVer=9859 newResVer=9859
2025-02-03 02:06:15.60: EndPointMonitor - start process kube event
2025-02-03 02:06:15.60: empty line received
2025-02-03 02:06:15.60: EndPointMonitor - start process kube event
2025-02-03 02:06:17.98: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10102 newResVer=10102
2025-02-03 02:06:17.98: NetworkPolicyMonitor - start process kube event
2025-02-03 02:06:17.98: empty line received
2025-02-03 02:06:17.98: NetworkPolicyMonitor - start process kube event
2025-02-03 02:06:23.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:06:23.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:06:23.59: PodMonitor - start process kube event
2025-02-03 02:06:23.59: empty line received
2025-02-03 02:06:23.59: PodMonitor - start process kube event
2025-02-03 02:06:55.08: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:06:55.08: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:06:55.08: PodMonitor - start process kube event
2025-02-03 02:06:55.08: empty line received
2025-02-03 02:06:55.08: PodMonitor - start process kube event
2025-02-03 02:07:05.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:07:05.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:07:05.59: PodMonitor - start process kube event
2025-02-03 02:07:05.59: empty line received
2025-02-03 02:07:05.59: PodMonitor - start process kube event
2025-02-03 02:07:14.47: NetworkMonitor - Received BOOKMARK: oldResVer=10655 newResVer=10655
2025-02-03 02:07:14.48: NetworkMonitor - start process kube event
2025-02-03 02:07:14.48: empty line received
2025-02-03 02:07:14.48: NetworkMonitor - start process kube event
2025-02-03 02:07:14.52: ServiceMonitor - Received BOOKMARK: oldResVer=9826 newResVer=9826
2025-02-03 02:07:14.52: ServiceMonitor - start process kube event
2025-02-03 02:07:14.52: empty line received
2025-02-03 02:07:14.52: ServiceMonitor - start process kube event
2025-02-03 02:07:14.94: IngressMonitor - Received BOOKMARK: oldResVer=10063 newResVer=10063
2025-02-03 02:07:14.94: IngressMonitor - start process kube event
2025-02-03 02:07:14.94: empty line received
2025-02-03 02:07:14.94: IngressMonitor - start process kube event
2025-02-03 02:07:15.17: NamespaceMonitor - Received BOOKMARK: oldResVer=10351 newResVer=10351
2025-02-03 02:07:15.17: NamespaceMonitor - start process kube event
2025-02-03 02:07:15.17: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 02:07:15.17: empty line received
2025-02-03 02:07:15.17: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 02:07:15.17: VncKubernetes - vnc_sync - Namespace start
2025-02-03 02:07:15.17: VncKubernetes - vnc_sync - Namespace done
2025-02-03 02:07:15.17: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:07:15.17: NamespaceMonitor - start process kube event
2025-02-03 02:07:15.23: EndPointMonitor - Received BOOKMARK: oldResVer=9859 newResVer=9859
2025-02-03 02:07:15.23: EndPointMonitor - start process kube event
2025-02-03 02:07:15.23: empty line received
2025-02-03 02:07:15.23: EndPointMonitor - start process kube event
2025-02-03 02:07:15.44: PodMonitor - Received BOOKMARK: oldResVer=10682 newResVer=10763
2025-02-03 02:07:15.44: PodMonitor - start process kube event
2025-02-03 02:07:15.44: empty line received
2025-02-03 02:07:15.44: PodMonitor - start process kube event
2025-02-03 02:07:18.05: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10102 newResVer=10102
2025-02-03 02:07:18.05: NetworkPolicyMonitor - start process kube event
2025-02-03 02:07:18.05: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 02:07:18.05: empty line received
2025-02-03 02:07:18.05: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 02:07:18.05: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 02:07:18.05: NetworkPolicyMonitor - start process kube event
2025-02-03 02:07:18.06: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 02:07:18.06: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:08:14.26: ServiceMonitor - Received BOOKMARK: oldResVer=9826 newResVer=10797
2025-02-03 02:08:14.26: ServiceMonitor - start process kube event
2025-02-03 02:08:14.26: empty line received
2025-02-03 02:08:14.26: ServiceMonitor - start process kube event
2025-02-03 02:08:14.38: IngressMonitor - Received BOOKMARK: oldResVer=10063 newResVer=10063
2025-02-03 02:08:14.38: IngressMonitor - start process kube event
2025-02-03 02:08:14.38: empty line received
2025-02-03 02:08:14.38: IngressMonitor - start process kube event
2025-02-03 02:08:14.47: NetworkMonitor - Received BOOKMARK: oldResVer=10655 newResVer=10655
2025-02-03 02:08:14.47: NetworkMonitor - start process kube event
2025-02-03 02:08:14.47: empty line received
2025-02-03 02:08:14.47: NetworkMonitor - start process kube event
2025-02-03 02:08:15.08: EndPointMonitor - Received BOOKMARK: oldResVer=9859 newResVer=10836
2025-02-03 02:08:15.08: EndPointMonitor - start process kube event
2025-02-03 02:08:15.08: empty line received
2025-02-03 02:08:15.08: EndPointMonitor - start process kube event
2025-02-03 02:08:15.58: PodMonitor - Received BOOKMARK: oldResVer=10763 newResVer=10763
2025-02-03 02:08:15.58: PodMonitor - start process kube event
2025-02-03 02:08:15.58: PodMonitor - _schedule_vnc_sync
2025-02-03 02:08:15.58: empty line received
2025-02-03 02:08:15.58: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 02:08:15.58: VncKubernetes - vnc_sync - Pod start
2025-02-03 02:08:15.58: VncKubernetes - vnc_sync - Pod done
2025-02-03 02:08:15.58: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:08:15.58: PodMonitor - start process kube event
2025-02-03 02:08:15.75: NamespaceMonitor - Received BOOKMARK: oldResVer=10351 newResVer=10351
2025-02-03 02:08:15.75: NamespaceMonitor - start process kube event
2025-02-03 02:08:15.75: empty line received
2025-02-03 02:08:15.75: NamespaceMonitor - start process kube event
2025-02-03 02:08:17.91: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10102 newResVer=10102
2025-02-03 02:08:17.91: NetworkPolicyMonitor - start process kube event
2025-02-03 02:08:17.91: empty line received
2025-02-03 02:08:17.91: NetworkPolicyMonitor - start process kube event
2025-02-03 02:09:14.17: ServiceMonitor - Received BOOKMARK: oldResVer=10797 newResVer=10797
2025-02-03 02:09:14.17: ServiceMonitor - start process kube event
2025-02-03 02:09:14.17: empty line received
2025-02-03 02:09:14.17: ServiceMonitor - start process kube event
2025-02-03 02:09:14.71: IngressMonitor - Received BOOKMARK: oldResVer=10063 newResVer=10063
2025-02-03 02:09:14.71: IngressMonitor - start process kube event
2025-02-03 02:09:14.71: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:09:14.71: empty line received
2025-02-03 02:09:14.71: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:09:14.71: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:09:14.71: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:09:14.71: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:09:14.71: IngressMonitor - start process kube event
2025-02-03 02:09:15.06: PodMonitor - Received BOOKMARK: oldResVer=10763 newResVer=10763
2025-02-03 02:09:15.06: PodMonitor - start process kube event
2025-02-03 02:09:15.06: empty line received
2025-02-03 02:09:15.06: PodMonitor - start process kube event
2025-02-03 02:09:15.11: NamespaceMonitor - Received BOOKMARK: oldResVer=10351 newResVer=10351
2025-02-03 02:09:15.11: NamespaceMonitor - start process kube event
2025-02-03 02:09:15.11: empty line received
2025-02-03 02:09:15.11: NamespaceMonitor - start process kube event
2025-02-03 02:09:15.46: NetworkMonitor - Received BOOKMARK: oldResVer=10655 newResVer=10655
2025-02-03 02:09:15.46: NetworkMonitor - start process kube event
2025-02-03 02:09:15.46: NetworkMonitor - _schedule_vnc_sync
2025-02-03 02:09:15.46: empty line received
2025-02-03 02:09:15.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 02:09:15.46: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 02:09:15.46: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:09:15.46: NetworkMonitor - start process kube event
2025-02-03 02:09:15.51: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-02-03 02:09:15.51: EndPointMonitor - start process kube event
2025-02-03 02:09:15.51: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:09:15.51: empty line received
2025-02-03 02:09:15.51: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:09:15.51: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:09:15.51: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:09:15.51: EndPointMonitor - start process kube event
2025-02-03 02:09:17.58: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10102 newResVer=10102
2025-02-03 02:09:17.58: NetworkPolicyMonitor - start process kube event
2025-02-03 02:09:17.58: empty line received
2025-02-03 02:09:17.58: NetworkPolicyMonitor - start process kube event
2025-02-03 02:10:15.02: IngressMonitor - Received BOOKMARK: oldResVer=10063 newResVer=10965
2025-02-03 02:10:15.02: ServiceMonitor - Received BOOKMARK: oldResVer=10797 newResVer=10797
2025-02-03 02:10:15.02: IngressMonitor - start process kube event
2025-02-03 02:10:15.02: empty line received
2025-02-03 02:10:15.02: ServiceMonitor - start process kube event
2025-02-03 02:10:15.02: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:10:15.02: empty line received
2025-02-03 02:10:15.02: IngressMonitor - start process kube event
2025-02-03 02:10:15.02: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:10:15.02: VncKubernetes - vnc_sync - Service start
2025-02-03 02:10:15.02: VncKubernetes - vnc_sync - Service done
2025-02-03 02:10:15.02: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:10:15.02: ServiceMonitor - start process kube event
2025-02-03 02:10:15.16: PodMonitor - Received BOOKMARK: oldResVer=10763 newResVer=10763
2025-02-03 02:10:15.16: PodMonitor - start process kube event
2025-02-03 02:10:15.16: empty line received
2025-02-03 02:10:15.16: PodMonitor - start process kube event
2025-02-03 02:10:15.21: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-02-03 02:10:15.21: EndPointMonitor - start process kube event
2025-02-03 02:10:15.21: empty line received
2025-02-03 02:10:15.21: EndPointMonitor - start process kube event
2025-02-03 02:10:15.34: NamespaceMonitor - Received BOOKMARK: oldResVer=10351 newResVer=10351
2025-02-03 02:10:15.34: NamespaceMonitor - start process kube event
2025-02-03 02:10:15.34: empty line received
2025-02-03 02:10:15.34: NamespaceMonitor - start process kube event
2025-02-03 02:10:16.01: NetworkMonitor - Received BOOKMARK: oldResVer=10655 newResVer=10655
2025-02-03 02:10:16.01: NetworkMonitor - start process kube event
2025-02-03 02:10:16.01: empty line received
2025-02-03 02:10:16.01: NetworkMonitor - start process kube event
2025-02-03 02:10:17.62: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10102 newResVer=11006
2025-02-03 02:10:17.63: NetworkPolicyMonitor - start process kube event
2025-02-03 02:10:17.63: empty line received
2025-02-03 02:10:17.63: NetworkPolicyMonitor - start process kube event
2025-02-03 02:10:32.24: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:10:32.24: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:10:32.24: PodMonitor - start process kube event
2025-02-03 02:10:32.24: empty line received
2025-02-03 02:10:32.24: PodMonitor - start process kube event
2025-02-03 02:10:43.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:10:43.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:10:43.59: PodMonitor - start process kube event
2025-02-03 02:10:43.59: empty line received
2025-02-03 02:10:43.59: PodMonitor - start process kube event
2025-02-03 02:11:14.73: IngressMonitor - Received BOOKMARK: oldResVer=10965 newResVer=10965
2025-02-03 02:11:14.73: IngressMonitor - start process kube event
2025-02-03 02:11:14.73: empty line received
2025-02-03 02:11:14.73: IngressMonitor - start process kube event
2025-02-03 02:11:15.10: ServiceMonitor - Received BOOKMARK: oldResVer=10797 newResVer=10797
2025-02-03 02:11:15.10: ServiceMonitor - start process kube event
2025-02-03 02:11:15.10: empty line received
2025-02-03 02:11:15.10: ServiceMonitor - start process kube event
2025-02-03 02:11:15.22: PodMonitor - Received BOOKMARK: oldResVer=10763 newResVer=11086
2025-02-03 02:11:15.22: PodMonitor - start process kube event
2025-02-03 02:11:15.22: empty line received
2025-02-03 02:11:15.22: PodMonitor - start process kube event
2025-02-03 02:11:15.43: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-02-03 02:11:15.43: EndPointMonitor - start process kube event
2025-02-03 02:11:15.43: empty line received
2025-02-03 02:11:15.43: EndPointMonitor - start process kube event
2025-02-03 02:11:15.95: NamespaceMonitor - Received BOOKMARK: oldResVer=10351 newResVer=10351
2025-02-03 02:11:15.95: NamespaceMonitor - start process kube event
2025-02-03 02:11:15.95: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 02:11:15.95: empty line received
2025-02-03 02:11:15.95: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 02:11:15.95: VncKubernetes - vnc_sync - Namespace start
2025-02-03 02:11:15.95: VncKubernetes - vnc_sync - Namespace done
2025-02-03 02:11:15.95: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:11:15.95: NamespaceMonitor - start process kube event
2025-02-03 02:11:16.30: NetworkMonitor - Received BOOKMARK: oldResVer=10655 newResVer=10655
2025-02-03 02:11:16.30: NetworkMonitor - start process kube event
2025-02-03 02:11:16.30: empty line received
2025-02-03 02:11:16.30: NetworkMonitor - start process kube event
2025-02-03 02:11:18.03: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11006 newResVer=11006
2025-02-03 02:11:18.03: NetworkPolicyMonitor - start process kube event
2025-02-03 02:11:18.03: empty line received
2025-02-03 02:11:18.03: NetworkPolicyMonitor - start process kube event
2025-02-03 02:11:21.43: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:11:21.43: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:11:21.43: PodMonitor - start process kube event
2025-02-03 02:11:21.43: empty line received
2025-02-03 02:11:21.43: PodMonitor - start process kube event
2025-02-03 02:11:59.36: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:11:59.36: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:11:59.36: PodMonitor - start process kube event
2025-02-03 02:11:59.36: empty line received
2025-02-03 02:11:59.36: PodMonitor - start process kube event
2025-02-03 02:12:14.47: IngressMonitor - Received BOOKMARK: oldResVer=10965 newResVer=10965
2025-02-03 02:12:14.47: IngressMonitor - start process kube event
2025-02-03 02:12:14.47: empty line received
2025-02-03 02:12:14.47: IngressMonitor - start process kube event
2025-02-03 02:12:15.04: PodMonitor - Received BOOKMARK: oldResVer=11086 newResVer=11197
2025-02-03 02:12:15.04: PodMonitor - start process kube event
2025-02-03 02:12:15.04: empty line received
2025-02-03 02:12:15.04: PodMonitor - start process kube event
2025-02-03 02:12:15.25: ServiceMonitor - Received BOOKMARK: oldResVer=10797 newResVer=10797
2025-02-03 02:12:15.25: ServiceMonitor - start process kube event
2025-02-03 02:12:15.25: empty line received
2025-02-03 02:12:15.25: ServiceMonitor - start process kube event
2025-02-03 02:12:15.35: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-02-03 02:12:15.35: EndPointMonitor - start process kube event
2025-02-03 02:12:15.35: empty line received
2025-02-03 02:12:15.35: EndPointMonitor - start process kube event
2025-02-03 02:12:16.17: NamespaceMonitor - Received BOOKMARK: oldResVer=10351 newResVer=10351
2025-02-03 02:12:16.17: NamespaceMonitor - start process kube event
2025-02-03 02:12:16.17: empty line received
2025-02-03 02:12:16.17: NamespaceMonitor - start process kube event
2025-02-03 02:12:16.59: NetworkMonitor - Received BOOKMARK: oldResVer=10655 newResVer=10655
2025-02-03 02:12:16.59: NetworkMonitor - start process kube event
2025-02-03 02:12:16.59: empty line received
2025-02-03 02:12:16.59: NetworkMonitor - start process kube event
2025-02-03 02:12:17.38: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11006 newResVer=11006
2025-02-03 02:12:17.38: NetworkPolicyMonitor - start process kube event
2025-02-03 02:12:17.38: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 02:12:17.38: empty line received
2025-02-03 02:12:17.38: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 02:12:17.38: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 02:12:17.38: NetworkPolicyMonitor - start process kube event
2025-02-03 02:12:17.38: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 02:12:17.38: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:12:21.93: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:12:21.93: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:12:21.93: PodMonitor - start process kube event
2025-02-03 02:12:21.93: PodMonitor - _schedule_vnc_sync
2025-02-03 02:12:21.93: empty line received
2025-02-03 02:12:21.93: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 02:12:21.93: VncKubernetes - vnc_sync - Pod start
2025-02-03 02:12:21.93: VncKubernetes - vnc_sync - Pod done
2025-02-03 02:12:21.93: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:12:21.93: PodMonitor - start process kube event
2025-02-03 02:12:32.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:12:32.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:12:32.59: PodMonitor - start process kube event
2025-02-03 02:12:32.59: empty line received
2025-02-03 02:12:32.59: PodMonitor - start process kube event
2025-02-03 02:12:59.85: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:12:59.85: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:12:59.85: PodMonitor - start process kube event
2025-02-03 02:12:59.85: empty line received
2025-02-03 02:12:59.85: PodMonitor - start process kube event
2025-02-03 02:13:14.97: IngressMonitor - Received BOOKMARK: oldResVer=10965 newResVer=10965
2025-02-03 02:13:14.97: IngressMonitor - start process kube event
2025-02-03 02:13:14.97: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:13:14.97: empty line received
2025-02-03 02:13:14.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:13:14.97: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:13:14.97: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:13:14.97: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:13:14.97: IngressMonitor - start process kube event
2025-02-03 02:13:15.19: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-02-03 02:13:15.19: EndPointMonitor - start process kube event
2025-02-03 02:13:15.19: empty line received
2025-02-03 02:13:15.19: EndPointMonitor - start process kube event
2025-02-03 02:13:15.28: PodMonitor - Received BOOKMARK: oldResVer=11197 newResVer=11284
2025-02-03 02:13:15.28: PodMonitor - start process kube event
2025-02-03 02:13:15.28: empty line received
2025-02-03 02:13:15.28: PodMonitor - start process kube event
2025-02-03 02:13:15.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:13:15.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:13:15.59: PodMonitor - start process kube event
2025-02-03 02:13:15.59: empty line received
2025-02-03 02:13:15.59: PodMonitor - start process kube event
2025-02-03 02:13:15.79: ServiceMonitor - Received BOOKMARK: oldResVer=10797 newResVer=10797
2025-02-03 02:13:15.79: ServiceMonitor - start process kube event
2025-02-03 02:13:15.79: empty line received
2025-02-03 02:13:15.79: ServiceMonitor - start process kube event
2025-02-03 02:13:16.56: NetworkMonitor - Received BOOKMARK: oldResVer=10655 newResVer=10655
2025-02-03 02:13:16.56: NetworkMonitor - start process kube event
2025-02-03 02:13:16.56: NetworkMonitor - _schedule_vnc_sync
2025-02-03 02:13:16.56: empty line received
2025-02-03 02:13:16.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 02:13:16.56: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 02:13:16.56: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:13:16.56: NetworkMonitor - start process kube event
2025-02-03 02:13:16.74: NamespaceMonitor - Received BOOKMARK: oldResVer=10351 newResVer=11271
2025-02-03 02:13:16.74: NamespaceMonitor - start process kube event
2025-02-03 02:13:16.74: empty line received
2025-02-03 02:13:16.74: NamespaceMonitor - start process kube event
2025-02-03 02:13:18.34: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11006 newResVer=11006
2025-02-03 02:13:18.34: NetworkPolicyMonitor - start process kube event
2025-02-03 02:13:18.34: empty line received
2025-02-03 02:13:18.34: NetworkPolicyMonitor - start process kube event
2025-02-03 02:14:14.43: IngressMonitor - Received BOOKMARK: oldResVer=10965 newResVer=10965
2025-02-03 02:14:14.43: IngressMonitor - start process kube event
2025-02-03 02:14:14.43: empty line received
2025-02-03 02:14:14.43: IngressMonitor - start process kube event
2025-02-03 02:14:15.03: ServiceMonitor - Received BOOKMARK: oldResVer=10797 newResVer=10797
2025-02-03 02:14:15.03: ServiceMonitor - start process kube event
2025-02-03 02:14:15.03: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:14:15.03: empty line received
2025-02-03 02:14:15.03: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:14:15.03: VncKubernetes - vnc_sync - Service start
2025-02-03 02:14:15.03: VncKubernetes - vnc_sync - Service done
2025-02-03 02:14:15.03: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:14:15.03: ServiceMonitor - start process kube event
2025-02-03 02:14:15.80: PodMonitor - Received BOOKMARK: oldResVer=11284 newResVer=11309
2025-02-03 02:14:15.80: PodMonitor - start process kube event
2025-02-03 02:14:15.80: empty line received
2025-02-03 02:14:15.80: PodMonitor - start process kube event
2025-02-03 02:14:15.81: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-02-03 02:14:15.81: EndPointMonitor - start process kube event
2025-02-03 02:14:15.81: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:14:15.81: empty line received
2025-02-03 02:14:15.81: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:14:15.81: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:14:15.81: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:14:15.81: EndPointMonitor - start process kube event
2025-02-03 02:14:16.49: NamespaceMonitor - Received BOOKMARK: oldResVer=11271 newResVer=11271
2025-02-03 02:14:16.49: NamespaceMonitor - start process kube event
2025-02-03 02:14:16.49: empty line received
2025-02-03 02:14:16.49: NamespaceMonitor - start process kube event
2025-02-03 02:14:16.89: NetworkMonitor - Received BOOKMARK: oldResVer=10655 newResVer=10655
2025-02-03 02:14:16.89: NetworkMonitor - start process kube event
2025-02-03 02:14:16.89: empty line received
2025-02-03 02:14:16.89: NetworkMonitor - start process kube event
2025-02-03 02:14:18.70: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11006 newResVer=11006
2025-02-03 02:14:18.70: NetworkPolicyMonitor - start process kube event
2025-02-03 02:14:18.70: empty line received
2025-02-03 02:14:18.70: NetworkPolicyMonitor - start process kube event
2025-02-03 02:15:15.03: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-02-03 02:15:15.03: EndPointMonitor - start process kube event
2025-02-03 02:15:15.03: empty line received
2025-02-03 02:15:15.03: EndPointMonitor - start process kube event
2025-02-03 02:15:15.08: ServiceMonitor - Received BOOKMARK: oldResVer=10797 newResVer=10797
2025-02-03 02:15:15.08: ServiceMonitor - start process kube event
2025-02-03 02:15:15.08: empty line received
2025-02-03 02:15:15.08: ServiceMonitor - start process kube event
2025-02-03 02:15:15.09: PodMonitor - Received BOOKMARK: oldResVer=11309 newResVer=11309
2025-02-03 02:15:15.09: PodMonitor - start process kube event
2025-02-03 02:15:15.09: empty line received
2025-02-03 02:15:15.09: PodMonitor - start process kube event
2025-02-03 02:15:15.29: IngressMonitor - Received BOOKMARK: oldResVer=10965 newResVer=10965
2025-02-03 02:15:15.29: IngressMonitor - start process kube event
2025-02-03 02:15:15.29: empty line received
2025-02-03 02:15:15.29: IngressMonitor - start process kube event
2025-02-03 02:15:16.66: NetworkMonitor - Received BOOKMARK: oldResVer=10655 newResVer=10655
2025-02-03 02:15:16.66: NetworkMonitor - start process kube event
2025-02-03 02:15:16.66: empty line received
2025-02-03 02:15:16.66: NetworkMonitor - start process kube event
2025-02-03 02:15:16.74: NamespaceMonitor - Received BOOKMARK: oldResVer=11271 newResVer=11271
2025-02-03 02:15:16.74: NamespaceMonitor - start process kube event
2025-02-03 02:15:16.74: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 02:15:16.74: empty line received
2025-02-03 02:15:16.74: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 02:15:16.74: VncKubernetes - vnc_sync - Namespace start
2025-02-03 02:15:16.74: VncKubernetes - vnc_sync - Namespace done
2025-02-03 02:15:16.74: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:15:16.74: NamespaceMonitor - start process kube event
2025-02-03 02:15:18.84: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11006 newResVer=11006
2025-02-03 02:15:18.84: NetworkPolicyMonitor - start process kube event
2025-02-03 02:15:18.84: empty line received
2025-02-03 02:15:18.84: NetworkPolicyMonitor - start process kube event
2025-02-03 02:15:36.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:15:36.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:15:36.69: PodMonitor - start process kube event
2025-02-03 02:15:36.69: empty line received
2025-02-03 02:15:36.69: PodMonitor - start process kube event
2025-02-03 02:15:49.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:15:49.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:15:49.59: PodMonitor - start process kube event
2025-02-03 02:15:49.59: empty line received
2025-02-03 02:15:49.59: PodMonitor - start process kube event
2025-02-03 02:16:15.02: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-02-03 02:16:15.02: EndPointMonitor - start process kube event
2025-02-03 02:16:15.02: empty line received
2025-02-03 02:16:15.02: EndPointMonitor - start process kube event
2025-02-03 02:16:15.28: IngressMonitor - Received BOOKMARK: oldResVer=10965 newResVer=10965
2025-02-03 02:16:15.28: IngressMonitor - start process kube event
2025-02-03 02:16:15.28: empty line received
2025-02-03 02:16:15.28: IngressMonitor - start process kube event
2025-02-03 02:16:15.39: ServiceMonitor - Received BOOKMARK: oldResVer=10797 newResVer=10797
2025-02-03 02:16:15.39: ServiceMonitor - start process kube event
2025-02-03 02:16:15.39: empty line received
2025-02-03 02:16:15.39: ServiceMonitor - start process kube event
2025-02-03 02:16:15.69: PodMonitor - Received BOOKMARK: oldResVer=11309 newResVer=11527
2025-02-03 02:16:15.69: PodMonitor - start process kube event
2025-02-03 02:16:15.69: empty line received
2025-02-03 02:16:15.69: PodMonitor - start process kube event
2025-02-03 02:16:16.05: NamespaceMonitor - Received BOOKMARK: oldResVer=11271 newResVer=11271
2025-02-03 02:16:16.05: NamespaceMonitor - start process kube event
2025-02-03 02:16:16.05: empty line received
2025-02-03 02:16:16.05: NamespaceMonitor - start process kube event
2025-02-03 02:16:16.91: NetworkMonitor - Received BOOKMARK: oldResVer=10655 newResVer=10655
2025-02-03 02:16:16.91: NetworkMonitor - start process kube event
2025-02-03 02:16:16.91: empty line received
2025-02-03 02:16:16.91: NetworkMonitor - start process kube event
2025-02-03 02:16:18.72: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11006 newResVer=11006
2025-02-03 02:16:18.72: NetworkPolicyMonitor - start process kube event
2025-02-03 02:16:18.72: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 02:16:18.72: empty line received
2025-02-03 02:16:18.72: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 02:16:18.72: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 02:16:18.72: NetworkPolicyMonitor - start process kube event
2025-02-03 02:16:18.72: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 02:16:18.72: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:17:15.02: PodMonitor - Received BOOKMARK: oldResVer=11527 newResVer=11527
2025-02-03 02:17:15.02: PodMonitor - start process kube event
2025-02-03 02:17:15.02: PodMonitor - _schedule_vnc_sync
2025-02-03 02:17:15.02: empty line received
2025-02-03 02:17:15.02: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 02:17:15.02: VncKubernetes - vnc_sync - Pod start
2025-02-03 02:17:15.02: VncKubernetes - vnc_sync - Pod done
2025-02-03 02:17:15.02: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:17:15.02: PodMonitor - start process kube event
2025-02-03 02:17:15.21: ServiceMonitor - Received BOOKMARK: oldResVer=10797 newResVer=10797
2025-02-03 02:17:15.21: ServiceMonitor - start process kube event
2025-02-03 02:17:15.21: empty line received
2025-02-03 02:17:15.21: ServiceMonitor - start process kube event
2025-02-03 02:17:15.32: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-02-03 02:17:15.32: EndPointMonitor - start process kube event
2025-02-03 02:17:15.32: empty line received
2025-02-03 02:17:15.32: EndPointMonitor - start process kube event
2025-02-03 02:17:15.39: IngressMonitor - Received BOOKMARK: oldResVer=10965 newResVer=10965
2025-02-03 02:17:15.39: IngressMonitor - start process kube event
2025-02-03 02:17:15.39: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:17:15.39: empty line received
2025-02-03 02:17:15.39: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:17:15.39: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:17:15.39: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:17:15.39: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:17:15.39: IngressMonitor - start process kube event
2025-02-03 02:17:16.25: NamespaceMonitor - Received BOOKMARK: oldResVer=11271 newResVer=11271
2025-02-03 02:17:16.25: NamespaceMonitor - start process kube event
2025-02-03 02:17:16.25: empty line received
2025-02-03 02:17:16.25: NamespaceMonitor - start process kube event
2025-02-03 02:17:16.96: NetworkMonitor - Received BOOKMARK: oldResVer=10655 newResVer=11589
2025-02-03 02:17:16.96: NetworkMonitor - start process kube event
2025-02-03 02:17:16.96: NetworkMonitor - _schedule_vnc_sync
2025-02-03 02:17:16.96: empty line received
2025-02-03 02:17:16.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 02:17:16.96: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 02:17:16.96: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:17:16.96: NetworkMonitor - start process kube event
2025-02-03 02:17:18.27: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11006 newResVer=11006
2025-02-03 02:17:18.27: NetworkPolicyMonitor - start process kube event
2025-02-03 02:17:18.27: empty line received
2025-02-03 02:17:18.27: NetworkPolicyMonitor - start process kube event
2025-02-03 02:17:29.35: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:17:29.35: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:17:29.35: PodMonitor - start process kube event
2025-02-03 02:17:29.35: empty line received
2025-02-03 02:17:29.35: PodMonitor - start process kube event
2025-02-03 02:18:09.34: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:18:09.34: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:18:09.34: PodMonitor - start process kube event
2025-02-03 02:18:09.34: empty line received
2025-02-03 02:18:09.34: PodMonitor - start process kube event
2025-02-03 02:18:15.14: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-02-03 02:18:15.14: EndPointMonitor - start process kube event
2025-02-03 02:18:15.14: empty line received
2025-02-03 02:18:15.14: EndPointMonitor - start process kube event
2025-02-03 02:18:15.51: IngressMonitor - Received BOOKMARK: oldResVer=10965 newResVer=10965
2025-02-03 02:18:15.51: IngressMonitor - start process kube event
2025-02-03 02:18:15.51: empty line received
2025-02-03 02:18:15.51: IngressMonitor - start process kube event
2025-02-03 02:18:15.80: PodMonitor - Received BOOKMARK: oldResVer=11527 newResVer=11725
2025-02-03 02:18:15.80: PodMonitor - start process kube event
2025-02-03 02:18:15.80: empty line received
2025-02-03 02:18:15.80: PodMonitor - start process kube event
2025-02-03 02:18:15.99: ServiceMonitor - Received BOOKMARK: oldResVer=10797 newResVer=10797
2025-02-03 02:18:15.99: ServiceMonitor - start process kube event
2025-02-03 02:18:15.99: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:18:15.99: empty line received
2025-02-03 02:18:15.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:18:15.99: VncKubernetes - vnc_sync - Service start
2025-02-03 02:18:15.99: VncKubernetes - vnc_sync - Service done
2025-02-03 02:18:15.99: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:18:15.99: ServiceMonitor - start process kube event
2025-02-03 02:18:17.01: NamespaceMonitor - Received BOOKMARK: oldResVer=11271 newResVer=11271
2025-02-03 02:18:17.01: NamespaceMonitor - start process kube event
2025-02-03 02:18:17.01: empty line received
2025-02-03 02:18:17.01: NamespaceMonitor - start process kube event
2025-02-03 02:18:17.14: NetworkMonitor - Received BOOKMARK: oldResVer=11589 newResVer=11589
2025-02-03 02:18:17.14: NetworkMonitor - start process kube event
2025-02-03 02:18:17.14: empty line received
2025-02-03 02:18:17.14: NetworkMonitor - start process kube event
2025-02-03 02:18:19.23: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11006 newResVer=11006
2025-02-03 02:18:19.23: NetworkPolicyMonitor - start process kube event
2025-02-03 02:18:19.23: empty line received
2025-02-03 02:18:19.23: NetworkPolicyMonitor - start process kube event
2025-02-03 02:18:29.83: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:18:29.83: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:18:29.83: PodMonitor - start process kube event
2025-02-03 02:18:29.83: empty line received
2025-02-03 02:18:29.83: PodMonitor - start process kube event
2025-02-03 02:18:40.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:18:40.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:18:40.60: PodMonitor - start process kube event
2025-02-03 02:18:40.60: empty line received
2025-02-03 02:18:40.60: PodMonitor - start process kube event
2025-02-03 02:19:09.90: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:19:09.90: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:19:09.90: PodMonitor - start process kube event
2025-02-03 02:19:09.90: empty line received
2025-02-03 02:19:09.90: PodMonitor - start process kube event
2025-02-03 02:19:15.19: PodMonitor - Received BOOKMARK: oldResVer=11725 newResVer=11812
2025-02-03 02:19:15.19: PodMonitor - start process kube event
2025-02-03 02:19:15.19: empty line received
2025-02-03 02:19:15.19: PodMonitor - start process kube event
2025-02-03 02:19:15.19: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=11778
2025-02-03 02:19:15.19: EndPointMonitor - start process kube event
2025-02-03 02:19:15.19: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:19:15.19: empty line received
2025-02-03 02:19:15.19: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:19:15.19: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:19:15.19: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:19:15.19: EndPointMonitor - start process kube event
2025-02-03 02:19:15.20: ServiceMonitor - Received BOOKMARK: oldResVer=10797 newResVer=11738
2025-02-03 02:19:15.20: ServiceMonitor - start process kube event
2025-02-03 02:19:15.20: empty line received
2025-02-03 02:19:15.20: ServiceMonitor - start process kube event
2025-02-03 02:19:15.73: IngressMonitor - Received BOOKMARK: oldResVer=10965 newResVer=10965
2025-02-03 02:19:15.73: IngressMonitor - start process kube event
2025-02-03 02:19:15.73: empty line received
2025-02-03 02:19:15.73: IngressMonitor - start process kube event
2025-02-03 02:19:16.75: NetworkMonitor - Received BOOKMARK: oldResVer=11589 newResVer=11589
2025-02-03 02:19:16.75: NetworkMonitor - start process kube event
2025-02-03 02:19:16.75: empty line received
2025-02-03 02:19:16.75: NetworkMonitor - start process kube event
2025-02-03 02:19:17.81: NamespaceMonitor - Received BOOKMARK: oldResVer=11271 newResVer=11271
2025-02-03 02:19:17.81: NamespaceMonitor - start process kube event
2025-02-03 02:19:17.81: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 02:19:17.81: empty line received
2025-02-03 02:19:17.81: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 02:19:17.81: VncKubernetes - vnc_sync - Namespace start
2025-02-03 02:19:17.81: VncKubernetes - vnc_sync - Namespace done
2025-02-03 02:19:17.81: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:19:17.81: NamespaceMonitor - start process kube event
2025-02-03 02:19:19.52: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11006 newResVer=11006
2025-02-03 02:19:19.52: NetworkPolicyMonitor - start process kube event
2025-02-03 02:19:19.52: empty line received
2025-02-03 02:19:19.52: NetworkPolicyMonitor - start process kube event
2025-02-03 02:19:21.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:19:21.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:19:21.59: PodMonitor - start process kube event
2025-02-03 02:19:21.59: empty line received
2025-02-03 02:19:21.59: PodMonitor - start process kube event
2025-02-03 02:20:15.13: IngressMonitor - Received BOOKMARK: oldResVer=10965 newResVer=11835
2025-02-03 02:20:15.13: IngressMonitor - start process kube event
2025-02-03 02:20:15.13: empty line received
2025-02-03 02:20:15.13: IngressMonitor - start process kube event
2025-02-03 02:20:15.22: ServiceMonitor - Received BOOKMARK: oldResVer=11738 newResVer=11738
2025-02-03 02:20:15.22: ServiceMonitor - start process kube event
2025-02-03 02:20:15.22: empty line received
2025-02-03 02:20:15.22: ServiceMonitor - start process kube event
2025-02-03 02:20:15.61: PodMonitor - Received BOOKMARK: oldResVer=11812 newResVer=11830
2025-02-03 02:20:15.61: PodMonitor - start process kube event
2025-02-03 02:20:15.61: empty line received
2025-02-03 02:20:15.61: PodMonitor - start process kube event
2025-02-03 02:20:15.77: EndPointMonitor - Received BOOKMARK: oldResVer=11778 newResVer=11778
2025-02-03 02:20:15.77: EndPointMonitor - start process kube event
2025-02-03 02:20:15.77: empty line received
2025-02-03 02:20:15.77: EndPointMonitor - start process kube event
2025-02-03 02:20:16.97: NetworkMonitor - Received BOOKMARK: oldResVer=11589 newResVer=11589
2025-02-03 02:20:16.97: NetworkMonitor - start process kube event
2025-02-03 02:20:16.97: empty line received
2025-02-03 02:20:16.97: NetworkMonitor - start process kube event
2025-02-03 02:20:17.25: NamespaceMonitor - Received BOOKMARK: oldResVer=11271 newResVer=11271
2025-02-03 02:20:17.25: NamespaceMonitor - start process kube event
2025-02-03 02:20:17.25: empty line received
2025-02-03 02:20:17.25: NamespaceMonitor - start process kube event
2025-02-03 02:20:19.95: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11006 newResVer=11877
2025-02-03 02:20:19.95: NetworkPolicyMonitor - start process kube event
2025-02-03 02:20:19.95: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 02:20:19.95: empty line received
2025-02-03 02:20:19.95: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 02:20:19.95: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 02:20:19.95: NetworkPolicyMonitor - start process kube event
2025-02-03 02:20:19.95: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 02:20:19.95: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:20:45.62: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:20:45.62: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:20:45.62: PodMonitor - start process kube event
2025-02-03 02:20:45.62: empty line received
2025-02-03 02:20:45.62: PodMonitor - start process kube event
2025-02-03 02:20:57.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:20:57.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:20:57.59: PodMonitor - start process kube event
2025-02-03 02:20:57.59: empty line received
2025-02-03 02:20:57.59: PodMonitor - start process kube event
2025-02-03 02:21:15.11: ServiceMonitor - Received BOOKMARK: oldResVer=11738 newResVer=11738
2025-02-03 02:21:15.11: ServiceMonitor - start process kube event
2025-02-03 02:21:15.11: empty line received
2025-02-03 02:21:15.11: ServiceMonitor - start process kube event
2025-02-03 02:21:15.30: PodMonitor - Received BOOKMARK: oldResVer=11830 newResVer=11967
2025-02-03 02:21:15.30: PodMonitor - start process kube event
2025-02-03 02:21:15.30: PodMonitor - _schedule_vnc_sync
2025-02-03 02:21:15.30: empty line received
2025-02-03 02:21:15.30: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 02:21:15.30: VncKubernetes - vnc_sync - Pod start
2025-02-03 02:21:15.30: VncKubernetes - vnc_sync - Pod done
2025-02-03 02:21:15.30: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:21:15.30: PodMonitor - start process kube event
2025-02-03 02:21:15.35: EndPointMonitor - Received BOOKMARK: oldResVer=11778 newResVer=11778
2025-02-03 02:21:15.35: EndPointMonitor - start process kube event
2025-02-03 02:21:15.35: empty line received
2025-02-03 02:21:15.35: EndPointMonitor - start process kube event
2025-02-03 02:21:15.42: IngressMonitor - Received BOOKMARK: oldResVer=11835 newResVer=11835
2025-02-03 02:21:15.42: IngressMonitor - start process kube event
2025-02-03 02:21:15.42: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:21:15.42: empty line received
2025-02-03 02:21:15.42: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:21:15.42: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:21:15.42: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:21:15.42: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:21:15.42: IngressMonitor - start process kube event
2025-02-03 02:21:17.26: NetworkMonitor - Received BOOKMARK: oldResVer=11589 newResVer=11589
2025-02-03 02:21:17.26: NetworkMonitor - start process kube event
2025-02-03 02:21:17.26: NetworkMonitor - _schedule_vnc_sync
2025-02-03 02:21:17.26: empty line received
2025-02-03 02:21:17.26: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 02:21:17.26: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 02:21:17.26: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:21:17.26: NetworkMonitor - start process kube event
2025-02-03 02:21:17.52: NamespaceMonitor - Received BOOKMARK: oldResVer=11271 newResVer=11271
2025-02-03 02:21:17.52: NamespaceMonitor - start process kube event
2025-02-03 02:21:17.52: empty line received
2025-02-03 02:21:17.52: NamespaceMonitor - start process kube event
2025-02-03 02:21:19.42: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11877 newResVer=11877
2025-02-03 02:21:19.42: NetworkPolicyMonitor - start process kube event
2025-02-03 02:21:19.42: empty line received
2025-02-03 02:21:19.42: NetworkPolicyMonitor - start process kube event
2025-02-03 02:22:15.29: ServiceMonitor - Received BOOKMARK: oldResVer=11738 newResVer=11738
2025-02-03 02:22:15.30: ServiceMonitor - start process kube event
2025-02-03 02:22:15.30: empty line received
2025-02-03 02:22:15.30: ServiceMonitor - start process kube event
2025-02-03 02:22:15.52: PodMonitor - Received BOOKMARK: oldResVer=11967 newResVer=11967
2025-02-03 02:22:15.52: PodMonitor - start process kube event
2025-02-03 02:22:15.52: empty line received
2025-02-03 02:22:15.52: PodMonitor - start process kube event
2025-02-03 02:22:15.55: EndPointMonitor - Received BOOKMARK: oldResVer=11778 newResVer=11778
2025-02-03 02:22:15.55: EndPointMonitor - start process kube event
2025-02-03 02:22:15.55: empty line received
2025-02-03 02:22:15.55: EndPointMonitor - start process kube event
2025-02-03 02:22:15.65: IngressMonitor - Received BOOKMARK: oldResVer=11835 newResVer=11835
2025-02-03 02:22:15.65: IngressMonitor - start process kube event
2025-02-03 02:22:15.65: empty line received
2025-02-03 02:22:15.65: IngressMonitor - start process kube event
2025-02-03 02:22:16.80: NetworkMonitor - Received BOOKMARK: oldResVer=11589 newResVer=11589
2025-02-03 02:22:16.80: NetworkMonitor - start process kube event
2025-02-03 02:22:16.80: empty line received
2025-02-03 02:22:16.80: NetworkMonitor - start process kube event
2025-02-03 02:22:18.10: NamespaceMonitor - Received BOOKMARK: oldResVer=11271 newResVer=11271
2025-02-03 02:22:18.10: NamespaceMonitor - start process kube event
2025-02-03 02:22:18.10: empty line received
2025-02-03 02:22:18.10: NamespaceMonitor - start process kube event
2025-02-03 02:22:19.96: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11877 newResVer=11877
2025-02-03 02:22:19.96: NetworkPolicyMonitor - start process kube event
2025-02-03 02:22:19.96: empty line received
2025-02-03 02:22:19.96: NetworkPolicyMonitor - start process kube event
2025-02-03 02:23:15.35: PodMonitor - Received BOOKMARK: oldResVer=11967 newResVer=11967
2025-02-03 02:23:15.35: PodMonitor - start process kube event
2025-02-03 02:23:15.35: empty line received
2025-02-03 02:23:15.35: PodMonitor - start process kube event
2025-02-03 02:23:15.43: ServiceMonitor - Received BOOKMARK: oldResVer=11738 newResVer=11738
2025-02-03 02:23:15.43: ServiceMonitor - start process kube event
2025-02-03 02:23:15.43: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:23:15.43: empty line received
2025-02-03 02:23:15.43: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:23:15.43: VncKubernetes - vnc_sync - Service start
2025-02-03 02:23:15.44: VncKubernetes - vnc_sync - Service done
2025-02-03 02:23:15.44: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:23:15.44: ServiceMonitor - start process kube event
2025-02-03 02:23:15.81: EndPointMonitor - Received BOOKMARK: oldResVer=11778 newResVer=11778
2025-02-03 02:23:15.81: EndPointMonitor - start process kube event
2025-02-03 02:23:15.81: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:23:15.81: empty line received
2025-02-03 02:23:15.81: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:23:15.81: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:23:15.81: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:23:15.81: EndPointMonitor - start process kube event
2025-02-03 02:23:15.85: IngressMonitor - Received BOOKMARK: oldResVer=11835 newResVer=11835
2025-02-03 02:23:15.85: IngressMonitor - start process kube event
2025-02-03 02:23:15.85: empty line received
2025-02-03 02:23:15.85: IngressMonitor - start process kube event
2025-02-03 02:23:17.16: NetworkMonitor - Received BOOKMARK: oldResVer=11589 newResVer=11589
2025-02-03 02:23:17.16: NetworkMonitor - start process kube event
2025-02-03 02:23:17.16: empty line received
2025-02-03 02:23:17.16: NetworkMonitor - start process kube event
2025-02-03 02:23:18.57: NamespaceMonitor - Received BOOKMARK: oldResVer=11271 newResVer=12156
2025-02-03 02:23:18.57: NamespaceMonitor - start process kube event
2025-02-03 02:23:18.57: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 02:23:18.57: empty line received
2025-02-03 02:23:18.57: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 02:23:18.57: VncKubernetes - vnc_sync - Namespace start
2025-02-03 02:23:18.57: VncKubernetes - vnc_sync - Namespace done
2025-02-03 02:23:18.57: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:23:18.57: NamespaceMonitor - start process kube event
2025-02-03 02:23:19.11: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11877 newResVer=11877
2025-02-03 02:23:19.11: NetworkPolicyMonitor - start process kube event
2025-02-03 02:23:19.11: empty line received
2025-02-03 02:23:19.11: NetworkPolicyMonitor - start process kube event
2025-02-03 02:23:33.88: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:23:33.88: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:23:33.89: PodMonitor - start process kube event
2025-02-03 02:23:33.89: empty line received
2025-02-03 02:23:33.89: PodMonitor - start process kube event
2025-02-03 02:24:12.93: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:24:12.93: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:24:12.93: PodMonitor - start process kube event
2025-02-03 02:24:12.93: empty line received
2025-02-03 02:24:12.93: PodMonitor - start process kube event
2025-02-03 02:24:15.33: PodMonitor - Received BOOKMARK: oldResVer=11967 newResVer=12242
2025-02-03 02:24:15.33: PodMonitor - start process kube event
2025-02-03 02:24:15.33: empty line received
2025-02-03 02:24:15.33: PodMonitor - start process kube event
2025-02-03 02:24:15.50: IngressMonitor - Received BOOKMARK: oldResVer=11835 newResVer=11835
2025-02-03 02:24:15.50: IngressMonitor - start process kube event
2025-02-03 02:24:15.50: empty line received
2025-02-03 02:24:15.50: IngressMonitor - start process kube event
2025-02-03 02:24:15.68: EndPointMonitor - Received BOOKMARK: oldResVer=11778 newResVer=11778
2025-02-03 02:24:15.68: EndPointMonitor - start process kube event
2025-02-03 02:24:15.68: empty line received
2025-02-03 02:24:15.68: EndPointMonitor - start process kube event
2025-02-03 02:24:16.20: ServiceMonitor - Received BOOKMARK: oldResVer=11738 newResVer=11738
2025-02-03 02:24:16.20: ServiceMonitor - start process kube event
2025-02-03 02:24:16.20: empty line received
2025-02-03 02:24:16.20: ServiceMonitor - start process kube event
2025-02-03 02:24:16.60: NetworkMonitor - Received BOOKMARK: oldResVer=11589 newResVer=11589
2025-02-03 02:24:16.60: NetworkMonitor - start process kube event
2025-02-03 02:24:16.60: empty line received
2025-02-03 02:24:16.60: NetworkMonitor - start process kube event
2025-02-03 02:24:18.79: NamespaceMonitor - Received BOOKMARK: oldResVer=12156 newResVer=12156
2025-02-03 02:24:18.79: NamespaceMonitor - start process kube event
2025-02-03 02:24:18.79: empty line received
2025-02-03 02:24:18.79: NamespaceMonitor - start process kube event
2025-02-03 02:24:20.18: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11877 newResVer=11877
2025-02-03 02:24:20.18: NetworkPolicyMonitor - start process kube event
2025-02-03 02:24:20.18: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 02:24:20.18: empty line received
2025-02-03 02:24:20.18: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 02:24:20.18: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 02:24:20.18: NetworkPolicyMonitor - start process kube event
2025-02-03 02:24:20.18: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 02:24:20.18: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:24:34.53: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:24:34.53: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:24:34.53: PodMonitor - start process kube event
2025-02-03 02:24:34.53: empty line received
2025-02-03 02:24:34.53: PodMonitor - start process kube event
2025-02-03 02:24:46.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:24:46.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:24:46.59: PodMonitor - start process kube event
2025-02-03 02:24:46.59: empty line received
2025-02-03 02:24:46.59: PodMonitor - start process kube event
2025-02-03 02:25:13.56: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:25:13.56: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:25:13.56: PodMonitor - start process kube event
2025-02-03 02:25:13.56: empty line received
2025-02-03 02:25:13.56: PodMonitor - start process kube event
2025-02-03 02:25:15.54: PodMonitor - Received BOOKMARK: oldResVer=12242 newResVer=12330
2025-02-03 02:25:15.54: PodMonitor - start process kube event
2025-02-03 02:25:15.54: PodMonitor - _schedule_vnc_sync
2025-02-03 02:25:15.54: empty line received
2025-02-03 02:25:15.54: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 02:25:15.54: VncKubernetes - vnc_sync - Pod start
2025-02-03 02:25:15.54: VncKubernetes - vnc_sync - Pod done
2025-02-03 02:25:15.54: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:25:15.54: PodMonitor - start process kube event
2025-02-03 02:25:15.56: EndPointMonitor - Received BOOKMARK: oldResVer=11778 newResVer=11778
2025-02-03 02:25:15.56: EndPointMonitor - start process kube event
2025-02-03 02:25:15.56: empty line received
2025-02-03 02:25:15.56: EndPointMonitor - start process kube event
2025-02-03 02:25:15.57: IngressMonitor - Received BOOKMARK: oldResVer=11835 newResVer=11835
2025-02-03 02:25:15.57: IngressMonitor - start process kube event
2025-02-03 02:25:15.57: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:25:15.57: empty line received
2025-02-03 02:25:15.57: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:25:15.57: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:25:15.57: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:25:15.57: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:25:15.57: IngressMonitor - start process kube event
2025-02-03 02:25:16.68: NetworkMonitor - Received BOOKMARK: oldResVer=11589 newResVer=11589
2025-02-03 02:25:16.68: NetworkMonitor - start process kube event
2025-02-03 02:25:16.68: empty line received
2025-02-03 02:25:16.68: NetworkMonitor - start process kube event
2025-02-03 02:25:16.81: ServiceMonitor - Received BOOKMARK: oldResVer=11738 newResVer=11738
2025-02-03 02:25:16.81: ServiceMonitor - start process kube event
2025-02-03 02:25:16.81: empty line received
2025-02-03 02:25:16.81: ServiceMonitor - start process kube event
2025-02-03 02:25:18.38: NamespaceMonitor - Received BOOKMARK: oldResVer=12156 newResVer=12156
2025-02-03 02:25:18.38: NamespaceMonitor - start process kube event
2025-02-03 02:25:18.38: empty line received
2025-02-03 02:25:18.38: NamespaceMonitor - start process kube event
2025-02-03 02:25:20.27: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11877 newResVer=11877
2025-02-03 02:25:20.27: NetworkPolicyMonitor - start process kube event
2025-02-03 02:25:20.27: empty line received
2025-02-03 02:25:20.27: NetworkPolicyMonitor - start process kube event
2025-02-03 02:25:26.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:25:26.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:25:26.59: PodMonitor - start process kube event
2025-02-03 02:25:26.59: empty line received
2025-02-03 02:25:26.59: PodMonitor - start process kube event
2025-02-03 02:25:51.60: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:25:51.60: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:25:51.60: PodMonitor - start process kube event
2025-02-03 02:25:51.60: empty line received
2025-02-03 02:25:51.61: PodMonitor - start process kube event
2025-02-03 02:26:06.60: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:26:06.60: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:26:06.60: PodMonitor - start process kube event
2025-02-03 02:26:06.60: empty line received
2025-02-03 02:26:06.60: PodMonitor - start process kube event
2025-02-03 02:26:15.28: IngressMonitor - Received BOOKMARK: oldResVer=11835 newResVer=11835
2025-02-03 02:26:15.28: IngressMonitor - start process kube event
2025-02-03 02:26:15.28: empty line received
2025-02-03 02:26:15.28: IngressMonitor - start process kube event
2025-02-03 02:26:15.39: PodMonitor - Received BOOKMARK: oldResVer=12330 newResVer=12409
2025-02-03 02:26:15.39: PodMonitor - start process kube event
2025-02-03 02:26:15.39: empty line received
2025-02-03 02:26:15.39: PodMonitor - start process kube event
2025-02-03 02:26:15.65: EndPointMonitor - Received BOOKMARK: oldResVer=11778 newResVer=11778
2025-02-03 02:26:15.65: EndPointMonitor - start process kube event
2025-02-03 02:26:15.65: empty line received
2025-02-03 02:26:15.65: EndPointMonitor - start process kube event
2025-02-03 02:26:16.87: NetworkMonitor - Received BOOKMARK: oldResVer=11589 newResVer=11589
2025-02-03 02:26:16.87: NetworkMonitor - start process kube event
2025-02-03 02:26:16.88: NetworkMonitor - _schedule_vnc_sync
2025-02-03 02:26:16.88: empty line received
2025-02-03 02:26:16.88: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 02:26:16.88: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 02:26:16.88: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:26:16.88: NetworkMonitor - start process kube event
2025-02-03 02:26:16.91: ServiceMonitor - Received BOOKMARK: oldResVer=11738 newResVer=11738
2025-02-03 02:26:16.91: ServiceMonitor - start process kube event
2025-02-03 02:26:16.91: empty line received
2025-02-03 02:26:16.91: ServiceMonitor - start process kube event
2025-02-03 02:26:18.44: NamespaceMonitor - Received BOOKMARK: oldResVer=12156 newResVer=12156
2025-02-03 02:26:18.44: NamespaceMonitor - start process kube event
2025-02-03 02:26:18.44: empty line received
2025-02-03 02:26:18.44: NamespaceMonitor - start process kube event
2025-02-03 02:26:20.11: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11877 newResVer=11877
2025-02-03 02:26:20.11: NetworkPolicyMonitor - start process kube event
2025-02-03 02:26:20.11: empty line received
2025-02-03 02:26:20.11: NetworkPolicyMonitor - start process kube event
2025-02-03 02:27:15.23: IngressMonitor - Received BOOKMARK: oldResVer=11835 newResVer=11835
2025-02-03 02:27:15.23: IngressMonitor - start process kube event
2025-02-03 02:27:15.23: empty line received
2025-02-03 02:27:15.23: IngressMonitor - start process kube event
2025-02-03 02:27:15.37: PodMonitor - Received BOOKMARK: oldResVer=12409 newResVer=12409
2025-02-03 02:27:15.37: PodMonitor - start process kube event
2025-02-03 02:27:15.37: empty line received
2025-02-03 02:27:15.37: PodMonitor - start process kube event
2025-02-03 02:27:15.66: EndPointMonitor - Received BOOKMARK: oldResVer=11778 newResVer=11778
2025-02-03 02:27:15.66: EndPointMonitor - start process kube event
2025-02-03 02:27:15.66: empty line received
2025-02-03 02:27:15.66: EndPointMonitor - start process kube event
2025-02-03 02:27:16.80: ServiceMonitor - Received BOOKMARK: oldResVer=11738 newResVer=11738
2025-02-03 02:27:16.80: ServiceMonitor - start process kube event
2025-02-03 02:27:16.80: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:27:16.80: empty line received
2025-02-03 02:27:16.80: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:27:16.80: VncKubernetes - vnc_sync - Service start
2025-02-03 02:27:16.81: VncKubernetes - vnc_sync - Service done
2025-02-03 02:27:16.81: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:27:16.81: ServiceMonitor - start process kube event
2025-02-03 02:27:17.15: NetworkMonitor - Received BOOKMARK: oldResVer=11589 newResVer=12503
2025-02-03 02:27:17.15: NetworkMonitor - start process kube event
2025-02-03 02:27:17.15: empty line received
2025-02-03 02:27:17.15: NetworkMonitor - start process kube event
2025-02-03 02:27:18.55: NamespaceMonitor - Received BOOKMARK: oldResVer=12156 newResVer=12156
2025-02-03 02:27:18.55: NamespaceMonitor - start process kube event
2025-02-03 02:27:18.55: empty line received
2025-02-03 02:27:18.55: NamespaceMonitor - start process kube event
2025-02-03 02:27:20.65: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11877 newResVer=11877
2025-02-03 02:27:20.65: NetworkPolicyMonitor - start process kube event
2025-02-03 02:27:20.65: empty line received
2025-02-03 02:27:20.65: NetworkPolicyMonitor - start process kube event
2025-02-03 02:27:51.09: ServiceMonitor - Received BOOKMARK: oldResVer=11738 newResVer=11738
2025-02-03 02:27:51.09: ServiceMonitor - start process kube event
2025-02-03 02:27:51.09: empty line received
2025-02-03 02:27:51.09: ServiceMonitor - start process kube event
2025-02-03 02:27:52.12: ServiceMonitor - Received BOOKMARK: oldResVer=11738 newResVer=11738
2025-02-03 02:27:52.12: ServiceMonitor - start process kube event
2025-02-03 02:27:52.12: empty line received
2025-02-03 02:27:52.12: ServiceMonitor - start process kube event
2025-02-03 02:27:53.27: stop iteration ServiceMonitor
2025-02-03 02:27:53.27: ServiceMonitor - start process kube event
2025-02-03 02:27:53.27: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=11738
2025-02-03 02:27:53.27: ServiceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:27:53.27: ServiceMonitor - Connect Kube API result 0
2025-02-03 02:27:53.27: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:27:53.27: ServiceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '11738'})(timeout=120)
2025-02-03 02:27:53.28: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:27:53.28: VncKubernetes - vnc_sync - Service start
2025-02-03 02:27:53.28: VncKubernetes - vnc_sync - Service done
2025-02-03 02:27:53.28: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:27:53.28: ServiceMonitor - Watches https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '11738'})
2025-02-03 02:28:15.47: PodMonitor - Received BOOKMARK: oldResVer=12409 newResVer=12409
2025-02-03 02:28:15.47: PodMonitor - start process kube event
2025-02-03 02:28:15.47: empty line received
2025-02-03 02:28:15.47: PodMonitor - start process kube event
2025-02-03 02:28:15.72: IngressMonitor - Received BOOKMARK: oldResVer=11835 newResVer=11835
2025-02-03 02:28:15.72: IngressMonitor - start process kube event
2025-02-03 02:28:15.72: empty line received
2025-02-03 02:28:15.72: IngressMonitor - start process kube event
2025-02-03 02:28:16.03: EndPointMonitor - Received BOOKMARK: oldResVer=11778 newResVer=11778
2025-02-03 02:28:16.03: EndPointMonitor - start process kube event
2025-02-03 02:28:16.03: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:28:16.03: empty line received
2025-02-03 02:28:16.03: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:28:16.03: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:28:16.03: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:28:16.03: EndPointMonitor - start process kube event
2025-02-03 02:28:16.66: NetworkMonitor - Received BOOKMARK: oldResVer=12503 newResVer=12503
2025-02-03 02:28:16.66: NetworkMonitor - start process kube event
2025-02-03 02:28:16.66: empty line received
2025-02-03 02:28:16.66: NetworkMonitor - start process kube event
2025-02-03 02:28:18.90: NamespaceMonitor - Received BOOKMARK: oldResVer=12156 newResVer=12156
2025-02-03 02:28:18.90: NamespaceMonitor - start process kube event
2025-02-03 02:28:18.90: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 02:28:18.90: empty line received
2025-02-03 02:28:18.90: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 02:28:18.90: VncKubernetes - vnc_sync - Namespace start
2025-02-03 02:28:18.90: VncKubernetes - vnc_sync - Namespace done
2025-02-03 02:28:18.90: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:28:18.90: NamespaceMonitor - start process kube event
2025-02-03 02:28:20.39: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11877 newResVer=11877
2025-02-03 02:28:20.39: NetworkPolicyMonitor - start process kube event
2025-02-03 02:28:20.39: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 02:28:20.39: empty line received
2025-02-03 02:28:20.39: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 02:28:20.39: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 02:28:20.39: NetworkPolicyMonitor - start process kube event
2025-02-03 02:28:20.40: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 02:28:20.40: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:29:15.20: IngressMonitor - Received BOOKMARK: oldResVer=11835 newResVer=11835
2025-02-03 02:29:15.20: IngressMonitor - start process kube event
2025-02-03 02:29:15.20: empty line received
2025-02-03 02:29:15.20: IngressMonitor - start process kube event
2025-02-03 02:29:15.41: PodMonitor - Received BOOKMARK: oldResVer=12409 newResVer=12409
2025-02-03 02:29:15.41: PodMonitor - start process kube event
2025-02-03 02:29:15.41: empty line received
2025-02-03 02:29:15.41: PodMonitor - start process kube event
2025-02-03 02:29:16.76: EndPointMonitor - Received BOOKMARK: oldResVer=11778 newResVer=11778
2025-02-03 02:29:16.76: EndPointMonitor - start process kube event
2025-02-03 02:29:16.76: empty line received
2025-02-03 02:29:16.76: EndPointMonitor - start process kube event
2025-02-03 02:29:17.54: NetworkMonitor - Received BOOKMARK: oldResVer=12503 newResVer=12503
2025-02-03 02:29:17.54: NetworkMonitor - start process kube event
2025-02-03 02:29:17.54: empty line received
2025-02-03 02:29:17.54: NetworkMonitor - start process kube event
2025-02-03 02:29:18.29: NamespaceMonitor - Received BOOKMARK: oldResVer=12156 newResVer=12156
2025-02-03 02:29:18.29: NamespaceMonitor - start process kube event
2025-02-03 02:29:18.29: empty line received
2025-02-03 02:29:18.29: NamespaceMonitor - start process kube event
2025-02-03 02:29:20.51: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11877 newResVer=11877
2025-02-03 02:29:20.51: NetworkPolicyMonitor - start process kube event
2025-02-03 02:29:20.51: empty line received
2025-02-03 02:29:20.51: NetworkPolicyMonitor - start process kube event
2025-02-03 02:29:36.25: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:29:36.25: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:29:36.25: PodMonitor - start process kube event
2025-02-03 02:29:36.25: PodMonitor - _schedule_vnc_sync
2025-02-03 02:29:36.25: empty line received
2025-02-03 02:29:36.25: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 02:29:36.25: VncKubernetes - vnc_sync - Pod start
2025-02-03 02:29:36.25: VncKubernetes - vnc_sync - Pod done
2025-02-03 02:29:36.25: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:29:36.25: PodMonitor - start process kube event
2025-02-03 02:29:53.28: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 02:29:53.29: ServiceMonitor - start process kube event
2025-02-03 02:29:53.29: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=11738
2025-02-03 02:29:53.29: ServiceMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:29:53.29: ServiceMonitor - Connect Kube API result 0
2025-02-03 02:29:53.29: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:29:53.29: ServiceMonitor - Start Watching request https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '11738'})(timeout=120)
2025-02-03 02:29:53.29: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:29:53.29: VncKubernetes - vnc_sync - Service start
2025-02-03 02:29:53.29: VncKubernetes - vnc_sync - Service done
2025-02-03 02:29:53.29: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:29:53.31: ServiceMonitor - Watches https://10.0.0.40:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '11738'})
2025-02-03 02:30:15.51: PodMonitor - Received BOOKMARK: oldResVer=12409 newResVer=12703
2025-02-03 02:30:15.51: PodMonitor - start process kube event
2025-02-03 02:30:15.51: empty line received
2025-02-03 02:30:15.51: PodMonitor - start process kube event
2025-02-03 02:30:15.93: IngressMonitor - Received BOOKMARK: oldResVer=11835 newResVer=12690
2025-02-03 02:30:15.93: IngressMonitor - start process kube event
2025-02-03 02:30:15.93: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:30:15.93: empty line received
2025-02-03 02:30:15.93: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:30:15.93: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:30:15.93: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:30:15.93: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:30:15.93: IngressMonitor - start process kube event
2025-02-03 02:30:16.30: EndPointMonitor - Received BOOKMARK: oldResVer=11778 newResVer=12702
2025-02-03 02:30:16.30: EndPointMonitor - start process kube event
2025-02-03 02:30:16.30: empty line received
2025-02-03 02:30:16.30: EndPointMonitor - start process kube event
2025-02-03 02:30:18.34: NetworkMonitor - Received BOOKMARK: oldResVer=12503 newResVer=12503
2025-02-03 02:30:18.34: NetworkMonitor - start process kube event
2025-02-03 02:30:18.34: NetworkMonitor - _schedule_vnc_sync
2025-02-03 02:30:18.34: empty line received
2025-02-03 02:30:18.34: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 02:30:18.34: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 02:30:18.34: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:30:18.34: NetworkMonitor - start process kube event
2025-02-03 02:30:18.68: NamespaceMonitor - Received BOOKMARK: oldResVer=12156 newResVer=12156
2025-02-03 02:30:18.68: NamespaceMonitor - start process kube event
2025-02-03 02:30:18.68: empty line received
2025-02-03 02:30:18.68: NamespaceMonitor - start process kube event
2025-02-03 02:30:20.74: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11877 newResVer=12739
2025-02-03 02:30:20.74: NetworkPolicyMonitor - start process kube event
2025-02-03 02:30:20.74: empty line received
2025-02-03 02:30:20.74: NetworkPolicyMonitor - start process kube event
2025-02-03 02:30:24.61: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:30:24.61: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:30:24.61: PodMonitor - start process kube event
2025-02-03 02:30:24.61: empty line received
2025-02-03 02:30:24.61: PodMonitor - start process kube event
2025-02-03 02:30:36.92: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:30:36.92: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:30:36.92: PodMonitor - start process kube event
2025-02-03 02:30:36.92: empty line received
2025-02-03 02:30:36.92: PodMonitor - start process kube event
2025-02-03 02:30:48.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:30:48.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:30:48.59: PodMonitor - start process kube event
2025-02-03 02:30:48.59: empty line received
2025-02-03 02:30:48.59: PodMonitor - start process kube event
2025-02-03 02:30:54.03: ServiceMonitor - Received BOOKMARK: oldResVer=11738 newResVer=12661
2025-02-03 02:30:54.03: ServiceMonitor - start process kube event
2025-02-03 02:30:54.03: empty line received
2025-02-03 02:30:54.03: ServiceMonitor - start process kube event
2025-02-03 02:31:01.67: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:31:01.67: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:31:01.67: PodMonitor - start process kube event
2025-02-03 02:31:01.67: empty line received
2025-02-03 02:31:01.67: PodMonitor - start process kube event
2025-02-03 02:31:15.58: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:31:15.58: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:31:15.59: PodMonitor - start process kube event
2025-02-03 02:31:15.59: empty line received
2025-02-03 02:31:15.59: PodMonitor - start process kube event
2025-02-03 02:31:15.94: PodMonitor - Received BOOKMARK: oldResVer=12703 newResVer=12849
2025-02-03 02:31:15.94: PodMonitor - start process kube event
2025-02-03 02:31:15.94: empty line received
2025-02-03 02:31:15.94: PodMonitor - start process kube event
2025-02-03 02:31:16.05: IngressMonitor - Received BOOKMARK: oldResVer=12690 newResVer=12690
2025-02-03 02:31:16.05: IngressMonitor - start process kube event
2025-02-03 02:31:16.05: empty line received
2025-02-03 02:31:16.05: IngressMonitor - start process kube event
2025-02-03 02:31:16.50: EndPointMonitor - Received BOOKMARK: oldResVer=12702 newResVer=12702
2025-02-03 02:31:16.50: EndPointMonitor - start process kube event
2025-02-03 02:31:16.50: empty line received
2025-02-03 02:31:16.50: EndPointMonitor - start process kube event
2025-02-03 02:31:17.61: NetworkMonitor - Received BOOKMARK: oldResVer=12503 newResVer=12503
2025-02-03 02:31:17.61: NetworkMonitor - start process kube event
2025-02-03 02:31:17.62: empty line received
2025-02-03 02:31:17.62: NetworkMonitor - start process kube event
2025-02-03 02:31:17.97: NamespaceMonitor - Received BOOKMARK: oldResVer=12156 newResVer=12156
2025-02-03 02:31:17.97: NamespaceMonitor - start process kube event
2025-02-03 02:31:17.97: empty line received
2025-02-03 02:31:17.97: NamespaceMonitor - start process kube event
2025-02-03 02:31:21.17: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12739 newResVer=12739
2025-02-03 02:31:21.17: NetworkPolicyMonitor - start process kube event
2025-02-03 02:31:21.17: empty line received
2025-02-03 02:31:21.17: NetworkPolicyMonitor - start process kube event
2025-02-03 02:31:24.28: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:31:24.28: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:31:24.28: PodMonitor - start process kube event
2025-02-03 02:31:24.28: empty line received
2025-02-03 02:31:24.28: PodMonitor - start process kube event
2025-02-03 02:31:29.18: IngressMonitor - Received BOOKMARK: oldResVer=12690 newResVer=12690
2025-02-03 02:31:29.18: IngressMonitor - start process kube event
2025-02-03 02:31:29.18: empty line received
2025-02-03 02:31:29.18: IngressMonitor - start process kube event
2025-02-03 02:31:30.29: IngressMonitor - Received BOOKMARK: oldResVer=12690 newResVer=12690
2025-02-03 02:31:30.29: IngressMonitor - start process kube event
2025-02-03 02:31:30.29: empty line received
2025-02-03 02:31:30.29: IngressMonitor - start process kube event
2025-02-03 02:31:31.73: stop iteration IngressMonitor
2025-02-03 02:31:31.73: IngressMonitor - start process kube event
2025-02-03 02:31:31.73: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12690
2025-02-03 02:31:31.73: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:31:31.73: IngressMonitor - Connect Kube API result 0
2025-02-03 02:31:31.73: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:31:31.73: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12690'})(timeout=120)
2025-02-03 02:31:31.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:31:31.73: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:31:31.73: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:31:31.73: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:31:31.74: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12690'})
2025-02-03 02:31:35.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:31:35.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:31:35.59: PodMonitor - start process kube event
2025-02-03 02:31:35.59: empty line received
2025-02-03 02:31:35.59: PodMonitor - start process kube event
2025-02-03 02:31:54.75: ServiceMonitor - Received BOOKMARK: oldResVer=12661 newResVer=12661
2025-02-03 02:31:54.75: ServiceMonitor - start process kube event
2025-02-03 02:31:54.75: empty line received
2025-02-03 02:31:54.75: ServiceMonitor - start process kube event
2025-02-03 02:32:16.05: PodMonitor - Received BOOKMARK: oldResVer=12849 newResVer=12878
2025-02-03 02:32:16.05: PodMonitor - start process kube event
2025-02-03 02:32:16.05: empty line received
2025-02-03 02:32:16.05: PodMonitor - start process kube event
2025-02-03 02:32:16.07: EndPointMonitor - Received BOOKMARK: oldResVer=12702 newResVer=12702
2025-02-03 02:32:16.07: EndPointMonitor - start process kube event
2025-02-03 02:32:16.07: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:32:16.07: empty line received
2025-02-03 02:32:16.07: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:32:16.07: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:32:16.07: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:32:16.07: EndPointMonitor - start process kube event
2025-02-03 02:32:17.89: NetworkMonitor - Received BOOKMARK: oldResVer=12503 newResVer=12503
2025-02-03 02:32:17.89: NetworkMonitor - start process kube event
2025-02-03 02:32:17.89: empty line received
2025-02-03 02:32:17.89: NetworkMonitor - start process kube event
2025-02-03 02:32:18.46: NamespaceMonitor - Received BOOKMARK: oldResVer=12156 newResVer=12156
2025-02-03 02:32:18.46: NamespaceMonitor - start process kube event
2025-02-03 02:32:18.46: empty line received
2025-02-03 02:32:18.46: NamespaceMonitor - start process kube event
2025-02-03 02:32:21.60: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12739 newResVer=12739
2025-02-03 02:32:21.60: NetworkPolicyMonitor - start process kube event
2025-02-03 02:32:21.60: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 02:32:21.60: empty line received
2025-02-03 02:32:21.60: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 02:32:21.60: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 02:32:21.60: NetworkPolicyMonitor - start process kube event
2025-02-03 02:32:21.60: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 02:32:21.60: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:32:54.53: ServiceMonitor - Received BOOKMARK: oldResVer=12661 newResVer=12661
2025-02-03 02:32:54.53: ServiceMonitor - start process kube event
2025-02-03 02:32:54.53: empty line received
2025-02-03 02:32:54.53: ServiceMonitor - start process kube event
2025-02-03 02:33:16.08: EndPointMonitor - Received BOOKMARK: oldResVer=12702 newResVer=12702
2025-02-03 02:33:16.08: EndPointMonitor - start process kube event
2025-02-03 02:33:16.08: empty line received
2025-02-03 02:33:16.08: EndPointMonitor - start process kube event
2025-02-03 02:33:16.70: PodMonitor - Received BOOKMARK: oldResVer=12878 newResVer=12878
2025-02-03 02:33:16.70: PodMonitor - start process kube event
2025-02-03 02:33:16.70: empty line received
2025-02-03 02:33:16.70: PodMonitor - start process kube event
2025-02-03 02:33:17.95: NetworkMonitor - Received BOOKMARK: oldResVer=12503 newResVer=12503
2025-02-03 02:33:17.95: NetworkMonitor - start process kube event
2025-02-03 02:33:17.95: empty line received
2025-02-03 02:33:17.95: NetworkMonitor - start process kube event
2025-02-03 02:33:18.61: NamespaceMonitor - Received BOOKMARK: oldResVer=12156 newResVer=12156
2025-02-03 02:33:18.61: NamespaceMonitor - start process kube event
2025-02-03 02:33:18.61: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 02:33:18.61: empty line received
2025-02-03 02:33:18.61: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 02:33:18.61: VncKubernetes - vnc_sync - Namespace start
2025-02-03 02:33:18.61: VncKubernetes - vnc_sync - Namespace done
2025-02-03 02:33:18.61: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:33:18.61: NamespaceMonitor - start process kube event
2025-02-03 02:33:21.95: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12739 newResVer=12739
2025-02-03 02:33:21.95: NetworkPolicyMonitor - start process kube event
2025-02-03 02:33:21.95: empty line received
2025-02-03 02:33:21.95: NetworkPolicyMonitor - start process kube event
2025-02-03 02:33:31.74: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 02:33:31.74: IngressMonitor - start process kube event
2025-02-03 02:33:31.74: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12690
2025-02-03 02:33:31.74: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:33:31.74: IngressMonitor - Connect Kube API result 0
2025-02-03 02:33:31.74: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:33:31.74: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12690'})(timeout=120)
2025-02-03 02:33:31.74: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:33:31.74: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:33:31.74: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:33:31.74: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:33:31.75: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12690'})
2025-02-03 02:33:55.06: ServiceMonitor - Received BOOKMARK: oldResVer=12661 newResVer=12661
2025-02-03 02:33:55.06: ServiceMonitor - start process kube event
2025-02-03 02:33:55.06: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:33:55.06: empty line received
2025-02-03 02:33:55.06: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:33:55.06: VncKubernetes - vnc_sync - Service start
2025-02-03 02:33:55.06: VncKubernetes - vnc_sync - Service done
2025-02-03 02:33:55.06: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:33:55.06: ServiceMonitor - start process kube event
2025-02-03 02:34:16.97: PodMonitor - Received BOOKMARK: oldResVer=12878 newResVer=12878
2025-02-03 02:34:16.97: PodMonitor - start process kube event
2025-02-03 02:34:16.97: PodMonitor - _schedule_vnc_sync
2025-02-03 02:34:16.97: empty line received
2025-02-03 02:34:16.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 02:34:16.97: VncKubernetes - vnc_sync - Pod start
2025-02-03 02:34:16.97: VncKubernetes - vnc_sync - Pod done
2025-02-03 02:34:16.97: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:34:16.97: PodMonitor - start process kube event
2025-02-03 02:34:17.01: EndPointMonitor - Received BOOKMARK: oldResVer=12702 newResVer=12702
2025-02-03 02:34:17.01: EndPointMonitor - start process kube event
2025-02-03 02:34:17.01: empty line received
2025-02-03 02:34:17.01: EndPointMonitor - start process kube event
2025-02-03 02:34:17.75: NetworkMonitor - Received BOOKMARK: oldResVer=12503 newResVer=12503
2025-02-03 02:34:17.75: NetworkMonitor - start process kube event
2025-02-03 02:34:17.75: empty line received
2025-02-03 02:34:17.75: NetworkMonitor - start process kube event
2025-02-03 02:34:18.37: NamespaceMonitor - Received BOOKMARK: oldResVer=12156 newResVer=13042
2025-02-03 02:34:18.37: NamespaceMonitor - start process kube event
2025-02-03 02:34:18.37: empty line received
2025-02-03 02:34:18.37: NamespaceMonitor - start process kube event
2025-02-03 02:34:21.82: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12739 newResVer=12739
2025-02-03 02:34:21.82: NetworkPolicyMonitor - start process kube event
2025-02-03 02:34:21.82: empty line received
2025-02-03 02:34:21.82: NetworkPolicyMonitor - start process kube event
2025-02-03 02:34:55.32: ServiceMonitor - Received BOOKMARK: oldResVer=12661 newResVer=12661
2025-02-03 02:34:55.32: ServiceMonitor - start process kube event
2025-02-03 02:34:55.32: empty line received
2025-02-03 02:34:55.32: ServiceMonitor - start process kube event
2025-02-03 02:35:16.97: PodMonitor - Received BOOKMARK: oldResVer=12878 newResVer=12878
2025-02-03 02:35:16.97: PodMonitor - start process kube event
2025-02-03 02:35:16.97: empty line received
2025-02-03 02:35:16.97: PodMonitor - start process kube event
2025-02-03 02:35:17.77: EndPointMonitor - Received BOOKMARK: oldResVer=12702 newResVer=12702
2025-02-03 02:35:17.77: EndPointMonitor - start process kube event
2025-02-03 02:35:17.77: empty line received
2025-02-03 02:35:17.77: EndPointMonitor - start process kube event
2025-02-03 02:35:18.46: NetworkMonitor - Received BOOKMARK: oldResVer=12503 newResVer=12503
2025-02-03 02:35:18.46: NetworkMonitor - start process kube event
2025-02-03 02:35:18.46: NetworkMonitor - _schedule_vnc_sync
2025-02-03 02:35:18.46: empty line received
2025-02-03 02:35:18.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 02:35:18.46: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 02:35:18.46: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:35:18.46: NetworkMonitor - start process kube event
2025-02-03 02:35:18.46: NamespaceMonitor - Received BOOKMARK: oldResVer=13042 newResVer=13042
2025-02-03 02:35:18.46: NamespaceMonitor - start process kube event
2025-02-03 02:35:18.46: empty line received
2025-02-03 02:35:18.46: NamespaceMonitor - start process kube event
2025-02-03 02:35:21.80: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12739 newResVer=12739
2025-02-03 02:35:21.80: NetworkPolicyMonitor - start process kube event
2025-02-03 02:35:21.80: empty line received
2025-02-03 02:35:21.80: NetworkPolicyMonitor - start process kube event
2025-02-03 02:35:31.75: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 02:35:31.75: IngressMonitor - start process kube event
2025-02-03 02:35:31.75: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12690
2025-02-03 02:35:31.75: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:35:31.75: IngressMonitor - Connect Kube API result 0
2025-02-03 02:35:31.75: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:35:31.75: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12690'})(timeout=120)
2025-02-03 02:35:31.75: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:35:31.75: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:35:31.75: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:35:31.75: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:35:31.76: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12690'})
2025-02-03 02:35:37.83: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:35:37.83: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:35:37.83: PodMonitor - start process kube event
2025-02-03 02:35:37.83: empty line received
2025-02-03 02:35:37.83: PodMonitor - start process kube event
2025-02-03 02:35:55.12: ServiceMonitor - Received BOOKMARK: oldResVer=12661 newResVer=12661
2025-02-03 02:35:55.12: ServiceMonitor - start process kube event
2025-02-03 02:35:55.12: empty line received
2025-02-03 02:35:55.12: ServiceMonitor - start process kube event
2025-02-03 02:36:02.57: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:36:02.57: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:36:02.57: PodMonitor - start process kube event
2025-02-03 02:36:02.57: empty line received
2025-02-03 02:36:02.57: PodMonitor - start process kube event
2025-02-03 02:36:15.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:36:15.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:36:15.59: PodMonitor - start process kube event
2025-02-03 02:36:15.59: empty line received
2025-02-03 02:36:15.59: PodMonitor - start process kube event
2025-02-03 02:36:16.01: PodMonitor - Received BOOKMARK: oldResVer=12878 newResVer=13274
2025-02-03 02:36:16.01: PodMonitor - start process kube event
2025-02-03 02:36:16.01: empty line received
2025-02-03 02:36:16.01: PodMonitor - start process kube event
2025-02-03 02:36:17.50: EndPointMonitor - Received BOOKMARK: oldResVer=12702 newResVer=12702
2025-02-03 02:36:17.50: EndPointMonitor - start process kube event
2025-02-03 02:36:17.50: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:36:17.50: empty line received
2025-02-03 02:36:17.50: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:36:17.50: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:36:17.50: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:36:17.50: EndPointMonitor - start process kube event
2025-02-03 02:36:18.99: NamespaceMonitor - Received BOOKMARK: oldResVer=13042 newResVer=13042
2025-02-03 02:36:18.99: NamespaceMonitor - start process kube event
2025-02-03 02:36:18.99: empty line received
2025-02-03 02:36:18.99: NamespaceMonitor - start process kube event
2025-02-03 02:36:19.24: NetworkMonitor - Received BOOKMARK: oldResVer=12503 newResVer=12503
2025-02-03 02:36:19.24: NetworkMonitor - start process kube event
2025-02-03 02:36:19.24: empty line received
2025-02-03 02:36:19.24: NetworkMonitor - start process kube event
2025-02-03 02:36:22.13: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12739 newResVer=12739
2025-02-03 02:36:22.13: NetworkPolicyMonitor - start process kube event
2025-02-03 02:36:22.13: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 02:36:22.13: empty line received
2025-02-03 02:36:22.13: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 02:36:22.13: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 02:36:22.13: NetworkPolicyMonitor - start process kube event
2025-02-03 02:36:22.13: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 02:36:22.13: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:36:29.29: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:36:29.29: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:36:29.29: PodMonitor - start process kube event
2025-02-03 02:36:29.29: empty line received
2025-02-03 02:36:29.29: PodMonitor - start process kube event
2025-02-03 02:36:38.52: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:36:38.52: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:36:38.52: PodMonitor - start process kube event
2025-02-03 02:36:38.52: empty line received
2025-02-03 02:36:38.52: PodMonitor - start process kube event
2025-02-03 02:36:50.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:36:50.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:36:50.59: PodMonitor - start process kube event
2025-02-03 02:36:50.59: empty line received
2025-02-03 02:36:50.59: PodMonitor - start process kube event
2025-02-03 02:36:55.11: ServiceMonitor - Received BOOKMARK: oldResVer=12661 newResVer=12661
2025-02-03 02:36:55.11: ServiceMonitor - start process kube event
2025-02-03 02:36:55.11: empty line received
2025-02-03 02:36:55.11: ServiceMonitor - start process kube event
2025-02-03 02:37:16.93: PodMonitor - Received BOOKMARK: oldResVer=13274 newResVer=13325
2025-02-03 02:37:16.93: PodMonitor - start process kube event
2025-02-03 02:37:16.93: empty line received
2025-02-03 02:37:16.93: PodMonitor - start process kube event
2025-02-03 02:37:17.15: EndPointMonitor - Received BOOKMARK: oldResVer=12702 newResVer=12702
2025-02-03 02:37:17.16: EndPointMonitor - start process kube event
2025-02-03 02:37:17.16: empty line received
2025-02-03 02:37:17.16: EndPointMonitor - start process kube event
2025-02-03 02:37:19.37: NetworkMonitor - Received BOOKMARK: oldResVer=12503 newResVer=12503
2025-02-03 02:37:19.37: NetworkMonitor - start process kube event
2025-02-03 02:37:19.37: empty line received
2025-02-03 02:37:19.37: NetworkMonitor - start process kube event
2025-02-03 02:37:20.00: NamespaceMonitor - Received BOOKMARK: oldResVer=13042 newResVer=13042
2025-02-03 02:37:20.00: NamespaceMonitor - start process kube event
2025-02-03 02:37:20.00: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 02:37:20.00: empty line received
2025-02-03 02:37:20.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 02:37:20.00: VncKubernetes - vnc_sync - Namespace start
2025-02-03 02:37:20.00: VncKubernetes - vnc_sync - Namespace done
2025-02-03 02:37:20.00: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:37:20.00: NamespaceMonitor - start process kube event
2025-02-03 02:37:22.18: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12739 newResVer=12739
2025-02-03 02:37:22.18: NetworkPolicyMonitor - start process kube event
2025-02-03 02:37:22.18: empty line received
2025-02-03 02:37:22.18: NetworkPolicyMonitor - start process kube event
2025-02-03 02:37:29.87: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:37:29.87: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:37:29.87: PodMonitor - start process kube event
2025-02-03 02:37:29.87: empty line received
2025-02-03 02:37:29.87: PodMonitor - start process kube event
2025-02-03 02:37:31.76: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 02:37:31.76: IngressMonitor - start process kube event
2025-02-03 02:37:31.76: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12690
2025-02-03 02:37:31.76: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:37:31.76: IngressMonitor - Connect Kube API result 0
2025-02-03 02:37:31.76: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:37:31.76: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12690'})(timeout=120)
2025-02-03 02:37:31.76: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:37:31.77: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:37:31.77: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:37:31.77: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:37:31.77: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12690'})
2025-02-03 02:37:43.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:37:43.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:37:43.59: PodMonitor - start process kube event
2025-02-03 02:37:43.59: empty line received
2025-02-03 02:37:43.59: PodMonitor - start process kube event
2025-02-03 02:37:55.83: ServiceMonitor - Received BOOKMARK: oldResVer=12661 newResVer=12661
2025-02-03 02:37:55.83: ServiceMonitor - start process kube event
2025-02-03 02:37:55.83: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:37:55.83: empty line received
2025-02-03 02:37:55.83: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:37:55.83: VncKubernetes - vnc_sync - Service start
2025-02-03 02:37:55.83: VncKubernetes - vnc_sync - Service done
2025-02-03 02:37:55.83: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:37:55.83: ServiceMonitor - start process kube event
2025-02-03 02:38:16.46: PodMonitor - Received BOOKMARK: oldResVer=13325 newResVer=13402
2025-02-03 02:38:16.46: PodMonitor - start process kube event
2025-02-03 02:38:16.46: empty line received
2025-02-03 02:38:16.46: PodMonitor - start process kube event
2025-02-03 02:38:17.64: EndPointMonitor - Received BOOKMARK: oldResVer=12702 newResVer=12702
2025-02-03 02:38:17.64: EndPointMonitor - start process kube event
2025-02-03 02:38:17.64: empty line received
2025-02-03 02:38:17.64: EndPointMonitor - start process kube event
2025-02-03 02:38:19.31: NetworkMonitor - Received BOOKMARK: oldResVer=12503 newResVer=13416
2025-02-03 02:38:19.31: NetworkMonitor - start process kube event
2025-02-03 02:38:19.31: empty line received
2025-02-03 02:38:19.31: NetworkMonitor - start process kube event
2025-02-03 02:38:21.08: NamespaceMonitor - Received BOOKMARK: oldResVer=13042 newResVer=13042
2025-02-03 02:38:21.08: NamespaceMonitor - start process kube event
2025-02-03 02:38:21.08: empty line received
2025-02-03 02:38:21.08: NamespaceMonitor - start process kube event
2025-02-03 02:38:22.47: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12739 newResVer=12739
2025-02-03 02:38:22.47: NetworkPolicyMonitor - start process kube event
2025-02-03 02:38:22.47: empty line received
2025-02-03 02:38:22.47: NetworkPolicyMonitor - start process kube event
2025-02-03 02:38:55.16: ServiceMonitor - Received BOOKMARK: oldResVer=12661 newResVer=12661
2025-02-03 02:38:55.16: ServiceMonitor - start process kube event
2025-02-03 02:38:55.16: empty line received
2025-02-03 02:38:55.16: ServiceMonitor - start process kube event
2025-02-03 02:39:16.96: PodMonitor - Received BOOKMARK: oldResVer=13402 newResVer=13402
2025-02-03 02:39:16.96: PodMonitor - start process kube event
2025-02-03 02:39:16.96: PodMonitor - _schedule_vnc_sync
2025-02-03 02:39:16.96: empty line received
2025-02-03 02:39:16.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 02:39:16.96: VncKubernetes - vnc_sync - Pod start
2025-02-03 02:39:16.96: VncKubernetes - vnc_sync - Pod done
2025-02-03 02:39:16.96: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:39:16.96: PodMonitor - start process kube event
2025-02-03 02:39:17.63: EndPointMonitor - Received BOOKMARK: oldResVer=12702 newResVer=12702
2025-02-03 02:39:17.63: EndPointMonitor - start process kube event
2025-02-03 02:39:17.63: empty line received
2025-02-03 02:39:17.63: EndPointMonitor - start process kube event
2025-02-03 02:39:19.36: NetworkMonitor - Received BOOKMARK: oldResVer=13416 newResVer=13416
2025-02-03 02:39:19.36: NetworkMonitor - start process kube event
2025-02-03 02:39:19.36: NetworkMonitor - _schedule_vnc_sync
2025-02-03 02:39:19.36: empty line received
2025-02-03 02:39:19.36: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-03 02:39:19.36: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-03 02:39:19.36: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:39:19.36: NetworkMonitor - start process kube event
2025-02-03 02:39:22.18: NamespaceMonitor - Received BOOKMARK: oldResVer=13042 newResVer=13042
2025-02-03 02:39:22.18: NamespaceMonitor - start process kube event
2025-02-03 02:39:22.18: empty line received
2025-02-03 02:39:22.18: NamespaceMonitor - start process kube event
2025-02-03 02:39:23.22: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12739 newResVer=12739
2025-02-03 02:39:23.22: NetworkPolicyMonitor - start process kube event
2025-02-03 02:39:23.22: empty line received
2025-02-03 02:39:23.22: NetworkPolicyMonitor - start process kube event
2025-02-03 02:39:31.77: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 02:39:31.77: IngressMonitor - start process kube event
2025-02-03 02:39:31.77: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12690
2025-02-03 02:39:31.77: IngressMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:39:31.77: IngressMonitor - Connect Kube API result 0
2025-02-03 02:39:31.78: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:39:31.78: IngressMonitor - Start Watching request https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12690'})(timeout=120)
2025-02-03 02:39:31.78: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:39:31.78: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:39:31.78: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:39:31.78: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:39:31.78: IngressMonitor - Watches https://10.0.0.40:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12690'})
2025-02-03 02:39:55.18: ServiceMonitor - Received BOOKMARK: oldResVer=12661 newResVer=13585
2025-02-03 02:39:55.18: ServiceMonitor - start process kube event
2025-02-03 02:39:55.18: empty line received
2025-02-03 02:39:55.18: ServiceMonitor - start process kube event
2025-02-03 02:40:16.73: PodMonitor - Received BOOKMARK: oldResVer=13402 newResVer=13402
2025-02-03 02:40:16.73: PodMonitor - start process kube event
2025-02-03 02:40:16.73: empty line received
2025-02-03 02:40:16.73: PodMonitor - start process kube event
2025-02-03 02:40:17.19: EndPointMonitor - Received BOOKMARK: oldResVer=12702 newResVer=12702
2025-02-03 02:40:17.19: EndPointMonitor - start process kube event
2025-02-03 02:40:17.19: empty line received
2025-02-03 02:40:17.19: EndPointMonitor - start process kube event
2025-02-03 02:40:18.50: NetworkMonitor - Received BOOKMARK: oldResVer=13416 newResVer=13416
2025-02-03 02:40:18.50: NetworkMonitor - start process kube event
2025-02-03 02:40:18.50: empty line received
2025-02-03 02:40:18.50: NetworkMonitor - start process kube event
2025-02-03 02:40:22.24: NamespaceMonitor - Received BOOKMARK: oldResVer=13042 newResVer=13042
2025-02-03 02:40:22.24: NamespaceMonitor - start process kube event
2025-02-03 02:40:22.24: empty line received
2025-02-03 02:40:22.24: NamespaceMonitor - start process kube event
2025-02-03 02:40:23.53: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12739 newResVer=13605
2025-02-03 02:40:23.53: NetworkPolicyMonitor - start process kube event
2025-02-03 02:40:23.53: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-03 02:40:23.53: empty line received
2025-02-03 02:40:23.53: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-03 02:40:23.53: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-03 02:40:23.53: NetworkPolicyMonitor - start process kube event
2025-02-03 02:40:23.53: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-03 02:40:23.54: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:40:31.48: IngressMonitor - Received BOOKMARK: oldResVer=12690 newResVer=13553
2025-02-03 02:40:31.48: IngressMonitor - start process kube event
2025-02-03 02:40:31.48: empty line received
2025-02-03 02:40:31.48: IngressMonitor - start process kube event
2025-02-03 02:40:55.63: ServiceMonitor - Received BOOKMARK: oldResVer=13585 newResVer=13585
2025-02-03 02:40:55.63: ServiceMonitor - start process kube event
2025-02-03 02:40:55.63: empty line received
2025-02-03 02:40:55.63: ServiceMonitor - start process kube event
2025-02-03 02:41:12.49: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:41:12.49: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:41:12.49: PodMonitor - start process kube event
2025-02-03 02:41:12.49: empty line received
2025-02-03 02:41:12.49: PodMonitor - start process kube event
2025-02-03 02:41:16.60: PodMonitor - Received BOOKMARK: oldResVer=13402 newResVer=13697
2025-02-03 02:41:16.60: PodMonitor - start process kube event
2025-02-03 02:41:16.60: empty line received
2025-02-03 02:41:16.60: PodMonitor - start process kube event
2025-02-03 02:41:17.17: EndPointMonitor - Received BOOKMARK: oldResVer=12702 newResVer=13630
2025-02-03 02:41:17.17: EndPointMonitor - start process kube event
2025-02-03 02:41:17.17: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:41:17.17: empty line received
2025-02-03 02:41:17.17: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:41:17.17: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:41:17.17: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:41:17.17: EndPointMonitor - start process kube event
2025-02-03 02:41:18.47: NetworkMonitor - Received BOOKMARK: oldResVer=13416 newResVer=13416
2025-02-03 02:41:18.47: NetworkMonitor - start process kube event
2025-02-03 02:41:18.47: empty line received
2025-02-03 02:41:18.47: NetworkMonitor - start process kube event
2025-02-03 02:41:22.49: NamespaceMonitor - Received BOOKMARK: oldResVer=13042 newResVer=13042
2025-02-03 02:41:22.49: NamespaceMonitor - start process kube event
2025-02-03 02:41:22.49: NamespaceMonitor - _schedule_vnc_sync
2025-02-03 02:41:22.49: empty line received
2025-02-03 02:41:22.49: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-03 02:41:22.49: VncKubernetes - vnc_sync - Namespace start
2025-02-03 02:41:22.49: VncKubernetes - vnc_sync - Namespace done
2025-02-03 02:41:22.49: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:41:22.49: NamespaceMonitor - start process kube event
2025-02-03 02:41:23.89: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13605 newResVer=13605
2025-02-03 02:41:23.89: NetworkPolicyMonitor - start process kube event
2025-02-03 02:41:23.89: empty line received
2025-02-03 02:41:23.89: NetworkPolicyMonitor - start process kube event
2025-02-03 02:41:24.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:41:24.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:41:24.59: PodMonitor - start process kube event
2025-02-03 02:41:24.59: empty line received
2025-02-03 02:41:24.59: PodMonitor - start process kube event
2025-02-03 02:41:32.17: IngressMonitor - Received BOOKMARK: oldResVer=13553 newResVer=13553
2025-02-03 02:41:32.17: IngressMonitor - start process kube event
2025-02-03 02:41:32.17: empty line received
2025-02-03 02:41:32.17: IngressMonitor - start process kube event
2025-02-03 02:41:36.93: EndPointMonitor - Received BOOKMARK: oldResVer=13630 newResVer=13630
2025-02-03 02:41:36.93: EndPointMonitor - start process kube event
2025-02-03 02:41:36.93: empty line received
2025-02-03 02:41:36.93: EndPointMonitor - start process kube event
2025-02-03 02:41:38.02: stop iteration EndPointMonitor
2025-02-03 02:41:38.02: EndPointMonitor - start process kube event
2025-02-03 02:41:38.02: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13630
2025-02-03 02:41:38.02: EndPointMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:41:38.02: EndPointMonitor - Connect Kube API result 0
2025-02-03 02:41:38.02: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:41:38.02: EndPointMonitor - Start Watching request https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13630'})(timeout=120)
2025-02-03 02:41:38.02: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:41:38.02: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:41:38.02: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:41:38.02: EndPointMonitor - Watches https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13630'})
2025-02-03 02:41:50.47: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:41:50.47: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:41:50.47: PodMonitor - start process kube event
2025-02-03 02:41:50.47: empty line received
2025-02-03 02:41:50.47: PodMonitor - start process kube event
2025-02-03 02:41:55.48: ServiceMonitor - Received BOOKMARK: oldResVer=13585 newResVer=13585
2025-02-03 02:41:55.48: ServiceMonitor - start process kube event
2025-02-03 02:41:55.48: empty line received
2025-02-03 02:41:55.48: ServiceMonitor - start process kube event
2025-02-03 02:42:16.97: PodMonitor - Received BOOKMARK: oldResVer=13697 newResVer=13752
2025-02-03 02:42:16.97: PodMonitor - start process kube event
2025-02-03 02:42:16.97: empty line received
2025-02-03 02:42:16.97: PodMonitor - start process kube event
2025-02-03 02:42:19.39: NetworkMonitor - Received BOOKMARK: oldResVer=13416 newResVer=13416
2025-02-03 02:42:19.39: NetworkMonitor - start process kube event
2025-02-03 02:42:19.40: empty line received
2025-02-03 02:42:19.40: NetworkMonitor - start process kube event
2025-02-03 02:42:22.52: NamespaceMonitor - Received BOOKMARK: oldResVer=13042 newResVer=13042
2025-02-03 02:42:22.52: NamespaceMonitor - start process kube event
2025-02-03 02:42:22.52: empty line received
2025-02-03 02:42:22.52: NamespaceMonitor - start process kube event
2025-02-03 02:42:23.36: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13605 newResVer=13605
2025-02-03 02:42:23.36: NetworkPolicyMonitor - start process kube event
2025-02-03 02:42:23.36: empty line received
2025-02-03 02:42:23.36: NetworkPolicyMonitor - start process kube event
2025-02-03 02:42:30.54: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:42:30.54: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:42:30.54: PodMonitor - start process kube event
2025-02-03 02:42:30.54: empty line received
2025-02-03 02:42:30.54: PodMonitor - start process kube event
2025-02-03 02:42:32.42: IngressMonitor - Received BOOKMARK: oldResVer=13553 newResVer=13553
2025-02-03 02:42:32.42: IngressMonitor - start process kube event
2025-02-03 02:42:32.42: empty line received
2025-02-03 02:42:32.42: IngressMonitor - start process kube event
2025-02-03 02:42:50.02: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:42:50.02: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:42:50.02: PodMonitor - start process kube event
2025-02-03 02:42:50.02: empty line received
2025-02-03 02:42:50.02: PodMonitor - start process kube event
2025-02-03 02:42:55.80: ServiceMonitor - Received BOOKMARK: oldResVer=13585 newResVer=13585
2025-02-03 02:42:55.80: ServiceMonitor - start process kube event
2025-02-03 02:42:55.80: ServiceMonitor - _schedule_vnc_sync
2025-02-03 02:42:55.80: empty line received
2025-02-03 02:42:55.80: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-03 02:42:55.80: VncKubernetes - vnc_sync - Service start
2025-02-03 02:42:55.80: VncKubernetes - vnc_sync - Service done
2025-02-03 02:42:55.80: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:42:55.80: ServiceMonitor - start process kube event
2025-02-03 02:43:00.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:43:00.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:43:00.59: PodMonitor - start process kube event
2025-02-03 02:43:00.59: empty line received
2025-02-03 02:43:00.59: PodMonitor - start process kube event
2025-02-03 02:43:16.74: PodMonitor - Received BOOKMARK: oldResVer=13752 newResVer=13853
2025-02-03 02:43:16.74: PodMonitor - start process kube event
2025-02-03 02:43:16.74: empty line received
2025-02-03 02:43:16.74: PodMonitor - start process kube event
2025-02-03 02:43:19.17: NetworkMonitor - Received BOOKMARK: oldResVer=13416 newResVer=13416
2025-02-03 02:43:19.17: NetworkMonitor - start process kube event
2025-02-03 02:43:19.17: empty line received
2025-02-03 02:43:19.17: NetworkMonitor - start process kube event
2025-02-03 02:43:22.65: NamespaceMonitor - Received BOOKMARK: oldResVer=13042 newResVer=13042
2025-02-03 02:43:22.65: NamespaceMonitor - start process kube event
2025-02-03 02:43:22.65: empty line received
2025-02-03 02:43:22.65: NamespaceMonitor - start process kube event
2025-02-03 02:43:23.63: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13605 newResVer=13605
2025-02-03 02:43:23.63: NetworkPolicyMonitor - start process kube event
2025-02-03 02:43:23.63: empty line received
2025-02-03 02:43:23.63: NetworkPolicyMonitor - start process kube event
2025-02-03 02:43:31.09: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-qnd7w:cfa574d9-08b0-4b7f-88a5-49f6d05fc912
2025-02-03 02:43:31.09: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-qnd7w (hostNetwork=True)
2025-02-03 02:43:31.09: PodMonitor - start process kube event
2025-02-03 02:43:31.09: PodMonitor - _schedule_vnc_sync
2025-02-03 02:43:31.09: empty line received
2025-02-03 02:43:31.09: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-03 02:43:31.09: VncKubernetes - vnc_sync - Pod start
2025-02-03 02:43:31.09: VncKubernetes - vnc_sync - Pod done
2025-02-03 02:43:31.09: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:43:31.09: PodMonitor - start process kube event
2025-02-03 02:43:32.83: IngressMonitor - Received BOOKMARK: oldResVer=13553 newResVer=13553
2025-02-03 02:43:32.83: IngressMonitor - start process kube event
2025-02-03 02:43:32.83: IngressMonitor - _schedule_vnc_sync
2025-02-03 02:43:32.83: empty line received
2025-02-03 02:43:32.83: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-03 02:43:32.83: VncKubernetes - vnc_sync - Ingress start
2025-02-03 02:43:32.83: VncKubernetes - vnc_sync - Ingress done
2025-02-03 02:43:32.83: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-03 02:43:32.83: IngressMonitor - start process kube event
2025-02-03 02:43:38.02: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.40', port=6443): Read timed out.
2025-02-03 02:43:38.03: EndPointMonitor - start process kube event
2025-02-03 02:43:38.03: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13630
2025-02-03 02:43:38.03: EndPointMonitor - Try to connect Kube API 10.0.0.40:6443
2025-02-03 02:43:38.03: EndPointMonitor - Connect Kube API result 0
2025-02-03 02:43:38.03: EndPointMonitor - _schedule_vnc_sync
2025-02-03 02:43:38.03: EndPointMonitor - Start Watching request https://10.0.0.40:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13630'})(timeout=120)
2025-02-03 02:43:38.03: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-03 02:43:38.03: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-03 02:43:38.03: VncKubernetes - wait event (qsize=0 timeout=120)