INFO: =================== Thu Feb 13 02:06:22 UTC 2025 =================== INFO: Waiting for cassandra 2/30 INFO: Waiting for cassandra 3/30 INFO: Waiting for cassandra 4/30 INFO: Waiting for cassandra 5/30 INFO: Waiting for cassandra 6/30 INFO: Waiting for cassandra 7/30 INFO: Waiting for cassandra 8/30 INFO: Waiting for cassandra 9/30 INFO: Waiting for cassandra 10/30 INFO: Cassandra is connected /usr/local/lib/python3.6/site-packages/cfgm_common/vnc_kombu.py:10: MonkeyPatchWarning: Patching more than once will result in the union of all True parameters being patched gevent.monkey.patch_all() 02/13/2025 02:08:00.930 7f21ecd74288 [contrail-kube-manager] [INFO]: SANDESH: CONNECT TO COLLECTOR: True 02/13/2025 02:08:01.156 7f21ecd74288 [contrail-kube-manager] [INFO]: SANDESH: Logging: LEVEL: [SYS_INFO] -> [SYS_NOTICE] 2025-02-13 02:08:02.51: KubeMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:08:02.51: KubeMonitor - Connect Kube API result 0 2025-02-13 02:08:02.82: KubeMonitor - KubeMonitor init done: url=https://10.0.0.29:6443/api/v1 2025-02-13 02:08:02.83: NamespaceMonitor - KubeMonitor init done: url=https://10.0.0.29:6443/api/v1 2025-02-13 02:08:02.84: NetworkMonitor - KubeMonitor init done: url=https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1 2025-02-13 02:08:02.84: PodMonitor - KubeMonitor init done: url=https://10.0.0.29:6443/api/v1 2025-02-13 02:08:02.85: ServiceMonitor - KubeMonitor init done: url=https://10.0.0.29:6443/api/v1 2025-02-13 02:08:02.85: NetworkPolicyMonitor - KubeMonitor init done: url=https://10.0.0.29:6443/apis/networking.k8s.io/v1 2025-02-13 02:08:02.86: EndPointMonitor - KubeMonitor init done: url=https://10.0.0.29:6443/api/v1 2025-02-13 02:08:02.86: IngressMonitor - KubeMonitor init done: url=https://10.0.0.29:6443/apis/networking.k8s.io/v1 2025-02-13 02:08:02.86: VncKubernetes - vnc_connect starting 2025-02-13 02:08:02.88: VncKubernetes - vnc_connect failed: 2025-02-13 02:08:05.89: VncKubernetes - vnc_connect failed: 2025-02-13 02:08:08.90: VncKubernetes - vnc_connect failed: 2025-02-13 02:08:11.92: VncKubernetes - vnc_connect failed: 2025-02-13 02:08:16.01: VncKubernetes - vnc_connect done 2025-02-13 02:08:17.04: default-domain domain available. 2025-02-13 02:08:30.37: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:08:30.37: NamespaceMonitor - start process kube event 2025-02-13 02:08:30.37: NamespaceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-02-13 02:08:30.37: NamespaceMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:08:30.37: NetworkMonitor - start process kube event 2025-02-13 02:08:30.37: NetworkMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-02-13 02:08:30.37: NetworkMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:08:30.37: PodMonitor - start process kube event 2025-02-13 02:08:30.37: PodMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-02-13 02:08:30.37: PodMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:08:30.37: ServiceMonitor - start process kube event 2025-02-13 02:08:30.37: ServiceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-02-13 02:08:30.37: ServiceMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:08:30.37: NetworkPolicyMonitor - start process kube event 2025-02-13 02:08:30.37: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-02-13 02:08:30.37: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:08:30.37: EndPointMonitor - start process kube event 2025-02-13 02:08:30.37: EndPointMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-02-13 02:08:30.37: EndPointMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:08:30.37: IngressMonitor - start process kube event 2025-02-13 02:08:30.37: IngressMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-02-13 02:08:30.37: IngressMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:08:30.37: IngressMonitor - Connect Kube API result 0 2025-02-13 02:08:30.37: IngressMonitor - Start init url=https://10.0.0.29:6443/apis/networking.k8s.io/v1/ingresses resource_version=None 2025-02-13 02:08:30.37: EndPointMonitor - Connect Kube API result 0 2025-02-13 02:08:30.37: EndPointMonitor - Start init url=https://10.0.0.29:6443/api/v1/endpoints resource_version=None 2025-02-13 02:08:30.41: NetworkPolicyMonitor - Connect Kube API result 0 2025-02-13 02:08:30.41: NetworkPolicyMonitor - Start init url=https://10.0.0.29:6443/apis/networking.k8s.io/v1/networkpolicies resource_version=None 2025-02-13 02:08:30.41: ServiceMonitor - Connect Kube API result 0 2025-02-13 02:08:30.41: ServiceMonitor - Start init url=https://10.0.0.29:6443/api/v1/services resource_version=None 2025-02-13 02:08:30.41: PodMonitor - Connect Kube API result 0 2025-02-13 02:08:30.41: PodMonitor - Start init url=https://10.0.0.29:6443/api/v1/pods resource_version=None 2025-02-13 02:08:30.41: NetworkMonitor - Connect Kube API result 0 2025-02-13 02:08:30.41: NamespaceMonitor - Connect Kube API result 0 2025-02-13 02:08:30.41: NamespaceMonitor - Start init url=https://10.0.0.29:6443/api/v1/namespaces resource_version=None 2025-02-13 02:08:30.46: NetworkPolicyMonitor - Done init url=https://10.0.0.29:6443/apis/networking.k8s.io/v1/networkpolicies, resource_version=10815 2025-02-13 02:08:30.46: NetworkPolicyMonitor - _schedule_vnc_sync 2025-02-13 02:08:30.46: NetworkPolicyMonitor - Start Watching request https://10.0.0.29:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:08:30.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-02-13 02:08:30.46: VncKubernetes - vnc_sync - NetworkPolicy start 2025-02-13 02:08:30.47: IngressMonitor - Done init url=https://10.0.0.29:6443/apis/networking.k8s.io/v1/ingresses, resource_version=10815 2025-02-13 02:08:30.47: IngressMonitor - _schedule_vnc_sync 2025-02-13 02:08:30.47: IngressMonitor - Start Watching request https://10.0.0.29:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:08:30.48: NetworkPolicyMonitor - Watches https://10.0.0.29:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:08:30.48: NetworkMonitor - Start init url=https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions resource_version=None 2025-02-13 02:08:30.49: EndPointMonitor - Got ADDED Endpoints default:kubernetes:32f147ab-b78f-405a-ac3b-2ac299f4bce4 2025-02-13 02:08:30.49: ServiceMonitor - Got ADDED Service default:kubernetes:66977630-c8ec-4feb-9894-1624df97bb3e 2025-02-13 02:08:30.49: NamespaceMonitor - Got ADDED Namespace None:default:0f3bbf8d-51fc-4601-9581-fd6e63e4d1a5 2025-02-13 02:08:30.49: VncKubernetes - vnc_sync - NetworkPolicy done 2025-02-13 02:08:30.49: VncKubernetes - wait event (qsize=4 timeout=120) 2025-02-13 02:08:30.49: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-02-13 02:08:30.49: VncKubernetes - vnc_sync - Ingress start 2025-02-13 02:08:30.49: VncKubernetes - vnc_sync - Ingress done 2025-02-13 02:08:30.49: VncKubernetes - wait event (qsize=3 timeout=120) 2025-02-13 02:08:30.49: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Endpoints ns=default) VncEndpoints - Got ADDED Endpoints default:kubernetes:32f147ab-b78f-405a-ac3b-2ac299f4bce4 2025-02-13 02:08:30.50: IngressMonitor - Watches https://10.0.0.29:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:08:30.50: PodMonitor - Skipped ADDED Pod kube-system:config-zookeeper-zgtq2 (hostNetwork=True) 2025-02-13 02:08:30.51: ServiceMonitor - Got ADDED Service kube-system:coredns:5846d5fe-b0d9-4907-a195-518b9cd48c34 2025-02-13 02:08:30.51: ServiceMonitor - Done init url=https://10.0.0.29:6443/api/v1/services, resource_version=10815 2025-02-13 02:08:30.51: ServiceMonitor - _schedule_vnc_sync 2025-02-13 02:08:30.51: ServiceMonitor - Start Watching request https://10.0.0.29:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:08:30.51: NamespaceMonitor - Got ADDED Namespace None:kube-node-lease:b9cd63da-1f79-4434-958a-bfabbadec182 2025-02-13 02:08:30.51: EndPointMonitor - Got ADDED Endpoints kube-system:coredns:a7bc51b5-1d70-4196-9462-62b4f2188322 2025-02-13 02:08:30.51: EndPointMonitor - Done init url=https://10.0.0.29:6443/api/v1/endpoints, resource_version=10815 2025-02-13 02:08:30.51: EndPointMonitor - _schedule_vnc_sync 2025-02-13 02:08:30.51: EndPointMonitor - Start Watching request https://10.0.0.29:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:08:30.51: PodMonitor - Skipped ADDED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:08:30.51: EndPointMonitor - Watches https://10.0.0.29:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:08:30.52: ServiceMonitor - Watches https://10.0.0.29:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:08:30.52: NetworkMonitor - Done init url=https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions, resource_version=10820 2025-02-13 02:08:30.52: NetworkMonitor - _schedule_vnc_sync 2025-02-13 02:08:30.52: NetworkMonitor - Start Watching request https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'})(timeout=120) 2025-02-13 02:08:30.52: NamespaceMonitor - Got ADDED Namespace None:kube-public:de4321d8-f152-4383-925a-db84e69e3e79 2025-02-13 02:08:30.52: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-alarm-nct2p (hostNetwork=True) 2025-02-13 02:08:30.52: NetworkMonitor - Watches https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'}) 2025-02-13 02:08:30.52: NamespaceMonitor - Got ADDED Namespace None:kube-system:2ab7e914-b60c-47b9-9a62-7fb3b3554f12 2025-02-13 02:08:30.52: NamespaceMonitor - Done init url=https://10.0.0.29:6443/api/v1/namespaces, resource_version=10815 2025-02-13 02:08:30.52: NamespaceMonitor - _schedule_vnc_sync 2025-02-13 02:08:30.52: NamespaceMonitor - Start Watching request https://10.0.0.29:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:08:30.53: VncKubernetes - wait event (qsize=11 timeout=120) 2025-02-13 02:08:30.53: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Service ns=default) VncService - Got ADDED Service default:kubernetes:66977630-c8ec-4feb-9894-1624df97bb3e 2025-02-13 02:08:30.53: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-rw8bm (hostNetwork=True) 2025-02-13 02:08:30.53: NamespaceMonitor - Watches https://10.0.0.29:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:08:30.54: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-snmp-djgd2 (hostNetwork=True) 2025-02-13 02:08:30.55: PodMonitor - Skipped ADDED Pod kube-system:contrail-analyticsdb-t49dj (hostNetwork=True) 2025-02-13 02:08:30.56: PodMonitor - Skipped ADDED Pod kube-system:contrail-configdb-7cz82 (hostNetwork=True) 2025-02-13 02:08:30.56: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-config-tmh48 (hostNetwork=True) 2025-02-13 02:08:30.57: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-control-8rsbf (hostNetwork=True) 2025-02-13 02:08:30.58: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-webui-qfc68 (hostNetwork=True) 2025-02-13 02:08:30.58: PodMonitor - Skipped ADDED Pod kube-system:contrail-kube-manager-zd4x6 (hostNetwork=True) 2025-02-13 02:08:30.59: PodMonitor - Got ADDED Pod kube-system:coredns-77f7cc69db-6dc6c:cb4787e0-3f23-4cdf-ae5d-c2c35d813a72 2025-02-13 02:08:30.60: PodMonitor - Got ADDED Pod kube-system:dns-autoscaler-595558c478-gm9jw:3c1106f2-cef5-4063-b307-0716adbd1497 2025-02-13 02:08:30.60: PodMonitor - Skipped ADDED Pod kube-system:kube-apiserver-cn-jenkins-deploy-platform-k8s-manifests-135-1 (hostNetwork=True) 2025-02-13 02:08:30.61: PodMonitor - Skipped ADDED Pod kube-system:kube-controller-manager-cn-jenkins-deploy-platform-k8s-manifests-135-1 (hostNetwork=True) 2025-02-13 02:08:30.61: PodMonitor - Skipped ADDED Pod kube-system:kube-proxy-7ghk6 (hostNetwork=True) 2025-02-13 02:08:30.62: PodMonitor - Skipped ADDED Pod kube-system:kube-scheduler-cn-jenkins-deploy-platform-k8s-manifests-135-1 (hostNetwork=True) 2025-02-13 02:08:30.62: PodMonitor - Skipped ADDED Pod kube-system:rabbitmq-ddbnt (hostNetwork=True) 2025-02-13 02:08:30.63: PodMonitor - Skipped ADDED Pod kube-system:redis-tm8vz (hostNetwork=True) 2025-02-13 02:08:30.63: PodMonitor - Done init url=https://10.0.0.29:6443/api/v1/pods, resource_version=10815 2025-02-13 02:08:30.63: PodMonitor - _schedule_vnc_sync 2025-02-13 02:08:30.63: PodMonitor - Start Watching request https://10.0.0.29:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:08:30.63: PodMonitor - Watches https://10.0.0.29:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:08:34.38: VncKubernetes - wait event (qsize=13 timeout=120) 2025-02-13 02:08:34.38: VncKubernetes - Process event (name=default event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace default:0f3bbf8d-51fc-4601-9581-fd6e63e4d1a5 2025-02-13 02:08:39.26: VncKubernetes - wait event (qsize=12 timeout=120) 2025-02-13 02:08:39.26: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Service ns=kube-system) VncService - Got ADDED Service kube-system:coredns:5846d5fe-b0d9-4907-a195-518b9cd48c34 2025-02-13 02:08:41.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:08:41.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:08:41.59: PodMonitor - start process kube event 2025-02-13 02:08:41.59: empty line received 2025-02-13 02:08:41.59: PodMonitor - start process kube event 2025-02-13 02:08:42.74: VncKubernetes - wait event (qsize=11 timeout=120) 2025-02-13 02:08:42.74: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-02-13 02:08:42.74: VncKubernetes - vnc_sync - Service start 2025-02-13 02:08:42.74: VncKubernetes - vnc_sync - Service done 2025-02-13 02:08:42.74: VncKubernetes - wait event (qsize=10 timeout=120) 2025-02-13 02:08:42.74: VncKubernetes - Process event (name=kube-node-lease event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace kube-node-lease:b9cd63da-1f79-4434-958a-bfabbadec182 2025-02-13 02:08:45.52: VncKubernetes - wait event (qsize=9 timeout=120) 2025-02-13 02:08:45.52: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Endpoints ns=kube-system) VncEndpoints - Got ADDED Endpoints kube-system:coredns:a7bc51b5-1d70-4196-9462-62b4f2188322 2025-02-13 02:08:45.64: VncKubernetes - wait event (qsize=8 timeout=120) 2025-02-13 02:08:45.64: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-02-13 02:08:45.64: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-02-13 02:08:45.64: VncKubernetes - wait event (qsize=7 timeout=120) 2025-02-13 02:08:45.64: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-02-13 02:08:45.64: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-02-13 02:08:45.64: VncKubernetes - wait event (qsize=6 timeout=120) 2025-02-13 02:08:45.64: VncKubernetes - Process event (name=kube-public event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace kube-public:de4321d8-f152-4383-925a-db84e69e3e79 2025-02-13 02:08:47.97: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:08:47.97: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:08:47.97: PodMonitor - start process kube event 2025-02-13 02:08:47.97: empty line received 2025-02-13 02:08:47.97: PodMonitor - start process kube event 2025-02-13 02:08:48.20: VncKubernetes - wait event (qsize=5 timeout=120) 2025-02-13 02:08:48.20: VncKubernetes - Process event (name=kube-system event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace kube-system:2ab7e914-b60c-47b9-9a62-7fb3b3554f12 2025-02-13 02:08:50.99: VncKubernetes - wait event (qsize=4 timeout=120) 2025-02-13 02:08:50.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-02-13 02:08:50.99: VncKubernetes - vnc_sync - Namespace start 2025-02-13 02:08:50.99: VncKubernetes - vnc_sync - Namespace done 2025-02-13 02:08:50.99: VncKubernetes - wait event (qsize=3 timeout=120) 2025-02-13 02:08:50.99: VncKubernetes - Process event (name=coredns-77f7cc69db-6dc6c event_type=ADDED kind=Pod ns=kube-system) VncPod - Got ADDED Pod kube-system:coredns-77f7cc69db-6dc6c:cb4787e0-3f23-4cdf-ae5d-c2c35d813a72 2025-02-13 02:08:53.03: PodMonitor - Received MODIFIED Pod kube-system:coredns-77f7cc69db-6dc6c:cb4787e0-3f23-4cdf-ae5d-c2c35d813a72 2025-02-13 02:08:53.03: PodMonitor - Got MODIFIED Pod kube-system:coredns-77f7cc69db-6dc6c:cb4787e0-3f23-4cdf-ae5d-c2c35d813a72 2025-02-13 02:08:53.03: PodMonitor - start process kube event 2025-02-13 02:08:53.03: empty line received 2025-02-13 02:08:53.04: VncKubernetes - wait event (qsize=3 timeout=120) 2025-02-13 02:08:53.04: VncKubernetes - Process event (name=dns-autoscaler-595558c478-gm9jw event_type=ADDED kind=Pod ns=kube-system) VncPod - Got ADDED Pod kube-system:dns-autoscaler-595558c478-gm9jw:3c1106f2-cef5-4063-b307-0716adbd1497 2025-02-13 02:08:53.04: PodMonitor - start process kube event 2025-02-13 02:08:54.37: PodMonitor - Received MODIFIED Pod kube-system:dns-autoscaler-595558c478-gm9jw:3c1106f2-cef5-4063-b307-0716adbd1497 2025-02-13 02:08:54.37: PodMonitor - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-gm9jw:3c1106f2-cef5-4063-b307-0716adbd1497 2025-02-13 02:08:54.37: VncKubernetes - wait event (qsize=3 timeout=120) 2025-02-13 02:08:54.37: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-02-13 02:08:54.37: VncKubernetes - vnc_sync - Pod start 2025-02-13 02:08:54.37: VncKubernetes - vnc_sync - Pod done 2025-02-13 02:08:54.37: VncKubernetes - wait event (qsize=2 timeout=120) 2025-02-13 02:08:54.37: VncKubernetes - Process event (name=coredns-77f7cc69db-6dc6c event_type=MODIFIED kind=Pod ns=kube-system) VncPod - Got MODIFIED Pod kube-system:coredns-77f7cc69db-6dc6c:cb4787e0-3f23-4cdf-ae5d-c2c35d813a72 2025-02-13 02:08:54.37: PodMonitor - start process kube event 2025-02-13 02:08:54.37: empty line received 2025-02-13 02:08:54.37: PodMonitor - start process kube event 2025-02-13 02:08:54.48: VncKubernetes - wait event (qsize=1 timeout=120) 2025-02-13 02:08:54.48: VncKubernetes - Process event (name=dns-autoscaler-595558c478-gm9jw event_type=MODIFIED kind=Pod ns=kube-system) VncPod - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-gm9jw:3c1106f2-cef5-4063-b307-0716adbd1497 2025-02-13 02:08:54.58: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:08:59.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:08:59.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:08:59.59: PodMonitor - start process kube event 2025-02-13 02:08:59.59: empty line received 2025-02-13 02:08:59.59: PodMonitor - start process kube event 2025-02-13 02:09:00.39: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:09:00.39: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:09:00.39: PodMonitor - start process kube event 2025-02-13 02:09:00.39: empty line received 2025-02-13 02:09:00.39: PodMonitor - start process kube event 2025-02-13 02:09:11.70: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:09:11.70: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:09:11.70: PodMonitor - start process kube event 2025-02-13 02:09:11.70: empty line received 2025-02-13 02:09:11.70: PodMonitor - start process kube event 2025-02-13 02:09:22.60: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:09:22.60: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:09:22.60: PodMonitor - start process kube event 2025-02-13 02:09:22.60: empty line received 2025-02-13 02:09:22.60: PodMonitor - start process kube event 2025-02-13 02:09:23.00: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:09:23.00: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:09:23.00: PodMonitor - start process kube event 2025-02-13 02:09:23.00: empty line received 2025-02-13 02:09:23.00: PodMonitor - start process kube event 2025-02-13 02:09:29.99: PodMonitor - Received BOOKMARK: oldResVer=10815 newResVer=10908 2025-02-13 02:09:29.99: PodMonitor - start process kube event 2025-02-13 02:09:29.99: empty line received 2025-02-13 02:09:29.99: PodMonitor - start process kube event 2025-02-13 02:09:30.10: IngressMonitor - Received BOOKMARK: oldResVer=10815 newResVer=10858 2025-02-13 02:09:30.10: IngressMonitor - start process kube event 2025-02-13 02:09:30.10: empty line received 2025-02-13 02:09:30.10: IngressMonitor - start process kube event 2025-02-13 02:09:30.19: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10815 newResVer=10838 2025-02-13 02:09:30.19: NetworkPolicyMonitor - start process kube event 2025-02-13 02:09:30.19: empty line received 2025-02-13 02:09:30.19: NetworkPolicyMonitor - start process kube event 2025-02-13 02:09:49.83: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:09:49.83: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:09:49.83: PodMonitor - start process kube event 2025-02-13 02:09:49.83: empty line received 2025-02-13 02:09:49.83: PodMonitor - start process kube event 2025-02-13 02:10:00.12: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:10:00.12: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:10:00.12: PodMonitor - start process kube event 2025-02-13 02:10:00.12: empty line received 2025-02-13 02:10:00.12: PodMonitor - start process kube event 2025-02-13 02:10:13.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:10:13.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:10:13.59: PodMonitor - start process kube event 2025-02-13 02:10:13.59: empty line received 2025-02-13 02:10:13.59: PodMonitor - start process kube event 2025-02-13 02:10:23.75: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:10:23.75: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:10:23.75: PodMonitor - start process kube event 2025-02-13 02:10:23.75: empty line received 2025-02-13 02:10:23.75: PodMonitor - start process kube event 2025-02-13 02:10:24.80: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:10:24.80: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:10:24.80: PodMonitor - start process kube event 2025-02-13 02:10:24.80: empty line received 2025-02-13 02:10:24.80: PodMonitor - start process kube event 2025-02-13 02:10:30.25: IngressMonitor - Received BOOKMARK: oldResVer=10858 newResVer=10858 2025-02-13 02:10:30.25: IngressMonitor - start process kube event 2025-02-13 02:10:30.25: empty line received 2025-02-13 02:10:30.25: IngressMonitor - start process kube event 2025-02-13 02:10:30.37: PodMonitor - Received BOOKMARK: oldResVer=10908 newResVer=11002 2025-02-13 02:10:30.37: PodMonitor - start process kube event 2025-02-13 02:10:30.37: empty line received 2025-02-13 02:10:30.37: PodMonitor - start process kube event 2025-02-13 02:10:30.52: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:10:30.52: EndPointMonitor - start process kube event 2025-02-13 02:10:30.52: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10815 2025-02-13 02:10:30.52: EndPointMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:10:30.52: EndPointMonitor - Connect Kube API result 0 2025-02-13 02:10:30.52: EndPointMonitor - _schedule_vnc_sync 2025-02-13 02:10:30.52: EndPointMonitor - Start Watching request https://10.0.0.29:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:10:30.52: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-02-13 02:10:30.52: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-02-13 02:10:30.52: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:10:30.52: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:10:30.52: ServiceMonitor - start process kube event 2025-02-13 02:10:30.52: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10815 2025-02-13 02:10:30.52: ServiceMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:10:30.52: ServiceMonitor - Connect Kube API result 0 2025-02-13 02:10:30.52: ServiceMonitor - _schedule_vnc_sync 2025-02-13 02:10:30.52: ServiceMonitor - Start Watching request https://10.0.0.29:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:10:30.52: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-02-13 02:10:30.52: VncKubernetes - vnc_sync - Service start 2025-02-13 02:10:30.52: VncKubernetes - vnc_sync - Service done 2025-02-13 02:10:30.52: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:10:30.52: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:10:30.52: NetworkMonitor - start process kube event 2025-02-13 02:10:30.52: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10820 2025-02-13 02:10:30.53: NetworkMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:10:30.53: NetworkMonitor - Connect Kube API result 0 2025-02-13 02:10:30.53: NetworkMonitor - _schedule_vnc_sync 2025-02-13 02:10:30.53: NetworkMonitor - Start Watching request https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'})(timeout=120) 2025-02-13 02:10:30.53: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-02-13 02:10:30.53: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-02-13 02:10:30.53: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:10:30.53: EndPointMonitor - Watches https://10.0.0.29:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:10:30.53: ServiceMonitor - Watches https://10.0.0.29:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:10:30.53: NetworkMonitor - Watches https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'}) 2025-02-13 02:10:30.53: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:10:30.53: NamespaceMonitor - start process kube event 2025-02-13 02:10:30.53: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10815 2025-02-13 02:10:30.53: NamespaceMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:10:30.54: NamespaceMonitor - Connect Kube API result 0 2025-02-13 02:10:30.54: NamespaceMonitor - _schedule_vnc_sync 2025-02-13 02:10:30.54: NamespaceMonitor - Start Watching request https://10.0.0.29:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:10:30.54: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-02-13 02:10:30.54: VncKubernetes - vnc_sync - Namespace start 2025-02-13 02:10:30.54: VncKubernetes - vnc_sync - Namespace done 2025-02-13 02:10:30.54: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:10:30.54: NamespaceMonitor - Watches https://10.0.0.29:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:10:30.70: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10838 newResVer=10838 2025-02-13 02:10:30.70: NetworkPolicyMonitor - start process kube event 2025-02-13 02:10:30.70: empty line received 2025-02-13 02:10:30.70: NetworkPolicyMonitor - start process kube event 2025-02-13 02:10:48.40: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:10:48.40: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:10:48.40: PodMonitor - start process kube event 2025-02-13 02:10:48.40: empty line received 2025-02-13 02:10:48.40: PodMonitor - start process kube event 2025-02-13 02:11:24.31: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:11:24.32: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:11:24.32: PodMonitor - start process kube event 2025-02-13 02:11:24.32: empty line received 2025-02-13 02:11:24.32: PodMonitor - start process kube event 2025-02-13 02:11:30.41: IngressMonitor - Received BOOKMARK: oldResVer=10858 newResVer=10858 2025-02-13 02:11:30.41: IngressMonitor - start process kube event 2025-02-13 02:11:30.41: empty line received 2025-02-13 02:11:30.41: IngressMonitor - start process kube event 2025-02-13 02:11:30.61: PodMonitor - Received BOOKMARK: oldResVer=11002 newResVer=11093 2025-02-13 02:11:30.61: PodMonitor - start process kube event 2025-02-13 02:11:30.61: empty line received 2025-02-13 02:11:30.61: PodMonitor - start process kube event 2025-02-13 02:11:31.16: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10838 newResVer=10838 2025-02-13 02:11:31.16: NetworkPolicyMonitor - start process kube event 2025-02-13 02:11:31.16: empty line received 2025-02-13 02:11:31.16: NetworkPolicyMonitor - start process kube event 2025-02-13 02:11:38.58: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:11:38.58: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:11:38.58: PodMonitor - start process kube event 2025-02-13 02:11:38.58: empty line received 2025-02-13 02:11:38.58: PodMonitor - start process kube event 2025-02-13 02:11:48.91: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:11:48.91: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:11:48.91: PodMonitor - start process kube event 2025-02-13 02:11:48.91: empty line received 2025-02-13 02:11:48.91: PodMonitor - start process kube event 2025-02-13 02:12:00.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:12:00.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:12:00.59: PodMonitor - start process kube event 2025-02-13 02:12:00.59: empty line received 2025-02-13 02:12:00.59: PodMonitor - start process kube event 2025-02-13 02:12:12.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:12:12.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:12:12.55: PodMonitor - start process kube event 2025-02-13 02:12:12.55: empty line received 2025-02-13 02:12:12.55: PodMonitor - start process kube event 2025-02-13 02:12:30.16: PodMonitor - Received BOOKMARK: oldResVer=11093 newResVer=11169 2025-02-13 02:12:30.16: PodMonitor - start process kube event 2025-02-13 02:12:30.16: empty line received 2025-02-13 02:12:30.16: PodMonitor - start process kube event 2025-02-13 02:12:30.53: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:12:30.53: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:12:30.53: EndPointMonitor - start process kube event 2025-02-13 02:12:30.53: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10815 2025-02-13 02:12:30.53: EndPointMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:12:30.53: ServiceMonitor - start process kube event 2025-02-13 02:12:30.53: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10815 2025-02-13 02:12:30.53: ServiceMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:12:30.53: ServiceMonitor - Connect Kube API result 0 2025-02-13 02:12:30.53: ServiceMonitor - _schedule_vnc_sync 2025-02-13 02:12:30.53: ServiceMonitor - Start Watching request https://10.0.0.29:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:12:30.54: EndPointMonitor - Connect Kube API result 0 2025-02-13 02:12:30.54: EndPointMonitor - _schedule_vnc_sync 2025-02-13 02:12:30.54: EndPointMonitor - Start Watching request https://10.0.0.29:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:12:30.54: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-02-13 02:12:30.54: VncKubernetes - vnc_sync - Service start 2025-02-13 02:12:30.54: VncKubernetes - vnc_sync - Service done 2025-02-13 02:12:30.54: VncKubernetes - wait event (qsize=1 timeout=120) 2025-02-13 02:12:30.54: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-02-13 02:12:30.54: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-02-13 02:12:30.54: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:12:30.54: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:12:30.54: NetworkMonitor - start process kube event 2025-02-13 02:12:30.54: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10820 2025-02-13 02:12:30.54: NetworkMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:12:30.54: NetworkMonitor - Connect Kube API result 0 2025-02-13 02:12:30.54: NetworkMonitor - _schedule_vnc_sync 2025-02-13 02:12:30.54: NetworkMonitor - Start Watching request https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'})(timeout=120) 2025-02-13 02:12:30.54: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-02-13 02:12:30.54: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-02-13 02:12:30.54: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:12:30.54: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:12:30.54: NamespaceMonitor - start process kube event 2025-02-13 02:12:30.54: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10815 2025-02-13 02:12:30.54: NamespaceMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:12:30.54: NamespaceMonitor - Connect Kube API result 0 2025-02-13 02:12:30.54: NamespaceMonitor - _schedule_vnc_sync 2025-02-13 02:12:30.54: NamespaceMonitor - Start Watching request https://10.0.0.29:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:12:30.55: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-02-13 02:12:30.55: VncKubernetes - vnc_sync - Namespace start 2025-02-13 02:12:30.55: VncKubernetes - vnc_sync - Namespace done 2025-02-13 02:12:30.55: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:12:30.55: EndPointMonitor - Watches https://10.0.0.29:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:12:30.55: ServiceMonitor - Watches https://10.0.0.29:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:12:30.55: NetworkMonitor - Watches https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'}) 2025-02-13 02:12:30.55: NamespaceMonitor - Watches https://10.0.0.29:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:12:30.75: IngressMonitor - Received BOOKMARK: oldResVer=10858 newResVer=10858 2025-02-13 02:12:30.75: IngressMonitor - start process kube event 2025-02-13 02:12:30.75: IngressMonitor - _schedule_vnc_sync 2025-02-13 02:12:30.75: empty line received 2025-02-13 02:12:30.75: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-02-13 02:12:30.75: VncKubernetes - vnc_sync - Ingress start 2025-02-13 02:12:30.75: VncKubernetes - vnc_sync - Ingress done 2025-02-13 02:12:30.75: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:12:30.75: IngressMonitor - start process kube event 2025-02-13 02:12:31.55: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10838 newResVer=10838 2025-02-13 02:12:31.55: NetworkPolicyMonitor - start process kube event 2025-02-13 02:12:31.55: NetworkPolicyMonitor - _schedule_vnc_sync 2025-02-13 02:12:31.55: empty line received 2025-02-13 02:12:31.55: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-02-13 02:12:31.55: VncKubernetes - vnc_sync - NetworkPolicy start 2025-02-13 02:12:31.55: NetworkPolicyMonitor - start process kube event 2025-02-13 02:12:31.55: VncKubernetes - vnc_sync - NetworkPolicy done 2025-02-13 02:12:31.55: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:12:38.17: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:12:38.17: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:12:38.17: PodMonitor - start process kube event 2025-02-13 02:12:38.17: PodMonitor - _schedule_vnc_sync 2025-02-13 02:12:38.17: empty line received 2025-02-13 02:12:38.17: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-02-13 02:12:38.17: VncKubernetes - vnc_sync - Pod start 2025-02-13 02:12:38.17: VncKubernetes - vnc_sync - Pod done 2025-02-13 02:12:38.17: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:12:38.17: PodMonitor - start process kube event 2025-02-13 02:12:52.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:12:52.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:12:52.59: PodMonitor - start process kube event 2025-02-13 02:12:52.59: empty line received 2025-02-13 02:12:52.59: PodMonitor - start process kube event 2025-02-13 02:13:11.95: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:13:11.95: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:13:11.95: PodMonitor - start process kube event 2025-02-13 02:13:11.95: empty line received 2025-02-13 02:13:11.95: PodMonitor - start process kube event 2025-02-13 02:13:25.60: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:13:25.60: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:13:25.60: PodMonitor - start process kube event 2025-02-13 02:13:25.60: empty line received 2025-02-13 02:13:25.60: PodMonitor - start process kube event 2025-02-13 02:13:30.38: PodMonitor - Received BOOKMARK: oldResVer=11169 newResVer=11277 2025-02-13 02:13:30.38: PodMonitor - start process kube event 2025-02-13 02:13:30.38: empty line received 2025-02-13 02:13:30.38: PodMonitor - start process kube event 2025-02-13 02:13:31.11: IngressMonitor - Received BOOKMARK: oldResVer=10858 newResVer=10858 2025-02-13 02:13:31.11: IngressMonitor - start process kube event 2025-02-13 02:13:31.11: empty line received 2025-02-13 02:13:31.11: IngressMonitor - start process kube event 2025-02-13 02:13:31.38: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10838 newResVer=10838 2025-02-13 02:13:31.38: NetworkPolicyMonitor - start process kube event 2025-02-13 02:13:31.38: empty line received 2025-02-13 02:13:31.38: NetworkPolicyMonitor - start process kube event 2025-02-13 02:13:38.61: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:13:38.61: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:13:38.61: PodMonitor - start process kube event 2025-02-13 02:13:38.61: empty line received 2025-02-13 02:13:38.61: PodMonitor - start process kube event 2025-02-13 02:13:53.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:13:53.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:13:53.59: PodMonitor - start process kube event 2025-02-13 02:13:53.59: empty line received 2025-02-13 02:13:53.59: PodMonitor - start process kube event 2025-02-13 02:14:30.55: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:14:30.55: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:14:30.55: EndPointMonitor - start process kube event 2025-02-13 02:14:30.55: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10815 2025-02-13 02:14:30.55: EndPointMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:14:30.55: ServiceMonitor - start process kube event 2025-02-13 02:14:30.55: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10815 2025-02-13 02:14:30.55: ServiceMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:14:30.55: EndPointMonitor - Connect Kube API result 0 2025-02-13 02:14:30.55: EndPointMonitor - _schedule_vnc_sync 2025-02-13 02:14:30.55: EndPointMonitor - Start Watching request https://10.0.0.29:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:14:30.56: ServiceMonitor - Connect Kube API result 0 2025-02-13 02:14:30.56: ServiceMonitor - _schedule_vnc_sync 2025-02-13 02:14:30.56: ServiceMonitor - Start Watching request https://10.0.0.29:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:14:30.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-02-13 02:14:30.56: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-02-13 02:14:30.56: VncKubernetes - wait event (qsize=1 timeout=120) 2025-02-13 02:14:30.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-02-13 02:14:30.56: VncKubernetes - vnc_sync - Service start 2025-02-13 02:14:30.56: VncKubernetes - vnc_sync - Service done 2025-02-13 02:14:30.56: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:14:30.56: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:14:30.56: NetworkMonitor - start process kube event 2025-02-13 02:14:30.56: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10820 2025-02-13 02:14:30.56: NetworkMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:14:30.56: NetworkMonitor - Connect Kube API result 0 2025-02-13 02:14:30.56: NetworkMonitor - _schedule_vnc_sync 2025-02-13 02:14:30.56: NetworkMonitor - Start Watching request https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'})(timeout=120) 2025-02-13 02:14:30.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-02-13 02:14:30.56: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-02-13 02:14:30.56: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:14:30.56: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:14:30.56: NamespaceMonitor - start process kube event 2025-02-13 02:14:30.56: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10815 2025-02-13 02:14:30.56: NamespaceMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:14:30.56: NamespaceMonitor - Connect Kube API result 0 2025-02-13 02:14:30.56: NamespaceMonitor - _schedule_vnc_sync 2025-02-13 02:14:30.56: NamespaceMonitor - Start Watching request https://10.0.0.29:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:14:30.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-02-13 02:14:30.56: VncKubernetes - vnc_sync - Namespace start 2025-02-13 02:14:30.56: VncKubernetes - vnc_sync - Namespace done 2025-02-13 02:14:30.56: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:14:30.57: ServiceMonitor - Watches https://10.0.0.29:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:14:30.57: EndPointMonitor - Watches https://10.0.0.29:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:14:30.57: NetworkMonitor - Watches https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'}) 2025-02-13 02:14:30.57: NamespaceMonitor - Watches https://10.0.0.29:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:14:30.77: PodMonitor - Received BOOKMARK: oldResVer=11277 newResVer=11320 2025-02-13 02:14:30.77: PodMonitor - start process kube event 2025-02-13 02:14:30.77: empty line received 2025-02-13 02:14:30.77: PodMonitor - start process kube event 2025-02-13 02:14:31.25: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10838 newResVer=10838 2025-02-13 02:14:31.25: NetworkPolicyMonitor - start process kube event 2025-02-13 02:14:31.25: empty line received 2025-02-13 02:14:31.25: NetworkPolicyMonitor - start process kube event 2025-02-13 02:14:31.58: IngressMonitor - Received BOOKMARK: oldResVer=10858 newResVer=10858 2025-02-13 02:14:31.58: IngressMonitor - start process kube event 2025-02-13 02:14:31.58: empty line received 2025-02-13 02:14:31.58: IngressMonitor - start process kube event 2025-02-13 02:14:44.11: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:14:44.11: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:14:44.11: PodMonitor - start process kube event 2025-02-13 02:14:44.11: empty line received 2025-02-13 02:14:44.11: PodMonitor - start process kube event 2025-02-13 02:15:10.80: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:15:10.80: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:15:10.80: PodMonitor - start process kube event 2025-02-13 02:15:10.80: empty line received 2025-02-13 02:15:10.80: PodMonitor - start process kube event 2025-02-13 02:15:30.14: ServiceMonitor - Received BOOKMARK: oldResVer=10815 newResVer=11397 2025-02-13 02:15:30.14: ServiceMonitor - start process kube event 2025-02-13 02:15:30.14: empty line received 2025-02-13 02:15:30.14: ServiceMonitor - start process kube event 2025-02-13 02:15:30.23: EndPointMonitor - Received BOOKMARK: oldResVer=10815 newResVer=11440 2025-02-13 02:15:30.23: EndPointMonitor - start process kube event 2025-02-13 02:15:30.23: empty line received 2025-02-13 02:15:30.23: EndPointMonitor - start process kube event 2025-02-13 02:15:30.49: PodMonitor - Received BOOKMARK: oldResVer=11320 newResVer=11433 2025-02-13 02:15:30.49: PodMonitor - start process kube event 2025-02-13 02:15:30.49: empty line received 2025-02-13 02:15:30.49: PodMonitor - start process kube event 2025-02-13 02:15:31.25: IngressMonitor - Received BOOKMARK: oldResVer=10858 newResVer=10858 2025-02-13 02:15:31.25: IngressMonitor - start process kube event 2025-02-13 02:15:31.25: empty line received 2025-02-13 02:15:31.25: IngressMonitor - start process kube event 2025-02-13 02:15:31.56: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10838 newResVer=10838 2025-02-13 02:15:31.56: NetworkPolicyMonitor - start process kube event 2025-02-13 02:15:31.56: empty line received 2025-02-13 02:15:31.56: NetworkPolicyMonitor - start process kube event 2025-02-13 02:15:44.62: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:15:44.62: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:15:44.62: PodMonitor - start process kube event 2025-02-13 02:15:44.62: empty line received 2025-02-13 02:15:44.62: PodMonitor - start process kube event 2025-02-13 02:15:57.58: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:15:57.58: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:15:57.58: PodMonitor - start process kube event 2025-02-13 02:15:57.58: empty line received 2025-02-13 02:15:57.58: PodMonitor - start process kube event 2025-02-13 02:16:11.31: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:16:11.31: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:16:11.31: PodMonitor - start process kube event 2025-02-13 02:16:11.31: empty line received 2025-02-13 02:16:11.31: PodMonitor - start process kube event 2025-02-13 02:16:22.58: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:16:22.58: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:16:22.58: PodMonitor - start process kube event 2025-02-13 02:16:22.58: empty line received 2025-02-13 02:16:22.58: PodMonitor - start process kube event 2025-02-13 02:16:29.93: PodMonitor - Received BOOKMARK: oldResVer=11433 newResVer=11543 2025-02-13 02:16:29.93: PodMonitor - start process kube event 2025-02-13 02:16:29.93: empty line received 2025-02-13 02:16:29.93: PodMonitor - start process kube event 2025-02-13 02:16:30.02: EndPointMonitor - Received BOOKMARK: oldResVer=11440 newResVer=11440 2025-02-13 02:16:30.02: EndPointMonitor - start process kube event 2025-02-13 02:16:30.02: empty line received 2025-02-13 02:16:30.02: EndPointMonitor - start process kube event 2025-02-13 02:16:30.08: ServiceMonitor - Received BOOKMARK: oldResVer=11397 newResVer=11397 2025-02-13 02:16:30.08: ServiceMonitor - start process kube event 2025-02-13 02:16:30.08: empty line received 2025-02-13 02:16:30.08: ServiceMonitor - start process kube event 2025-02-13 02:16:30.56: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:16:30.57: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:16:30.57: NetworkMonitor - start process kube event 2025-02-13 02:16:30.57: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10820 2025-02-13 02:16:30.57: NetworkMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:16:30.57: NetworkMonitor - Connect Kube API result 0 2025-02-13 02:16:30.57: NetworkMonitor - _schedule_vnc_sync 2025-02-13 02:16:30.57: NetworkMonitor - Start Watching request https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'})(timeout=120) 2025-02-13 02:16:30.58: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-02-13 02:16:30.58: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-02-13 02:16:30.58: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:16:30.58: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:16:30.58: NamespaceMonitor - start process kube event 2025-02-13 02:16:30.58: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10815 2025-02-13 02:16:30.58: NamespaceMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:16:30.58: NamespaceMonitor - Connect Kube API result 0 2025-02-13 02:16:30.58: NamespaceMonitor - _schedule_vnc_sync 2025-02-13 02:16:30.58: NamespaceMonitor - Start Watching request https://10.0.0.29:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'})(timeout=120) 2025-02-13 02:16:30.58: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-02-13 02:16:30.58: VncKubernetes - vnc_sync - Namespace start 2025-02-13 02:16:30.58: VncKubernetes - vnc_sync - Namespace done 2025-02-13 02:16:30.58: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:16:30.59: NamespaceMonitor - Watches https://10.0.0.29:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10815'}) 2025-02-13 02:16:30.59: NetworkMonitor - Watches https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'}) 2025-02-13 02:16:31.98: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10838 newResVer=10838 2025-02-13 02:16:31.98: NetworkPolicyMonitor - start process kube event 2025-02-13 02:16:31.98: NetworkPolicyMonitor - _schedule_vnc_sync 2025-02-13 02:16:31.98: empty line received 2025-02-13 02:16:31.98: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-02-13 02:16:31.98: VncKubernetes - vnc_sync - NetworkPolicy start 2025-02-13 02:16:31.98: NetworkPolicyMonitor - start process kube event 2025-02-13 02:16:31.98: VncKubernetes - vnc_sync - NetworkPolicy done 2025-02-13 02:16:31.98: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:16:32.00: IngressMonitor - Received BOOKMARK: oldResVer=10858 newResVer=10858 2025-02-13 02:16:32.00: IngressMonitor - start process kube event 2025-02-13 02:16:32.00: IngressMonitor - _schedule_vnc_sync 2025-02-13 02:16:32.00: empty line received 2025-02-13 02:16:32.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-02-13 02:16:32.00: VncKubernetes - vnc_sync - Ingress start 2025-02-13 02:16:32.00: VncKubernetes - vnc_sync - Ingress done 2025-02-13 02:16:32.00: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:16:32.00: IngressMonitor - start process kube event 2025-02-13 02:17:30.19: ServiceMonitor - Received BOOKMARK: oldResVer=11397 newResVer=11397 2025-02-13 02:17:30.19: ServiceMonitor - start process kube event 2025-02-13 02:17:30.19: empty line received 2025-02-13 02:17:30.19: ServiceMonitor - start process kube event 2025-02-13 02:17:30.24: NamespaceMonitor - Received BOOKMARK: oldResVer=10815 newResVer=11468 2025-02-13 02:17:30.24: NamespaceMonitor - start process kube event 2025-02-13 02:17:30.24: empty line received 2025-02-13 02:17:30.24: NamespaceMonitor - start process kube event 2025-02-13 02:17:30.60: EndPointMonitor - Received BOOKMARK: oldResVer=11440 newResVer=11440 2025-02-13 02:17:30.60: EndPointMonitor - start process kube event 2025-02-13 02:17:30.60: empty line received 2025-02-13 02:17:30.60: EndPointMonitor - start process kube event 2025-02-13 02:17:30.61: PodMonitor - Received BOOKMARK: oldResVer=11543 newResVer=11543 2025-02-13 02:17:30.61: PodMonitor - start process kube event 2025-02-13 02:17:30.61: PodMonitor - _schedule_vnc_sync 2025-02-13 02:17:30.61: empty line received 2025-02-13 02:17:30.61: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-02-13 02:17:30.61: VncKubernetes - vnc_sync - Pod start 2025-02-13 02:17:30.61: VncKubernetes - vnc_sync - Pod done 2025-02-13 02:17:30.61: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:17:30.61: PodMonitor - start process kube event 2025-02-13 02:17:31.28: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10838 newResVer=10838 2025-02-13 02:17:31.28: NetworkPolicyMonitor - start process kube event 2025-02-13 02:17:31.28: empty line received 2025-02-13 02:17:31.28: NetworkPolicyMonitor - start process kube event 2025-02-13 02:17:31.46: IngressMonitor - Received BOOKMARK: oldResVer=10858 newResVer=10858 2025-02-13 02:17:31.46: IngressMonitor - start process kube event 2025-02-13 02:17:31.46: empty line received 2025-02-13 02:17:31.46: IngressMonitor - start process kube event 2025-02-13 02:17:43.53: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:17:43.53: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:17:43.53: PodMonitor - start process kube event 2025-02-13 02:17:43.53: empty line received 2025-02-13 02:17:43.53: PodMonitor - start process kube event 2025-02-13 02:17:56.58: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:17:56.58: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:17:56.58: PodMonitor - start process kube event 2025-02-13 02:17:56.58: empty line received 2025-02-13 02:17:56.58: PodMonitor - start process kube event 2025-02-13 02:18:30.59: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.29', port=6443): Read timed out. 2025-02-13 02:18:30.59: NetworkMonitor - start process kube event 2025-02-13 02:18:30.59: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10820 2025-02-13 02:18:30.59: NetworkMonitor - Try to connect Kube API 10.0.0.29:6443 2025-02-13 02:18:30.59: NetworkMonitor - Connect Kube API result 0 2025-02-13 02:18:30.59: NetworkMonitor - _schedule_vnc_sync 2025-02-13 02:18:30.59: NetworkMonitor - Start Watching request https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'})(timeout=120) 2025-02-13 02:18:30.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-02-13 02:18:30.59: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-02-13 02:18:30.59: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:18:30.60: NetworkMonitor - Watches https://10.0.0.29:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10820'}) 2025-02-13 02:18:30.82: NamespaceMonitor - Received BOOKMARK: oldResVer=11468 newResVer=11468 2025-02-13 02:18:30.82: NamespaceMonitor - start process kube event 2025-02-13 02:18:30.82: empty line received 2025-02-13 02:18:30.82: NamespaceMonitor - start process kube event 2025-02-13 02:18:30.89: EndPointMonitor - Received BOOKMARK: oldResVer=11440 newResVer=11440 2025-02-13 02:18:30.89: EndPointMonitor - start process kube event 2025-02-13 02:18:30.89: EndPointMonitor - _schedule_vnc_sync 2025-02-13 02:18:30.89: empty line received 2025-02-13 02:18:30.89: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-02-13 02:18:30.89: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-02-13 02:18:30.89: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:18:30.89: EndPointMonitor - start process kube event 2025-02-13 02:18:30.93: PodMonitor - Received BOOKMARK: oldResVer=11543 newResVer=11678 2025-02-13 02:18:30.93: PodMonitor - start process kube event 2025-02-13 02:18:30.93: empty line received 2025-02-13 02:18:30.93: PodMonitor - start process kube event 2025-02-13 02:18:31.07: ServiceMonitor - Received BOOKMARK: oldResVer=11397 newResVer=11397 2025-02-13 02:18:31.07: ServiceMonitor - start process kube event 2025-02-13 02:18:31.07: ServiceMonitor - _schedule_vnc_sync 2025-02-13 02:18:31.07: empty line received 2025-02-13 02:18:31.07: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-02-13 02:18:31.07: VncKubernetes - vnc_sync - Service start 2025-02-13 02:18:31.07: VncKubernetes - vnc_sync - Service done 2025-02-13 02:18:31.07: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:18:31.07: ServiceMonitor - start process kube event 2025-02-13 02:18:31.25: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10838 newResVer=10838 2025-02-13 02:18:31.26: NetworkPolicyMonitor - start process kube event 2025-02-13 02:18:31.26: empty line received 2025-02-13 02:18:31.26: NetworkPolicyMonitor - start process kube event 2025-02-13 02:18:32.01: IngressMonitor - Received BOOKMARK: oldResVer=10858 newResVer=10858 2025-02-13 02:18:32.01: IngressMonitor - start process kube event 2025-02-13 02:18:32.01: empty line received 2025-02-13 02:18:32.01: IngressMonitor - start process kube event 2025-02-13 02:18:33.77: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:18:33.77: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:18:33.77: PodMonitor - start process kube event 2025-02-13 02:18:33.77: empty line received 2025-02-13 02:18:33.77: PodMonitor - start process kube event 2025-02-13 02:19:01.46: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:19:01.46: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:19:01.46: PodMonitor - start process kube event 2025-02-13 02:19:01.46: empty line received 2025-02-13 02:19:01.46: PodMonitor - start process kube event 2025-02-13 02:19:30.89: NamespaceMonitor - Received BOOKMARK: oldResVer=11468 newResVer=11468 2025-02-13 02:19:30.89: NamespaceMonitor - start process kube event 2025-02-13 02:19:30.89: empty line received 2025-02-13 02:19:30.89: NamespaceMonitor - start process kube event 2025-02-13 02:19:31.10: ServiceMonitor - Received BOOKMARK: oldResVer=11397 newResVer=11397 2025-02-13 02:19:31.10: ServiceMonitor - start process kube event 2025-02-13 02:19:31.10: empty line received 2025-02-13 02:19:31.10: ServiceMonitor - start process kube event 2025-02-13 02:19:31.49: EndPointMonitor - Received BOOKMARK: oldResVer=11440 newResVer=11440 2025-02-13 02:19:31.49: EndPointMonitor - start process kube event 2025-02-13 02:19:31.49: empty line received 2025-02-13 02:19:31.49: EndPointMonitor - start process kube event 2025-02-13 02:19:31.56: PodMonitor - Received BOOKMARK: oldResVer=11678 newResVer=11777 2025-02-13 02:19:31.56: PodMonitor - start process kube event 2025-02-13 02:19:31.56: empty line received 2025-02-13 02:19:31.56: PodMonitor - start process kube event 2025-02-13 02:19:31.62: NetworkMonitor - Received BOOKMARK: oldResVer=10820 newResVer=11745 2025-02-13 02:19:31.62: NetworkMonitor - start process kube event 2025-02-13 02:19:31.62: empty line received 2025-02-13 02:19:31.62: NetworkMonitor - start process kube event 2025-02-13 02:19:32.01: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10838 newResVer=10838 2025-02-13 02:19:32.01: NetworkPolicyMonitor - start process kube event 2025-02-13 02:19:32.01: empty line received 2025-02-13 02:19:32.01: NetworkPolicyMonitor - start process kube event 2025-02-13 02:19:32.03: IngressMonitor - Received BOOKMARK: oldResVer=10858 newResVer=10858 2025-02-13 02:19:32.03: IngressMonitor - start process kube event 2025-02-13 02:19:32.03: empty line received 2025-02-13 02:19:32.03: IngressMonitor - start process kube event 2025-02-13 02:19:33.26: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:19:33.26: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:19:33.26: PodMonitor - start process kube event 2025-02-13 02:19:33.26: empty line received 2025-02-13 02:19:33.26: PodMonitor - start process kube event 2025-02-13 02:19:44.58: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:19:44.58: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:19:44.58: PodMonitor - start process kube event 2025-02-13 02:19:44.58: empty line received 2025-02-13 02:19:44.58: PodMonitor - start process kube event 2025-02-13 02:20:00.97: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:20:00.97: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:20:00.97: PodMonitor - start process kube event 2025-02-13 02:20:00.97: empty line received 2025-02-13 02:20:00.97: PodMonitor - start process kube event 2025-02-13 02:20:11.60: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:20:11.60: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:20:11.60: PodMonitor - start process kube event 2025-02-13 02:20:11.60: empty line received 2025-02-13 02:20:11.60: PodMonitor - start process kube event 2025-02-13 02:20:30.86: NamespaceMonitor - Received BOOKMARK: oldResVer=11468 newResVer=11468 2025-02-13 02:20:30.86: NamespaceMonitor - start process kube event 2025-02-13 02:20:30.86: NamespaceMonitor - _schedule_vnc_sync 2025-02-13 02:20:30.86: empty line received 2025-02-13 02:20:30.86: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-02-13 02:20:30.86: VncKubernetes - vnc_sync - Namespace start 2025-02-13 02:20:30.86: VncKubernetes - vnc_sync - Namespace done 2025-02-13 02:20:30.86: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:20:30.86: NamespaceMonitor - start process kube event 2025-02-13 02:20:31.19: ServiceMonitor - Received BOOKMARK: oldResVer=11397 newResVer=11397 2025-02-13 02:20:31.19: ServiceMonitor - start process kube event 2025-02-13 02:20:31.19: empty line received 2025-02-13 02:20:31.19: ServiceMonitor - start process kube event 2025-02-13 02:20:31.80: NetworkMonitor - Received BOOKMARK: oldResVer=11745 newResVer=11745 2025-02-13 02:20:31.80: NetworkMonitor - start process kube event 2025-02-13 02:20:31.80: empty line received 2025-02-13 02:20:31.80: NetworkMonitor - start process kube event 2025-02-13 02:20:31.83: PodMonitor - Received BOOKMARK: oldResVer=11777 newResVer=11883 2025-02-13 02:20:31.83: PodMonitor - start process kube event 2025-02-13 02:20:31.83: empty line received 2025-02-13 02:20:31.83: PodMonitor - start process kube event 2025-02-13 02:20:31.89: EndPointMonitor - Received BOOKMARK: oldResVer=11440 newResVer=11440 2025-02-13 02:20:31.89: EndPointMonitor - start process kube event 2025-02-13 02:20:31.89: empty line received 2025-02-13 02:20:31.89: EndPointMonitor - start process kube event 2025-02-13 02:20:32.55: IngressMonitor - Received BOOKMARK: oldResVer=10858 newResVer=11848 2025-02-13 02:20:32.55: IngressMonitor - start process kube event 2025-02-13 02:20:32.55: IngressMonitor - _schedule_vnc_sync 2025-02-13 02:20:32.55: empty line received 2025-02-13 02:20:32.55: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-02-13 02:20:32.55: VncKubernetes - vnc_sync - Ingress start 2025-02-13 02:20:32.55: VncKubernetes - vnc_sync - Ingress done 2025-02-13 02:20:32.55: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:20:32.55: IngressMonitor - start process kube event 2025-02-13 02:20:32.70: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10838 newResVer=11831 2025-02-13 02:20:32.70: NetworkPolicyMonitor - start process kube event 2025-02-13 02:20:32.70: NetworkPolicyMonitor - _schedule_vnc_sync 2025-02-13 02:20:32.70: empty line received 2025-02-13 02:20:32.70: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-02-13 02:20:32.70: VncKubernetes - vnc_sync - NetworkPolicy start 2025-02-13 02:20:32.70: NetworkPolicyMonitor - start process kube event 2025-02-13 02:20:32.70: VncKubernetes - vnc_sync - NetworkPolicy done 2025-02-13 02:20:32.70: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:21:31.25: PodMonitor - Received BOOKMARK: oldResVer=11883 newResVer=11883 2025-02-13 02:21:31.25: PodMonitor - start process kube event 2025-02-13 02:21:31.25: PodMonitor - _schedule_vnc_sync 2025-02-13 02:21:31.25: empty line received 2025-02-13 02:21:31.25: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-02-13 02:21:31.25: VncKubernetes - vnc_sync - Pod start 2025-02-13 02:21:31.25: VncKubernetes - vnc_sync - Pod done 2025-02-13 02:21:31.25: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:21:31.25: PodMonitor - start process kube event 2025-02-13 02:21:31.26: ServiceMonitor - Received BOOKMARK: oldResVer=11397 newResVer=11397 2025-02-13 02:21:31.26: ServiceMonitor - start process kube event 2025-02-13 02:21:31.26: empty line received 2025-02-13 02:21:31.26: ServiceMonitor - start process kube event 2025-02-13 02:21:31.53: NamespaceMonitor - Received BOOKMARK: oldResVer=11468 newResVer=11468 2025-02-13 02:21:31.53: NamespaceMonitor - start process kube event 2025-02-13 02:21:31.53: empty line received 2025-02-13 02:21:31.53: NamespaceMonitor - start process kube event 2025-02-13 02:21:31.82: NetworkMonitor - Received BOOKMARK: oldResVer=11745 newResVer=11745 2025-02-13 02:21:31.82: NetworkMonitor - start process kube event 2025-02-13 02:21:31.82: empty line received 2025-02-13 02:21:31.82: NetworkMonitor - start process kube event 2025-02-13 02:21:32.33: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11831 newResVer=11831 2025-02-13 02:21:32.33: NetworkPolicyMonitor - start process kube event 2025-02-13 02:21:32.33: empty line received 2025-02-13 02:21:32.33: NetworkPolicyMonitor - start process kube event 2025-02-13 02:21:32.88: EndPointMonitor - Received BOOKMARK: oldResVer=11440 newResVer=11440 2025-02-13 02:21:32.88: EndPointMonitor - start process kube event 2025-02-13 02:21:32.88: empty line received 2025-02-13 02:21:32.88: EndPointMonitor - start process kube event 2025-02-13 02:21:33.03: IngressMonitor - Received BOOKMARK: oldResVer=11848 newResVer=11848 2025-02-13 02:21:33.03: IngressMonitor - start process kube event 2025-02-13 02:21:33.03: empty line received 2025-02-13 02:21:33.03: IngressMonitor - start process kube event 2025-02-13 02:22:30.92: NamespaceMonitor - Received BOOKMARK: oldResVer=11468 newResVer=11468 2025-02-13 02:22:30.92: NamespaceMonitor - start process kube event 2025-02-13 02:22:30.92: empty line received 2025-02-13 02:22:30.92: NamespaceMonitor - start process kube event 2025-02-13 02:22:31.19: PodMonitor - Received BOOKMARK: oldResVer=11883 newResVer=11883 2025-02-13 02:22:31.19: PodMonitor - start process kube event 2025-02-13 02:22:31.19: empty line received 2025-02-13 02:22:31.19: PodMonitor - start process kube event 2025-02-13 02:22:31.19: ServiceMonitor - Received BOOKMARK: oldResVer=11397 newResVer=11397 2025-02-13 02:22:31.19: ServiceMonitor - start process kube event 2025-02-13 02:22:31.19: ServiceMonitor - _schedule_vnc_sync 2025-02-13 02:22:31.19: empty line received 2025-02-13 02:22:31.19: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-02-13 02:22:31.19: VncKubernetes - vnc_sync - Service start 2025-02-13 02:22:31.19: VncKubernetes - vnc_sync - Service done 2025-02-13 02:22:31.19: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:22:31.19: ServiceMonitor - start process kube event 2025-02-13 02:22:32.01: NetworkMonitor - Received BOOKMARK: oldResVer=11745 newResVer=11745 2025-02-13 02:22:32.01: NetworkMonitor - start process kube event 2025-02-13 02:22:32.01: NetworkMonitor - _schedule_vnc_sync 2025-02-13 02:22:32.01: empty line received 2025-02-13 02:22:32.01: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-02-13 02:22:32.01: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-02-13 02:22:32.01: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:22:32.01: NetworkMonitor - start process kube event 2025-02-13 02:22:32.52: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11831 newResVer=11831 2025-02-13 02:22:32.52: NetworkPolicyMonitor - start process kube event 2025-02-13 02:22:32.52: empty line received 2025-02-13 02:22:32.52: NetworkPolicyMonitor - start process kube event 2025-02-13 02:22:32.88: EndPointMonitor - Received BOOKMARK: oldResVer=11440 newResVer=11440 2025-02-13 02:22:32.88: EndPointMonitor - start process kube event 2025-02-13 02:22:32.88: EndPointMonitor - _schedule_vnc_sync 2025-02-13 02:22:32.88: empty line received 2025-02-13 02:22:32.88: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-02-13 02:22:32.88: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-02-13 02:22:32.88: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:22:32.88: EndPointMonitor - start process kube event 2025-02-13 02:22:34.15: IngressMonitor - Received BOOKMARK: oldResVer=11848 newResVer=11848 2025-02-13 02:22:34.15: IngressMonitor - start process kube event 2025-02-13 02:22:34.15: empty line received 2025-02-13 02:22:34.15: IngressMonitor - start process kube event 2025-02-13 02:22:48.96: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:22:48.96: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:22:48.96: PodMonitor - start process kube event 2025-02-13 02:22:48.96: empty line received 2025-02-13 02:22:48.96: PodMonitor - start process kube event 2025-02-13 02:22:50.02: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:22:50.02: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:22:50.02: PodMonitor - start process kube event 2025-02-13 02:22:50.02: empty line received 2025-02-13 02:22:50.02: PodMonitor - start process kube event 2025-02-13 02:23:00.58: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:23:00.58: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:23:00.58: PodMonitor - start process kube event 2025-02-13 02:23:00.58: empty line received 2025-02-13 02:23:00.58: PodMonitor - start process kube event 2025-02-13 02:23:31.25: PodMonitor - Received BOOKMARK: oldResVer=11883 newResVer=12129 2025-02-13 02:23:31.25: PodMonitor - start process kube event 2025-02-13 02:23:31.25: empty line received 2025-02-13 02:23:31.25: PodMonitor - start process kube event 2025-02-13 02:23:31.30: NamespaceMonitor - Received BOOKMARK: oldResVer=11468 newResVer=11468 2025-02-13 02:23:31.30: NamespaceMonitor - start process kube event 2025-02-13 02:23:31.30: empty line received 2025-02-13 02:23:31.30: NamespaceMonitor - start process kube event 2025-02-13 02:23:31.55: NetworkMonitor - Received BOOKMARK: oldResVer=11745 newResVer=11745 2025-02-13 02:23:31.55: NetworkMonitor - start process kube event 2025-02-13 02:23:31.55: empty line received 2025-02-13 02:23:31.55: NetworkMonitor - start process kube event 2025-02-13 02:23:31.90: ServiceMonitor - Received BOOKMARK: oldResVer=11397 newResVer=11397 2025-02-13 02:23:31.90: ServiceMonitor - start process kube event 2025-02-13 02:23:31.90: empty line received 2025-02-13 02:23:31.90: ServiceMonitor - start process kube event 2025-02-13 02:23:32.43: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11831 newResVer=11831 2025-02-13 02:23:32.43: NetworkPolicyMonitor - start process kube event 2025-02-13 02:23:32.43: empty line received 2025-02-13 02:23:32.43: NetworkPolicyMonitor - start process kube event 2025-02-13 02:23:33.45: EndPointMonitor - Received BOOKMARK: oldResVer=11440 newResVer=11440 2025-02-13 02:23:33.45: EndPointMonitor - start process kube event 2025-02-13 02:23:33.45: empty line received 2025-02-13 02:23:33.45: EndPointMonitor - start process kube event 2025-02-13 02:23:34.87: IngressMonitor - Received BOOKMARK: oldResVer=11848 newResVer=11848 2025-02-13 02:23:34.87: IngressMonitor - start process kube event 2025-02-13 02:23:34.87: empty line received 2025-02-13 02:23:34.87: IngressMonitor - start process kube event 2025-02-13 02:24:31.22: ServiceMonitor - Received BOOKMARK: oldResVer=11397 newResVer=11397 2025-02-13 02:24:31.22: ServiceMonitor - start process kube event 2025-02-13 02:24:31.22: empty line received 2025-02-13 02:24:31.22: ServiceMonitor - start process kube event 2025-02-13 02:24:31.26: NamespaceMonitor - Received BOOKMARK: oldResVer=11468 newResVer=11468 2025-02-13 02:24:31.26: NamespaceMonitor - start process kube event 2025-02-13 02:24:31.26: NamespaceMonitor - _schedule_vnc_sync 2025-02-13 02:24:31.26: empty line received 2025-02-13 02:24:31.26: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-02-13 02:24:31.26: VncKubernetes - vnc_sync - Namespace start 2025-02-13 02:24:31.26: VncKubernetes - vnc_sync - Namespace done 2025-02-13 02:24:31.26: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:24:31.26: NamespaceMonitor - start process kube event 2025-02-13 02:24:31.76: PodMonitor - Received BOOKMARK: oldResVer=12129 newResVer=12129 2025-02-13 02:24:31.76: PodMonitor - start process kube event 2025-02-13 02:24:31.76: empty line received 2025-02-13 02:24:31.76: PodMonitor - start process kube event 2025-02-13 02:24:32.08: NetworkMonitor - Received BOOKMARK: oldResVer=11745 newResVer=11745 2025-02-13 02:24:32.08: NetworkMonitor - start process kube event 2025-02-13 02:24:32.08: empty line received 2025-02-13 02:24:32.08: NetworkMonitor - start process kube event 2025-02-13 02:24:32.15: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11831 newResVer=11831 2025-02-13 02:24:32.15: NetworkPolicyMonitor - start process kube event 2025-02-13 02:24:32.15: empty line received 2025-02-13 02:24:32.15: NetworkPolicyMonitor - start process kube event 2025-02-13 02:24:33.12: EndPointMonitor - Received BOOKMARK: oldResVer=11440 newResVer=11440 2025-02-13 02:24:33.12: EndPointMonitor - start process kube event 2025-02-13 02:24:33.12: empty line received 2025-02-13 02:24:33.12: EndPointMonitor - start process kube event 2025-02-13 02:24:34.09: IngressMonitor - Received BOOKMARK: oldResVer=11848 newResVer=11848 2025-02-13 02:24:34.09: IngressMonitor - start process kube event 2025-02-13 02:24:34.09: IngressMonitor - _schedule_vnc_sync 2025-02-13 02:24:34.09: empty line received 2025-02-13 02:24:34.09: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-02-13 02:24:34.09: VncKubernetes - vnc_sync - Ingress start 2025-02-13 02:24:34.09: VncKubernetes - vnc_sync - Ingress done 2025-02-13 02:24:34.09: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:24:34.09: IngressMonitor - start process kube event 2025-02-13 02:24:40.62: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:24:40.62: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:24:40.62: PodMonitor - start process kube event 2025-02-13 02:24:40.62: empty line received 2025-02-13 02:24:40.62: PodMonitor - start process kube event 2025-02-13 02:25:09.28: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:25:09.28: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:25:09.28: PodMonitor - start process kube event 2025-02-13 02:25:09.28: empty line received 2025-02-13 02:25:09.28: PodMonitor - start process kube event 2025-02-13 02:25:30.93: ServiceMonitor - Received BOOKMARK: oldResVer=11397 newResVer=12325 2025-02-13 02:25:30.93: ServiceMonitor - start process kube event 2025-02-13 02:25:30.93: empty line received 2025-02-13 02:25:30.93: ServiceMonitor - start process kube event 2025-02-13 02:25:31.05: NamespaceMonitor - Received BOOKMARK: oldResVer=11468 newResVer=11468 2025-02-13 02:25:31.05: NamespaceMonitor - start process kube event 2025-02-13 02:25:31.05: empty line received 2025-02-13 02:25:31.05: NamespaceMonitor - start process kube event 2025-02-13 02:25:31.07: PodMonitor - Received BOOKMARK: oldResVer=12129 newResVer=12318 2025-02-13 02:25:31.07: PodMonitor - start process kube event 2025-02-13 02:25:31.07: empty line received 2025-02-13 02:25:31.07: PodMonitor - start process kube event 2025-02-13 02:25:32.28: NetworkMonitor - Received BOOKMARK: oldResVer=11745 newResVer=11745 2025-02-13 02:25:32.28: NetworkMonitor - start process kube event 2025-02-13 02:25:32.28: empty line received 2025-02-13 02:25:32.28: NetworkMonitor - start process kube event 2025-02-13 02:25:32.85: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11831 newResVer=11831 2025-02-13 02:25:32.85: NetworkPolicyMonitor - start process kube event 2025-02-13 02:25:32.85: NetworkPolicyMonitor - _schedule_vnc_sync 2025-02-13 02:25:32.85: empty line received 2025-02-13 02:25:32.85: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-02-13 02:25:32.85: VncKubernetes - vnc_sync - NetworkPolicy start 2025-02-13 02:25:32.85: NetworkPolicyMonitor - start process kube event 2025-02-13 02:25:32.85: VncKubernetes - vnc_sync - NetworkPolicy done 2025-02-13 02:25:32.85: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:25:33.82: EndPointMonitor - Received BOOKMARK: oldResVer=11440 newResVer=11440 2025-02-13 02:25:33.82: EndPointMonitor - start process kube event 2025-02-13 02:25:33.83: empty line received 2025-02-13 02:25:33.83: EndPointMonitor - start process kube event 2025-02-13 02:25:34.05: IngressMonitor - Received BOOKMARK: oldResVer=11848 newResVer=11848 2025-02-13 02:25:34.05: IngressMonitor - start process kube event 2025-02-13 02:25:34.05: empty line received 2025-02-13 02:25:34.05: IngressMonitor - start process kube event 2025-02-13 02:25:40.01: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:25:40.01: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:25:40.01: PodMonitor - start process kube event 2025-02-13 02:25:40.01: PodMonitor - _schedule_vnc_sync 2025-02-13 02:25:40.01: empty line received 2025-02-13 02:25:40.01: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-02-13 02:25:40.01: VncKubernetes - vnc_sync - Pod start 2025-02-13 02:25:40.01: VncKubernetes - vnc_sync - Pod done 2025-02-13 02:25:40.01: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:25:40.01: PodMonitor - start process kube event 2025-02-13 02:25:53.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:25:53.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:25:53.59: PodMonitor - start process kube event 2025-02-13 02:25:53.59: empty line received 2025-02-13 02:25:53.59: PodMonitor - start process kube event 2025-02-13 02:26:09.75: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:26:09.75: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:26:09.75: PodMonitor - start process kube event 2025-02-13 02:26:09.75: empty line received 2025-02-13 02:26:09.75: PodMonitor - start process kube event 2025-02-13 02:26:20.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:26:20.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:26:20.59: PodMonitor - start process kube event 2025-02-13 02:26:20.59: empty line received 2025-02-13 02:26:20.59: PodMonitor - start process kube event 2025-02-13 02:26:30.89: NamespaceMonitor - Received BOOKMARK: oldResVer=11468 newResVer=12404 2025-02-13 02:26:30.89: NamespaceMonitor - start process kube event 2025-02-13 02:26:30.89: empty line received 2025-02-13 02:26:30.89: NamespaceMonitor - start process kube event 2025-02-13 02:26:31.03: PodMonitor - Received BOOKMARK: oldResVer=12318 newResVer=12423 2025-02-13 02:26:31.03: PodMonitor - start process kube event 2025-02-13 02:26:31.03: empty line received 2025-02-13 02:26:31.03: PodMonitor - start process kube event 2025-02-13 02:26:31.38: ServiceMonitor - Received BOOKMARK: oldResVer=12325 newResVer=12325 2025-02-13 02:26:31.38: ServiceMonitor - start process kube event 2025-02-13 02:26:31.38: ServiceMonitor - _schedule_vnc_sync 2025-02-13 02:26:31.38: empty line received 2025-02-13 02:26:31.38: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-02-13 02:26:31.38: VncKubernetes - vnc_sync - Service start 2025-02-13 02:26:31.38: VncKubernetes - vnc_sync - Service done 2025-02-13 02:26:31.38: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:26:31.38: ServiceMonitor - start process kube event 2025-02-13 02:26:32.19: NetworkMonitor - Received BOOKMARK: oldResVer=11745 newResVer=11745 2025-02-13 02:26:32.19: NetworkMonitor - start process kube event 2025-02-13 02:26:32.19: NetworkMonitor - _schedule_vnc_sync 2025-02-13 02:26:32.19: empty line received 2025-02-13 02:26:32.19: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-02-13 02:26:32.19: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-02-13 02:26:32.19: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:26:32.19: NetworkMonitor - start process kube event 2025-02-13 02:26:32.82: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11831 newResVer=11831 2025-02-13 02:26:32.82: NetworkPolicyMonitor - start process kube event 2025-02-13 02:26:32.82: empty line received 2025-02-13 02:26:32.82: NetworkPolicyMonitor - start process kube event 2025-02-13 02:26:33.73: EndPointMonitor - Received BOOKMARK: oldResVer=11440 newResVer=12373 2025-02-13 02:26:33.73: EndPointMonitor - start process kube event 2025-02-13 02:26:33.73: EndPointMonitor - _schedule_vnc_sync 2025-02-13 02:26:33.73: empty line received 2025-02-13 02:26:33.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-02-13 02:26:33.73: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-02-13 02:26:33.73: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:26:33.73: EndPointMonitor - start process kube event 2025-02-13 02:26:34.72: IngressMonitor - Received BOOKMARK: oldResVer=11848 newResVer=11848 2025-02-13 02:26:34.72: IngressMonitor - start process kube event 2025-02-13 02:26:34.72: empty line received 2025-02-13 02:26:34.72: IngressMonitor - start process kube event 2025-02-13 02:27:30.97: ServiceMonitor - Received BOOKMARK: oldResVer=12325 newResVer=12325 2025-02-13 02:27:30.97: ServiceMonitor - start process kube event 2025-02-13 02:27:30.97: empty line received 2025-02-13 02:27:30.97: ServiceMonitor - start process kube event 2025-02-13 02:27:31.37: NamespaceMonitor - Received BOOKMARK: oldResVer=12404 newResVer=12404 2025-02-13 02:27:31.37: NamespaceMonitor - start process kube event 2025-02-13 02:27:31.37: empty line received 2025-02-13 02:27:31.37: NamespaceMonitor - start process kube event 2025-02-13 02:27:31.65: PodMonitor - Received BOOKMARK: oldResVer=12423 newResVer=12423 2025-02-13 02:27:31.65: PodMonitor - start process kube event 2025-02-13 02:27:31.65: empty line received 2025-02-13 02:27:31.65: PodMonitor - start process kube event 2025-02-13 02:27:32.46: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11831 newResVer=11831 2025-02-13 02:27:32.46: NetworkPolicyMonitor - start process kube event 2025-02-13 02:27:32.46: empty line received 2025-02-13 02:27:32.46: NetworkPolicyMonitor - start process kube event 2025-02-13 02:27:32.47: NetworkMonitor - Received BOOKMARK: oldResVer=11745 newResVer=11745 2025-02-13 02:27:32.47: NetworkMonitor - start process kube event 2025-02-13 02:27:32.47: empty line received 2025-02-13 02:27:32.47: NetworkMonitor - start process kube event 2025-02-13 02:27:33.16: EndPointMonitor - Received BOOKMARK: oldResVer=12373 newResVer=12373 2025-02-13 02:27:33.16: EndPointMonitor - start process kube event 2025-02-13 02:27:33.16: empty line received 2025-02-13 02:27:33.16: EndPointMonitor - start process kube event 2025-02-13 02:27:34.18: IngressMonitor - Received BOOKMARK: oldResVer=11848 newResVer=11848 2025-02-13 02:27:34.18: IngressMonitor - start process kube event 2025-02-13 02:27:34.18: empty line received 2025-02-13 02:27:34.18: IngressMonitor - start process kube event 2025-02-13 02:27:56.22: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:27:56.22: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:27:56.22: PodMonitor - start process kube event 2025-02-13 02:27:56.22: empty line received 2025-02-13 02:27:56.22: PodMonitor - start process kube event 2025-02-13 02:28:09.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-6qdbb:01a5cd1a-923d-445b-95c9-796a9784ed70 2025-02-13 02:28:09.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-6qdbb (hostNetwork=True) 2025-02-13 02:28:09.59: PodMonitor - start process kube event 2025-02-13 02:28:09.59: empty line received 2025-02-13 02:28:09.59: PodMonitor - start process kube event 2025-02-13 02:28:31.67: ServiceMonitor - Received BOOKMARK: oldResVer=12325 newResVer=12325 2025-02-13 02:28:31.67: ServiceMonitor - start process kube event 2025-02-13 02:28:31.67: empty line received 2025-02-13 02:28:31.67: ServiceMonitor - start process kube event 2025-02-13 02:28:31.69: PodMonitor - Received BOOKMARK: oldResVer=12423 newResVer=12578 2025-02-13 02:28:31.69: PodMonitor - start process kube event 2025-02-13 02:28:31.69: empty line received 2025-02-13 02:28:31.69: PodMonitor - start process kube event 2025-02-13 02:28:31.74: NetworkMonitor - Received BOOKMARK: oldResVer=11745 newResVer=11745 2025-02-13 02:28:31.74: NetworkMonitor - start process kube event 2025-02-13 02:28:31.74: empty line received 2025-02-13 02:28:31.74: NetworkMonitor - start process kube event 2025-02-13 02:28:31.80: NamespaceMonitor - Received BOOKMARK: oldResVer=12404 newResVer=12404 2025-02-13 02:28:31.80: NamespaceMonitor - start process kube event 2025-02-13 02:28:31.80: NamespaceMonitor - _schedule_vnc_sync 2025-02-13 02:28:31.80: empty line received 2025-02-13 02:28:31.80: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-02-13 02:28:31.80: VncKubernetes - vnc_sync - Namespace start 2025-02-13 02:28:31.80: VncKubernetes - vnc_sync - Namespace done 2025-02-13 02:28:31.80: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:28:31.80: NamespaceMonitor - start process kube event 2025-02-13 02:28:32.31: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11831 newResVer=11831 2025-02-13 02:28:32.31: NetworkPolicyMonitor - start process kube event 2025-02-13 02:28:32.31: empty line received 2025-02-13 02:28:32.31: NetworkPolicyMonitor - start process kube event 2025-02-13 02:28:32.94: EndPointMonitor - Received BOOKMARK: oldResVer=12373 newResVer=12373 2025-02-13 02:28:32.94: EndPointMonitor - start process kube event 2025-02-13 02:28:32.94: empty line received 2025-02-13 02:28:32.94: EndPointMonitor - start process kube event 2025-02-13 02:28:34.30: IngressMonitor - Received BOOKMARK: oldResVer=11848 newResVer=11848 2025-02-13 02:28:34.30: IngressMonitor - start process kube event 2025-02-13 02:28:34.30: IngressMonitor - _schedule_vnc_sync 2025-02-13 02:28:34.30: empty line received 2025-02-13 02:28:34.30: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-02-13 02:28:34.30: VncKubernetes - vnc_sync - Ingress start 2025-02-13 02:28:34.30: VncKubernetes - vnc_sync - Ingress done 2025-02-13 02:28:34.30: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:28:34.30: IngressMonitor - start process kube event 2025-02-13 02:29:30.95: NamespaceMonitor - Received BOOKMARK: oldResVer=12404 newResVer=12404 2025-02-13 02:29:30.95: NamespaceMonitor - start process kube event 2025-02-13 02:29:30.95: empty line received 2025-02-13 02:29:30.95: NamespaceMonitor - start process kube event 2025-02-13 02:29:30.97: ServiceMonitor - Received BOOKMARK: oldResVer=12325 newResVer=12325 2025-02-13 02:29:30.97: ServiceMonitor - start process kube event 2025-02-13 02:29:30.97: empty line received 2025-02-13 02:29:30.97: ServiceMonitor - start process kube event 2025-02-13 02:29:31.25: PodMonitor - Received BOOKMARK: oldResVer=12578 newResVer=12578 2025-02-13 02:29:31.25: PodMonitor - start process kube event 2025-02-13 02:29:31.25: empty line received 2025-02-13 02:29:31.25: PodMonitor - start process kube event 2025-02-13 02:29:32.03: NetworkMonitor - Received BOOKMARK: oldResVer=11745 newResVer=12632 2025-02-13 02:29:32.03: NetworkMonitor - start process kube event 2025-02-13 02:29:32.03: empty line received 2025-02-13 02:29:32.03: NetworkMonitor - start process kube event 2025-02-13 02:29:32.22: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11831 newResVer=11831 2025-02-13 02:29:32.22: NetworkPolicyMonitor - start process kube event 2025-02-13 02:29:32.22: empty line received 2025-02-13 02:29:32.22: NetworkPolicyMonitor - start process kube event 2025-02-13 02:29:32.90: EndPointMonitor - Received BOOKMARK: oldResVer=12373 newResVer=12373 2025-02-13 02:29:32.90: EndPointMonitor - start process kube event 2025-02-13 02:29:32.90: empty line received 2025-02-13 02:29:32.90: EndPointMonitor - start process kube event 2025-02-13 02:29:34.20: IngressMonitor - Received BOOKMARK: oldResVer=11848 newResVer=11848 2025-02-13 02:29:34.20: IngressMonitor - start process kube event 2025-02-13 02:29:34.20: empty line received 2025-02-13 02:29:34.20: IngressMonitor - start process kube event 2025-02-13 02:30:30.90: NamespaceMonitor - Received BOOKMARK: oldResVer=12404 newResVer=12404 2025-02-13 02:30:30.90: NamespaceMonitor - start process kube event 2025-02-13 02:30:30.90: empty line received 2025-02-13 02:30:30.90: NamespaceMonitor - start process kube event 2025-02-13 02:30:31.70: ServiceMonitor - Received BOOKMARK: oldResVer=12325 newResVer=12325 2025-02-13 02:30:31.70: ServiceMonitor - start process kube event 2025-02-13 02:30:31.70: ServiceMonitor - _schedule_vnc_sync 2025-02-13 02:30:31.70: empty line received 2025-02-13 02:30:31.70: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-02-13 02:30:31.70: VncKubernetes - vnc_sync - Service start 2025-02-13 02:30:31.70: VncKubernetes - vnc_sync - Service done 2025-02-13 02:30:31.70: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:30:31.70: ServiceMonitor - start process kube event 2025-02-13 02:30:31.96: NetworkMonitor - Received BOOKMARK: oldResVer=12632 newResVer=12632 2025-02-13 02:30:31.96: NetworkMonitor - start process kube event 2025-02-13 02:30:31.96: empty line received 2025-02-13 02:30:31.96: NetworkMonitor - start process kube event 2025-02-13 02:30:31.96: PodMonitor - Received BOOKMARK: oldResVer=12578 newResVer=12578 2025-02-13 02:30:31.96: PodMonitor - start process kube event 2025-02-13 02:30:31.96: PodMonitor - _schedule_vnc_sync 2025-02-13 02:30:31.96: empty line received 2025-02-13 02:30:31.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-02-13 02:30:31.96: VncKubernetes - vnc_sync - Pod start 2025-02-13 02:30:31.96: VncKubernetes - vnc_sync - Pod done 2025-02-13 02:30:31.96: VncKubernetes - wait event (qsize=0 timeout=120) 2025-02-13 02:30:31.96: PodMonitor - start process kube event