INFO: =================== Thu Jan 16 01:55:52 UTC 2025 ===================
INFO: Waiting for cassandra 2/30
INFO: Waiting for cassandra 3/30
INFO: Waiting for cassandra 4/30
INFO: Waiting for cassandra 5/30
INFO: Waiting for cassandra 6/30
INFO: Waiting for cassandra 7/30
INFO: Waiting for cassandra 8/30
INFO: Waiting for cassandra 9/30
INFO: Cassandra is connected
/usr/local/lib/python3.6/site-packages/cfgm_common/vnc_kombu.py:10: MonkeyPatchWarning: Patching more than once will result in the union of all True parameters being patched
  gevent.monkey.patch_all()
01/16/2025 01:57:21.862 7f307c81ffc8 [contrail-kube-manager] [INFO]: SANDESH: CONNECT TO COLLECTOR: True
01/16/2025 01:57:22.152 7f307c81ffc8 [contrail-kube-manager] [INFO]: SANDESH: Logging: LEVEL: [SYS_INFO] -> [SYS_NOTICE]
2025-01-16 01:57:22.62: KubeMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 01:57:22.62: KubeMonitor - Connect Kube API result 0
2025-01-16 01:57:22.71: KubeMonitor - KubeMonitor init done: url=https://10.0.0.12:6443/api/v1
2025-01-16 01:57:22.71: NamespaceMonitor - KubeMonitor init done: url=https://10.0.0.12:6443/api/v1
2025-01-16 01:57:22.72: NetworkMonitor - KubeMonitor init done: url=https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1
2025-01-16 01:57:22.73: PodMonitor - KubeMonitor init done: url=https://10.0.0.12:6443/api/v1
2025-01-16 01:57:22.73: ServiceMonitor - KubeMonitor init done: url=https://10.0.0.12:6443/api/v1
2025-01-16 01:57:22.74: NetworkPolicyMonitor - KubeMonitor init done: url=https://10.0.0.12:6443/apis/networking.k8s.io/v1
2025-01-16 01:57:22.74: EndPointMonitor - KubeMonitor init done: url=https://10.0.0.12:6443/api/v1
2025-01-16 01:57:22.75: IngressMonitor - KubeMonitor init done: url=https://10.0.0.12:6443/apis/networking.k8s.io/v1
2025-01-16 01:57:22.75: VncKubernetes - vnc_connect starting
2025-01-16 01:57:22.77: VncKubernetes - vnc_connect failed: 
2025-01-16 01:57:25.80: VncKubernetes - vnc_connect failed: 
2025-01-16 01:57:28.83: VncKubernetes - vnc_connect failed: 
2025-01-16 01:57:31.85: VncKubernetes - vnc_connect failed: 
2025-01-16 01:57:34.88: VncKubernetes - vnc_connect failed: 
2025-01-16 01:57:37.91: VncKubernetes - vnc_connect failed: 
2025-01-16 01:57:40.93: VncKubernetes - vnc_connect failed: 
2025-01-16 01:57:44.04: VncKubernetes - vnc_connect failed: 
2025-01-16 01:57:47.09: VncKubernetes - vnc_connect failed: 
2025-01-16 01:57:50.11: VncKubernetes - vnc_connect failed: 
2025-01-16 01:57:53.14: VncKubernetes - vnc_connect failed: 
2025-01-16 01:57:56.17: VncKubernetes - vnc_connect done
2025-01-16 01:57:56.66: default-domain domain available.
2025-01-16 01:58:09.52: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 01:58:09.52: NamespaceMonitor - start process kube event
2025-01-16 01:58:09.52: NamespaceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-01-16 01:58:09.52: NamespaceMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 01:58:09.52: NetworkMonitor - start process kube event
2025-01-16 01:58:09.52: NetworkMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-01-16 01:58:09.52: NetworkMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 01:58:09.52: PodMonitor - start process kube event
2025-01-16 01:58:09.52: PodMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-01-16 01:58:09.52: PodMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 01:58:09.52: ServiceMonitor - start process kube event
2025-01-16 01:58:09.52: ServiceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-01-16 01:58:09.52: ServiceMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 01:58:09.52: NetworkPolicyMonitor - start process kube event
2025-01-16 01:58:09.52: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-01-16 01:58:09.52: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 01:58:09.52: EndPointMonitor - start process kube event
2025-01-16 01:58:09.52: EndPointMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-01-16 01:58:09.52: EndPointMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 01:58:09.52: IngressMonitor - start process kube event
2025-01-16 01:58:09.52: IngressMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-01-16 01:58:09.52: IngressMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 01:58:09.52: IngressMonitor - Connect Kube API result 0
2025-01-16 01:58:09.52: IngressMonitor - Start init url=https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses resource_version=None
2025-01-16 01:58:09.53: EndPointMonitor - Connect Kube API result 0
2025-01-16 01:58:09.53: EndPointMonitor - Start init url=https://10.0.0.12:6443/api/v1/endpoints resource_version=None
2025-01-16 01:58:09.53: NetworkPolicyMonitor - Connect Kube API result 0
2025-01-16 01:58:09.53: NetworkPolicyMonitor - Start init url=https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies resource_version=None
2025-01-16 01:58:09.53: ServiceMonitor - Connect Kube API result 0
2025-01-16 01:58:09.53: ServiceMonitor - Start init url=https://10.0.0.12:6443/api/v1/services resource_version=None
2025-01-16 01:58:09.53: PodMonitor - Connect Kube API result 0
2025-01-16 01:58:09.53: PodMonitor - Start init url=https://10.0.0.12:6443/api/v1/pods resource_version=None
2025-01-16 01:58:09.53: NetworkMonitor - Connect Kube API result 0
2025-01-16 01:58:09.54: NamespaceMonitor - Connect Kube API result 0
2025-01-16 01:58:09.54: NamespaceMonitor - Start init url=https://10.0.0.12:6443/api/v1/namespaces resource_version=None
2025-01-16 01:58:09.60: NetworkPolicyMonitor - Done init url=https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies, resource_version=9932
2025-01-16 01:58:09.60: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 01:58:09.60: NetworkPolicyMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 01:58:09.60: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 01:58:09.60: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 01:58:09.61: NetworkPolicyMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 01:58:09.61: IngressMonitor - Done init url=https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses, resource_version=9932
2025-01-16 01:58:09.61: IngressMonitor - _schedule_vnc_sync
2025-01-16 01:58:09.61: IngressMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 01:58:09.63: NamespaceMonitor - Got ADDED Namespace None:default:b0c43f3d-847c-4e7c-9191-a891f96b1529
2025-01-16 01:58:09.64: EndPointMonitor - Got ADDED Endpoints default:kubernetes:4686b634-d302-4a85-843d-fcca8b6bac65
2025-01-16 01:58:09.64: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 01:58:09.64: VncKubernetes - wait event (qsize=3 timeout=120)
2025-01-16 01:58:09.64: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 01:58:09.64: VncKubernetes - vnc_sync - Ingress start
2025-01-16 01:58:09.64: VncKubernetes - vnc_sync - Ingress done
2025-01-16 01:58:09.64: VncKubernetes - wait event (qsize=2 timeout=120)
2025-01-16 01:58:09.64: VncKubernetes - Process event (name=default event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace default:b0c43f3d-847c-4e7c-9191-a891f96b1529
2025-01-16 01:58:09.65: IngressMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 01:58:09.65: PodMonitor - Skipped ADDED Pod kube-system:config-zookeeper-t7gdd (hostNetwork=True)
2025-01-16 01:58:09.66: ServiceMonitor - Got ADDED Service default:kubernetes:5b0bdf3b-ffab-4b56-8889-421af4c17afd
2025-01-16 01:58:09.66: NetworkMonitor - Start init url=https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions resource_version=None
2025-01-16 01:58:09.66: ServiceMonitor - Got ADDED Service kube-system:coredns:148978fe-bdb6-4f48-b2f8-2ef2ecdc030c
2025-01-16 01:58:09.66: ServiceMonitor - Done init url=https://10.0.0.12:6443/api/v1/services, resource_version=9932
2025-01-16 01:58:09.66: ServiceMonitor - _schedule_vnc_sync
2025-01-16 01:58:09.66: ServiceMonitor - Start Watching request https://10.0.0.12:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 01:58:09.67: EndPointMonitor - Got ADDED Endpoints kube-system:coredns:97a753c5-9050-4879-a5e6-8df49581204c
2025-01-16 01:58:09.67: EndPointMonitor - Done init url=https://10.0.0.12:6443/api/v1/endpoints, resource_version=9932
2025-01-16 01:58:09.67: EndPointMonitor - _schedule_vnc_sync
2025-01-16 01:58:09.67: EndPointMonitor - Start Watching request https://10.0.0.12:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 01:58:09.67: PodMonitor - Skipped ADDED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 01:58:09.68: NamespaceMonitor - Got ADDED Namespace None:kube-node-lease:933bd9fe-951f-4fb9-8e09-a698a12f3e04
2025-01-16 01:58:09.68: HTTPError: NetworkMonitor - invalidate resourceVersion None (response 410)
2025-01-16 01:58:09.68: NetworkMonitor - start process kube event
2025-01-16 01:58:09.68: NetworkMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-01-16 01:58:09.68: NetworkMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 01:58:09.68: NetworkMonitor - Connect Kube API result 0
2025-01-16 01:58:09.69: ServiceMonitor - Watches https://10.0.0.12:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 01:58:09.69: EndPointMonitor - Watches https://10.0.0.12:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 01:58:09.69: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-alarm-2ksmm (hostNetwork=True)
2025-01-16 01:58:09.69: NamespaceMonitor - Got ADDED Namespace None:kube-public:e6933852-acf2-4444-98d1-1573c5a2ce14
2025-01-16 01:58:09.70: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-m24d8 (hostNetwork=True)
2025-01-16 01:58:09.70: NetworkMonitor - Start init url=https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions resource_version=None
2025-01-16 01:58:09.71: NamespaceMonitor - Got ADDED Namespace None:kube-system:2f48b348-648f-49f3-a195-477190cb2e3f
2025-01-16 01:58:09.71: NamespaceMonitor - Done init url=https://10.0.0.12:6443/api/v1/namespaces, resource_version=9932
2025-01-16 01:58:09.71: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 01:58:09.71: NamespaceMonitor - Start Watching request https://10.0.0.12:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 01:58:09.71: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-snmp-bpc4h (hostNetwork=True)
2025-01-16 01:58:09.71: NamespaceMonitor - Watches https://10.0.0.12:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 01:58:09.72: PodMonitor - Skipped ADDED Pod kube-system:contrail-analyticsdb-qf9hb (hostNetwork=True)
2025-01-16 01:58:09.73: NetworkMonitor - Done init url=https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions, resource_version=9936
2025-01-16 01:58:09.73: NetworkMonitor - _schedule_vnc_sync
2025-01-16 01:58:09.73: NetworkMonitor - Start Watching request https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})(timeout=120)
2025-01-16 01:58:09.73: PodMonitor - Skipped ADDED Pod kube-system:contrail-configdb-6skpn (hostNetwork=True)
2025-01-16 01:58:09.74: NetworkMonitor - Watches https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})
2025-01-16 01:58:09.74: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-config-7hdpr (hostNetwork=True)
2025-01-16 01:58:09.75: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-control-l8m8z (hostNetwork=True)
2025-01-16 01:58:09.76: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-webui-lwjqw (hostNetwork=True)
2025-01-16 01:58:09.77: PodMonitor - Skipped ADDED Pod kube-system:contrail-kube-manager-t92km (hostNetwork=True)
2025-01-16 01:58:09.80: PodMonitor - Got ADDED Pod kube-system:coredns-77f7cc69db-jg6wq:d2e24f47-9186-4cc3-872a-078d0e0e42c1
2025-01-16 01:58:09.82: PodMonitor - Got ADDED Pod kube-system:dns-autoscaler-595558c478-77fsg:1ab2987c-9c8c-4360-a47c-052ce409bc38
2025-01-16 01:58:09.83: PodMonitor - Skipped ADDED Pod kube-system:kube-apiserver-cn-jenkins-deploy-platform-k8s-manifests-127-1 (hostNetwork=True)
2025-01-16 01:58:09.85: PodMonitor - Skipped ADDED Pod kube-system:kube-controller-manager-cn-jenkins-deploy-platform-k8s-manifests-127-1 (hostNetwork=True)
2025-01-16 01:58:09.87: PodMonitor - Skipped ADDED Pod kube-system:kube-proxy-twlt8 (hostNetwork=True)
2025-01-16 01:58:09.89: PodMonitor - Skipped ADDED Pod kube-system:kube-scheduler-cn-jenkins-deploy-platform-k8s-manifests-127-1 (hostNetwork=True)
2025-01-16 01:58:09.90: PodMonitor - Skipped ADDED Pod kube-system:rabbitmq-b8psm (hostNetwork=True)
2025-01-16 01:58:09.91: PodMonitor - Skipped ADDED Pod kube-system:redis-lj8hc (hostNetwork=True)
2025-01-16 01:58:09.91: PodMonitor - Done init url=https://10.0.0.12:6443/api/v1/pods, resource_version=9932
2025-01-16 01:58:09.91: PodMonitor - _schedule_vnc_sync
2025-01-16 01:58:09.91: PodMonitor - Start Watching request https://10.0.0.12:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 01:58:09.92: PodMonitor - Watches https://10.0.0.12:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 01:58:14.43: VncKubernetes - wait event (qsize=14 timeout=120)
2025-01-16 01:58:14.43: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Endpoints ns=default)
VncEndpoints - Got ADDED Endpoints default:kubernetes:4686b634-d302-4a85-843d-fcca8b6bac65
2025-01-16 01:58:14.48: VncKubernetes - wait event (qsize=13 timeout=120)
2025-01-16 01:58:14.48: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Service ns=default)
VncService - Got ADDED Service default:kubernetes:5b0bdf3b-ffab-4b56-8889-421af4c17afd
2025-01-16 01:58:16.40: VncKubernetes - wait event (qsize=12 timeout=120)
2025-01-16 01:58:16.40: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Service ns=kube-system)
VncService - Got ADDED Service kube-system:coredns:148978fe-bdb6-4f48-b2f8-2ef2ecdc030c
2025-01-16 01:58:17.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 01:58:17.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 01:58:17.06: PodMonitor - start process kube event
2025-01-16 01:58:17.06: empty line received
2025-01-16 01:58:17.06: PodMonitor - start process kube event
2025-01-16 01:58:19.31: VncKubernetes - wait event (qsize=11 timeout=120)
2025-01-16 01:58:19.31: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 01:58:19.31: VncKubernetes - vnc_sync - Service start
2025-01-16 01:58:19.31: VncKubernetes - vnc_sync - Service done
2025-01-16 01:58:19.31: VncKubernetes - wait event (qsize=10 timeout=120)
2025-01-16 01:58:19.31: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Endpoints ns=kube-system)
VncEndpoints - Got ADDED Endpoints kube-system:coredns:97a753c5-9050-4879-a5e6-8df49581204c
2025-01-16 01:58:19.42: VncKubernetes - wait event (qsize=9 timeout=120)
2025-01-16 01:58:19.42: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 01:58:19.42: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 01:58:19.42: VncKubernetes - wait event (qsize=8 timeout=120)
2025-01-16 01:58:19.42: VncKubernetes - Process event (name=kube-node-lease event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-node-lease:933bd9fe-951f-4fb9-8e09-a698a12f3e04
2025-01-16 01:58:20.10: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 01:58:20.11: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 01:58:20.11: PodMonitor - start process kube event
2025-01-16 01:58:20.11: empty line received
2025-01-16 01:58:20.11: PodMonitor - start process kube event
2025-01-16 01:58:22.52: VncKubernetes - wait event (qsize=7 timeout=120)
2025-01-16 01:58:22.52: VncKubernetes - Process event (name=kube-public event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-public:e6933852-acf2-4444-98d1-1573c5a2ce14
2025-01-16 01:58:26.16: VncKubernetes - wait event (qsize=6 timeout=120)
2025-01-16 01:58:26.16: VncKubernetes - Process event (name=kube-system event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-system:2f48b348-648f-49f3-a195-477190cb2e3f
2025-01-16 01:58:28.75: VncKubernetes - wait event (qsize=5 timeout=120)
2025-01-16 01:58:28.75: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 01:58:28.75: VncKubernetes - vnc_sync - Namespace start
2025-01-16 01:58:28.75: VncKubernetes - vnc_sync - Namespace done
2025-01-16 01:58:28.75: VncKubernetes - wait event (qsize=4 timeout=120)
2025-01-16 01:58:28.75: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 01:58:28.75: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 01:58:28.75: VncKubernetes - wait event (qsize=3 timeout=120)
2025-01-16 01:58:28.75: VncKubernetes - Process event (name=coredns-77f7cc69db-jg6wq event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:coredns-77f7cc69db-jg6wq:d2e24f47-9186-4cc3-872a-078d0e0e42c1
2025-01-16 01:58:30.73: PodMonitor - Received MODIFIED Pod kube-system:coredns-77f7cc69db-jg6wq:d2e24f47-9186-4cc3-872a-078d0e0e42c1
2025-01-16 01:58:30.73: PodMonitor - Got MODIFIED Pod kube-system:coredns-77f7cc69db-jg6wq:d2e24f47-9186-4cc3-872a-078d0e0e42c1
2025-01-16 01:58:30.73: PodMonitor - start process kube event
2025-01-16 01:58:30.73: empty line received
2025-01-16 01:58:30.73: VncKubernetes - wait event (qsize=3 timeout=120)
2025-01-16 01:58:30.73: VncKubernetes - Process event (name=dns-autoscaler-595558c478-77fsg event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:dns-autoscaler-595558c478-77fsg:1ab2987c-9c8c-4360-a47c-052ce409bc38
2025-01-16 01:58:30.73: PodMonitor - start process kube event
2025-01-16 01:58:32.22: VncKubernetes - wait event (qsize=2 timeout=120)
2025-01-16 01:58:32.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-01-16 01:58:32.22: VncKubernetes - vnc_sync - Pod start
2025-01-16 01:58:32.22: VncKubernetes - vnc_sync - Pod done
2025-01-16 01:58:32.22: VncKubernetes - wait event (qsize=1 timeout=120)
2025-01-16 01:58:32.22: VncKubernetes - Process event (name=coredns-77f7cc69db-jg6wq event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:coredns-77f7cc69db-jg6wq:d2e24f47-9186-4cc3-872a-078d0e0e42c1
2025-01-16 01:58:32.22: PodMonitor - Received MODIFIED Pod kube-system:dns-autoscaler-595558c478-77fsg:1ab2987c-9c8c-4360-a47c-052ce409bc38
2025-01-16 01:58:32.23: PodMonitor - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-77fsg:1ab2987c-9c8c-4360-a47c-052ce409bc38
2025-01-16 01:58:32.23: PodMonitor - start process kube event
2025-01-16 01:58:32.23: empty line received
2025-01-16 01:58:32.23: PodMonitor - start process kube event
2025-01-16 01:58:32.33: VncKubernetes - wait event (qsize=1 timeout=120)
2025-01-16 01:58:32.33: VncKubernetes - Process event (name=dns-autoscaler-595558c478-77fsg event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-77fsg:1ab2987c-9c8c-4360-a47c-052ce409bc38
2025-01-16 01:58:32.44: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 01:58:34.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 01:58:34.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 01:58:34.06: PodMonitor - start process kube event
2025-01-16 01:58:34.06: empty line received
2025-01-16 01:58:34.06: PodMonitor - start process kube event
2025-01-16 01:58:34.56: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 01:58:34.56: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 01:58:34.56: PodMonitor - start process kube event
2025-01-16 01:58:34.56: empty line received
2025-01-16 01:58:34.56: PodMonitor - start process kube event
2025-01-16 01:58:35.62: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 01:58:35.62: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 01:58:35.62: PodMonitor - start process kube event
2025-01-16 01:58:35.62: empty line received
2025-01-16 01:58:35.62: PodMonitor - start process kube event
2025-01-16 01:58:52.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 01:58:52.05: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 01:58:52.05: PodMonitor - start process kube event
2025-01-16 01:58:52.05: empty line received
2025-01-16 01:58:52.05: PodMonitor - start process kube event
2025-01-16 01:59:09.74: PodMonitor - Received BOOKMARK: oldResVer=9932 newResVer=10008
2025-01-16 01:59:09.74: PodMonitor - start process kube event
2025-01-16 01:59:09.74: empty line received
2025-01-16 01:59:09.74: PodMonitor - start process kube event
2025-01-16 01:59:10.20: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9932 newResVer=9958
2025-01-16 01:59:10.21: NetworkPolicyMonitor - start process kube event
2025-01-16 01:59:10.21: empty line received
2025-01-16 01:59:10.21: NetworkPolicyMonitor - start process kube event
2025-01-16 01:59:33.11: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 01:59:33.11: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 01:59:33.11: PodMonitor - start process kube event
2025-01-16 01:59:33.11: empty line received
2025-01-16 01:59:33.11: PodMonitor - start process kube event
2025-01-16 01:59:35.20: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 01:59:35.20: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 01:59:35.20: PodMonitor - start process kube event
2025-01-16 01:59:35.20: empty line received
2025-01-16 01:59:35.20: PodMonitor - start process kube event
2025-01-16 01:59:47.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 01:59:47.05: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 01:59:47.05: PodMonitor - start process kube event
2025-01-16 01:59:47.05: empty line received
2025-01-16 01:59:47.05: PodMonitor - start process kube event
2025-01-16 01:59:51.61: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 01:59:51.61: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 01:59:51.61: PodMonitor - start process kube event
2025-01-16 01:59:51.61: empty line received
2025-01-16 01:59:51.61: PodMonitor - start process kube event
2025-01-16 02:00:06.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:00:06.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:00:06.06: PodMonitor - start process kube event
2025-01-16 02:00:06.06: empty line received
2025-01-16 02:00:06.06: PodMonitor - start process kube event
2025-01-16 02:00:07.03: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:00:07.03: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:00:07.03: PodMonitor - start process kube event
2025-01-16 02:00:07.03: empty line received
2025-01-16 02:00:07.03: PodMonitor - start process kube event
2025-01-16 02:00:09.65: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:00:09.65: IngressMonitor - start process kube event
2025-01-16 02:00:09.65: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:00:09.65: IngressMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:00:09.65: IngressMonitor - Connect Kube API result 0
2025-01-16 02:00:09.65: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:00:09.65: IngressMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:00:09.65: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:00:09.65: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:00:09.65: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:00:09.65: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:00:09.66: IngressMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:00:09.69: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:00:09.69: ServiceMonitor - start process kube event
2025-01-16 02:00:09.69: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:00:09.69: ServiceMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:00:09.69: ServiceMonitor - Connect Kube API result 0
2025-01-16 02:00:09.69: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:00:09.69: ServiceMonitor - Start Watching request https://10.0.0.12:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:00:09.69: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:00:09.69: VncKubernetes - vnc_sync - Service start
2025-01-16 02:00:09.69: VncKubernetes - vnc_sync - Service done
2025-01-16 02:00:09.69: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:00:09.69: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:00:09.70: EndPointMonitor - start process kube event
2025-01-16 02:00:09.70: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:00:09.70: EndPointMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:00:09.70: EndPointMonitor - Connect Kube API result 0
2025-01-16 02:00:09.70: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:00:09.70: EndPointMonitor - Start Watching request https://10.0.0.12:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:00:09.70: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:00:09.70: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:00:09.70: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:00:09.70: ServiceMonitor - Watches https://10.0.0.12:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:00:09.71: EndPointMonitor - Watches https://10.0.0.12:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:00:09.72: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:00:09.72: NamespaceMonitor - start process kube event
2025-01-16 02:00:09.72: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:00:09.72: NamespaceMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:00:09.72: NamespaceMonitor - Connect Kube API result 0
2025-01-16 02:00:09.72: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:00:09.72: NamespaceMonitor - Start Watching request https://10.0.0.12:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:00:09.72: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:00:09.72: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:00:09.72: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:00:09.72: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:00:09.72: NamespaceMonitor - Watches https://10.0.0.12:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:00:09.74: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:00:09.74: NetworkMonitor - start process kube event
2025-01-16 02:00:09.74: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9936
2025-01-16 02:00:09.74: NetworkMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:00:09.74: NetworkMonitor - Connect Kube API result 0
2025-01-16 02:00:09.74: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:00:09.74: NetworkMonitor - Start Watching request https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})(timeout=120)
2025-01-16 02:00:09.74: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:00:09.74: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:00:09.74: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:00:09.75: NetworkMonitor - Watches https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})
2025-01-16 02:00:09.96: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9958 newResVer=9958
2025-01-16 02:00:09.96: NetworkPolicyMonitor - start process kube event
2025-01-16 02:00:09.96: empty line received
2025-01-16 02:00:09.96: NetworkPolicyMonitor - start process kube event
2025-01-16 02:00:10.12: PodMonitor - Received BOOKMARK: oldResVer=10008 newResVer=10121
2025-01-16 02:00:10.12: PodMonitor - start process kube event
2025-01-16 02:00:10.12: empty line received
2025-01-16 02:00:10.12: PodMonitor - start process kube event
2025-01-16 02:00:18.37: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:00:18.37: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:00:18.37: PodMonitor - start process kube event
2025-01-16 02:00:18.37: empty line received
2025-01-16 02:00:18.37: PodMonitor - start process kube event
2025-01-16 02:01:06.61: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:01:06.61: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:01:06.61: PodMonitor - start process kube event
2025-01-16 02:01:06.61: empty line received
2025-01-16 02:01:06.61: PodMonitor - start process kube event
2025-01-16 02:01:09.78: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9958 newResVer=9958
2025-01-16 02:01:09.78: NetworkPolicyMonitor - start process kube event
2025-01-16 02:01:09.78: empty line received
2025-01-16 02:01:09.78: NetworkPolicyMonitor - start process kube event
2025-01-16 02:01:10.39: PodMonitor - Received BOOKMARK: oldResVer=10121 newResVer=10208
2025-01-16 02:01:10.39: PodMonitor - start process kube event
2025-01-16 02:01:10.39: empty line received
2025-01-16 02:01:10.39: PodMonitor - start process kube event
2025-01-16 02:01:18.98: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:01:18.98: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:01:18.98: PodMonitor - start process kube event
2025-01-16 02:01:18.98: empty line received
2025-01-16 02:01:18.98: PodMonitor - start process kube event
2025-01-16 02:01:33.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:01:33.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:01:33.06: PodMonitor - start process kube event
2025-01-16 02:01:33.06: empty line received
2025-01-16 02:01:33.06: PodMonitor - start process kube event
2025-01-16 02:01:48.82: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:01:48.82: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:01:48.82: PodMonitor - start process kube event
2025-01-16 02:01:48.82: empty line received
2025-01-16 02:01:48.82: PodMonitor - start process kube event
2025-01-16 02:02:03.25: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:02:03.25: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:02:03.25: PodMonitor - start process kube event
2025-01-16 02:02:03.25: empty line received
2025-01-16 02:02:03.25: PodMonitor - start process kube event
2025-01-16 02:02:09.47: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9958 newResVer=9958
2025-01-16 02:02:09.47: NetworkPolicyMonitor - start process kube event
2025-01-16 02:02:09.47: empty line received
2025-01-16 02:02:09.47: NetworkPolicyMonitor - start process kube event
2025-01-16 02:02:09.67: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:02:09.67: IngressMonitor - start process kube event
2025-01-16 02:02:09.67: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:02:09.67: IngressMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:02:09.67: IngressMonitor - Connect Kube API result 0
2025-01-16 02:02:09.67: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:02:09.67: IngressMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:02:09.67: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:02:09.67: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:02:09.67: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:02:09.67: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:02:09.68: IngressMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:02:09.70: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:02:09.70: ServiceMonitor - start process kube event
2025-01-16 02:02:09.70: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:02:09.71: ServiceMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:02:09.71: ServiceMonitor - Connect Kube API result 0
2025-01-16 02:02:09.71: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:02:09.71: ServiceMonitor - Start Watching request https://10.0.0.12:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:02:09.71: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:02:09.71: VncKubernetes - vnc_sync - Service start
2025-01-16 02:02:09.71: VncKubernetes - vnc_sync - Service done
2025-01-16 02:02:09.71: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:02:09.71: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:02:09.71: EndPointMonitor - start process kube event
2025-01-16 02:02:09.71: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:02:09.71: EndPointMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:02:09.71: EndPointMonitor - Connect Kube API result 0
2025-01-16 02:02:09.71: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:02:09.71: EndPointMonitor - Start Watching request https://10.0.0.12:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:02:09.71: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:02:09.71: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:02:09.71: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:02:09.72: EndPointMonitor - Watches https://10.0.0.12:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:02:09.72: ServiceMonitor - Watches https://10.0.0.12:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:02:09.73: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:02:09.73: NamespaceMonitor - start process kube event
2025-01-16 02:02:09.73: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:02:09.73: NamespaceMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:02:09.73: NamespaceMonitor - Connect Kube API result 0
2025-01-16 02:02:09.73: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:02:09.73: NamespaceMonitor - Start Watching request https://10.0.0.12:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:02:09.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:02:09.73: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:02:09.73: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:02:09.73: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:02:09.74: NamespaceMonitor - Watches https://10.0.0.12:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:02:09.75: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:02:09.75: NetworkMonitor - start process kube event
2025-01-16 02:02:09.75: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9936
2025-01-16 02:02:09.75: NetworkMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:02:09.75: NetworkMonitor - Connect Kube API result 0
2025-01-16 02:02:09.75: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:02:09.75: NetworkMonitor - Start Watching request https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})(timeout=120)
2025-01-16 02:02:09.75: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:02:09.75: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:02:09.75: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:02:09.76: NetworkMonitor - Watches https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})
2025-01-16 02:02:10.24: PodMonitor - Received BOOKMARK: oldResVer=10208 newResVer=10294
2025-01-16 02:02:10.24: PodMonitor - start process kube event
2025-01-16 02:02:10.24: PodMonitor - _schedule_vnc_sync
2025-01-16 02:02:10.24: empty line received
2025-01-16 02:02:10.24: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-01-16 02:02:10.24: VncKubernetes - vnc_sync - Pod start
2025-01-16 02:02:10.24: VncKubernetes - vnc_sync - Pod done
2025-01-16 02:02:10.24: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:02:10.24: PodMonitor - start process kube event
2025-01-16 02:02:18.73: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:02:18.73: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:02:18.73: PodMonitor - start process kube event
2025-01-16 02:02:18.73: empty line received
2025-01-16 02:02:18.73: PodMonitor - start process kube event
2025-01-16 02:02:30.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:02:30.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:02:30.06: PodMonitor - start process kube event
2025-01-16 02:02:30.06: empty line received
2025-01-16 02:02:30.06: PodMonitor - start process kube event
2025-01-16 02:02:48.71: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:02:48.71: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:02:48.71: PodMonitor - start process kube event
2025-01-16 02:02:48.71: empty line received
2025-01-16 02:02:48.71: PodMonitor - start process kube event
2025-01-16 02:03:02.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:03:02.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:03:02.06: PodMonitor - start process kube event
2025-01-16 02:03:02.06: empty line received
2025-01-16 02:03:02.06: PodMonitor - start process kube event
2025-01-16 02:03:04.15: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:03:04.15: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:03:04.15: PodMonitor - start process kube event
2025-01-16 02:03:04.15: empty line received
2025-01-16 02:03:04.15: PodMonitor - start process kube event
2025-01-16 02:03:10.44: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9958 newResVer=9958
2025-01-16 02:03:10.44: NetworkPolicyMonitor - start process kube event
2025-01-16 02:03:10.44: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:03:10.44: empty line received
2025-01-16 02:03:10.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:03:10.44: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:03:10.44: NetworkPolicyMonitor - start process kube event
2025-01-16 02:03:10.44: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:03:10.44: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:03:11.11: PodMonitor - Received BOOKMARK: oldResVer=10294 newResVer=10389
2025-01-16 02:03:11.11: PodMonitor - start process kube event
2025-01-16 02:03:11.11: empty line received
2025-01-16 02:03:11.11: PodMonitor - start process kube event
2025-01-16 02:03:15.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:03:15.05: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:03:15.05: PodMonitor - start process kube event
2025-01-16 02:03:15.05: empty line received
2025-01-16 02:03:15.05: PodMonitor - start process kube event
2025-01-16 02:04:09.68: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:04:09.68: IngressMonitor - start process kube event
2025-01-16 02:04:09.68: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:04:09.68: IngressMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:04:09.68: IngressMonitor - Connect Kube API result 0
2025-01-16 02:04:09.68: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:04:09.68: IngressMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:04:09.68: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:04:09.68: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:04:09.68: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:04:09.68: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:04:09.69: IngressMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:04:09.72: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:04:09.72: EndPointMonitor - start process kube event
2025-01-16 02:04:09.73: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:04:09.73: EndPointMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:04:09.73: EndPointMonitor - Connect Kube API result 0
2025-01-16 02:04:09.73: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:04:09.73: EndPointMonitor - Start Watching request https://10.0.0.12:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:04:09.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:04:09.73: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:04:09.73: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:04:09.73: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:04:09.73: ServiceMonitor - start process kube event
2025-01-16 02:04:09.73: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:04:09.73: ServiceMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:04:09.73: ServiceMonitor - Connect Kube API result 0
2025-01-16 02:04:09.73: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:04:09.73: ServiceMonitor - Start Watching request https://10.0.0.12:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:04:09.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:04:09.73: VncKubernetes - vnc_sync - Service start
2025-01-16 02:04:09.73: VncKubernetes - vnc_sync - Service done
2025-01-16 02:04:09.73: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:04:09.74: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:04:09.74: NamespaceMonitor - start process kube event
2025-01-16 02:04:09.74: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:04:09.74: NamespaceMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:04:09.74: NamespaceMonitor - Connect Kube API result 0
2025-01-16 02:04:09.74: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:04:09.74: NamespaceMonitor - Start Watching request https://10.0.0.12:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:04:09.74: EndPointMonitor - Watches https://10.0.0.12:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:04:09.74: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:04:09.74: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:04:09.74: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:04:09.74: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:04:09.74: ServiceMonitor - Watches https://10.0.0.12:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:04:09.75: NamespaceMonitor - Watches https://10.0.0.12:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:04:09.76: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:04:09.76: NetworkMonitor - start process kube event
2025-01-16 02:04:09.76: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9936
2025-01-16 02:04:09.76: NetworkMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:04:09.76: NetworkMonitor - Connect Kube API result 0
2025-01-16 02:04:09.76: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:04:09.76: NetworkMonitor - Start Watching request https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})(timeout=120)
2025-01-16 02:04:09.77: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:04:09.77: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:04:09.77: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:04:09.77: NetworkMonitor - Watches https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})
2025-01-16 02:04:10.42: PodMonitor - Received BOOKMARK: oldResVer=10389 newResVer=10407
2025-01-16 02:04:10.42: PodMonitor - start process kube event
2025-01-16 02:04:10.42: empty line received
2025-01-16 02:04:10.42: PodMonitor - start process kube event
2025-01-16 02:04:10.83: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9958 newResVer=9958
2025-01-16 02:04:10.83: NetworkPolicyMonitor - start process kube event
2025-01-16 02:04:10.83: empty line received
2025-01-16 02:04:10.83: NetworkPolicyMonitor - start process kube event
2025-01-16 02:04:20.19: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:04:20.19: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:04:20.19: PodMonitor - start process kube event
2025-01-16 02:04:20.19: empty line received
2025-01-16 02:04:20.19: PodMonitor - start process kube event
2025-01-16 02:04:35.61: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:04:35.61: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:04:35.61: PodMonitor - start process kube event
2025-01-16 02:04:35.61: empty line received
2025-01-16 02:04:35.61: PodMonitor - start process kube event
2025-01-16 02:05:10.72: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9958 newResVer=9958
2025-01-16 02:05:10.72: NetworkPolicyMonitor - start process kube event
2025-01-16 02:05:10.72: empty line received
2025-01-16 02:05:10.72: NetworkPolicyMonitor - start process kube event
2025-01-16 02:05:11.31: PodMonitor - Received BOOKMARK: oldResVer=10407 newResVer=10525
2025-01-16 02:05:11.31: PodMonitor - start process kube event
2025-01-16 02:05:11.31: empty line received
2025-01-16 02:05:11.31: PodMonitor - start process kube event
2025-01-16 02:05:19.82: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:05:19.82: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:05:19.82: PodMonitor - start process kube event
2025-01-16 02:05:19.82: empty line received
2025-01-16 02:05:19.82: PodMonitor - start process kube event
2025-01-16 02:05:34.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:05:34.05: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:05:34.05: PodMonitor - start process kube event
2025-01-16 02:05:34.05: empty line received
2025-01-16 02:05:34.05: PodMonitor - start process kube event
2025-01-16 02:05:36.33: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:05:36.33: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:05:36.33: PodMonitor - start process kube event
2025-01-16 02:05:36.33: empty line received
2025-01-16 02:05:36.33: PodMonitor - start process kube event
2025-01-16 02:05:48.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:05:48.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:05:48.06: PodMonitor - start process kube event
2025-01-16 02:05:48.06: empty line received
2025-01-16 02:05:48.06: PodMonitor - start process kube event
2025-01-16 02:06:09.69: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:06:09.69: IngressMonitor - start process kube event
2025-01-16 02:06:09.69: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:06:09.69: IngressMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:06:09.69: IngressMonitor - Connect Kube API result 0
2025-01-16 02:06:09.69: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:06:09.69: IngressMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:06:09.69: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:06:09.69: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:06:09.69: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:06:09.69: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:06:09.70: IngressMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:06:09.74: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:06:09.75: EndPointMonitor - start process kube event
2025-01-16 02:06:09.75: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:06:09.75: EndPointMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:06:09.75: EndPointMonitor - Connect Kube API result 0
2025-01-16 02:06:09.75: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:06:09.75: EndPointMonitor - Start Watching request https://10.0.0.12:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:06:09.75: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:06:09.75: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:06:09.75: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:06:09.75: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:06:09.75: ServiceMonitor - start process kube event
2025-01-16 02:06:09.75: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:06:09.75: ServiceMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:06:09.75: ServiceMonitor - Connect Kube API result 0
2025-01-16 02:06:09.75: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:06:09.75: ServiceMonitor - Start Watching request https://10.0.0.12:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:06:09.75: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:06:09.75: VncKubernetes - vnc_sync - Service start
2025-01-16 02:06:09.75: VncKubernetes - vnc_sync - Service done
2025-01-16 02:06:09.75: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:06:09.75: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:06:09.75: NamespaceMonitor - start process kube event
2025-01-16 02:06:09.75: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:06:09.75: NamespaceMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:06:09.75: NamespaceMonitor - Connect Kube API result 0
2025-01-16 02:06:09.75: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:06:09.75: NamespaceMonitor - Start Watching request https://10.0.0.12:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:06:09.75: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:06:09.75: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:06:09.75: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:06:09.75: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:06:09.76: ServiceMonitor - Watches https://10.0.0.12:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:06:09.76: EndPointMonitor - Watches https://10.0.0.12:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:06:09.76: NamespaceMonitor - Watches https://10.0.0.12:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:06:09.78: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:06:09.78: NetworkMonitor - start process kube event
2025-01-16 02:06:09.78: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9936
2025-01-16 02:06:09.78: NetworkMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:06:09.78: NetworkMonitor - Connect Kube API result 0
2025-01-16 02:06:09.78: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:06:09.78: NetworkMonitor - Start Watching request https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})(timeout=120)
2025-01-16 02:06:09.78: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:06:09.78: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:06:09.78: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:06:09.79: NetworkMonitor - Watches https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})
2025-01-16 02:06:10.90: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9958 newResVer=9958
2025-01-16 02:06:10.90: NetworkPolicyMonitor - start process kube event
2025-01-16 02:06:10.90: empty line received
2025-01-16 02:06:10.90: NetworkPolicyMonitor - start process kube event
2025-01-16 02:06:11.66: PodMonitor - Received BOOKMARK: oldResVer=10525 newResVer=10635
2025-01-16 02:06:11.66: PodMonitor - start process kube event
2025-01-16 02:06:11.66: PodMonitor - _schedule_vnc_sync
2025-01-16 02:06:11.66: empty line received
2025-01-16 02:06:11.66: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-01-16 02:06:11.66: VncKubernetes - vnc_sync - Pod start
2025-01-16 02:06:11.66: VncKubernetes - vnc_sync - Pod done
2025-01-16 02:06:11.66: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:06:11.66: PodMonitor - start process kube event
2025-01-16 02:07:09.55: NamespaceMonitor - Received BOOKMARK: oldResVer=9932 newResVer=10649
2025-01-16 02:07:09.55: NamespaceMonitor - start process kube event
2025-01-16 02:07:09.55: empty line received
2025-01-16 02:07:09.55: NamespaceMonitor - start process kube event
2025-01-16 02:07:09.77: ServiceMonitor - Received BOOKMARK: oldResVer=9932 newResVer=10751
2025-01-16 02:07:09.77: ServiceMonitor - start process kube event
2025-01-16 02:07:09.77: empty line received
2025-01-16 02:07:09.77: ServiceMonitor - start process kube event
2025-01-16 02:07:10.86: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9958 newResVer=9958
2025-01-16 02:07:10.86: NetworkPolicyMonitor - start process kube event
2025-01-16 02:07:10.86: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:07:10.86: empty line received
2025-01-16 02:07:10.86: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:07:10.86: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:07:10.86: NetworkPolicyMonitor - start process kube event
2025-01-16 02:07:10.86: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:07:10.86: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:07:12.15: PodMonitor - Received BOOKMARK: oldResVer=10635 newResVer=10635
2025-01-16 02:07:12.15: PodMonitor - start process kube event
2025-01-16 02:07:12.15: empty line received
2025-01-16 02:07:12.15: PodMonitor - start process kube event
2025-01-16 02:07:23.21: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:07:23.21: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:07:23.21: PodMonitor - start process kube event
2025-01-16 02:07:23.21: empty line received
2025-01-16 02:07:23.21: PodMonitor - start process kube event
2025-01-16 02:07:37.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:07:37.05: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:07:37.06: PodMonitor - start process kube event
2025-01-16 02:07:37.06: empty line received
2025-01-16 02:07:37.06: PodMonitor - start process kube event
2025-01-16 02:08:02.32: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:08:02.32: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:08:02.32: PodMonitor - start process kube event
2025-01-16 02:08:02.32: empty line received
2025-01-16 02:08:02.32: PodMonitor - start process kube event
2025-01-16 02:08:09.27: EndPointMonitor - Received BOOKMARK: oldResVer=9932 newResVer=10836
2025-01-16 02:08:09.27: EndPointMonitor - start process kube event
2025-01-16 02:08:09.27: empty line received
2025-01-16 02:08:09.27: EndPointMonitor - start process kube event
2025-01-16 02:08:09.70: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:08:09.70: IngressMonitor - start process kube event
2025-01-16 02:08:09.71: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9932
2025-01-16 02:08:09.71: IngressMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:08:09.71: IngressMonitor - Connect Kube API result 0
2025-01-16 02:08:09.71: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:08:09.71: IngressMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})(timeout=120)
2025-01-16 02:08:09.71: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:08:09.71: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:08:09.71: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:08:09.71: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:08:09.72: IngressMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9932'})
2025-01-16 02:08:09.74: NamespaceMonitor - Received BOOKMARK: oldResVer=10649 newResVer=10649
2025-01-16 02:08:09.74: NamespaceMonitor - start process kube event
2025-01-16 02:08:09.74: empty line received
2025-01-16 02:08:09.74: NamespaceMonitor - start process kube event
2025-01-16 02:08:09.79: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:08:09.79: NetworkMonitor - start process kube event
2025-01-16 02:08:09.79: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9936
2025-01-16 02:08:09.79: NetworkMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:08:09.79: NetworkMonitor - Connect Kube API result 0
2025-01-16 02:08:09.79: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:08:09.79: NetworkMonitor - Start Watching request https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})(timeout=120)
2025-01-16 02:08:09.79: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:08:09.79: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:08:09.79: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:08:09.80: NetworkMonitor - Watches https://10.0.0.12:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9936'})
2025-01-16 02:08:09.87: ServiceMonitor - Received BOOKMARK: oldResVer=10751 newResVer=10751
2025-01-16 02:08:09.87: ServiceMonitor - start process kube event
2025-01-16 02:08:09.87: empty line received
2025-01-16 02:08:09.87: ServiceMonitor - start process kube event
2025-01-16 02:08:11.09: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9958 newResVer=9958
2025-01-16 02:08:11.09: NetworkPolicyMonitor - start process kube event
2025-01-16 02:08:11.09: empty line received
2025-01-16 02:08:11.09: NetworkPolicyMonitor - start process kube event
2025-01-16 02:08:12.53: PodMonitor - Received BOOKMARK: oldResVer=10635 newResVer=10832
2025-01-16 02:08:12.53: PodMonitor - start process kube event
2025-01-16 02:08:12.53: empty line received
2025-01-16 02:08:12.53: PodMonitor - start process kube event
2025-01-16 02:08:17.74: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:08:17.74: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:08:17.74: PodMonitor - start process kube event
2025-01-16 02:08:17.74: empty line received
2025-01-16 02:08:17.74: PodMonitor - start process kube event
2025-01-16 02:09:03.02: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:09:03.02: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:09:03.02: PodMonitor - start process kube event
2025-01-16 02:09:03.02: empty line received
2025-01-16 02:09:03.02: PodMonitor - start process kube event
2025-01-16 02:09:09.28: NamespaceMonitor - Received BOOKMARK: oldResVer=10649 newResVer=10649
2025-01-16 02:09:09.28: NamespaceMonitor - start process kube event
2025-01-16 02:09:09.28: empty line received
2025-01-16 02:09:09.28: NamespaceMonitor - start process kube event
2025-01-16 02:09:09.67: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-01-16 02:09:09.67: EndPointMonitor - start process kube event
2025-01-16 02:09:09.67: empty line received
2025-01-16 02:09:09.67: EndPointMonitor - start process kube event
2025-01-16 02:09:09.90: NetworkMonitor - Received BOOKMARK: oldResVer=9936 newResVer=10927
2025-01-16 02:09:09.90: NetworkMonitor - start process kube event
2025-01-16 02:09:09.90: empty line received
2025-01-16 02:09:09.90: NetworkMonitor - start process kube event
2025-01-16 02:09:10.01: IngressMonitor - Received BOOKMARK: oldResVer=9932 newResVer=10767
2025-01-16 02:09:10.01: IngressMonitor - start process kube event
2025-01-16 02:09:10.01: empty line received
2025-01-16 02:09:10.01: IngressMonitor - start process kube event
2025-01-16 02:09:10.12: ServiceMonitor - Received BOOKMARK: oldResVer=10751 newResVer=10751
2025-01-16 02:09:10.12: ServiceMonitor - start process kube event
2025-01-16 02:09:10.12: empty line received
2025-01-16 02:09:10.12: ServiceMonitor - start process kube event
2025-01-16 02:09:10.87: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9958 newResVer=9958
2025-01-16 02:09:10.87: NetworkPolicyMonitor - start process kube event
2025-01-16 02:09:10.87: empty line received
2025-01-16 02:09:10.87: NetworkPolicyMonitor - start process kube event
2025-01-16 02:09:12.46: PodMonitor - Received BOOKMARK: oldResVer=10832 newResVer=10927
2025-01-16 02:09:12.46: PodMonitor - start process kube event
2025-01-16 02:09:12.46: empty line received
2025-01-16 02:09:12.46: PodMonitor - start process kube event
2025-01-16 02:09:17.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:09:17.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:09:17.06: PodMonitor - start process kube event
2025-01-16 02:09:17.06: empty line received
2025-01-16 02:09:17.06: PodMonitor - start process kube event
2025-01-16 02:09:18.52: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:09:18.52: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:09:18.52: PodMonitor - start process kube event
2025-01-16 02:09:18.52: empty line received
2025-01-16 02:09:18.52: PodMonitor - start process kube event
2025-01-16 02:09:32.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:09:32.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:09:32.06: PodMonitor - start process kube event
2025-01-16 02:09:32.06: empty line received
2025-01-16 02:09:32.06: PodMonitor - start process kube event
2025-01-16 02:10:09.22: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-01-16 02:10:09.22: EndPointMonitor - start process kube event
2025-01-16 02:10:09.22: empty line received
2025-01-16 02:10:09.22: EndPointMonitor - start process kube event
2025-01-16 02:10:09.38: NamespaceMonitor - Received BOOKMARK: oldResVer=10649 newResVer=10649
2025-01-16 02:10:09.38: NamespaceMonitor - start process kube event
2025-01-16 02:10:09.38: empty line received
2025-01-16 02:10:09.38: NamespaceMonitor - start process kube event
2025-01-16 02:10:09.38: IngressMonitor - Received BOOKMARK: oldResVer=10767 newResVer=10767
2025-01-16 02:10:09.38: IngressMonitor - start process kube event
2025-01-16 02:10:09.38: empty line received
2025-01-16 02:10:09.38: IngressMonitor - start process kube event
2025-01-16 02:10:09.42: ServiceMonitor - Received BOOKMARK: oldResVer=10751 newResVer=10751
2025-01-16 02:10:09.42: ServiceMonitor - start process kube event
2025-01-16 02:10:09.42: empty line received
2025-01-16 02:10:09.42: ServiceMonitor - start process kube event
2025-01-16 02:10:09.80: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:10:10.23: NetworkMonitor - Received BOOKMARK: oldResVer=10927 newResVer=10927
2025-01-16 02:10:10.23: NetworkMonitor - start process kube event
2025-01-16 02:10:10.23: empty line received
2025-01-16 02:10:10.23: NetworkMonitor - start process kube event
2025-01-16 02:10:10.69: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9958 newResVer=10957
2025-01-16 02:10:10.69: NetworkPolicyMonitor - start process kube event
2025-01-16 02:10:10.69: empty line received
2025-01-16 02:10:10.69: NetworkPolicyMonitor - start process kube event
2025-01-16 02:10:12.23: PodMonitor - Received BOOKMARK: oldResVer=10927 newResVer=10971
2025-01-16 02:10:12.23: PodMonitor - start process kube event
2025-01-16 02:10:12.23: PodMonitor - _schedule_vnc_sync
2025-01-16 02:10:12.23: empty line received
2025-01-16 02:10:12.23: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-01-16 02:10:12.23: VncKubernetes - vnc_sync - Pod start
2025-01-16 02:10:12.23: VncKubernetes - vnc_sync - Pod done
2025-01-16 02:10:12.23: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:10:12.23: PodMonitor - start process kube event
2025-01-16 02:11:09.22: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-01-16 02:11:09.22: EndPointMonitor - start process kube event
2025-01-16 02:11:09.22: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:11:09.22: empty line received
2025-01-16 02:11:09.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:11:09.22: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:11:09.22: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:11:09.22: EndPointMonitor - start process kube event
2025-01-16 02:11:09.36: ServiceMonitor - Received BOOKMARK: oldResVer=10751 newResVer=10751
2025-01-16 02:11:09.36: ServiceMonitor - start process kube event
2025-01-16 02:11:09.36: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:11:09.36: empty line received
2025-01-16 02:11:09.36: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:11:09.36: VncKubernetes - vnc_sync - Service start
2025-01-16 02:11:09.36: VncKubernetes - vnc_sync - Service done
2025-01-16 02:11:09.36: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:11:09.36: ServiceMonitor - start process kube event
2025-01-16 02:11:09.52: NamespaceMonitor - Received BOOKMARK: oldResVer=10649 newResVer=10649
2025-01-16 02:11:09.52: NamespaceMonitor - start process kube event
2025-01-16 02:11:09.52: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:11:09.52: empty line received
2025-01-16 02:11:09.52: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:11:09.52: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:11:09.52: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:11:09.52: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:11:09.52: NamespaceMonitor - start process kube event
2025-01-16 02:11:09.86: NetworkMonitor - Received BOOKMARK: oldResVer=10927 newResVer=10927
2025-01-16 02:11:09.86: NetworkMonitor - start process kube event
2025-01-16 02:11:09.86: empty line received
2025-01-16 02:11:09.86: NetworkMonitor - start process kube event
2025-01-16 02:11:09.97: IngressMonitor - Received BOOKMARK: oldResVer=10767 newResVer=10767
2025-01-16 02:11:09.97: IngressMonitor - start process kube event
2025-01-16 02:11:09.97: empty line received
2025-01-16 02:11:09.97: IngressMonitor - start process kube event
2025-01-16 02:11:10.80: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10957 newResVer=10957
2025-01-16 02:11:10.80: NetworkPolicyMonitor - start process kube event
2025-01-16 02:11:10.80: empty line received
2025-01-16 02:11:10.80: NetworkPolicyMonitor - start process kube event
2025-01-16 02:11:12.29: PodMonitor - Received BOOKMARK: oldResVer=10971 newResVer=10971
2025-01-16 02:11:12.29: PodMonitor - start process kube event
2025-01-16 02:11:12.29: empty line received
2025-01-16 02:11:12.29: PodMonitor - start process kube event
2025-01-16 02:12:09.71: IngressMonitor - Received BOOKMARK: oldResVer=10767 newResVer=10767
2025-01-16 02:12:09.71: IngressMonitor - start process kube event
2025-01-16 02:12:09.71: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:12:09.71: empty line received
2025-01-16 02:12:09.71: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:12:09.71: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:12:09.71: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:12:09.71: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:12:09.71: IngressMonitor - start process kube event
2025-01-16 02:12:09.88: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-01-16 02:12:09.88: EndPointMonitor - start process kube event
2025-01-16 02:12:09.88: empty line received
2025-01-16 02:12:09.88: EndPointMonitor - start process kube event
2025-01-16 02:12:09.97: ServiceMonitor - Received BOOKMARK: oldResVer=10751 newResVer=10751
2025-01-16 02:12:09.97: ServiceMonitor - start process kube event
2025-01-16 02:12:09.97: empty line received
2025-01-16 02:12:09.97: ServiceMonitor - start process kube event
2025-01-16 02:12:10.06: NamespaceMonitor - Received BOOKMARK: oldResVer=10649 newResVer=10649
2025-01-16 02:12:10.06: NamespaceMonitor - start process kube event
2025-01-16 02:12:10.06: empty line received
2025-01-16 02:12:10.06: NamespaceMonitor - start process kube event
2025-01-16 02:12:10.47: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10957 newResVer=10957
2025-01-16 02:12:10.47: NetworkPolicyMonitor - start process kube event
2025-01-16 02:12:10.47: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:12:10.47: empty line received
2025-01-16 02:12:10.47: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:12:10.47: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:12:10.47: NetworkPolicyMonitor - start process kube event
2025-01-16 02:12:10.47: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:12:10.47: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:12:10.61: NetworkMonitor - Received BOOKMARK: oldResVer=10927 newResVer=10927
2025-01-16 02:12:10.61: NetworkMonitor - start process kube event
2025-01-16 02:12:10.61: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:12:10.61: empty line received
2025-01-16 02:12:10.61: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:12:10.61: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:12:10.61: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:12:10.61: NetworkMonitor - start process kube event
2025-01-16 02:12:12.63: PodMonitor - Received BOOKMARK: oldResVer=10971 newResVer=10971
2025-01-16 02:12:12.63: PodMonitor - start process kube event
2025-01-16 02:12:12.63: empty line received
2025-01-16 02:12:12.63: PodMonitor - start process kube event
2025-01-16 02:12:27.60: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:12:27.60: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:12:27.60: PodMonitor - start process kube event
2025-01-16 02:12:27.60: empty line received
2025-01-16 02:12:27.60: PodMonitor - start process kube event
2025-01-16 02:12:42.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:12:42.05: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:12:42.05: PodMonitor - start process kube event
2025-01-16 02:12:42.05: empty line received
2025-01-16 02:12:42.05: PodMonitor - start process kube event
2025-01-16 02:13:09.45: ServiceMonitor - Received BOOKMARK: oldResVer=10751 newResVer=10751
2025-01-16 02:13:09.46: ServiceMonitor - start process kube event
2025-01-16 02:13:09.46: empty line received
2025-01-16 02:13:09.46: ServiceMonitor - start process kube event
2025-01-16 02:13:09.86: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-01-16 02:13:09.86: EndPointMonitor - start process kube event
2025-01-16 02:13:09.86: empty line received
2025-01-16 02:13:09.86: EndPointMonitor - start process kube event
2025-01-16 02:13:10.10: NamespaceMonitor - Received BOOKMARK: oldResVer=10649 newResVer=10649
2025-01-16 02:13:10.10: NamespaceMonitor - start process kube event
2025-01-16 02:13:10.10: empty line received
2025-01-16 02:13:10.10: NamespaceMonitor - start process kube event
2025-01-16 02:13:10.30: IngressMonitor - Received BOOKMARK: oldResVer=10767 newResVer=10767
2025-01-16 02:13:10.30: IngressMonitor - start process kube event
2025-01-16 02:13:10.30: empty line received
2025-01-16 02:13:10.30: IngressMonitor - start process kube event
2025-01-16 02:13:10.54: NetworkMonitor - Received BOOKMARK: oldResVer=10927 newResVer=10927
2025-01-16 02:13:10.54: NetworkMonitor - start process kube event
2025-01-16 02:13:10.54: empty line received
2025-01-16 02:13:10.54: NetworkMonitor - start process kube event
2025-01-16 02:13:10.84: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10957 newResVer=10957
2025-01-16 02:13:10.84: NetworkPolicyMonitor - start process kube event
2025-01-16 02:13:10.84: empty line received
2025-01-16 02:13:10.84: NetworkPolicyMonitor - start process kube event
2025-01-16 02:13:12.99: PodMonitor - Received BOOKMARK: oldResVer=10971 newResVer=11245
2025-01-16 02:13:12.99: PodMonitor - start process kube event
2025-01-16 02:13:12.99: empty line received
2025-01-16 02:13:12.99: PodMonitor - start process kube event
2025-01-16 02:14:09.30: ServiceMonitor - Received BOOKMARK: oldResVer=10751 newResVer=10751
2025-01-16 02:14:09.30: ServiceMonitor - start process kube event
2025-01-16 02:14:09.30: empty line received
2025-01-16 02:14:09.30: ServiceMonitor - start process kube event
2025-01-16 02:14:09.99: NetworkMonitor - Received BOOKMARK: oldResVer=10927 newResVer=10927
2025-01-16 02:14:09.99: NetworkMonitor - start process kube event
2025-01-16 02:14:09.99: empty line received
2025-01-16 02:14:09.99: NetworkMonitor - start process kube event
2025-01-16 02:14:10.20: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-01-16 02:14:10.20: EndPointMonitor - start process kube event
2025-01-16 02:14:10.20: empty line received
2025-01-16 02:14:10.20: EndPointMonitor - start process kube event
2025-01-16 02:14:10.62: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:14:10.65: NamespaceMonitor - Received BOOKMARK: oldResVer=10649 newResVer=10649
2025-01-16 02:14:10.65: NamespaceMonitor - start process kube event
2025-01-16 02:14:10.65: empty line received
2025-01-16 02:14:10.65: NamespaceMonitor - start process kube event
2025-01-16 02:14:11.24: IngressMonitor - Received BOOKMARK: oldResVer=10767 newResVer=10767
2025-01-16 02:14:11.24: IngressMonitor - start process kube event
2025-01-16 02:14:11.24: empty line received
2025-01-16 02:14:11.24: IngressMonitor - start process kube event
2025-01-16 02:14:11.33: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10957 newResVer=10957
2025-01-16 02:14:11.33: NetworkPolicyMonitor - start process kube event
2025-01-16 02:14:11.33: empty line received
2025-01-16 02:14:11.33: NetworkPolicyMonitor - start process kube event
2025-01-16 02:14:12.39: PodMonitor - Received BOOKMARK: oldResVer=11245 newResVer=11245
2025-01-16 02:14:12.39: PodMonitor - start process kube event
2025-01-16 02:14:12.39: PodMonitor - _schedule_vnc_sync
2025-01-16 02:14:12.39: empty line received
2025-01-16 02:14:12.39: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-01-16 02:14:12.39: VncKubernetes - vnc_sync - Pod start
2025-01-16 02:14:12.39: VncKubernetes - vnc_sync - Pod done
2025-01-16 02:14:12.39: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:14:12.39: PodMonitor - start process kube event
2025-01-16 02:14:15.51: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:14:15.51: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:14:15.51: PodMonitor - start process kube event
2025-01-16 02:14:15.51: empty line received
2025-01-16 02:14:15.51: PodMonitor - start process kube event
2025-01-16 02:14:30.01: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:14:30.01: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:14:30.01: PodMonitor - start process kube event
2025-01-16 02:14:30.01: empty line received
2025-01-16 02:14:30.01: PodMonitor - start process kube event
2025-01-16 02:15:09.86: ServiceMonitor - Received BOOKMARK: oldResVer=10751 newResVer=10751
2025-01-16 02:15:09.86: ServiceMonitor - start process kube event
2025-01-16 02:15:09.86: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:15:09.86: empty line received
2025-01-16 02:15:09.86: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:15:09.86: VncKubernetes - vnc_sync - Service start
2025-01-16 02:15:09.86: VncKubernetes - vnc_sync - Service done
2025-01-16 02:15:09.86: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:15:09.86: ServiceMonitor - start process kube event
2025-01-16 02:15:10.44: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-01-16 02:15:10.44: EndPointMonitor - start process kube event
2025-01-16 02:15:10.44: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:15:10.44: empty line received
2025-01-16 02:15:10.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:15:10.44: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:15:10.44: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:15:10.44: EndPointMonitor - start process kube event
2025-01-16 02:15:10.68: NetworkMonitor - Received BOOKMARK: oldResVer=10927 newResVer=10927
2025-01-16 02:15:10.68: NetworkMonitor - start process kube event
2025-01-16 02:15:10.68: empty line received
2025-01-16 02:15:10.68: NetworkMonitor - start process kube event
2025-01-16 02:15:11.15: IngressMonitor - Received BOOKMARK: oldResVer=10767 newResVer=10767
2025-01-16 02:15:11.15: IngressMonitor - start process kube event
2025-01-16 02:15:11.15: empty line received
2025-01-16 02:15:11.15: IngressMonitor - start process kube event
2025-01-16 02:15:11.22: NamespaceMonitor - Received BOOKMARK: oldResVer=10649 newResVer=10649
2025-01-16 02:15:11.22: NamespaceMonitor - start process kube event
2025-01-16 02:15:11.22: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:15:11.22: empty line received
2025-01-16 02:15:11.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:15:11.22: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:15:11.22: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:15:11.22: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:15:11.22: NamespaceMonitor - start process kube event
2025-01-16 02:15:11.89: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10957 newResVer=10957
2025-01-16 02:15:11.89: NetworkPolicyMonitor - start process kube event
2025-01-16 02:15:11.89: empty line received
2025-01-16 02:15:11.89: NetworkPolicyMonitor - start process kube event
2025-01-16 02:15:12.71: PodMonitor - Received BOOKMARK: oldResVer=11245 newResVer=11408
2025-01-16 02:15:12.71: PodMonitor - start process kube event
2025-01-16 02:15:12.71: empty line received
2025-01-16 02:15:12.71: PodMonitor - start process kube event
2025-01-16 02:15:16.32: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:15:16.32: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:15:16.32: PodMonitor - start process kube event
2025-01-16 02:15:16.32: empty line received
2025-01-16 02:15:16.32: PodMonitor - start process kube event
2025-01-16 02:15:29.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:15:29.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:15:29.06: PodMonitor - start process kube event
2025-01-16 02:15:29.06: empty line received
2025-01-16 02:15:29.06: PodMonitor - start process kube event
2025-01-16 02:15:29.80: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:15:29.80: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:15:29.80: PodMonitor - start process kube event
2025-01-16 02:15:29.80: empty line received
2025-01-16 02:15:29.80: PodMonitor - start process kube event
2025-01-16 02:15:42.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:15:42.05: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:15:42.05: PodMonitor - start process kube event
2025-01-16 02:15:42.05: empty line received
2025-01-16 02:15:42.05: PodMonitor - start process kube event
2025-01-16 02:16:10.23: ServiceMonitor - Received BOOKMARK: oldResVer=10751 newResVer=10751
2025-01-16 02:16:10.23: ServiceMonitor - start process kube event
2025-01-16 02:16:10.23: empty line received
2025-01-16 02:16:10.23: ServiceMonitor - start process kube event
2025-01-16 02:16:10.23: NetworkMonitor - Received BOOKMARK: oldResVer=10927 newResVer=10927
2025-01-16 02:16:10.23: NetworkMonitor - start process kube event
2025-01-16 02:16:10.23: empty line received
2025-01-16 02:16:10.23: NetworkMonitor - start process kube event
2025-01-16 02:16:10.56: IngressMonitor - Received BOOKMARK: oldResVer=10767 newResVer=10767
2025-01-16 02:16:10.56: IngressMonitor - start process kube event
2025-01-16 02:16:10.56: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:16:10.56: empty line received
2025-01-16 02:16:10.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:16:10.56: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:16:10.56: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:16:10.56: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:16:10.56: IngressMonitor - start process kube event
2025-01-16 02:16:11.04: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-01-16 02:16:11.04: EndPointMonitor - start process kube event
2025-01-16 02:16:11.04: empty line received
2025-01-16 02:16:11.04: EndPointMonitor - start process kube event
2025-01-16 02:16:11.65: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10957 newResVer=10957
2025-01-16 02:16:11.65: NetworkPolicyMonitor - start process kube event
2025-01-16 02:16:11.65: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:16:11.65: empty line received
2025-01-16 02:16:11.65: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:16:11.65: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:16:11.65: NetworkPolicyMonitor - start process kube event
2025-01-16 02:16:11.65: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:16:11.65: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:16:11.83: NamespaceMonitor - Received BOOKMARK: oldResVer=10649 newResVer=10649
2025-01-16 02:16:11.83: NamespaceMonitor - start process kube event
2025-01-16 02:16:11.83: empty line received
2025-01-16 02:16:11.83: NamespaceMonitor - start process kube event
2025-01-16 02:16:12.92: PodMonitor - Received BOOKMARK: oldResVer=11408 newResVer=11513
2025-01-16 02:16:12.92: PodMonitor - start process kube event
2025-01-16 02:16:12.92: empty line received
2025-01-16 02:16:12.92: PodMonitor - start process kube event
2025-01-16 02:17:10.00: NetworkMonitor - Received BOOKMARK: oldResVer=10927 newResVer=10927
2025-01-16 02:17:10.00: NetworkMonitor - start process kube event
2025-01-16 02:17:10.00: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:17:10.00: empty line received
2025-01-16 02:17:10.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:17:10.00: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:17:10.00: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:17:10.00: NetworkMonitor - start process kube event
2025-01-16 02:17:10.72: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-01-16 02:17:10.72: EndPointMonitor - start process kube event
2025-01-16 02:17:10.72: empty line received
2025-01-16 02:17:10.72: EndPointMonitor - start process kube event
2025-01-16 02:17:10.81: IngressMonitor - Received BOOKMARK: oldResVer=10767 newResVer=10767
2025-01-16 02:17:10.81: IngressMonitor - start process kube event
2025-01-16 02:17:10.81: empty line received
2025-01-16 02:17:10.81: IngressMonitor - start process kube event
2025-01-16 02:17:11.04: ServiceMonitor - Received BOOKMARK: oldResVer=10751 newResVer=10751
2025-01-16 02:17:11.04: ServiceMonitor - start process kube event
2025-01-16 02:17:11.04: empty line received
2025-01-16 02:17:11.04: ServiceMonitor - start process kube event
2025-01-16 02:17:11.11: NamespaceMonitor - Received BOOKMARK: oldResVer=10649 newResVer=11590
2025-01-16 02:17:11.11: NamespaceMonitor - start process kube event
2025-01-16 02:17:11.11: empty line received
2025-01-16 02:17:11.11: NamespaceMonitor - start process kube event
2025-01-16 02:17:11.94: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10957 newResVer=10957
2025-01-16 02:17:11.95: NetworkPolicyMonitor - start process kube event
2025-01-16 02:17:11.95: empty line received
2025-01-16 02:17:11.95: NetworkPolicyMonitor - start process kube event
2025-01-16 02:17:13.01: PodMonitor - Received BOOKMARK: oldResVer=11513 newResVer=11513
2025-01-16 02:17:13.01: PodMonitor - start process kube event
2025-01-16 02:17:13.01: empty line received
2025-01-16 02:17:13.01: PodMonitor - start process kube event
2025-01-16 02:17:35.19: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:17:35.19: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:17:35.19: PodMonitor - start process kube event
2025-01-16 02:17:35.19: empty line received
2025-01-16 02:17:35.19: PodMonitor - start process kube event
2025-01-16 02:17:47.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:17:47.05: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:17:47.05: PodMonitor - start process kube event
2025-01-16 02:17:47.05: empty line received
2025-01-16 02:17:47.05: PodMonitor - start process kube event
2025-01-16 02:18:10.66: IngressMonitor - Received BOOKMARK: oldResVer=10767 newResVer=11718
2025-01-16 02:18:10.66: IngressMonitor - start process kube event
2025-01-16 02:18:10.66: empty line received
2025-01-16 02:18:10.66: IngressMonitor - start process kube event
2025-01-16 02:18:10.68: NetworkMonitor - Received BOOKMARK: oldResVer=10927 newResVer=10927
2025-01-16 02:18:10.68: NetworkMonitor - start process kube event
2025-01-16 02:18:10.68: empty line received
2025-01-16 02:18:10.68: NetworkMonitor - start process kube event
2025-01-16 02:18:11.04: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=10836
2025-01-16 02:18:11.04: EndPointMonitor - start process kube event
2025-01-16 02:18:11.04: empty line received
2025-01-16 02:18:11.04: EndPointMonitor - start process kube event
2025-01-16 02:18:11.17: ServiceMonitor - Received BOOKMARK: oldResVer=10751 newResVer=11702
2025-01-16 02:18:11.17: ServiceMonitor - start process kube event
2025-01-16 02:18:11.17: empty line received
2025-01-16 02:18:11.17: ServiceMonitor - start process kube event
2025-01-16 02:18:11.62: NamespaceMonitor - Received BOOKMARK: oldResVer=11590 newResVer=11590
2025-01-16 02:18:11.62: NamespaceMonitor - start process kube event
2025-01-16 02:18:11.62: empty line received
2025-01-16 02:18:11.62: NamespaceMonitor - start process kube event
2025-01-16 02:18:12.03: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10957 newResVer=10957
2025-01-16 02:18:12.03: NetworkPolicyMonitor - start process kube event
2025-01-16 02:18:12.03: empty line received
2025-01-16 02:18:12.03: NetworkPolicyMonitor - start process kube event
2025-01-16 02:18:12.25: PodMonitor - Received BOOKMARK: oldResVer=11513 newResVer=11688
2025-01-16 02:18:12.25: PodMonitor - start process kube event
2025-01-16 02:18:12.25: empty line received
2025-01-16 02:18:12.25: PodMonitor - start process kube event
2025-01-16 02:19:10.01: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:19:10.33: EndPointMonitor - Received BOOKMARK: oldResVer=10836 newResVer=11787
2025-01-16 02:19:10.33: EndPointMonitor - start process kube event
2025-01-16 02:19:10.33: empty line received
2025-01-16 02:19:10.33: EndPointMonitor - start process kube event
2025-01-16 02:19:10.48: NetworkMonitor - Received BOOKMARK: oldResVer=10927 newResVer=10927
2025-01-16 02:19:10.48: NetworkMonitor - start process kube event
2025-01-16 02:19:10.48: empty line received
2025-01-16 02:19:10.48: NetworkMonitor - start process kube event
2025-01-16 02:19:10.76: IngressMonitor - Received BOOKMARK: oldResVer=11718 newResVer=11718
2025-01-16 02:19:10.76: IngressMonitor - start process kube event
2025-01-16 02:19:10.76: empty line received
2025-01-16 02:19:10.76: IngressMonitor - start process kube event
2025-01-16 02:19:11.40: NamespaceMonitor - Received BOOKMARK: oldResVer=11590 newResVer=11590
2025-01-16 02:19:11.40: NamespaceMonitor - start process kube event
2025-01-16 02:19:11.40: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:19:11.40: empty line received
2025-01-16 02:19:11.40: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:19:11.40: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:19:11.40: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:19:11.40: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:19:11.40: NamespaceMonitor - start process kube event
2025-01-16 02:19:11.91: ServiceMonitor - Received BOOKMARK: oldResVer=11702 newResVer=11702
2025-01-16 02:19:11.91: ServiceMonitor - start process kube event
2025-01-16 02:19:11.91: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:19:11.91: empty line received
2025-01-16 02:19:11.91: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:19:11.91: VncKubernetes - vnc_sync - Service start
2025-01-16 02:19:11.91: VncKubernetes - vnc_sync - Service done
2025-01-16 02:19:11.91: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:19:11.91: ServiceMonitor - start process kube event
2025-01-16 02:19:12.32: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10957 newResVer=10957
2025-01-16 02:19:12.32: NetworkPolicyMonitor - start process kube event
2025-01-16 02:19:12.32: empty line received
2025-01-16 02:19:12.32: NetworkPolicyMonitor - start process kube event
2025-01-16 02:19:13.03: PodMonitor - Received BOOKMARK: oldResVer=11688 newResVer=11688
2025-01-16 02:19:13.03: PodMonitor - start process kube event
2025-01-16 02:19:13.03: PodMonitor - _schedule_vnc_sync
2025-01-16 02:19:13.03: empty line received
2025-01-16 02:19:13.03: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-01-16 02:19:13.03: VncKubernetes - vnc_sync - Pod start
2025-01-16 02:19:13.03: VncKubernetes - vnc_sync - Pod done
2025-01-16 02:19:13.03: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:19:13.03: PodMonitor - start process kube event
2025-01-16 02:20:10.38: EndPointMonitor - Received BOOKMARK: oldResVer=11787 newResVer=11787
2025-01-16 02:20:10.38: EndPointMonitor - start process kube event
2025-01-16 02:20:10.38: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:20:10.38: empty line received
2025-01-16 02:20:10.38: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:20:10.38: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:20:10.38: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:20:10.38: EndPointMonitor - start process kube event
2025-01-16 02:20:10.61: NetworkMonitor - Received BOOKMARK: oldResVer=10927 newResVer=11871
2025-01-16 02:20:10.61: NetworkMonitor - start process kube event
2025-01-16 02:20:10.61: empty line received
2025-01-16 02:20:10.61: NetworkMonitor - start process kube event
2025-01-16 02:20:11.04: IngressMonitor - Received BOOKMARK: oldResVer=11718 newResVer=11718
2025-01-16 02:20:11.04: IngressMonitor - start process kube event
2025-01-16 02:20:11.04: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:20:11.04: empty line received
2025-01-16 02:20:11.04: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:20:11.04: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:20:11.04: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:20:11.04: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:20:11.04: IngressMonitor - start process kube event
2025-01-16 02:20:11.35: ServiceMonitor - Received BOOKMARK: oldResVer=11702 newResVer=11702
2025-01-16 02:20:11.35: ServiceMonitor - start process kube event
2025-01-16 02:20:11.35: empty line received
2025-01-16 02:20:11.35: ServiceMonitor - start process kube event
2025-01-16 02:20:11.54: NamespaceMonitor - Received BOOKMARK: oldResVer=11590 newResVer=11590
2025-01-16 02:20:11.54: NamespaceMonitor - start process kube event
2025-01-16 02:20:11.54: empty line received
2025-01-16 02:20:11.54: NamespaceMonitor - start process kube event
2025-01-16 02:20:13.07: PodMonitor - Received BOOKMARK: oldResVer=11688 newResVer=11688
2025-01-16 02:20:13.07: PodMonitor - start process kube event
2025-01-16 02:20:13.07: empty line received
2025-01-16 02:20:13.07: PodMonitor - start process kube event
2025-01-16 02:20:13.18: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10957 newResVer=10957
2025-01-16 02:20:13.18: NetworkPolicyMonitor - start process kube event
2025-01-16 02:20:13.18: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:20:13.18: empty line received
2025-01-16 02:20:13.18: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:20:13.18: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:20:13.18: NetworkPolicyMonitor - start process kube event
2025-01-16 02:20:13.19: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:20:13.19: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:20:16.28: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:20:16.28: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:20:16.28: PodMonitor - start process kube event
2025-01-16 02:20:16.28: empty line received
2025-01-16 02:20:16.28: PodMonitor - start process kube event
2025-01-16 02:20:30.75: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:20:30.75: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:20:30.75: PodMonitor - start process kube event
2025-01-16 02:20:30.75: empty line received
2025-01-16 02:20:30.75: PodMonitor - start process kube event
2025-01-16 02:21:10.49: IngressMonitor - Received BOOKMARK: oldResVer=11718 newResVer=11718
2025-01-16 02:21:10.49: IngressMonitor - start process kube event
2025-01-16 02:21:10.49: empty line received
2025-01-16 02:21:10.49: IngressMonitor - start process kube event
2025-01-16 02:21:10.59: EndPointMonitor - Received BOOKMARK: oldResVer=11787 newResVer=11787
2025-01-16 02:21:10.59: EndPointMonitor - start process kube event
2025-01-16 02:21:10.59: empty line received
2025-01-16 02:21:10.59: EndPointMonitor - start process kube event
2025-01-16 02:21:10.72: NetworkMonitor - Received BOOKMARK: oldResVer=11871 newResVer=11871
2025-01-16 02:21:10.72: NetworkMonitor - start process kube event
2025-01-16 02:21:10.72: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:21:10.72: empty line received
2025-01-16 02:21:10.72: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:21:10.72: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:21:10.72: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:21:10.72: NetworkMonitor - start process kube event
2025-01-16 02:21:11.14: NamespaceMonitor - Received BOOKMARK: oldResVer=11590 newResVer=11590
2025-01-16 02:21:11.14: NamespaceMonitor - start process kube event
2025-01-16 02:21:11.14: empty line received
2025-01-16 02:21:11.14: NamespaceMonitor - start process kube event
2025-01-16 02:21:12.14: ServiceMonitor - Received BOOKMARK: oldResVer=11702 newResVer=11702
2025-01-16 02:21:12.14: ServiceMonitor - start process kube event
2025-01-16 02:21:12.14: empty line received
2025-01-16 02:21:12.14: ServiceMonitor - start process kube event
2025-01-16 02:21:13.24: PodMonitor - Received BOOKMARK: oldResVer=11688 newResVer=11921
2025-01-16 02:21:13.24: PodMonitor - start process kube event
2025-01-16 02:21:13.24: empty line received
2025-01-16 02:21:13.24: PodMonitor - start process kube event
2025-01-16 02:21:13.26: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10957 newResVer=11906
2025-01-16 02:21:13.26: NetworkPolicyMonitor - start process kube event
2025-01-16 02:21:13.26: empty line received
2025-01-16 02:21:13.26: NetworkPolicyMonitor - start process kube event
2025-01-16 02:21:17.99: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:21:17.99: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:21:17.99: PodMonitor - start process kube event
2025-01-16 02:21:17.99: empty line received
2025-01-16 02:21:17.99: PodMonitor - start process kube event
2025-01-16 02:21:29.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:21:29.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:21:29.06: PodMonitor - start process kube event
2025-01-16 02:21:29.06: empty line received
2025-01-16 02:21:29.06: PodMonitor - start process kube event
2025-01-16 02:21:31.49: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:21:31.49: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:21:31.49: PodMonitor - start process kube event
2025-01-16 02:21:31.49: empty line received
2025-01-16 02:21:31.49: PodMonitor - start process kube event
2025-01-16 02:21:46.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:21:46.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:21:46.06: PodMonitor - start process kube event
2025-01-16 02:21:46.06: empty line received
2025-01-16 02:21:46.06: PodMonitor - start process kube event
2025-01-16 02:22:09.83: NetworkMonitor - Received BOOKMARK: oldResVer=11871 newResVer=11871
2025-01-16 02:22:09.83: NetworkMonitor - start process kube event
2025-01-16 02:22:09.83: empty line received
2025-01-16 02:22:09.83: NetworkMonitor - start process kube event
2025-01-16 02:22:10.65: IngressMonitor - Received BOOKMARK: oldResVer=11718 newResVer=11718
2025-01-16 02:22:10.65: IngressMonitor - start process kube event
2025-01-16 02:22:10.65: empty line received
2025-01-16 02:22:10.65: IngressMonitor - start process kube event
2025-01-16 02:22:11.21: NamespaceMonitor - Received BOOKMARK: oldResVer=11590 newResVer=11590
2025-01-16 02:22:11.21: NamespaceMonitor - start process kube event
2025-01-16 02:22:11.21: empty line received
2025-01-16 02:22:11.21: NamespaceMonitor - start process kube event
2025-01-16 02:22:11.24: EndPointMonitor - Received BOOKMARK: oldResVer=11787 newResVer=11787
2025-01-16 02:22:11.24: EndPointMonitor - start process kube event
2025-01-16 02:22:11.24: empty line received
2025-01-16 02:22:11.24: EndPointMonitor - start process kube event
2025-01-16 02:22:12.54: ServiceMonitor - Received BOOKMARK: oldResVer=11702 newResVer=11702
2025-01-16 02:22:12.54: ServiceMonitor - start process kube event
2025-01-16 02:22:12.54: empty line received
2025-01-16 02:22:12.54: ServiceMonitor - start process kube event
2025-01-16 02:22:13.12: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11906 newResVer=11906
2025-01-16 02:22:13.12: NetworkPolicyMonitor - start process kube event
2025-01-16 02:22:13.12: empty line received
2025-01-16 02:22:13.12: NetworkPolicyMonitor - start process kube event
2025-01-16 02:22:13.69: PodMonitor - Received BOOKMARK: oldResVer=11921 newResVer=12030
2025-01-16 02:22:13.70: PodMonitor - start process kube event
2025-01-16 02:22:13.70: empty line received
2025-01-16 02:22:13.70: PodMonitor - start process kube event
2025-01-16 02:22:40.73: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:22:40.73: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:22:40.74: PodMonitor - start process kube event
2025-01-16 02:22:40.74: empty line received
2025-01-16 02:22:40.74: PodMonitor - start process kube event
2025-01-16 02:22:41.86: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:22:41.86: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:22:41.86: PodMonitor - start process kube event
2025-01-16 02:22:41.86: empty line received
2025-01-16 02:22:41.86: PodMonitor - start process kube event
2025-01-16 02:23:10.04: NetworkMonitor - Received BOOKMARK: oldResVer=11871 newResVer=11871
2025-01-16 02:23:10.04: NetworkMonitor - start process kube event
2025-01-16 02:23:10.04: empty line received
2025-01-16 02:23:10.04: NetworkMonitor - start process kube event
2025-01-16 02:23:10.66: IngressMonitor - Received BOOKMARK: oldResVer=11718 newResVer=11718
2025-01-16 02:23:10.66: IngressMonitor - start process kube event
2025-01-16 02:23:10.66: empty line received
2025-01-16 02:23:10.66: IngressMonitor - start process kube event
2025-01-16 02:23:10.72: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:23:11.20: NamespaceMonitor - Received BOOKMARK: oldResVer=11590 newResVer=11590
2025-01-16 02:23:11.20: NamespaceMonitor - start process kube event
2025-01-16 02:23:11.20: empty line received
2025-01-16 02:23:11.20: NamespaceMonitor - start process kube event
2025-01-16 02:23:11.27: EndPointMonitor - Received BOOKMARK: oldResVer=11787 newResVer=11787
2025-01-16 02:23:11.27: EndPointMonitor - start process kube event
2025-01-16 02:23:11.27: empty line received
2025-01-16 02:23:11.27: EndPointMonitor - start process kube event
2025-01-16 02:23:12.33: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11906 newResVer=11906
2025-01-16 02:23:12.33: NetworkPolicyMonitor - start process kube event
2025-01-16 02:23:12.33: empty line received
2025-01-16 02:23:12.33: NetworkPolicyMonitor - start process kube event
2025-01-16 02:23:13.27: ServiceMonitor - Received BOOKMARK: oldResVer=11702 newResVer=11702
2025-01-16 02:23:13.27: ServiceMonitor - start process kube event
2025-01-16 02:23:13.27: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:23:13.27: empty line received
2025-01-16 02:23:13.27: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:23:13.27: VncKubernetes - vnc_sync - Service start
2025-01-16 02:23:13.27: VncKubernetes - vnc_sync - Service done
2025-01-16 02:23:13.27: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:23:13.27: ServiceMonitor - start process kube event
2025-01-16 02:23:13.48: PodMonitor - Received BOOKMARK: oldResVer=12030 newResVer=12110
2025-01-16 02:23:13.48: PodMonitor - start process kube event
2025-01-16 02:23:13.48: PodMonitor - _schedule_vnc_sync
2025-01-16 02:23:13.48: empty line received
2025-01-16 02:23:13.48: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-01-16 02:23:13.48: VncKubernetes - vnc_sync - Pod start
2025-01-16 02:23:13.48: VncKubernetes - vnc_sync - Pod done
2025-01-16 02:23:13.48: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:23:13.48: PodMonitor - start process kube event
2025-01-16 02:24:09.80: NetworkMonitor - Received BOOKMARK: oldResVer=11871 newResVer=11871
2025-01-16 02:24:09.80: NetworkMonitor - start process kube event
2025-01-16 02:24:09.80: empty line received
2025-01-16 02:24:09.80: NetworkMonitor - start process kube event
2025-01-16 02:24:10.86: IngressMonitor - Received BOOKMARK: oldResVer=11718 newResVer=11718
2025-01-16 02:24:10.86: IngressMonitor - start process kube event
2025-01-16 02:24:10.86: empty line received
2025-01-16 02:24:10.86: IngressMonitor - start process kube event
2025-01-16 02:24:11.65: NamespaceMonitor - Received BOOKMARK: oldResVer=11590 newResVer=11590
2025-01-16 02:24:11.65: NamespaceMonitor - start process kube event
2025-01-16 02:24:11.65: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:24:11.65: empty line received
2025-01-16 02:24:11.65: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:24:11.65: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:24:11.65: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:24:11.65: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:24:11.65: NamespaceMonitor - start process kube event
2025-01-16 02:24:12.08: EndPointMonitor - Received BOOKMARK: oldResVer=11787 newResVer=11787
2025-01-16 02:24:12.08: EndPointMonitor - start process kube event
2025-01-16 02:24:12.08: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:24:12.09: empty line received
2025-01-16 02:24:12.09: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:24:12.09: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:24:12.09: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:24:12.09: EndPointMonitor - start process kube event
2025-01-16 02:24:12.36: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11906 newResVer=11906
2025-01-16 02:24:12.36: NetworkPolicyMonitor - start process kube event
2025-01-16 02:24:12.36: empty line received
2025-01-16 02:24:12.36: NetworkPolicyMonitor - start process kube event
2025-01-16 02:24:13.88: PodMonitor - Received BOOKMARK: oldResVer=12110 newResVer=12110
2025-01-16 02:24:13.88: PodMonitor - start process kube event
2025-01-16 02:24:13.88: empty line received
2025-01-16 02:24:13.88: PodMonitor - start process kube event
2025-01-16 02:24:14.00: ServiceMonitor - Received BOOKMARK: oldResVer=11702 newResVer=11702
2025-01-16 02:24:14.00: ServiceMonitor - start process kube event
2025-01-16 02:24:14.00: empty line received
2025-01-16 02:24:14.00: ServiceMonitor - start process kube event
2025-01-16 02:25:09.80: NetworkMonitor - Received BOOKMARK: oldResVer=11871 newResVer=11871
2025-01-16 02:25:09.80: NetworkMonitor - start process kube event
2025-01-16 02:25:09.80: empty line received
2025-01-16 02:25:09.80: NetworkMonitor - start process kube event
2025-01-16 02:25:11.07: IngressMonitor - Received BOOKMARK: oldResVer=11718 newResVer=11718
2025-01-16 02:25:11.07: IngressMonitor - start process kube event
2025-01-16 02:25:11.07: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:25:11.07: empty line received
2025-01-16 02:25:11.07: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:25:11.07: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:25:11.07: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:25:11.07: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:25:11.07: IngressMonitor - start process kube event
2025-01-16 02:25:11.54: EndPointMonitor - Received BOOKMARK: oldResVer=11787 newResVer=11787
2025-01-16 02:25:11.54: EndPointMonitor - start process kube event
2025-01-16 02:25:11.54: empty line received
2025-01-16 02:25:11.54: EndPointMonitor - start process kube event
2025-01-16 02:25:11.98: NamespaceMonitor - Received BOOKMARK: oldResVer=11590 newResVer=11590
2025-01-16 02:25:11.98: NamespaceMonitor - start process kube event
2025-01-16 02:25:11.98: empty line received
2025-01-16 02:25:11.98: NamespaceMonitor - start process kube event
2025-01-16 02:25:12.75: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11906 newResVer=11906
2025-01-16 02:25:12.75: NetworkPolicyMonitor - start process kube event
2025-01-16 02:25:12.75: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:25:12.75: empty line received
2025-01-16 02:25:12.75: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:25:12.75: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:25:12.75: NetworkPolicyMonitor - start process kube event
2025-01-16 02:25:12.75: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:25:12.75: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:25:13.35: ServiceMonitor - Received BOOKMARK: oldResVer=11702 newResVer=11702
2025-01-16 02:25:13.35: ServiceMonitor - start process kube event
2025-01-16 02:25:13.35: empty line received
2025-01-16 02:25:13.35: ServiceMonitor - start process kube event
2025-01-16 02:25:13.90: PodMonitor - Received BOOKMARK: oldResVer=12110 newResVer=12110
2025-01-16 02:25:13.90: PodMonitor - start process kube event
2025-01-16 02:25:13.90: empty line received
2025-01-16 02:25:13.90: PodMonitor - start process kube event
2025-01-16 02:26:09.79: NetworkMonitor - Received BOOKMARK: oldResVer=11871 newResVer=11871
2025-01-16 02:26:09.79: NetworkMonitor - start process kube event
2025-01-16 02:26:09.79: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:26:09.79: empty line received
2025-01-16 02:26:09.79: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:26:09.79: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:26:09.79: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:26:09.79: NetworkMonitor - start process kube event
2025-01-16 02:26:10.62: IngressMonitor - Received BOOKMARK: oldResVer=11718 newResVer=11718
2025-01-16 02:26:10.62: IngressMonitor - start process kube event
2025-01-16 02:26:10.62: empty line received
2025-01-16 02:26:10.62: IngressMonitor - start process kube event
2025-01-16 02:26:11.41: EndPointMonitor - Received BOOKMARK: oldResVer=11787 newResVer=11787
2025-01-16 02:26:11.41: EndPointMonitor - start process kube event
2025-01-16 02:26:11.41: empty line received
2025-01-16 02:26:11.41: EndPointMonitor - start process kube event
2025-01-16 02:26:11.96: NamespaceMonitor - Received BOOKMARK: oldResVer=11590 newResVer=11590
2025-01-16 02:26:11.96: NamespaceMonitor - start process kube event
2025-01-16 02:26:11.96: empty line received
2025-01-16 02:26:11.96: NamespaceMonitor - start process kube event
2025-01-16 02:26:12.49: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11906 newResVer=11906
2025-01-16 02:26:12.49: NetworkPolicyMonitor - start process kube event
2025-01-16 02:26:12.49: empty line received
2025-01-16 02:26:12.49: NetworkPolicyMonitor - start process kube event
2025-01-16 02:26:13.68: PodMonitor - Received BOOKMARK: oldResVer=12110 newResVer=12110
2025-01-16 02:26:13.68: PodMonitor - start process kube event
2025-01-16 02:26:13.68: empty line received
2025-01-16 02:26:13.68: PodMonitor - start process kube event
2025-01-16 02:26:13.73: ServiceMonitor - Received BOOKMARK: oldResVer=11702 newResVer=11702
2025-01-16 02:26:13.73: ServiceMonitor - start process kube event
2025-01-16 02:26:13.73: empty line received
2025-01-16 02:26:13.73: ServiceMonitor - start process kube event
2025-01-16 02:26:26.33: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:26:26.33: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:26:26.33: PodMonitor - start process kube event
2025-01-16 02:26:26.33: empty line received
2025-01-16 02:26:26.33: PodMonitor - start process kube event
2025-01-16 02:26:38.72: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:26:38.72: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:26:38.72: PodMonitor - start process kube event
2025-01-16 02:26:38.72: empty line received
2025-01-16 02:26:38.72: PodMonitor - start process kube event
2025-01-16 02:27:10.74: NetworkMonitor - Received BOOKMARK: oldResVer=11871 newResVer=11871
2025-01-16 02:27:10.74: NetworkMonitor - start process kube event
2025-01-16 02:27:10.74: empty line received
2025-01-16 02:27:10.74: NetworkMonitor - start process kube event
2025-01-16 02:27:10.76: IngressMonitor - Received BOOKMARK: oldResVer=11718 newResVer=11718
2025-01-16 02:27:10.76: IngressMonitor - start process kube event
2025-01-16 02:27:10.76: empty line received
2025-01-16 02:27:10.76: IngressMonitor - start process kube event
2025-01-16 02:27:11.43: EndPointMonitor - Received BOOKMARK: oldResVer=11787 newResVer=11787
2025-01-16 02:27:11.43: EndPointMonitor - start process kube event
2025-01-16 02:27:11.43: empty line received
2025-01-16 02:27:11.43: EndPointMonitor - start process kube event
2025-01-16 02:27:11.52: NamespaceMonitor - Received BOOKMARK: oldResVer=11590 newResVer=11590
2025-01-16 02:27:11.52: NamespaceMonitor - start process kube event
2025-01-16 02:27:11.52: empty line received
2025-01-16 02:27:11.52: NamespaceMonitor - start process kube event
2025-01-16 02:27:12.87: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11906 newResVer=11906
2025-01-16 02:27:12.87: NetworkPolicyMonitor - start process kube event
2025-01-16 02:27:12.87: empty line received
2025-01-16 02:27:12.87: NetworkPolicyMonitor - start process kube event
2025-01-16 02:27:13.60: ServiceMonitor - Received BOOKMARK: oldResVer=11702 newResVer=11702
2025-01-16 02:27:13.60: ServiceMonitor - start process kube event
2025-01-16 02:27:13.60: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:27:13.60: empty line received
2025-01-16 02:27:13.60: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:27:13.60: VncKubernetes - vnc_sync - Service start
2025-01-16 02:27:13.60: VncKubernetes - vnc_sync - Service done
2025-01-16 02:27:13.60: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:27:13.60: ServiceMonitor - start process kube event
2025-01-16 02:27:13.72: PodMonitor - Received BOOKMARK: oldResVer=12110 newResVer=12443
2025-01-16 02:27:13.72: PodMonitor - start process kube event
2025-01-16 02:27:13.72: PodMonitor - _schedule_vnc_sync
2025-01-16 02:27:13.72: empty line received
2025-01-16 02:27:13.72: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-01-16 02:27:13.72: VncKubernetes - vnc_sync - Pod start
2025-01-16 02:27:13.72: VncKubernetes - vnc_sync - Pod done
2025-01-16 02:27:13.72: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:27:13.72: PodMonitor - start process kube event
2025-01-16 02:27:27.19: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:27:27.19: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:27:27.19: PodMonitor - start process kube event
2025-01-16 02:27:27.19: empty line received
2025-01-16 02:27:27.19: PodMonitor - start process kube event
2025-01-16 02:27:38.57: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:27:38.57: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:27:38.57: PodMonitor - start process kube event
2025-01-16 02:27:38.57: empty line received
2025-01-16 02:27:38.57: PodMonitor - start process kube event
2025-01-16 02:27:51.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:27:51.05: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:27:51.05: PodMonitor - start process kube event
2025-01-16 02:27:51.05: empty line received
2025-01-16 02:27:51.05: PodMonitor - start process kube event
2025-01-16 02:27:52.04: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:27:52.04: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:27:52.04: PodMonitor - start process kube event
2025-01-16 02:27:52.04: empty line received
2025-01-16 02:27:52.04: PodMonitor - start process kube event
2025-01-16 02:28:06.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:28:06.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:28:06.06: PodMonitor - start process kube event
2025-01-16 02:28:06.06: empty line received
2025-01-16 02:28:06.06: PodMonitor - start process kube event
2025-01-16 02:28:10.88: IngressMonitor - Received BOOKMARK: oldResVer=11718 newResVer=11718
2025-01-16 02:28:10.88: IngressMonitor - start process kube event
2025-01-16 02:28:10.88: empty line received
2025-01-16 02:28:10.88: IngressMonitor - start process kube event
2025-01-16 02:28:11.33: NetworkMonitor - Received BOOKMARK: oldResVer=11871 newResVer=11871
2025-01-16 02:28:11.33: NetworkMonitor - start process kube event
2025-01-16 02:28:11.33: empty line received
2025-01-16 02:28:11.33: NetworkMonitor - start process kube event
2025-01-16 02:28:11.47: EndPointMonitor - Received BOOKMARK: oldResVer=11787 newResVer=11787
2025-01-16 02:28:11.47: EndPointMonitor - start process kube event
2025-01-16 02:28:11.47: empty line received
2025-01-16 02:28:11.47: EndPointMonitor - start process kube event
2025-01-16 02:28:12.06: NamespaceMonitor - Received BOOKMARK: oldResVer=11590 newResVer=12499
2025-01-16 02:28:12.06: NamespaceMonitor - start process kube event
2025-01-16 02:28:12.06: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:28:12.06: empty line received
2025-01-16 02:28:12.06: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:28:12.06: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:28:12.06: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:28:12.06: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:28:12.06: NamespaceMonitor - start process kube event
2025-01-16 02:28:13.38: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11906 newResVer=11906
2025-01-16 02:28:13.38: NetworkPolicyMonitor - start process kube event
2025-01-16 02:28:13.38: empty line received
2025-01-16 02:28:13.38: NetworkPolicyMonitor - start process kube event
2025-01-16 02:28:13.54: ServiceMonitor - Received BOOKMARK: oldResVer=11702 newResVer=11702
2025-01-16 02:28:13.54: ServiceMonitor - start process kube event
2025-01-16 02:28:13.54: empty line received
2025-01-16 02:28:13.54: ServiceMonitor - start process kube event
2025-01-16 02:28:13.77: PodMonitor - Received BOOKMARK: oldResVer=12443 newResVer=12573
2025-01-16 02:28:13.77: PodMonitor - start process kube event
2025-01-16 02:28:13.77: empty line received
2025-01-16 02:28:13.77: PodMonitor - start process kube event
2025-01-16 02:29:11.05: IngressMonitor - Received BOOKMARK: oldResVer=11718 newResVer=12641
2025-01-16 02:29:11.05: IngressMonitor - start process kube event
2025-01-16 02:29:11.05: empty line received
2025-01-16 02:29:11.05: IngressMonitor - start process kube event
2025-01-16 02:29:11.36: EndPointMonitor - Received BOOKMARK: oldResVer=11787 newResVer=11787
2025-01-16 02:29:11.36: EndPointMonitor - start process kube event
2025-01-16 02:29:11.36: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:29:11.36: empty line received
2025-01-16 02:29:11.36: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:29:11.36: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:29:11.36: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:29:11.36: EndPointMonitor - start process kube event
2025-01-16 02:29:11.50: NetworkMonitor - Received BOOKMARK: oldResVer=11871 newResVer=11871
2025-01-16 02:29:11.50: NetworkMonitor - start process kube event
2025-01-16 02:29:11.50: empty line received
2025-01-16 02:29:11.50: NetworkMonitor - start process kube event
2025-01-16 02:29:13.27: NamespaceMonitor - Received BOOKMARK: oldResVer=12499 newResVer=12499
2025-01-16 02:29:13.27: NamespaceMonitor - start process kube event
2025-01-16 02:29:13.27: empty line received
2025-01-16 02:29:13.27: NamespaceMonitor - start process kube event
2025-01-16 02:29:13.56: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11906 newResVer=11906
2025-01-16 02:29:13.56: NetworkPolicyMonitor - start process kube event
2025-01-16 02:29:13.56: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:29:13.56: empty line received
2025-01-16 02:29:13.56: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:29:13.56: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:29:13.57: NetworkPolicyMonitor - start process kube event
2025-01-16 02:29:13.57: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:29:13.57: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:29:13.88: PodMonitor - Received BOOKMARK: oldResVer=12573 newResVer=12573
2025-01-16 02:29:13.88: PodMonitor - start process kube event
2025-01-16 02:29:13.88: empty line received
2025-01-16 02:29:13.88: PodMonitor - start process kube event
2025-01-16 02:29:14.26: ServiceMonitor - Received BOOKMARK: oldResVer=11702 newResVer=12623
2025-01-16 02:29:14.26: ServiceMonitor - start process kube event
2025-01-16 02:29:14.26: empty line received
2025-01-16 02:29:14.26: ServiceMonitor - start process kube event
2025-01-16 02:30:10.96: NetworkMonitor - Received BOOKMARK: oldResVer=11871 newResVer=11871
2025-01-16 02:30:10.96: NetworkMonitor - start process kube event
2025-01-16 02:30:10.96: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:30:10.96: empty line received
2025-01-16 02:30:10.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:30:10.96: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:30:10.96: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:30:10.96: NetworkMonitor - start process kube event
2025-01-16 02:30:11.09: IngressMonitor - Received BOOKMARK: oldResVer=12641 newResVer=12641
2025-01-16 02:30:11.09: IngressMonitor - start process kube event
2025-01-16 02:30:11.09: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:30:11.09: empty line received
2025-01-16 02:30:11.09: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:30:11.09: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:30:11.09: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:30:11.09: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:30:11.09: IngressMonitor - start process kube event
2025-01-16 02:30:11.38: EndPointMonitor - Received BOOKMARK: oldResVer=11787 newResVer=12714
2025-01-16 02:30:11.38: EndPointMonitor - start process kube event
2025-01-16 02:30:11.38: empty line received
2025-01-16 02:30:11.38: EndPointMonitor - start process kube event
2025-01-16 02:30:13.64: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11906 newResVer=11906
2025-01-16 02:30:13.64: NetworkPolicyMonitor - start process kube event
2025-01-16 02:30:13.64: empty line received
2025-01-16 02:30:13.64: NetworkPolicyMonitor - start process kube event
2025-01-16 02:30:14.00: NamespaceMonitor - Received BOOKMARK: oldResVer=12499 newResVer=12499
2025-01-16 02:30:14.00: NamespaceMonitor - start process kube event
2025-01-16 02:30:14.00: empty line received
2025-01-16 02:30:14.00: NamespaceMonitor - start process kube event
2025-01-16 02:30:14.08: PodMonitor - Received BOOKMARK: oldResVer=12573 newResVer=12573
2025-01-16 02:30:14.08: PodMonitor - start process kube event
2025-01-16 02:30:14.08: empty line received
2025-01-16 02:30:14.08: PodMonitor - start process kube event
2025-01-16 02:30:14.23: ServiceMonitor - Received BOOKMARK: oldResVer=12623 newResVer=12623
2025-01-16 02:30:14.23: ServiceMonitor - start process kube event
2025-01-16 02:30:14.23: empty line received
2025-01-16 02:30:14.23: ServiceMonitor - start process kube event
2025-01-16 02:31:10.98: IngressMonitor - Received BOOKMARK: oldResVer=12641 newResVer=12641
2025-01-16 02:31:10.98: IngressMonitor - start process kube event
2025-01-16 02:31:10.98: empty line received
2025-01-16 02:31:10.99: IngressMonitor - start process kube event
2025-01-16 02:31:11.74: NetworkMonitor - Received BOOKMARK: oldResVer=11871 newResVer=12802
2025-01-16 02:31:11.74: NetworkMonitor - start process kube event
2025-01-16 02:31:11.74: empty line received
2025-01-16 02:31:11.74: NetworkMonitor - start process kube event
2025-01-16 02:31:11.76: EndPointMonitor - Received BOOKMARK: oldResVer=12714 newResVer=12714
2025-01-16 02:31:11.76: EndPointMonitor - start process kube event
2025-01-16 02:31:11.76: empty line received
2025-01-16 02:31:11.76: EndPointMonitor - start process kube event
2025-01-16 02:31:13.57: NamespaceMonitor - Received BOOKMARK: oldResVer=12499 newResVer=12499
2025-01-16 02:31:13.57: NamespaceMonitor - start process kube event
2025-01-16 02:31:13.57: empty line received
2025-01-16 02:31:13.57: NamespaceMonitor - start process kube event
2025-01-16 02:31:13.81: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11906 newResVer=11906
2025-01-16 02:31:13.81: NetworkPolicyMonitor - start process kube event
2025-01-16 02:31:13.81: empty line received
2025-01-16 02:31:13.81: NetworkPolicyMonitor - start process kube event
2025-01-16 02:31:13.93: PodMonitor - Received BOOKMARK: oldResVer=12573 newResVer=12573
2025-01-16 02:31:13.93: PodMonitor - start process kube event
2025-01-16 02:31:13.93: PodMonitor - _schedule_vnc_sync
2025-01-16 02:31:13.93: empty line received
2025-01-16 02:31:13.93: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-01-16 02:31:13.93: VncKubernetes - vnc_sync - Pod start
2025-01-16 02:31:13.93: VncKubernetes - vnc_sync - Pod done
2025-01-16 02:31:13.93: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:31:13.93: PodMonitor - start process kube event
2025-01-16 02:31:14.78: ServiceMonitor - Received BOOKMARK: oldResVer=12623 newResVer=12623
2025-01-16 02:31:14.78: ServiceMonitor - start process kube event
2025-01-16 02:31:14.78: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:31:14.78: empty line received
2025-01-16 02:31:14.78: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:31:14.78: VncKubernetes - vnc_sync - Service start
2025-01-16 02:31:14.78: VncKubernetes - vnc_sync - Service done
2025-01-16 02:31:14.78: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:31:14.78: ServiceMonitor - start process kube event
2025-01-16 02:31:57.12: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11906 newResVer=12843
2025-01-16 02:31:57.12: NetworkPolicyMonitor - start process kube event
2025-01-16 02:31:57.12: empty line received
2025-01-16 02:31:57.12: NetworkPolicyMonitor - start process kube event
2025-01-16 02:31:58.19: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12843 newResVer=12843
2025-01-16 02:31:58.19: NetworkPolicyMonitor - start process kube event
2025-01-16 02:31:58.19: empty line received
2025-01-16 02:31:58.19: NetworkPolicyMonitor - start process kube event
2025-01-16 02:31:59.22: stop iteration NetworkPolicyMonitor
2025-01-16 02:31:59.22: NetworkPolicyMonitor - start process kube event
2025-01-16 02:31:59.22: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12843
2025-01-16 02:31:59.22: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:31:59.22: NetworkPolicyMonitor - Connect Kube API result 0
2025-01-16 02:31:59.22: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:31:59.22: NetworkPolicyMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12843'})(timeout=120)
2025-01-16 02:31:59.23: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:31:59.23: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:31:59.23: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:31:59.23: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:31:59.23: NetworkPolicyMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12843'})
2025-01-16 02:32:11.11: IngressMonitor - Received BOOKMARK: oldResVer=12641 newResVer=12641
2025-01-16 02:32:11.11: IngressMonitor - start process kube event
2025-01-16 02:32:11.11: empty line received
2025-01-16 02:32:11.11: IngressMonitor - start process kube event
2025-01-16 02:32:11.95: EndPointMonitor - Received BOOKMARK: oldResVer=12714 newResVer=12714
2025-01-16 02:32:11.95: EndPointMonitor - start process kube event
2025-01-16 02:32:11.95: empty line received
2025-01-16 02:32:11.95: EndPointMonitor - start process kube event
2025-01-16 02:32:12.22: NetworkMonitor - Received BOOKMARK: oldResVer=12802 newResVer=12802
2025-01-16 02:32:12.22: NetworkMonitor - start process kube event
2025-01-16 02:32:12.22: empty line received
2025-01-16 02:32:12.22: NetworkMonitor - start process kube event
2025-01-16 02:32:13.83: PodMonitor - Received BOOKMARK: oldResVer=12573 newResVer=12573
2025-01-16 02:32:13.83: PodMonitor - start process kube event
2025-01-16 02:32:13.83: empty line received
2025-01-16 02:32:13.83: PodMonitor - start process kube event
2025-01-16 02:32:14.09: NamespaceMonitor - Received BOOKMARK: oldResVer=12499 newResVer=12499
2025-01-16 02:32:14.09: NamespaceMonitor - start process kube event
2025-01-16 02:32:14.09: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:32:14.09: empty line received
2025-01-16 02:32:14.09: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:32:14.09: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:32:14.09: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:32:14.09: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:32:14.09: NamespaceMonitor - start process kube event
2025-01-16 02:32:14.26: ServiceMonitor - Received BOOKMARK: oldResVer=12623 newResVer=12623
2025-01-16 02:32:14.26: ServiceMonitor - start process kube event
2025-01-16 02:32:14.26: empty line received
2025-01-16 02:32:14.26: ServiceMonitor - start process kube event
2025-01-16 02:32:28.37: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:32:28.37: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:32:28.37: PodMonitor - start process kube event
2025-01-16 02:32:28.37: empty line received
2025-01-16 02:32:28.37: PodMonitor - start process kube event
2025-01-16 02:32:44.83: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:32:44.83: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:32:44.83: PodMonitor - start process kube event
2025-01-16 02:32:44.83: empty line received
2025-01-16 02:32:44.83: PodMonitor - start process kube event
2025-01-16 02:32:58.31: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:32:58.31: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:32:58.31: PodMonitor - start process kube event
2025-01-16 02:32:58.31: empty line received
2025-01-16 02:32:58.31: PodMonitor - start process kube event
2025-01-16 02:33:10.37: IngressMonitor - Received BOOKMARK: oldResVer=12641 newResVer=12641
2025-01-16 02:33:10.37: IngressMonitor - start process kube event
2025-01-16 02:33:10.37: empty line received
2025-01-16 02:33:10.37: IngressMonitor - start process kube event
2025-01-16 02:33:11.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:33:11.05: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:33:11.05: PodMonitor - start process kube event
2025-01-16 02:33:11.05: empty line received
2025-01-16 02:33:11.05: PodMonitor - start process kube event
2025-01-16 02:33:11.88: NetworkMonitor - Received BOOKMARK: oldResVer=12802 newResVer=12802
2025-01-16 02:33:11.88: NetworkMonitor - start process kube event
2025-01-16 02:33:11.88: empty line received
2025-01-16 02:33:11.88: NetworkMonitor - start process kube event
2025-01-16 02:33:12.25: EndPointMonitor - Received BOOKMARK: oldResVer=12714 newResVer=12714
2025-01-16 02:33:12.25: EndPointMonitor - start process kube event
2025-01-16 02:33:12.25: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:33:12.25: empty line received
2025-01-16 02:33:12.25: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:33:12.25: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:33:12.25: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:33:12.25: EndPointMonitor - start process kube event
2025-01-16 02:33:13.17: PodMonitor - Received BOOKMARK: oldResVer=12573 newResVer=13005
2025-01-16 02:33:13.17: PodMonitor - start process kube event
2025-01-16 02:33:13.17: empty line received
2025-01-16 02:33:13.17: PodMonitor - start process kube event
2025-01-16 02:33:14.62: ServiceMonitor - Received BOOKMARK: oldResVer=12623 newResVer=12623
2025-01-16 02:33:14.62: ServiceMonitor - start process kube event
2025-01-16 02:33:14.62: empty line received
2025-01-16 02:33:14.62: ServiceMonitor - start process kube event
2025-01-16 02:33:15.24: NamespaceMonitor - Received BOOKMARK: oldResVer=12499 newResVer=12499
2025-01-16 02:33:15.24: NamespaceMonitor - start process kube event
2025-01-16 02:33:15.24: empty line received
2025-01-16 02:33:15.24: NamespaceMonitor - start process kube event
2025-01-16 02:33:29.34: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:33:29.34: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:33:29.34: PodMonitor - start process kube event
2025-01-16 02:33:29.34: empty line received
2025-01-16 02:33:29.34: PodMonitor - start process kube event
2025-01-16 02:33:37.71: PodMonitor - Received BOOKMARK: oldResVer=13005 newResVer=13031
2025-01-16 02:33:37.71: PodMonitor - start process kube event
2025-01-16 02:33:37.71: empty line received
2025-01-16 02:33:37.71: PodMonitor - start process kube event
2025-01-16 02:33:38.80: PodMonitor - Received BOOKMARK: oldResVer=13031 newResVer=13031
2025-01-16 02:33:38.80: PodMonitor - start process kube event
2025-01-16 02:33:38.80: empty line received
2025-01-16 02:33:38.80: PodMonitor - start process kube event
2025-01-16 02:33:39.95: stop iteration PodMonitor
2025-01-16 02:33:39.95: PodMonitor - start process kube event
2025-01-16 02:33:39.95: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13031
2025-01-16 02:33:39.95: PodMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:33:39.95: PodMonitor - Connect Kube API result 0
2025-01-16 02:33:39.95: PodMonitor - _schedule_vnc_sync
2025-01-16 02:33:39.95: PodMonitor - Start Watching request https://10.0.0.12:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13031'})(timeout=120)
2025-01-16 02:33:39.95: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-01-16 02:33:39.95: VncKubernetes - vnc_sync - Pod start
2025-01-16 02:33:39.95: VncKubernetes - vnc_sync - Pod done
2025-01-16 02:33:39.95: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:33:39.95: PodMonitor - Watches https://10.0.0.12:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13031'})
2025-01-16 02:33:41.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:33:41.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:33:41.06: PodMonitor - start process kube event
2025-01-16 02:33:41.06: empty line received
2025-01-16 02:33:41.06: PodMonitor - start process kube event
2025-01-16 02:33:44.85: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:33:44.85: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:33:44.85: PodMonitor - start process kube event
2025-01-16 02:33:44.85: empty line received
2025-01-16 02:33:44.85: PodMonitor - start process kube event
2025-01-16 02:33:58.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:33:58.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:33:58.06: PodMonitor - start process kube event
2025-01-16 02:33:58.06: empty line received
2025-01-16 02:33:58.06: PodMonitor - start process kube event
2025-01-16 02:33:59.23: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:33:59.23: NetworkPolicyMonitor - start process kube event
2025-01-16 02:33:59.23: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12843
2025-01-16 02:33:59.23: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:33:59.23: NetworkPolicyMonitor - Connect Kube API result 0
2025-01-16 02:33:59.23: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:33:59.23: NetworkPolicyMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12843'})(timeout=120)
2025-01-16 02:33:59.24: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:33:59.24: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:33:59.24: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:33:59.24: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:33:59.24: NetworkPolicyMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12843'})
2025-01-16 02:34:10.29: IngressMonitor - Received BOOKMARK: oldResVer=12641 newResVer=12641
2025-01-16 02:34:10.29: IngressMonitor - start process kube event
2025-01-16 02:34:10.29: empty line received
2025-01-16 02:34:10.29: IngressMonitor - start process kube event
2025-01-16 02:34:11.99: NetworkMonitor - Received BOOKMARK: oldResVer=12802 newResVer=12802
2025-01-16 02:34:11.99: NetworkMonitor - start process kube event
2025-01-16 02:34:11.99: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:34:11.99: empty line received
2025-01-16 02:34:11.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:34:11.99: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:34:11.99: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:34:11.99: NetworkMonitor - start process kube event
2025-01-16 02:34:12.32: EndPointMonitor - Received BOOKMARK: oldResVer=12714 newResVer=12714
2025-01-16 02:34:12.32: EndPointMonitor - start process kube event
2025-01-16 02:34:12.32: empty line received
2025-01-16 02:34:12.32: EndPointMonitor - start process kube event
2025-01-16 02:34:14.96: ServiceMonitor - Received BOOKMARK: oldResVer=12623 newResVer=12623
2025-01-16 02:34:14.96: ServiceMonitor - start process kube event
2025-01-16 02:34:14.96: empty line received
2025-01-16 02:34:14.96: ServiceMonitor - start process kube event
2025-01-16 02:34:15.65: NamespaceMonitor - Received BOOKMARK: oldResVer=12499 newResVer=12499
2025-01-16 02:34:15.65: NamespaceMonitor - start process kube event
2025-01-16 02:34:15.65: empty line received
2025-01-16 02:34:15.65: NamespaceMonitor - start process kube event
2025-01-16 02:34:39.16: PodMonitor - Received BOOKMARK: oldResVer=13031 newResVer=13074
2025-01-16 02:34:39.16: PodMonitor - start process kube event
2025-01-16 02:34:39.16: empty line received
2025-01-16 02:34:39.16: PodMonitor - start process kube event
2025-01-16 02:35:11.07: IngressMonitor - Received BOOKMARK: oldResVer=12641 newResVer=12641
2025-01-16 02:35:11.07: IngressMonitor - start process kube event
2025-01-16 02:35:11.07: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:35:11.07: empty line received
2025-01-16 02:35:11.07: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:35:11.07: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:35:11.07: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:35:11.07: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:35:11.07: IngressMonitor - start process kube event
2025-01-16 02:35:12.32: EndPointMonitor - Received BOOKMARK: oldResVer=12714 newResVer=12714
2025-01-16 02:35:12.32: EndPointMonitor - start process kube event
2025-01-16 02:35:12.32: empty line received
2025-01-16 02:35:12.32: EndPointMonitor - start process kube event
2025-01-16 02:35:12.63: NetworkMonitor - Received BOOKMARK: oldResVer=12802 newResVer=12802
2025-01-16 02:35:12.63: NetworkMonitor - start process kube event
2025-01-16 02:35:12.63: empty line received
2025-01-16 02:35:12.63: NetworkMonitor - start process kube event
2025-01-16 02:35:14.90: ServiceMonitor - Received BOOKMARK: oldResVer=12623 newResVer=12623
2025-01-16 02:35:14.90: ServiceMonitor - start process kube event
2025-01-16 02:35:14.90: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:35:14.90: empty line received
2025-01-16 02:35:14.90: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:35:14.90: VncKubernetes - vnc_sync - Service start
2025-01-16 02:35:14.90: VncKubernetes - vnc_sync - Service done
2025-01-16 02:35:14.90: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:35:14.90: ServiceMonitor - start process kube event
2025-01-16 02:35:15.43: NamespaceMonitor - Received BOOKMARK: oldResVer=12499 newResVer=12499
2025-01-16 02:35:15.43: NamespaceMonitor - start process kube event
2025-01-16 02:35:15.43: empty line received
2025-01-16 02:35:15.43: NamespaceMonitor - start process kube event
2025-01-16 02:35:39.20: PodMonitor - Received BOOKMARK: oldResVer=13074 newResVer=13074
2025-01-16 02:35:39.20: PodMonitor - start process kube event
2025-01-16 02:35:39.20: empty line received
2025-01-16 02:35:39.20: PodMonitor - start process kube event
2025-01-16 02:35:59.25: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:35:59.25: NetworkPolicyMonitor - start process kube event
2025-01-16 02:35:59.25: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12843
2025-01-16 02:35:59.25: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:35:59.25: NetworkPolicyMonitor - Connect Kube API result 0
2025-01-16 02:35:59.25: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:35:59.25: NetworkPolicyMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12843'})(timeout=120)
2025-01-16 02:35:59.25: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:35:59.25: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:35:59.26: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:35:59.26: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:35:59.26: NetworkPolicyMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12843'})
2025-01-16 02:36:10.96: IngressMonitor - Received BOOKMARK: oldResVer=12641 newResVer=12641
2025-01-16 02:36:10.96: IngressMonitor - start process kube event
2025-01-16 02:36:10.96: empty line received
2025-01-16 02:36:10.96: IngressMonitor - start process kube event
2025-01-16 02:36:12.36: NetworkMonitor - Received BOOKMARK: oldResVer=12802 newResVer=12802
2025-01-16 02:36:12.36: NetworkMonitor - start process kube event
2025-01-16 02:36:12.36: empty line received
2025-01-16 02:36:12.36: NetworkMonitor - start process kube event
2025-01-16 02:36:13.08: EndPointMonitor - Received BOOKMARK: oldResVer=12714 newResVer=12714
2025-01-16 02:36:13.08: EndPointMonitor - start process kube event
2025-01-16 02:36:13.08: empty line received
2025-01-16 02:36:13.08: EndPointMonitor - start process kube event
2025-01-16 02:36:14.46: ServiceMonitor - Received BOOKMARK: oldResVer=12623 newResVer=12623
2025-01-16 02:36:14.46: ServiceMonitor - start process kube event
2025-01-16 02:36:14.46: empty line received
2025-01-16 02:36:14.46: ServiceMonitor - start process kube event
2025-01-16 02:36:16.16: NamespaceMonitor - Received BOOKMARK: oldResVer=12499 newResVer=12499
2025-01-16 02:36:16.16: NamespaceMonitor - start process kube event
2025-01-16 02:36:16.16: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:36:16.16: empty line received
2025-01-16 02:36:16.16: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:36:16.16: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:36:16.16: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:36:16.16: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:36:16.16: NamespaceMonitor - start process kube event
2025-01-16 02:36:39.52: PodMonitor - Received BOOKMARK: oldResVer=13074 newResVer=13074
2025-01-16 02:36:39.52: PodMonitor - start process kube event
2025-01-16 02:36:39.52: empty line received
2025-01-16 02:36:39.52: PodMonitor - start process kube event
2025-01-16 02:37:10.70: IngressMonitor - Received BOOKMARK: oldResVer=12641 newResVer=12641
2025-01-16 02:37:10.71: IngressMonitor - start process kube event
2025-01-16 02:37:10.71: empty line received
2025-01-16 02:37:10.71: IngressMonitor - start process kube event
2025-01-16 02:37:12.02: NetworkMonitor - Received BOOKMARK: oldResVer=12802 newResVer=12802
2025-01-16 02:37:12.02: NetworkMonitor - start process kube event
2025-01-16 02:37:12.02: empty line received
2025-01-16 02:37:12.02: NetworkMonitor - start process kube event
2025-01-16 02:37:13.02: EndPointMonitor - Received BOOKMARK: oldResVer=12714 newResVer=12714
2025-01-16 02:37:13.02: EndPointMonitor - start process kube event
2025-01-16 02:37:13.02: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:37:13.02: empty line received
2025-01-16 02:37:13.02: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:37:13.02: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:37:13.02: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:37:13.02: EndPointMonitor - start process kube event
2025-01-16 02:37:14.14: ServiceMonitor - Received BOOKMARK: oldResVer=12623 newResVer=12623
2025-01-16 02:37:14.14: ServiceMonitor - start process kube event
2025-01-16 02:37:14.14: empty line received
2025-01-16 02:37:14.14: ServiceMonitor - start process kube event
2025-01-16 02:37:16.75: NamespaceMonitor - Received BOOKMARK: oldResVer=12499 newResVer=12499
2025-01-16 02:37:16.75: NamespaceMonitor - start process kube event
2025-01-16 02:37:16.75: empty line received
2025-01-16 02:37:16.75: NamespaceMonitor - start process kube event
2025-01-16 02:37:39.87: PodMonitor - Received BOOKMARK: oldResVer=13074 newResVer=13074
2025-01-16 02:37:39.87: PodMonitor - start process kube event
2025-01-16 02:37:39.87: empty line received
2025-01-16 02:37:39.87: PodMonitor - start process kube event
2025-01-16 02:37:59.26: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:37:59.26: NetworkPolicyMonitor - start process kube event
2025-01-16 02:37:59.26: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12843
2025-01-16 02:37:59.26: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:37:59.26: NetworkPolicyMonitor - Connect Kube API result 0
2025-01-16 02:37:59.26: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:37:59.26: NetworkPolicyMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12843'})(timeout=120)
2025-01-16 02:37:59.26: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:37:59.26: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:37:59.27: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:37:59.27: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:37:59.27: NetworkPolicyMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12843'})
2025-01-16 02:38:06.75: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:38:06.75: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:38:06.75: PodMonitor - start process kube event
2025-01-16 02:38:06.75: PodMonitor - _schedule_vnc_sync
2025-01-16 02:38:06.75: empty line received
2025-01-16 02:38:06.75: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-01-16 02:38:06.75: VncKubernetes - vnc_sync - Pod start
2025-01-16 02:38:06.75: VncKubernetes - vnc_sync - Pod done
2025-01-16 02:38:06.75: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:38:06.75: PodMonitor - start process kube event
2025-01-16 02:38:07.82: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:38:07.82: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:38:07.82: PodMonitor - start process kube event
2025-01-16 02:38:07.82: empty line received
2025-01-16 02:38:07.82: PodMonitor - start process kube event
2025-01-16 02:38:10.91: IngressMonitor - Received BOOKMARK: oldResVer=12641 newResVer=12641
2025-01-16 02:38:10.91: IngressMonitor - start process kube event
2025-01-16 02:38:10.91: empty line received
2025-01-16 02:38:10.91: IngressMonitor - start process kube event
2025-01-16 02:38:12.70: NetworkMonitor - Received BOOKMARK: oldResVer=12802 newResVer=12802
2025-01-16 02:38:12.70: NetworkMonitor - start process kube event
2025-01-16 02:38:12.70: NetworkMonitor - _schedule_vnc_sync
2025-01-16 02:38:12.70: empty line received
2025-01-16 02:38:12.70: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-01-16 02:38:12.70: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-01-16 02:38:12.70: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:38:12.70: NetworkMonitor - start process kube event
2025-01-16 02:38:12.97: EndPointMonitor - Received BOOKMARK: oldResVer=12714 newResVer=12714
2025-01-16 02:38:12.97: EndPointMonitor - start process kube event
2025-01-16 02:38:12.97: empty line received
2025-01-16 02:38:12.97: EndPointMonitor - start process kube event
2025-01-16 02:38:14.42: ServiceMonitor - Received BOOKMARK: oldResVer=12623 newResVer=12623
2025-01-16 02:38:14.42: ServiceMonitor - start process kube event
2025-01-16 02:38:14.42: empty line received
2025-01-16 02:38:14.42: ServiceMonitor - start process kube event
2025-01-16 02:38:16.32: NamespaceMonitor - Received BOOKMARK: oldResVer=12499 newResVer=13410
2025-01-16 02:38:16.32: NamespaceMonitor - start process kube event
2025-01-16 02:38:16.32: empty line received
2025-01-16 02:38:16.32: NamespaceMonitor - start process kube event
2025-01-16 02:38:33.70: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:38:33.70: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:38:33.70: PodMonitor - start process kube event
2025-01-16 02:38:33.70: empty line received
2025-01-16 02:38:33.70: PodMonitor - start process kube event
2025-01-16 02:38:39.56: PodMonitor - Received BOOKMARK: oldResVer=13074 newResVer=13463
2025-01-16 02:38:39.56: PodMonitor - start process kube event
2025-01-16 02:38:39.56: empty line received
2025-01-16 02:38:39.56: PodMonitor - start process kube event
2025-01-16 02:38:47.17: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:38:47.17: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:38:47.17: PodMonitor - start process kube event
2025-01-16 02:38:47.17: empty line received
2025-01-16 02:38:47.17: PodMonitor - start process kube event
2025-01-16 02:39:11.19: IngressMonitor - Received BOOKMARK: oldResVer=12641 newResVer=12641
2025-01-16 02:39:11.19: IngressMonitor - start process kube event
2025-01-16 02:39:11.19: IngressMonitor - _schedule_vnc_sync
2025-01-16 02:39:11.19: empty line received
2025-01-16 02:39:11.19: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-01-16 02:39:11.19: VncKubernetes - vnc_sync - Ingress start
2025-01-16 02:39:11.19: VncKubernetes - vnc_sync - Ingress done
2025-01-16 02:39:11.19: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:39:11.19: IngressMonitor - start process kube event
2025-01-16 02:39:12.14: NetworkMonitor - Received BOOKMARK: oldResVer=12802 newResVer=12802
2025-01-16 02:39:12.14: NetworkMonitor - start process kube event
2025-01-16 02:39:12.14: empty line received
2025-01-16 02:39:12.14: NetworkMonitor - start process kube event
2025-01-16 02:39:12.69: EndPointMonitor - Received BOOKMARK: oldResVer=12714 newResVer=12714
2025-01-16 02:39:12.70: EndPointMonitor - start process kube event
2025-01-16 02:39:12.70: empty line received
2025-01-16 02:39:12.70: EndPointMonitor - start process kube event
2025-01-16 02:39:14.80: ServiceMonitor - Received BOOKMARK: oldResVer=12623 newResVer=12623
2025-01-16 02:39:14.80: ServiceMonitor - start process kube event
2025-01-16 02:39:14.80: empty line received
2025-01-16 02:39:14.80: ServiceMonitor - start process kube event
2025-01-16 02:39:16.21: NamespaceMonitor - Received BOOKMARK: oldResVer=13410 newResVer=13410
2025-01-16 02:39:16.21: NamespaceMonitor - start process kube event
2025-01-16 02:39:16.21: empty line received
2025-01-16 02:39:16.21: NamespaceMonitor - start process kube event
2025-01-16 02:39:33.46: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:39:33.46: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:39:33.46: PodMonitor - start process kube event
2025-01-16 02:39:33.46: empty line received
2025-01-16 02:39:33.46: PodMonitor - start process kube event
2025-01-16 02:39:39.62: PodMonitor - Received BOOKMARK: oldResVer=13463 newResVer=13550
2025-01-16 02:39:39.62: PodMonitor - start process kube event
2025-01-16 02:39:39.62: empty line received
2025-01-16 02:39:39.62: PodMonitor - start process kube event
2025-01-16 02:39:46.86: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:39:46.86: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:39:46.86: PodMonitor - start process kube event
2025-01-16 02:39:46.86: empty line received
2025-01-16 02:39:46.86: PodMonitor - start process kube event
2025-01-16 02:39:58.06: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-2jg8r:6210d3da-2b73-4b71-9690-ff9cc3760d50
2025-01-16 02:39:58.06: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-2jg8r (hostNetwork=True)
2025-01-16 02:39:58.06: PodMonitor - start process kube event
2025-01-16 02:39:58.06: empty line received
2025-01-16 02:39:58.06: PodMonitor - start process kube event
2025-01-16 02:39:59.27: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:39:59.27: NetworkPolicyMonitor - start process kube event
2025-01-16 02:39:59.27: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12843
2025-01-16 02:39:59.27: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:39:59.27: NetworkPolicyMonitor - Connect Kube API result 0
2025-01-16 02:39:59.28: NetworkPolicyMonitor - _schedule_vnc_sync
2025-01-16 02:39:59.28: NetworkPolicyMonitor - Start Watching request https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12843'})(timeout=120)
2025-01-16 02:39:59.28: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-01-16 02:39:59.28: VncKubernetes - vnc_sync - NetworkPolicy start
2025-01-16 02:39:59.28: VncKubernetes - vnc_sync - NetworkPolicy done
2025-01-16 02:39:59.28: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:39:59.29: NetworkPolicyMonitor - Watches https://10.0.0.12:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12843'})
2025-01-16 02:40:11.34: IngressMonitor - Received BOOKMARK: oldResVer=12641 newResVer=13560
2025-01-16 02:40:11.34: IngressMonitor - start process kube event
2025-01-16 02:40:11.34: empty line received
2025-01-16 02:40:11.34: IngressMonitor - start process kube event
2025-01-16 02:40:12.26: NetworkMonitor - Received BOOKMARK: oldResVer=12802 newResVer=12802
2025-01-16 02:40:12.26: NetworkMonitor - start process kube event
2025-01-16 02:40:12.26: empty line received
2025-01-16 02:40:12.26: NetworkMonitor - start process kube event
2025-01-16 02:40:13.01: EndPointMonitor - Received BOOKMARK: oldResVer=12714 newResVer=12714
2025-01-16 02:40:13.01: EndPointMonitor - start process kube event
2025-01-16 02:40:13.01: empty line received
2025-01-16 02:40:13.01: EndPointMonitor - start process kube event
2025-01-16 02:40:14.44: ServiceMonitor - Received BOOKMARK: oldResVer=12623 newResVer=13540
2025-01-16 02:40:14.44: ServiceMonitor - start process kube event
2025-01-16 02:40:14.44: ServiceMonitor - _schedule_vnc_sync
2025-01-16 02:40:14.44: empty line received
2025-01-16 02:40:14.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-01-16 02:40:14.44: VncKubernetes - vnc_sync - Service start
2025-01-16 02:40:14.44: VncKubernetes - vnc_sync - Service done
2025-01-16 02:40:14.44: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:40:14.44: ServiceMonitor - start process kube event
2025-01-16 02:40:16.72: NamespaceMonitor - Received BOOKMARK: oldResVer=13410 newResVer=13410
2025-01-16 02:40:16.72: NamespaceMonitor - start process kube event
2025-01-16 02:40:16.72: NamespaceMonitor - _schedule_vnc_sync
2025-01-16 02:40:16.72: empty line received
2025-01-16 02:40:16.72: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-01-16 02:40:16.72: VncKubernetes - vnc_sync - Namespace start
2025-01-16 02:40:16.72: VncKubernetes - vnc_sync - Namespace done
2025-01-16 02:40:16.72: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:40:16.72: NamespaceMonitor - start process kube event
2025-01-16 02:40:39.74: PodMonitor - Received BOOKMARK: oldResVer=13550 newResVer=13585
2025-01-16 02:40:39.74: PodMonitor - start process kube event
2025-01-16 02:40:39.74: empty line received
2025-01-16 02:40:39.74: PodMonitor - start process kube event
2025-01-16 02:41:11.63: IngressMonitor - Received BOOKMARK: oldResVer=13560 newResVer=13560
2025-01-16 02:41:11.64: IngressMonitor - start process kube event
2025-01-16 02:41:11.64: empty line received
2025-01-16 02:41:11.64: IngressMonitor - start process kube event
2025-01-16 02:41:12.78: NetworkMonitor - Received BOOKMARK: oldResVer=12802 newResVer=12802
2025-01-16 02:41:12.78: NetworkMonitor - start process kube event
2025-01-16 02:41:12.78: empty line received
2025-01-16 02:41:12.79: NetworkMonitor - start process kube event
2025-01-16 02:41:13.24: EndPointMonitor - Received BOOKMARK: oldResVer=12714 newResVer=13641
2025-01-16 02:41:13.24: EndPointMonitor - start process kube event
2025-01-16 02:41:13.24: EndPointMonitor - _schedule_vnc_sync
2025-01-16 02:41:13.24: empty line received
2025-01-16 02:41:13.24: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-01-16 02:41:13.24: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-01-16 02:41:13.24: VncKubernetes - wait event (qsize=0 timeout=120)
2025-01-16 02:41:13.24: EndPointMonitor - start process kube event
2025-01-16 02:41:14.83: ServiceMonitor - Received BOOKMARK: oldResVer=13540 newResVer=13540
2025-01-16 02:41:14.83: ServiceMonitor - start process kube event
2025-01-16 02:41:14.83: empty line received
2025-01-16 02:41:14.83: ServiceMonitor - start process kube event
2025-01-16 02:41:16.72: NamespaceMonitor - Received BOOKMARK: oldResVer=13410 newResVer=13410
2025-01-16 02:41:16.72: NamespaceMonitor - start process kube event
2025-01-16 02:41:16.72: empty line received
2025-01-16 02:41:16.72: NamespaceMonitor - start process kube event
2025-01-16 02:41:39.23: PodMonitor - Received BOOKMARK: oldResVer=13585 newResVer=13585
2025-01-16 02:41:39.23: PodMonitor - start process kube event
2025-01-16 02:41:39.23: empty line received
2025-01-16 02:41:39.23: PodMonitor - start process kube event
2025-01-16 02:41:59.29: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.12', port=6443): Read timed out.
2025-01-16 02:41:59.29: NetworkPolicyMonitor - start process kube event
2025-01-16 02:41:59.29: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12843
2025-01-16 02:41:59.29: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.12:6443
2025-01-16 02:41:59.29: NetworkPolicyMonitor - Connect Kube API result 0
2025-01-16 02:41:59.29: NetworkPolicyMonitor - _schedule_vnc_sync