INFO: =================== Mon Jan 13 01:58:26 UTC 2025 =================== INFO: Waiting for cassandra 2/30 INFO: Waiting for cassandra 3/30 INFO: Waiting for cassandra 4/30 INFO: Waiting for cassandra 5/30 INFO: Waiting for cassandra 6/30 INFO: Waiting for cassandra 7/30 INFO: Waiting for cassandra 8/30 INFO: Waiting for cassandra 9/30 INFO: Waiting for cassandra 10/30 INFO: Cassandra is connected /usr/local/lib/python3.6/site-packages/cfgm_common/vnc_kombu.py:10: MonkeyPatchWarning: Patching more than once will result in the union of all True parameters being patched gevent.monkey.patch_all() 01/13/2025 02:00:07.288 7fbdccfb1ec8 [contrail-kube-manager] [INFO]: SANDESH: CONNECT TO COLLECTOR: True 01/13/2025 02:00:07.593 7fbdccfb1ec8 [contrail-kube-manager] [INFO]: SANDESH: Logging: LEVEL: [SYS_INFO] -> [SYS_NOTICE] 2025-01-13 02:00:08.16: KubeMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:00:08.16: KubeMonitor - Connect Kube API result 0 2025-01-13 02:00:08.27: KubeMonitor - KubeMonitor init done: url=https://10.0.0.27:6443/api/v1 2025-01-13 02:00:08.28: NamespaceMonitor - KubeMonitor init done: url=https://10.0.0.27:6443/api/v1 2025-01-13 02:00:08.28: NetworkMonitor - KubeMonitor init done: url=https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1 2025-01-13 02:00:08.29: PodMonitor - KubeMonitor init done: url=https://10.0.0.27:6443/api/v1 2025-01-13 02:00:08.30: ServiceMonitor - KubeMonitor init done: url=https://10.0.0.27:6443/api/v1 2025-01-13 02:00:08.30: NetworkPolicyMonitor - KubeMonitor init done: url=https://10.0.0.27:6443/apis/networking.k8s.io/v1 2025-01-13 02:00:08.31: EndPointMonitor - KubeMonitor init done: url=https://10.0.0.27:6443/api/v1 2025-01-13 02:00:08.31: IngressMonitor - KubeMonitor init done: url=https://10.0.0.27:6443/apis/networking.k8s.io/v1 2025-01-13 02:00:08.31: VncKubernetes - vnc_connect starting 2025-01-13 02:00:08.33: VncKubernetes - vnc_connect failed: 2025-01-13 02:00:11.39: VncKubernetes - vnc_connect failed: 2025-01-13 02:00:14.41: VncKubernetes - vnc_connect failed: 2025-01-13 02:00:17.48: VncKubernetes - vnc_connect failed: 2025-01-13 02:00:20.52: VncKubernetes - vnc_connect failed: 2025-01-13 02:00:23.54: VncKubernetes - vnc_connect failed: 2025-01-13 02:00:26.56: VncKubernetes - vnc_connect failed: 2025-01-13 02:00:29.67: VncKubernetes - vnc_connect done 2025-01-13 02:00:30.61: default-domain domain available. 2025-01-13 02:00:41.79: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:00:41.79: NamespaceMonitor - start process kube event 2025-01-13 02:00:41.79: NamespaceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-01-13 02:00:41.79: NamespaceMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:00:41.79: NetworkMonitor - start process kube event 2025-01-13 02:00:41.79: NetworkMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-01-13 02:00:41.79: NetworkMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:00:41.79: PodMonitor - start process kube event 2025-01-13 02:00:41.79: PodMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-01-13 02:00:41.79: PodMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:00:41.79: ServiceMonitor - start process kube event 2025-01-13 02:00:41.79: ServiceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-01-13 02:00:41.79: ServiceMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:00:41.79: NetworkPolicyMonitor - start process kube event 2025-01-13 02:00:41.79: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-01-13 02:00:41.79: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:00:41.79: EndPointMonitor - start process kube event 2025-01-13 02:00:41.79: EndPointMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-01-13 02:00:41.79: EndPointMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:00:41.79: IngressMonitor - start process kube event 2025-01-13 02:00:41.79: IngressMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None 2025-01-13 02:00:41.79: IngressMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:00:41.79: IngressMonitor - Connect Kube API result 0 2025-01-13 02:00:41.79: IngressMonitor - Start init url=https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses resource_version=None 2025-01-13 02:00:41.79: EndPointMonitor - Connect Kube API result 0 2025-01-13 02:00:41.79: EndPointMonitor - Start init url=https://10.0.0.27:6443/api/v1/endpoints resource_version=None 2025-01-13 02:00:41.80: NetworkPolicyMonitor - Connect Kube API result 0 2025-01-13 02:00:41.80: NetworkPolicyMonitor - Start init url=https://10.0.0.27:6443/apis/networking.k8s.io/v1/networkpolicies resource_version=None 2025-01-13 02:00:41.80: ServiceMonitor - Connect Kube API result 0 2025-01-13 02:00:41.80: ServiceMonitor - Start init url=https://10.0.0.27:6443/api/v1/services resource_version=None 2025-01-13 02:00:41.80: PodMonitor - Connect Kube API result 0 2025-01-13 02:00:41.80: PodMonitor - Start init url=https://10.0.0.27:6443/api/v1/pods resource_version=None 2025-01-13 02:00:41.80: NetworkMonitor - Connect Kube API result 0 2025-01-13 02:00:41.80: NamespaceMonitor - Connect Kube API result 0 2025-01-13 02:00:41.81: NamespaceMonitor - Start init url=https://10.0.0.27:6443/api/v1/namespaces resource_version=None 2025-01-13 02:00:41.84: IngressMonitor - Done init url=https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses, resource_version=10187 2025-01-13 02:00:41.84: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:00:41.84: IngressMonitor - Start Watching request https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:00:41.84: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:00:41.84: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:00:41.84: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:00:41.84: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:00:41.85: IngressMonitor - Watches https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:00:41.85: ServiceMonitor - Got ADDED Service default:kubernetes:f46c494d-fe06-407e-8e1e-8241ee72e7c8 2025-01-13 02:00:41.86: NamespaceMonitor - Got ADDED Namespace None:default:aea16c69-f00d-4539-8b46-15e4190e8f1a 2025-01-13 02:00:41.86: EndPointMonitor - Got ADDED Endpoints default:kubernetes:870fe378-6d56-4d54-a29f-d8c7aac57d6f 2025-01-13 02:00:41.86: NetworkPolicyMonitor - Done init url=https://10.0.0.27:6443/apis/networking.k8s.io/v1/networkpolicies, resource_version=10187 2025-01-13 02:00:41.86: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:00:41.86: NetworkPolicyMonitor - Start Watching request https://10.0.0.27:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:00:41.86: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Service ns=default) VncService - Got ADDED Service default:kubernetes:f46c494d-fe06-407e-8e1e-8241ee72e7c8 2025-01-13 02:00:41.87: PodMonitor - Skipped ADDED Pod kube-system:config-zookeeper-j9s4n (hostNetwork=True) 2025-01-13 02:00:41.87: NetworkMonitor - Start init url=https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions resource_version=None 2025-01-13 02:00:41.87: NetworkPolicyMonitor - Watches https://10.0.0.27:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:00:41.87: EndPointMonitor - Got ADDED Endpoints kube-system:coredns:0df65d6d-8815-4a95-9790-cb07b7433312 2025-01-13 02:00:41.87: EndPointMonitor - Done init url=https://10.0.0.27:6443/api/v1/endpoints, resource_version=10187 2025-01-13 02:00:41.87: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:00:41.87: EndPointMonitor - Start Watching request https://10.0.0.27:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:00:41.88: ServiceMonitor - Got ADDED Service kube-system:coredns:ad8e352a-eddd-403f-9cf4-8fc3f72d9b59 2025-01-13 02:00:41.88: ServiceMonitor - Done init url=https://10.0.0.27:6443/api/v1/services, resource_version=10187 2025-01-13 02:00:41.88: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:00:41.88: ServiceMonitor - Start Watching request https://10.0.0.27:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:00:41.88: NamespaceMonitor - Got ADDED Namespace None:kube-node-lease:b7136fcc-2970-4d72-8ed9-4767b2c14a09 2025-01-13 02:00:41.88: ServiceMonitor - Watches https://10.0.0.27:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:00:41.88: EndPointMonitor - Watches https://10.0.0.27:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:00:41.88: PodMonitor - Skipped ADDED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:00:41.88: NamespaceMonitor - Got ADDED Namespace None:kube-public:77e9cb44-e988-44b2-a932-4f4f4879b717 2025-01-13 02:00:41.89: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-alarm-zr4tp (hostNetwork=True) 2025-01-13 02:00:41.89: NamespaceMonitor - Got ADDED Namespace None:kube-system:5ef680e4-6223-4d88-881a-ca4fc8db3acb 2025-01-13 02:00:41.89: NamespaceMonitor - Done init url=https://10.0.0.27:6443/api/v1/namespaces, resource_version=10187 2025-01-13 02:00:41.89: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:00:41.89: NamespaceMonitor - Start Watching request https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:00:41.89: NetworkMonitor - Done init url=https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions, resource_version=10191 2025-01-13 02:00:41.89: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:00:41.89: NetworkMonitor - Start Watching request https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'})(timeout=120) 2025-01-13 02:00:41.90: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-qwbps (hostNetwork=True) 2025-01-13 02:00:41.90: NamespaceMonitor - Watches https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:00:41.90: NetworkMonitor - Watches https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'}) 2025-01-13 02:00:41.90: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-snmp-qn4c8 (hostNetwork=True) 2025-01-13 02:00:41.91: PodMonitor - Skipped ADDED Pod kube-system:contrail-analyticsdb-5bfsd (hostNetwork=True) 2025-01-13 02:00:41.91: PodMonitor - Skipped ADDED Pod kube-system:contrail-configdb-r4c7f (hostNetwork=True) 2025-01-13 02:00:41.92: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-config-fk5qt (hostNetwork=True) 2025-01-13 02:00:41.92: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-control-7rb5b (hostNetwork=True) 2025-01-13 02:00:41.92: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-webui-vp4gj (hostNetwork=True) 2025-01-13 02:00:41.93: PodMonitor - Skipped ADDED Pod kube-system:contrail-kube-manager-wc4gq (hostNetwork=True) 2025-01-13 02:00:41.93: PodMonitor - Got ADDED Pod kube-system:coredns-77f7cc69db-mqvcz:3a49d474-43c7-4d35-91fe-a6c4ba101ac2 2025-01-13 02:00:41.94: PodMonitor - Got ADDED Pod kube-system:dns-autoscaler-595558c478-qz6dx:990e4698-8c9d-42d0-8512-004070b63026 2025-01-13 02:00:41.95: PodMonitor - Skipped ADDED Pod kube-system:kube-apiserver-cn-jenkins-deploy-platform-k8s-manifests-126-1 (hostNetwork=True) 2025-01-13 02:00:41.95: PodMonitor - Skipped ADDED Pod kube-system:kube-controller-manager-cn-jenkins-deploy-platform-k8s-manifests-126-1 (hostNetwork=True) 2025-01-13 02:00:41.96: PodMonitor - Skipped ADDED Pod kube-system:kube-proxy-bcq9d (hostNetwork=True) 2025-01-13 02:00:41.97: PodMonitor - Skipped ADDED Pod kube-system:kube-scheduler-cn-jenkins-deploy-platform-k8s-manifests-126-1 (hostNetwork=True) 2025-01-13 02:00:41.97: PodMonitor - Skipped ADDED Pod kube-system:rabbitmq-zkx4h (hostNetwork=True) 2025-01-13 02:00:41.98: PodMonitor - Skipped ADDED Pod kube-system:redis-692ds (hostNetwork=True) 2025-01-13 02:00:41.98: PodMonitor - Done init url=https://10.0.0.27:6443/api/v1/pods, resource_version=10187 2025-01-13 02:00:41.98: PodMonitor - _schedule_vnc_sync 2025-01-13 02:00:41.98: PodMonitor - Start Watching request https://10.0.0.27:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:00:41.98: PodMonitor - Watches https://10.0.0.27:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:00:43.87: VncKubernetes - wait event (qsize=15 timeout=120) 2025-01-13 02:00:43.87: VncKubernetes - Process event (name=default event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace default:aea16c69-f00d-4539-8b46-15e4190e8f1a 2025-01-13 02:00:47.67: VncKubernetes - wait event (qsize=14 timeout=120) 2025-01-13 02:00:47.67: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Endpoints ns=default) VncEndpoints - Got ADDED Endpoints default:kubernetes:870fe378-6d56-4d54-a29f-d8c7aac57d6f 2025-01-13 02:00:47.76: VncKubernetes - wait event (qsize=13 timeout=120) 2025-01-13 02:00:47.76: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:00:47.76: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:00:47.77: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:00:47.77: VncKubernetes - wait event (qsize=12 timeout=120) 2025-01-13 02:00:47.77: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Endpoints ns=kube-system) VncEndpoints - Got ADDED Endpoints kube-system:coredns:0df65d6d-8815-4a95-9790-cb07b7433312 2025-01-13 02:00:47.82: VncKubernetes - wait event (qsize=11 timeout=120) 2025-01-13 02:00:47.82: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:00:47.82: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:00:47.82: VncKubernetes - wait event (qsize=10 timeout=120) 2025-01-13 02:00:47.82: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Service ns=kube-system) VncService - Got ADDED Service kube-system:coredns:ad8e352a-eddd-403f-9cf4-8fc3f72d9b59 2025-01-13 02:00:50.48: VncKubernetes - wait event (qsize=9 timeout=120) 2025-01-13 02:00:50.48: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:00:50.48: VncKubernetes - vnc_sync - Service start 2025-01-13 02:00:50.48: VncKubernetes - vnc_sync - Service done 2025-01-13 02:00:50.48: VncKubernetes - wait event (qsize=8 timeout=120) 2025-01-13 02:00:50.48: VncKubernetes - Process event (name=kube-node-lease event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace kube-node-lease:b7136fcc-2970-4d72-8ed9-4767b2c14a09 2025-01-13 02:00:53.19: VncKubernetes - wait event (qsize=7 timeout=120) 2025-01-13 02:00:53.19: VncKubernetes - Process event (name=kube-public event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace kube-public:77e9cb44-e988-44b2-a932-4f4f4879b717 2025-01-13 02:00:55.80: VncKubernetes - wait event (qsize=6 timeout=120) 2025-01-13 02:00:55.80: VncKubernetes - Process event (name=kube-system event_type=ADDED kind=Namespace ns=None) VncNamespace - Got ADDED Namespace kube-system:5ef680e4-6223-4d88-881a-ca4fc8db3acb 2025-01-13 02:00:58.27: VncKubernetes - wait event (qsize=5 timeout=120) 2025-01-13 02:00:58.27: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:00:58.27: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:00:58.27: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:00:58.27: VncKubernetes - wait event (qsize=4 timeout=120) 2025-01-13 02:00:58.27: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:00:58.27: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:00:58.27: VncKubernetes - wait event (qsize=3 timeout=120) 2025-01-13 02:00:58.27: VncKubernetes - Process event (name=coredns-77f7cc69db-mqvcz event_type=ADDED kind=Pod ns=kube-system) VncPod - Got ADDED Pod kube-system:coredns-77f7cc69db-mqvcz:3a49d474-43c7-4d35-91fe-a6c4ba101ac2 2025-01-13 02:01:00.02: PodMonitor - Received MODIFIED Pod kube-system:coredns-77f7cc69db-mqvcz:3a49d474-43c7-4d35-91fe-a6c4ba101ac2 2025-01-13 02:01:00.02: PodMonitor - Got MODIFIED Pod kube-system:coredns-77f7cc69db-mqvcz:3a49d474-43c7-4d35-91fe-a6c4ba101ac2 2025-01-13 02:01:00.03: VncKubernetes - wait event (qsize=3 timeout=120) 2025-01-13 02:01:00.03: VncKubernetes - Process event (name=dns-autoscaler-595558c478-qz6dx event_type=ADDED kind=Pod ns=kube-system) VncPod - Got ADDED Pod kube-system:dns-autoscaler-595558c478-qz6dx:990e4698-8c9d-42d0-8512-004070b63026 2025-01-13 02:01:00.03: PodMonitor - start process kube event 2025-01-13 02:01:00.03: empty line received 2025-01-13 02:01:00.03: PodMonitor - start process kube event 2025-01-13 02:01:01.32: PodMonitor - Received MODIFIED Pod kube-system:dns-autoscaler-595558c478-qz6dx:990e4698-8c9d-42d0-8512-004070b63026 2025-01-13 02:01:01.32: PodMonitor - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-qz6dx:990e4698-8c9d-42d0-8512-004070b63026 2025-01-13 02:01:01.32: PodMonitor - start process kube event 2025-01-13 02:01:01.32: empty line received 2025-01-13 02:01:01.32: VncKubernetes - wait event (qsize=3 timeout=120) 2025-01-13 02:01:01.32: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:01:01.32: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:01:01.32: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:01:01.32: VncKubernetes - wait event (qsize=2 timeout=120) 2025-01-13 02:01:01.32: VncKubernetes - Process event (name=coredns-77f7cc69db-mqvcz event_type=MODIFIED kind=Pod ns=kube-system) VncPod - Got MODIFIED Pod kube-system:coredns-77f7cc69db-mqvcz:3a49d474-43c7-4d35-91fe-a6c4ba101ac2 2025-01-13 02:01:01.32: PodMonitor - start process kube event 2025-01-13 02:01:01.41: VncKubernetes - wait event (qsize=1 timeout=120) 2025-01-13 02:01:01.41: VncKubernetes - Process event (name=dns-autoscaler-595558c478-qz6dx event_type=MODIFIED kind=Pod ns=kube-system) VncPod - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-qz6dx:990e4698-8c9d-42d0-8512-004070b63026 2025-01-13 02:01:01.52: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:01:03.07: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:01:03.07: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:01:03.07: PodMonitor - start process kube event 2025-01-13 02:01:03.07: empty line received 2025-01-13 02:01:03.07: PodMonitor - start process kube event 2025-01-13 02:01:04.11: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:01:04.11: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:01:04.11: PodMonitor - start process kube event 2025-01-13 02:01:04.11: empty line received 2025-01-13 02:01:04.11: PodMonitor - start process kube event 2025-01-13 02:01:19.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:01:19.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:01:19.55: PodMonitor - start process kube event 2025-01-13 02:01:19.55: empty line received 2025-01-13 02:01:19.55: PodMonitor - start process kube event 2025-01-13 02:01:20.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:01:20.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:01:20.55: PodMonitor - start process kube event 2025-01-13 02:01:20.55: empty line received 2025-01-13 02:01:20.55: PodMonitor - start process kube event 2025-01-13 02:01:42.42: PodMonitor - Received BOOKMARK: oldResVer=10187 newResVer=10251 2025-01-13 02:01:42.42: PodMonitor - start process kube event 2025-01-13 02:01:42.42: empty line received 2025-01-13 02:01:42.42: PodMonitor - start process kube event 2025-01-13 02:01:51.32: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:01:51.32: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:01:51.32: PodMonitor - start process kube event 2025-01-13 02:01:51.32: empty line received 2025-01-13 02:01:51.32: PodMonitor - start process kube event 2025-01-13 02:02:03.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:02:03.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:02:03.55: PodMonitor - start process kube event 2025-01-13 02:02:03.55: empty line received 2025-01-13 02:02:03.55: PodMonitor - start process kube event 2025-01-13 02:02:20.03: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:02:20.03: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:02:20.03: PodMonitor - start process kube event 2025-01-13 02:02:20.03: empty line received 2025-01-13 02:02:20.03: PodMonitor - start process kube event 2025-01-13 02:02:34.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:02:34.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:02:34.55: PodMonitor - start process kube event 2025-01-13 02:02:34.55: empty line received 2025-01-13 02:02:34.55: PodMonitor - start process kube event 2025-01-13 02:02:41.85: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:02:41.86: IngressMonitor - start process kube event 2025-01-13 02:02:41.86: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10187 2025-01-13 02:02:41.86: IngressMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:02:41.86: IngressMonitor - Connect Kube API result 0 2025-01-13 02:02:41.86: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:02:41.86: IngressMonitor - Start Watching request https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:02:41.86: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:02:41.86: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:02:41.86: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:02:41.86: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:02:41.86: IngressMonitor - Watches https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:02:41.87: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:02:41.87: NetworkPolicyMonitor - start process kube event 2025-01-13 02:02:41.87: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10187 2025-01-13 02:02:41.87: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:02:41.87: NetworkPolicyMonitor - Connect Kube API result 0 2025-01-13 02:02:41.87: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:02:41.87: NetworkPolicyMonitor - Start Watching request https://10.0.0.27:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:02:41.87: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:02:41.87: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:02:41.88: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:02:41.88: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:02:41.88: NetworkPolicyMonitor - Watches https://10.0.0.27:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:02:41.88: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:02:41.88: ServiceMonitor - start process kube event 2025-01-13 02:02:41.88: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10187 2025-01-13 02:02:41.88: ServiceMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:02:41.88: ServiceMonitor - Connect Kube API result 0 2025-01-13 02:02:41.88: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:02:41.88: ServiceMonitor - Start Watching request https://10.0.0.27:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:02:41.88: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:02:41.88: VncKubernetes - vnc_sync - Service start 2025-01-13 02:02:41.88: VncKubernetes - vnc_sync - Service done 2025-01-13 02:02:41.88: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:02:41.88: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:02:41.88: EndPointMonitor - start process kube event 2025-01-13 02:02:41.88: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10187 2025-01-13 02:02:41.88: EndPointMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:02:41.88: EndPointMonitor - Connect Kube API result 0 2025-01-13 02:02:41.88: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:02:41.88: EndPointMonitor - Start Watching request https://10.0.0.27:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:02:41.89: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:02:41.89: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:02:41.89: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:02:41.89: ServiceMonitor - Watches https://10.0.0.27:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:02:41.89: EndPointMonitor - Watches https://10.0.0.27:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:02:41.90: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:02:41.90: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:02:41.90: NamespaceMonitor - start process kube event 2025-01-13 02:02:41.90: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10187 2025-01-13 02:02:41.90: NamespaceMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:02:41.90: NetworkMonitor - start process kube event 2025-01-13 02:02:41.90: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10191 2025-01-13 02:02:41.90: NetworkMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:02:41.90: NamespaceMonitor - Connect Kube API result 0 2025-01-13 02:02:41.90: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:02:41.90: NamespaceMonitor - Start Watching request https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:02:41.90: NetworkMonitor - Connect Kube API result 0 2025-01-13 02:02:41.90: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:02:41.90: NetworkMonitor - Start Watching request https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'})(timeout=120) 2025-01-13 02:02:41.91: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:02:41.91: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:02:41.91: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:02:41.91: VncKubernetes - wait event (qsize=1 timeout=120) 2025-01-13 02:02:41.91: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:02:41.91: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:02:41.91: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:02:41.91: NamespaceMonitor - Watches https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:02:41.91: NetworkMonitor - Watches https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'}) 2025-01-13 02:02:41.95: PodMonitor - Received BOOKMARK: oldResVer=10251 newResVer=10362 2025-01-13 02:02:41.95: PodMonitor - start process kube event 2025-01-13 02:02:41.95: empty line received 2025-01-13 02:02:41.95: PodMonitor - start process kube event 2025-01-13 02:02:47.76: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:02:47.76: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:02:47.76: PodMonitor - start process kube event 2025-01-13 02:02:47.76: empty line received 2025-01-13 02:02:47.76: PodMonitor - start process kube event 2025-01-13 02:03:41.92: PodMonitor - Received BOOKMARK: oldResVer=10362 newResVer=10386 2025-01-13 02:03:41.92: PodMonitor - start process kube event 2025-01-13 02:03:41.92: empty line received 2025-01-13 02:03:41.92: PodMonitor - start process kube event 2025-01-13 02:03:42.07: EndPointMonitor - Received BOOKMARK: oldResVer=10187 newResVer=10432 2025-01-13 02:03:42.07: EndPointMonitor - start process kube event 2025-01-13 02:03:42.07: empty line received 2025-01-13 02:03:42.07: EndPointMonitor - start process kube event 2025-01-13 02:03:42.23: NamespaceMonitor - Received BOOKMARK: oldResVer=10187 newResVer=10461 2025-01-13 02:03:42.23: NamespaceMonitor - start process kube event 2025-01-13 02:03:42.23: empty line received 2025-01-13 02:03:42.23: NamespaceMonitor - start process kube event 2025-01-13 02:03:47.15: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:03:47.15: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:03:47.15: PodMonitor - start process kube event 2025-01-13 02:03:47.15: empty line received 2025-01-13 02:03:47.15: PodMonitor - start process kube event 2025-01-13 02:03:59.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:03:59.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:03:59.55: PodMonitor - start process kube event 2025-01-13 02:03:59.55: empty line received 2025-01-13 02:03:59.55: PodMonitor - start process kube event 2025-01-13 02:04:30.25: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:04:30.25: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:04:30.25: PodMonitor - start process kube event 2025-01-13 02:04:30.25: empty line received 2025-01-13 02:04:30.25: PodMonitor - start process kube event 2025-01-13 02:04:41.87: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:04:41.87: IngressMonitor - start process kube event 2025-01-13 02:04:41.87: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10187 2025-01-13 02:04:41.87: IngressMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:04:41.87: IngressMonitor - Connect Kube API result 0 2025-01-13 02:04:41.87: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:04:41.87: IngressMonitor - Start Watching request https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:04:41.87: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:04:41.87: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:04:41.87: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:04:41.87: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:04:41.88: IngressMonitor - Watches https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:04:41.88: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10187 newResVer=10530 2025-01-13 02:04:41.88: NetworkPolicyMonitor - start process kube event 2025-01-13 02:04:41.88: empty line received 2025-01-13 02:04:41.88: NetworkPolicyMonitor - start process kube event 2025-01-13 02:04:41.89: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:04:41.89: ServiceMonitor - start process kube event 2025-01-13 02:04:41.89: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10187 2025-01-13 02:04:41.89: ServiceMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:04:41.89: ServiceMonitor - Connect Kube API result 0 2025-01-13 02:04:41.89: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:04:41.89: ServiceMonitor - Start Watching request https://10.0.0.27:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:04:41.89: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:04:41.90: VncKubernetes - vnc_sync - Service start 2025-01-13 02:04:41.90: VncKubernetes - vnc_sync - Service done 2025-01-13 02:04:41.90: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:04:41.90: ServiceMonitor - Watches https://10.0.0.27:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:04:41.91: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:04:41.91: NetworkMonitor - start process kube event 2025-01-13 02:04:41.91: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10191 2025-01-13 02:04:41.91: NetworkMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:04:41.91: NetworkMonitor - Connect Kube API result 0 2025-01-13 02:04:41.91: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:04:41.91: NetworkMonitor - Start Watching request https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'})(timeout=120) 2025-01-13 02:04:41.92: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:04:41.92: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:04:41.92: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:04:41.92: NetworkMonitor - Watches https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'}) 2025-01-13 02:04:42.28: NamespaceMonitor - Received BOOKMARK: oldResVer=10461 newResVer=10461 2025-01-13 02:04:42.28: NamespaceMonitor - start process kube event 2025-01-13 02:04:42.28: empty line received 2025-01-13 02:04:42.28: NamespaceMonitor - start process kube event 2025-01-13 02:04:42.76: PodMonitor - Received BOOKMARK: oldResVer=10386 newResVer=10537 2025-01-13 02:04:42.76: PodMonitor - start process kube event 2025-01-13 02:04:42.76: PodMonitor - _schedule_vnc_sync 2025-01-13 02:04:42.76: empty line received 2025-01-13 02:04:42.76: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:04:42.76: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:04:42.76: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:04:42.76: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:04:42.76: PodMonitor - start process kube event 2025-01-13 02:04:42.94: EndPointMonitor - Received BOOKMARK: oldResVer=10432 newResVer=10432 2025-01-13 02:04:42.94: EndPointMonitor - start process kube event 2025-01-13 02:04:42.94: empty line received 2025-01-13 02:04:42.94: EndPointMonitor - start process kube event 2025-01-13 02:04:44.63: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:04:44.63: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:04:44.63: PodMonitor - start process kube event 2025-01-13 02:04:44.63: empty line received 2025-01-13 02:04:44.63: PodMonitor - start process kube event 2025-01-13 02:05:00.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:05:00.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:05:00.55: PodMonitor - start process kube event 2025-01-13 02:05:00.55: empty line received 2025-01-13 02:05:00.56: PodMonitor - start process kube event 2025-01-13 02:05:30.83: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:05:30.83: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:05:30.83: PodMonitor - start process kube event 2025-01-13 02:05:30.83: empty line received 2025-01-13 02:05:30.83: PodMonitor - start process kube event 2025-01-13 02:05:31.88: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:05:31.88: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:05:31.88: PodMonitor - start process kube event 2025-01-13 02:05:31.88: empty line received 2025-01-13 02:05:31.88: PodMonitor - start process kube event 2025-01-13 02:05:41.58: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10530 newResVer=10530 2025-01-13 02:05:41.58: NetworkPolicyMonitor - start process kube event 2025-01-13 02:05:41.58: empty line received 2025-01-13 02:05:41.58: NetworkPolicyMonitor - start process kube event 2025-01-13 02:05:42.24: NamespaceMonitor - Received BOOKMARK: oldResVer=10461 newResVer=10461 2025-01-13 02:05:42.24: NamespaceMonitor - start process kube event 2025-01-13 02:05:42.24: empty line received 2025-01-13 02:05:42.24: NamespaceMonitor - start process kube event 2025-01-13 02:05:42.38: ServiceMonitor - Received BOOKMARK: oldResVer=10187 newResVer=10492 2025-01-13 02:05:42.38: ServiceMonitor - start process kube event 2025-01-13 02:05:42.38: empty line received 2025-01-13 02:05:42.38: ServiceMonitor - start process kube event 2025-01-13 02:05:42.48: PodMonitor - Received BOOKMARK: oldResVer=10537 newResVer=10632 2025-01-13 02:05:42.48: PodMonitor - start process kube event 2025-01-13 02:05:42.48: empty line received 2025-01-13 02:05:42.48: PodMonitor - start process kube event 2025-01-13 02:05:43.61: EndPointMonitor - Received BOOKMARK: oldResVer=10432 newResVer=10432 2025-01-13 02:05:43.61: EndPointMonitor - start process kube event 2025-01-13 02:05:43.61: empty line received 2025-01-13 02:05:43.61: EndPointMonitor - start process kube event 2025-01-13 02:06:41.13: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10530 newResVer=10530 2025-01-13 02:06:41.13: NetworkPolicyMonitor - start process kube event 2025-01-13 02:06:41.13: empty line received 2025-01-13 02:06:41.13: NetworkPolicyMonitor - start process kube event 2025-01-13 02:06:41.83: PodMonitor - Received BOOKMARK: oldResVer=10632 newResVer=10632 2025-01-13 02:06:41.83: PodMonitor - start process kube event 2025-01-13 02:06:41.83: empty line received 2025-01-13 02:06:41.83: PodMonitor - start process kube event 2025-01-13 02:06:41.87: NamespaceMonitor - Received BOOKMARK: oldResVer=10461 newResVer=10461 2025-01-13 02:06:41.87: NamespaceMonitor - start process kube event 2025-01-13 02:06:41.87: empty line received 2025-01-13 02:06:41.87: NamespaceMonitor - start process kube event 2025-01-13 02:06:41.88: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:06:41.88: IngressMonitor - start process kube event 2025-01-13 02:06:41.88: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10187 2025-01-13 02:06:41.88: IngressMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:06:41.88: IngressMonitor - Connect Kube API result 0 2025-01-13 02:06:41.88: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:06:41.88: IngressMonitor - Start Watching request https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:06:41.88: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:06:41.88: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:06:41.88: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:06:41.88: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:06:41.89: IngressMonitor - Watches https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:06:41.92: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:06:41.92: NetworkMonitor - start process kube event 2025-01-13 02:06:41.92: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10191 2025-01-13 02:06:41.92: NetworkMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:06:41.92: NetworkMonitor - Connect Kube API result 0 2025-01-13 02:06:41.92: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:06:41.92: NetworkMonitor - Start Watching request https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'})(timeout=120) 2025-01-13 02:06:41.93: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:06:41.93: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:06:41.93: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:06:41.93: NetworkMonitor - Watches https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'}) 2025-01-13 02:06:42.66: ServiceMonitor - Received BOOKMARK: oldResVer=10492 newResVer=10492 2025-01-13 02:06:42.66: ServiceMonitor - start process kube event 2025-01-13 02:06:42.66: empty line received 2025-01-13 02:06:42.66: ServiceMonitor - start process kube event 2025-01-13 02:06:43.01: EndPointMonitor - Received BOOKMARK: oldResVer=10432 newResVer=10432 2025-01-13 02:06:43.01: EndPointMonitor - start process kube event 2025-01-13 02:06:43.01: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:06:43.01: empty line received 2025-01-13 02:06:43.01: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:06:43.01: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:06:43.01: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:06:43.01: EndPointMonitor - start process kube event 2025-01-13 02:06:53.87: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:06:53.87: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:06:53.87: PodMonitor - start process kube event 2025-01-13 02:06:53.87: empty line received 2025-01-13 02:06:53.87: PodMonitor - start process kube event 2025-01-13 02:07:41.19: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10530 newResVer=10530 2025-01-13 02:07:41.19: NetworkPolicyMonitor - start process kube event 2025-01-13 02:07:41.19: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:07:41.19: empty line received 2025-01-13 02:07:41.19: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:07:41.19: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:07:41.19: NetworkPolicyMonitor - start process kube event 2025-01-13 02:07:41.19: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:07:41.19: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:07:41.87: NamespaceMonitor - Received BOOKMARK: oldResVer=10461 newResVer=10461 2025-01-13 02:07:41.87: NamespaceMonitor - start process kube event 2025-01-13 02:07:41.87: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:07:41.87: empty line received 2025-01-13 02:07:41.87: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:07:41.87: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:07:41.87: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:07:41.87: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:07:41.87: NamespaceMonitor - start process kube event 2025-01-13 02:07:42.44: PodMonitor - Received BOOKMARK: oldResVer=10632 newResVer=10751 2025-01-13 02:07:42.44: PodMonitor - start process kube event 2025-01-13 02:07:42.44: empty line received 2025-01-13 02:07:42.44: PodMonitor - start process kube event 2025-01-13 02:07:42.45: ServiceMonitor - Received BOOKMARK: oldResVer=10492 newResVer=10492 2025-01-13 02:07:42.45: ServiceMonitor - start process kube event 2025-01-13 02:07:42.45: empty line received 2025-01-13 02:07:42.45: ServiceMonitor - start process kube event 2025-01-13 02:07:43.54: EndPointMonitor - Received BOOKMARK: oldResVer=10432 newResVer=10432 2025-01-13 02:07:43.54: EndPointMonitor - start process kube event 2025-01-13 02:07:43.54: empty line received 2025-01-13 02:07:43.54: EndPointMonitor - start process kube event 2025-01-13 02:07:54.29: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:07:54.29: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:07:54.29: PodMonitor - start process kube event 2025-01-13 02:07:54.29: empty line received 2025-01-13 02:07:54.29: PodMonitor - start process kube event 2025-01-13 02:07:55.33: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:07:55.33: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:07:55.33: PodMonitor - start process kube event 2025-01-13 02:07:55.33: empty line received 2025-01-13 02:07:55.33: PodMonitor - start process kube event 2025-01-13 02:08:41.82: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10530 newResVer=10530 2025-01-13 02:08:41.82: NetworkPolicyMonitor - start process kube event 2025-01-13 02:08:41.82: empty line received 2025-01-13 02:08:41.82: NetworkPolicyMonitor - start process kube event 2025-01-13 02:08:41.89: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:08:41.89: IngressMonitor - start process kube event 2025-01-13 02:08:41.89: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10187 2025-01-13 02:08:41.89: IngressMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:08:41.89: IngressMonitor - Connect Kube API result 0 2025-01-13 02:08:41.89: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:08:41.89: IngressMonitor - Start Watching request https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'})(timeout=120) 2025-01-13 02:08:41.89: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:08:41.89: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:08:41.89: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:08:41.89: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:08:41.90: IngressMonitor - Watches https://10.0.0.27:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10187'}) 2025-01-13 02:08:41.93: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:08:41.93: NetworkMonitor - start process kube event 2025-01-13 02:08:41.93: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10191 2025-01-13 02:08:41.93: NetworkMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:08:41.93: NetworkMonitor - Connect Kube API result 0 2025-01-13 02:08:41.93: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:08:41.93: NetworkMonitor - Start Watching request https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'})(timeout=120) 2025-01-13 02:08:41.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:08:41.94: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:08:41.94: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:08:41.95: NetworkMonitor - Watches https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'}) 2025-01-13 02:08:42.46: ServiceMonitor - Received BOOKMARK: oldResVer=10492 newResVer=10492 2025-01-13 02:08:42.46: ServiceMonitor - start process kube event 2025-01-13 02:08:42.46: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:08:42.46: empty line received 2025-01-13 02:08:42.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:08:42.46: VncKubernetes - vnc_sync - Service start 2025-01-13 02:08:42.46: VncKubernetes - vnc_sync - Service done 2025-01-13 02:08:42.46: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:08:42.46: ServiceMonitor - start process kube event 2025-01-13 02:08:42.68: PodMonitor - Received BOOKMARK: oldResVer=10751 newResVer=10842 2025-01-13 02:08:42.68: PodMonitor - start process kube event 2025-01-13 02:08:42.68: empty line received 2025-01-13 02:08:42.68: PodMonitor - start process kube event 2025-01-13 02:08:42.82: NamespaceMonitor - Received BOOKMARK: oldResVer=10461 newResVer=10461 2025-01-13 02:08:42.82: NamespaceMonitor - start process kube event 2025-01-13 02:08:42.82: empty line received 2025-01-13 02:08:42.82: NamespaceMonitor - start process kube event 2025-01-13 02:08:43.79: EndPointMonitor - Received BOOKMARK: oldResVer=10432 newResVer=10432 2025-01-13 02:08:43.80: EndPointMonitor - start process kube event 2025-01-13 02:08:43.80: empty line received 2025-01-13 02:08:43.80: EndPointMonitor - start process kube event 2025-01-13 02:09:41.23: IngressMonitor - Received BOOKMARK: oldResVer=10187 newResVer=10951 2025-01-13 02:09:41.23: IngressMonitor - start process kube event 2025-01-13 02:09:41.23: empty line received 2025-01-13 02:09:41.23: IngressMonitor - start process kube event 2025-01-13 02:09:41.23: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10530 newResVer=10530 2025-01-13 02:09:41.23: NetworkPolicyMonitor - start process kube event 2025-01-13 02:09:41.23: empty line received 2025-01-13 02:09:41.23: NetworkPolicyMonitor - start process kube event 2025-01-13 02:09:42.55: ServiceMonitor - Received BOOKMARK: oldResVer=10492 newResVer=10492 2025-01-13 02:09:42.55: ServiceMonitor - start process kube event 2025-01-13 02:09:42.55: empty line received 2025-01-13 02:09:42.55: ServiceMonitor - start process kube event 2025-01-13 02:09:42.62: PodMonitor - Received BOOKMARK: oldResVer=10842 newResVer=10842 2025-01-13 02:09:42.62: PodMonitor - start process kube event 2025-01-13 02:09:42.62: PodMonitor - _schedule_vnc_sync 2025-01-13 02:09:42.62: empty line received 2025-01-13 02:09:42.62: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:09:42.62: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:09:42.62: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:09:42.62: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:09:42.62: PodMonitor - start process kube event 2025-01-13 02:09:43.57: NamespaceMonitor - Received BOOKMARK: oldResVer=10461 newResVer=10461 2025-01-13 02:09:43.57: NamespaceMonitor - start process kube event 2025-01-13 02:09:43.57: empty line received 2025-01-13 02:09:43.57: NamespaceMonitor - start process kube event 2025-01-13 02:09:43.92: EndPointMonitor - Received BOOKMARK: oldResVer=10432 newResVer=10432 2025-01-13 02:09:43.92: EndPointMonitor - start process kube event 2025-01-13 02:09:43.92: empty line received 2025-01-13 02:09:43.92: EndPointMonitor - start process kube event 2025-01-13 02:09:56.33: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:09:56.33: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:09:56.33: PodMonitor - start process kube event 2025-01-13 02:09:56.33: empty line received 2025-01-13 02:09:56.33: PodMonitor - start process kube event 2025-01-13 02:10:08.56: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:10:08.56: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:10:08.56: PodMonitor - start process kube event 2025-01-13 02:10:08.56: empty line received 2025-01-13 02:10:08.56: PodMonitor - start process kube event 2025-01-13 02:10:35.48: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:10:35.48: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:10:35.48: PodMonitor - start process kube event 2025-01-13 02:10:35.48: empty line received 2025-01-13 02:10:35.48: PodMonitor - start process kube event 2025-01-13 02:10:41.64: IngressMonitor - Received BOOKMARK: oldResVer=10951 newResVer=10951 2025-01-13 02:10:41.64: IngressMonitor - start process kube event 2025-01-13 02:10:41.64: empty line received 2025-01-13 02:10:41.64: IngressMonitor - start process kube event 2025-01-13 02:10:41.74: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10530 newResVer=10530 2025-01-13 02:10:41.74: NetworkPolicyMonitor - start process kube event 2025-01-13 02:10:41.74: empty line received 2025-01-13 02:10:41.74: NetworkPolicyMonitor - start process kube event 2025-01-13 02:10:41.95: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:10:41.95: NetworkMonitor - start process kube event 2025-01-13 02:10:41.95: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=10191 2025-01-13 02:10:41.95: NetworkMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:10:41.95: NetworkMonitor - Connect Kube API result 0 2025-01-13 02:10:41.95: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:10:41.95: NetworkMonitor - Start Watching request https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'})(timeout=120) 2025-01-13 02:10:41.95: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:10:41.95: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:10:41.95: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:10:41.96: NetworkMonitor - Watches https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '10191'}) 2025-01-13 02:10:42.23: ServiceMonitor - Received BOOKMARK: oldResVer=10492 newResVer=10492 2025-01-13 02:10:42.23: ServiceMonitor - start process kube event 2025-01-13 02:10:42.23: empty line received 2025-01-13 02:10:42.23: ServiceMonitor - start process kube event 2025-01-13 02:10:42.25: PodMonitor - Received BOOKMARK: oldResVer=10842 newResVer=11082 2025-01-13 02:10:42.25: PodMonitor - start process kube event 2025-01-13 02:10:42.25: empty line received 2025-01-13 02:10:42.25: PodMonitor - start process kube event 2025-01-13 02:10:42.89: NamespaceMonitor - Received BOOKMARK: oldResVer=10461 newResVer=10461 2025-01-13 02:10:42.89: NamespaceMonitor - start process kube event 2025-01-13 02:10:42.89: empty line received 2025-01-13 02:10:42.89: NamespaceMonitor - start process kube event 2025-01-13 02:10:44.86: EndPointMonitor - Received BOOKMARK: oldResVer=10432 newResVer=10432 2025-01-13 02:10:44.86: EndPointMonitor - start process kube event 2025-01-13 02:10:44.86: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:10:44.86: empty line received 2025-01-13 02:10:44.86: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:10:44.86: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:10:44.86: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:10:44.86: EndPointMonitor - start process kube event 2025-01-13 02:11:35.95: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:11:35.95: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:11:35.95: PodMonitor - start process kube event 2025-01-13 02:11:35.95: empty line received 2025-01-13 02:11:35.95: PodMonitor - start process kube event 2025-01-13 02:11:41.46: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10530 newResVer=10530 2025-01-13 02:11:41.46: NetworkPolicyMonitor - start process kube event 2025-01-13 02:11:41.46: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:11:41.46: empty line received 2025-01-13 02:11:41.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:11:41.46: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:11:41.47: NetworkPolicyMonitor - start process kube event 2025-01-13 02:11:41.47: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:11:41.47: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:11:41.99: IngressMonitor - Received BOOKMARK: oldResVer=10951 newResVer=10951 2025-01-13 02:11:41.99: IngressMonitor - start process kube event 2025-01-13 02:11:41.99: empty line received 2025-01-13 02:11:41.99: IngressMonitor - start process kube event 2025-01-13 02:11:42.00: PodMonitor - Received BOOKMARK: oldResVer=11082 newResVer=11172 2025-01-13 02:11:42.00: PodMonitor - start process kube event 2025-01-13 02:11:42.00: empty line received 2025-01-13 02:11:42.00: PodMonitor - start process kube event 2025-01-13 02:11:42.23: ServiceMonitor - Received BOOKMARK: oldResVer=10492 newResVer=10492 2025-01-13 02:11:42.23: ServiceMonitor - start process kube event 2025-01-13 02:11:42.23: empty line received 2025-01-13 02:11:42.23: ServiceMonitor - start process kube event 2025-01-13 02:11:42.65: NetworkMonitor - Received BOOKMARK: oldResVer=10191 newResVer=11145 2025-01-13 02:11:42.65: NetworkMonitor - start process kube event 2025-01-13 02:11:42.65: empty line received 2025-01-13 02:11:42.65: NetworkMonitor - start process kube event 2025-01-13 02:11:43.51: NamespaceMonitor - Received BOOKMARK: oldResVer=10461 newResVer=10461 2025-01-13 02:11:43.51: NamespaceMonitor - start process kube event 2025-01-13 02:11:43.51: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:11:43.51: empty line received 2025-01-13 02:11:43.51: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:11:43.51: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:11:43.51: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:11:43.51: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:11:43.51: NamespaceMonitor - start process kube event 2025-01-13 02:11:45.46: EndPointMonitor - Received BOOKMARK: oldResVer=10432 newResVer=10432 2025-01-13 02:11:45.46: EndPointMonitor - start process kube event 2025-01-13 02:11:45.46: empty line received 2025-01-13 02:11:45.46: EndPointMonitor - start process kube event 2025-01-13 02:11:47.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:11:47.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:11:47.55: PodMonitor - start process kube event 2025-01-13 02:11:47.55: empty line received 2025-01-13 02:11:47.55: PodMonitor - start process kube event 2025-01-13 02:12:40.92: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10530 newResVer=10530 2025-01-13 02:12:40.92: NetworkPolicyMonitor - start process kube event 2025-01-13 02:12:40.92: empty line received 2025-01-13 02:12:40.92: NetworkPolicyMonitor - start process kube event 2025-01-13 02:12:41.93: NetworkMonitor - Received BOOKMARK: oldResVer=11145 newResVer=11145 2025-01-13 02:12:41.93: NetworkMonitor - start process kube event 2025-01-13 02:12:41.93: empty line received 2025-01-13 02:12:41.93: NetworkMonitor - start process kube event 2025-01-13 02:12:41.95: PodMonitor - Received BOOKMARK: oldResVer=11172 newResVer=11188 2025-01-13 02:12:41.95: PodMonitor - start process kube event 2025-01-13 02:12:41.95: empty line received 2025-01-13 02:12:41.95: PodMonitor - start process kube event 2025-01-13 02:12:41.97: IngressMonitor - Received BOOKMARK: oldResVer=10951 newResVer=10951 2025-01-13 02:12:41.97: IngressMonitor - start process kube event 2025-01-13 02:12:41.97: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:12:41.97: empty line received 2025-01-13 02:12:41.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:12:41.97: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:12:41.97: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:12:41.97: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:12:41.97: IngressMonitor - start process kube event 2025-01-13 02:12:42.11: ServiceMonitor - Received BOOKMARK: oldResVer=10492 newResVer=10492 2025-01-13 02:12:42.11: ServiceMonitor - start process kube event 2025-01-13 02:12:42.11: empty line received 2025-01-13 02:12:42.11: ServiceMonitor - start process kube event 2025-01-13 02:12:43.58: NamespaceMonitor - Received BOOKMARK: oldResVer=10461 newResVer=10461 2025-01-13 02:12:43.58: NamespaceMonitor - start process kube event 2025-01-13 02:12:43.58: empty line received 2025-01-13 02:12:43.58: NamespaceMonitor - start process kube event 2025-01-13 02:12:45.45: EndPointMonitor - Received BOOKMARK: oldResVer=10432 newResVer=10432 2025-01-13 02:12:45.45: EndPointMonitor - start process kube event 2025-01-13 02:12:45.45: empty line received 2025-01-13 02:12:45.45: EndPointMonitor - start process kube event 2025-01-13 02:13:41.02: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10530 newResVer=10530 2025-01-13 02:13:41.02: NetworkPolicyMonitor - start process kube event 2025-01-13 02:13:41.02: empty line received 2025-01-13 02:13:41.02: NetworkPolicyMonitor - start process kube event 2025-01-13 02:13:41.85: PodMonitor - Received BOOKMARK: oldResVer=11188 newResVer=11188 2025-01-13 02:13:41.85: PodMonitor - start process kube event 2025-01-13 02:13:41.85: empty line received 2025-01-13 02:13:41.85: PodMonitor - start process kube event 2025-01-13 02:13:42.68: NetworkMonitor - Received BOOKMARK: oldResVer=11145 newResVer=11145 2025-01-13 02:13:42.68: NetworkMonitor - start process kube event 2025-01-13 02:13:42.68: empty line received 2025-01-13 02:13:42.68: NetworkMonitor - start process kube event 2025-01-13 02:13:42.72: ServiceMonitor - Received BOOKMARK: oldResVer=10492 newResVer=10492 2025-01-13 02:13:42.72: ServiceMonitor - start process kube event 2025-01-13 02:13:42.72: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:13:42.72: empty line received 2025-01-13 02:13:42.72: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:13:42.72: VncKubernetes - vnc_sync - Service start 2025-01-13 02:13:42.72: VncKubernetes - vnc_sync - Service done 2025-01-13 02:13:42.72: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:13:42.72: ServiceMonitor - start process kube event 2025-01-13 02:13:42.99: IngressMonitor - Received BOOKMARK: oldResVer=10951 newResVer=10951 2025-01-13 02:13:42.99: IngressMonitor - start process kube event 2025-01-13 02:13:42.99: empty line received 2025-01-13 02:13:42.99: IngressMonitor - start process kube event 2025-01-13 02:13:43.90: NamespaceMonitor - Received BOOKMARK: oldResVer=10461 newResVer=10461 2025-01-13 02:13:43.90: NamespaceMonitor - start process kube event 2025-01-13 02:13:43.90: empty line received 2025-01-13 02:13:43.90: NamespaceMonitor - start process kube event 2025-01-13 02:13:45.60: EndPointMonitor - Received BOOKMARK: oldResVer=10432 newResVer=10432 2025-01-13 02:13:45.60: EndPointMonitor - start process kube event 2025-01-13 02:13:45.60: empty line received 2025-01-13 02:13:45.60: EndPointMonitor - start process kube event 2025-01-13 02:14:41.42: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10530 newResVer=10530 2025-01-13 02:14:41.42: NetworkPolicyMonitor - start process kube event 2025-01-13 02:14:41.42: empty line received 2025-01-13 02:14:41.42: NetworkPolicyMonitor - start process kube event 2025-01-13 02:14:42.23: NetworkMonitor - Received BOOKMARK: oldResVer=11145 newResVer=11145 2025-01-13 02:14:42.23: NetworkMonitor - start process kube event 2025-01-13 02:14:42.23: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:14:42.23: empty line received 2025-01-13 02:14:42.23: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:14:42.23: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:14:42.23: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:14:42.23: NetworkMonitor - start process kube event 2025-01-13 02:14:42.57: PodMonitor - Received BOOKMARK: oldResVer=11188 newResVer=11188 2025-01-13 02:14:42.57: PodMonitor - start process kube event 2025-01-13 02:14:42.57: PodMonitor - _schedule_vnc_sync 2025-01-13 02:14:42.57: empty line received 2025-01-13 02:14:42.57: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:14:42.57: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:14:42.57: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:14:42.57: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:14:42.57: PodMonitor - start process kube event 2025-01-13 02:14:43.05: ServiceMonitor - Received BOOKMARK: oldResVer=10492 newResVer=11424 2025-01-13 02:14:43.05: ServiceMonitor - start process kube event 2025-01-13 02:14:43.05: empty line received 2025-01-13 02:14:43.05: ServiceMonitor - start process kube event 2025-01-13 02:14:43.47: IngressMonitor - Received BOOKMARK: oldResVer=10951 newResVer=10951 2025-01-13 02:14:43.47: IngressMonitor - start process kube event 2025-01-13 02:14:43.47: empty line received 2025-01-13 02:14:43.47: IngressMonitor - start process kube event 2025-01-13 02:14:44.27: NamespaceMonitor - Received BOOKMARK: oldResVer=10461 newResVer=11393 2025-01-13 02:14:44.27: NamespaceMonitor - start process kube event 2025-01-13 02:14:44.27: empty line received 2025-01-13 02:14:44.27: NamespaceMonitor - start process kube event 2025-01-13 02:14:45.41: EndPointMonitor - Received BOOKMARK: oldResVer=10432 newResVer=11360 2025-01-13 02:14:45.41: EndPointMonitor - start process kube event 2025-01-13 02:14:45.41: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:14:45.41: empty line received 2025-01-13 02:14:45.41: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:14:45.41: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:14:45.41: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:14:45.41: EndPointMonitor - start process kube event 2025-01-13 02:15:03.99: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:15:03.99: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:15:03.99: PodMonitor - start process kube event 2025-01-13 02:15:03.99: empty line received 2025-01-13 02:15:03.99: PodMonitor - start process kube event 2025-01-13 02:15:05.04: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:15:05.04: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:15:05.04: PodMonitor - start process kube event 2025-01-13 02:15:05.04: empty line received 2025-01-13 02:15:05.04: PodMonitor - start process kube event 2025-01-13 02:15:41.79: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10530 newResVer=11462 2025-01-13 02:15:41.79: NetworkPolicyMonitor - start process kube event 2025-01-13 02:15:41.79: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:15:41.79: empty line received 2025-01-13 02:15:41.79: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:15:41.79: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:15:41.79: NetworkPolicyMonitor - start process kube event 2025-01-13 02:15:41.79: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:15:41.79: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:15:42.34: NetworkMonitor - Received BOOKMARK: oldResVer=11145 newResVer=11145 2025-01-13 02:15:42.34: NetworkMonitor - start process kube event 2025-01-13 02:15:42.34: empty line received 2025-01-13 02:15:42.34: NetworkMonitor - start process kube event 2025-01-13 02:15:42.89: PodMonitor - Received BOOKMARK: oldResVer=11188 newResVer=11475 2025-01-13 02:15:42.89: PodMonitor - start process kube event 2025-01-13 02:15:42.89: empty line received 2025-01-13 02:15:42.89: PodMonitor - start process kube event 2025-01-13 02:15:43.53: IngressMonitor - Received BOOKMARK: oldResVer=10951 newResVer=10951 2025-01-13 02:15:43.53: IngressMonitor - start process kube event 2025-01-13 02:15:43.53: empty line received 2025-01-13 02:15:43.53: IngressMonitor - start process kube event 2025-01-13 02:15:43.70: ServiceMonitor - Received BOOKMARK: oldResVer=11424 newResVer=11424 2025-01-13 02:15:43.70: ServiceMonitor - start process kube event 2025-01-13 02:15:43.70: empty line received 2025-01-13 02:15:43.70: ServiceMonitor - start process kube event 2025-01-13 02:15:44.97: NamespaceMonitor - Received BOOKMARK: oldResVer=11393 newResVer=11393 2025-01-13 02:15:44.97: NamespaceMonitor - start process kube event 2025-01-13 02:15:44.97: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:15:44.97: empty line received 2025-01-13 02:15:44.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:15:44.97: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:15:44.97: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:15:44.97: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:15:44.97: NamespaceMonitor - start process kube event 2025-01-13 02:15:45.60: EndPointMonitor - Received BOOKMARK: oldResVer=11360 newResVer=11360 2025-01-13 02:15:45.60: EndPointMonitor - start process kube event 2025-01-13 02:15:45.60: empty line received 2025-01-13 02:15:45.60: EndPointMonitor - start process kube event 2025-01-13 02:16:36.25: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:16:36.25: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:16:36.25: PodMonitor - start process kube event 2025-01-13 02:16:36.25: empty line received 2025-01-13 02:16:36.25: PodMonitor - start process kube event 2025-01-13 02:16:41.83: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11462 newResVer=11462 2025-01-13 02:16:41.83: NetworkPolicyMonitor - start process kube event 2025-01-13 02:16:41.83: empty line received 2025-01-13 02:16:41.83: NetworkPolicyMonitor - start process kube event 2025-01-13 02:16:42.56: NetworkMonitor - Received BOOKMARK: oldResVer=11145 newResVer=11145 2025-01-13 02:16:42.56: NetworkMonitor - start process kube event 2025-01-13 02:16:42.56: empty line received 2025-01-13 02:16:42.56: NetworkMonitor - start process kube event 2025-01-13 02:16:43.04: ServiceMonitor - Received BOOKMARK: oldResVer=11424 newResVer=11424 2025-01-13 02:16:43.04: ServiceMonitor - start process kube event 2025-01-13 02:16:43.04: empty line received 2025-01-13 02:16:43.04: ServiceMonitor - start process kube event 2025-01-13 02:16:43.77: PodMonitor - Received BOOKMARK: oldResVer=11475 newResVer=11606 2025-01-13 02:16:43.77: PodMonitor - start process kube event 2025-01-13 02:16:43.77: empty line received 2025-01-13 02:16:43.77: PodMonitor - start process kube event 2025-01-13 02:16:43.77: IngressMonitor - Received BOOKMARK: oldResVer=10951 newResVer=10951 2025-01-13 02:16:43.77: IngressMonitor - start process kube event 2025-01-13 02:16:43.77: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:16:43.77: empty line received 2025-01-13 02:16:43.77: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:16:43.77: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:16:43.77: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:16:43.77: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:16:43.77: IngressMonitor - start process kube event 2025-01-13 02:16:45.74: EndPointMonitor - Received BOOKMARK: oldResVer=11360 newResVer=11360 2025-01-13 02:16:45.74: EndPointMonitor - start process kube event 2025-01-13 02:16:45.74: empty line received 2025-01-13 02:16:45.74: EndPointMonitor - start process kube event 2025-01-13 02:16:45.76: NamespaceMonitor - Received BOOKMARK: oldResVer=11393 newResVer=11393 2025-01-13 02:16:45.76: NamespaceMonitor - start process kube event 2025-01-13 02:16:45.76: empty line received 2025-01-13 02:16:45.76: NamespaceMonitor - start process kube event 2025-01-13 02:17:36.75: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:17:36.75: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:17:36.75: PodMonitor - start process kube event 2025-01-13 02:17:36.75: empty line received 2025-01-13 02:17:36.75: PodMonitor - start process kube event 2025-01-13 02:17:37.80: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:17:37.80: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:17:37.80: PodMonitor - start process kube event 2025-01-13 02:17:37.80: empty line received 2025-01-13 02:17:37.80: PodMonitor - start process kube event 2025-01-13 02:17:41.88: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11462 newResVer=11462 2025-01-13 02:17:41.88: NetworkPolicyMonitor - start process kube event 2025-01-13 02:17:41.88: empty line received 2025-01-13 02:17:41.88: NetworkPolicyMonitor - start process kube event 2025-01-13 02:17:42.49: NetworkMonitor - Received BOOKMARK: oldResVer=11145 newResVer=11145 2025-01-13 02:17:42.49: NetworkMonitor - start process kube event 2025-01-13 02:17:42.49: empty line received 2025-01-13 02:17:42.49: NetworkMonitor - start process kube event 2025-01-13 02:17:43.35: PodMonitor - Received BOOKMARK: oldResVer=11606 newResVer=11698 2025-01-13 02:17:43.35: PodMonitor - start process kube event 2025-01-13 02:17:43.35: empty line received 2025-01-13 02:17:43.35: PodMonitor - start process kube event 2025-01-13 02:17:43.45: IngressMonitor - Received BOOKMARK: oldResVer=10951 newResVer=10951 2025-01-13 02:17:43.45: IngressMonitor - start process kube event 2025-01-13 02:17:43.45: empty line received 2025-01-13 02:17:43.45: IngressMonitor - start process kube event 2025-01-13 02:17:43.49: ServiceMonitor - Received BOOKMARK: oldResVer=11424 newResVer=11424 2025-01-13 02:17:43.49: ServiceMonitor - start process kube event 2025-01-13 02:17:43.49: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:17:43.49: empty line received 2025-01-13 02:17:43.49: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:17:43.49: VncKubernetes - vnc_sync - Service start 2025-01-13 02:17:43.49: VncKubernetes - vnc_sync - Service done 2025-01-13 02:17:43.49: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:17:43.49: ServiceMonitor - start process kube event 2025-01-13 02:17:44.87: EndPointMonitor - Received BOOKMARK: oldResVer=11360 newResVer=11360 2025-01-13 02:17:44.87: EndPointMonitor - start process kube event 2025-01-13 02:17:44.87: empty line received 2025-01-13 02:17:44.87: EndPointMonitor - start process kube event 2025-01-13 02:17:46.59: NamespaceMonitor - Received BOOKMARK: oldResVer=11393 newResVer=11393 2025-01-13 02:17:46.59: NamespaceMonitor - start process kube event 2025-01-13 02:17:46.59: empty line received 2025-01-13 02:17:46.59: NamespaceMonitor - start process kube event 2025-01-13 02:18:41.05: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11462 newResVer=11462 2025-01-13 02:18:41.05: NetworkPolicyMonitor - start process kube event 2025-01-13 02:18:41.05: empty line received 2025-01-13 02:18:41.05: NetworkPolicyMonitor - start process kube event 2025-01-13 02:18:42.08: NetworkMonitor - Received BOOKMARK: oldResVer=11145 newResVer=11145 2025-01-13 02:18:42.08: NetworkMonitor - start process kube event 2025-01-13 02:18:42.08: empty line received 2025-01-13 02:18:42.08: NetworkMonitor - start process kube event 2025-01-13 02:18:43.18: ServiceMonitor - Received BOOKMARK: oldResVer=11424 newResVer=11424 2025-01-13 02:18:43.18: ServiceMonitor - start process kube event 2025-01-13 02:18:43.18: empty line received 2025-01-13 02:18:43.18: ServiceMonitor - start process kube event 2025-01-13 02:18:43.32: IngressMonitor - Received BOOKMARK: oldResVer=10951 newResVer=10951 2025-01-13 02:18:43.32: IngressMonitor - start process kube event 2025-01-13 02:18:43.32: empty line received 2025-01-13 02:18:43.32: IngressMonitor - start process kube event 2025-01-13 02:18:43.59: PodMonitor - Received BOOKMARK: oldResVer=11698 newResVer=11698 2025-01-13 02:18:43.59: PodMonitor - start process kube event 2025-01-13 02:18:43.59: PodMonitor - _schedule_vnc_sync 2025-01-13 02:18:43.59: empty line received 2025-01-13 02:18:43.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:18:43.59: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:18:43.59: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:18:43.59: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:18:43.59: PodMonitor - start process kube event 2025-01-13 02:18:44.92: EndPointMonitor - Received BOOKMARK: oldResVer=11360 newResVer=11360 2025-01-13 02:18:44.92: EndPointMonitor - start process kube event 2025-01-13 02:18:44.92: empty line received 2025-01-13 02:18:44.92: EndPointMonitor - start process kube event 2025-01-13 02:18:45.86: NamespaceMonitor - Received BOOKMARK: oldResVer=11393 newResVer=11393 2025-01-13 02:18:45.86: NamespaceMonitor - start process kube event 2025-01-13 02:18:45.86: empty line received 2025-01-13 02:18:45.86: NamespaceMonitor - start process kube event 2025-01-13 02:19:41.06: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11462 newResVer=11462 2025-01-13 02:19:41.06: NetworkPolicyMonitor - start process kube event 2025-01-13 02:19:41.06: empty line received 2025-01-13 02:19:41.06: NetworkPolicyMonitor - start process kube event 2025-01-13 02:19:42.61: NetworkMonitor - Received BOOKMARK: oldResVer=11145 newResVer=11145 2025-01-13 02:19:42.61: NetworkMonitor - start process kube event 2025-01-13 02:19:42.61: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:19:42.61: empty line received 2025-01-13 02:19:42.61: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:19:42.61: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:19:42.61: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:19:42.61: NetworkMonitor - start process kube event 2025-01-13 02:19:43.16: ServiceMonitor - Received BOOKMARK: oldResVer=11424 newResVer=11424 2025-01-13 02:19:43.16: ServiceMonitor - start process kube event 2025-01-13 02:19:43.16: empty line received 2025-01-13 02:19:43.16: ServiceMonitor - start process kube event 2025-01-13 02:19:43.33: IngressMonitor - Received BOOKMARK: oldResVer=10951 newResVer=10951 2025-01-13 02:19:43.33: IngressMonitor - start process kube event 2025-01-13 02:19:43.33: empty line received 2025-01-13 02:19:43.33: IngressMonitor - start process kube event 2025-01-13 02:19:43.93: PodMonitor - Received BOOKMARK: oldResVer=11698 newResVer=11698 2025-01-13 02:19:43.94: PodMonitor - start process kube event 2025-01-13 02:19:43.94: empty line received 2025-01-13 02:19:43.94: PodMonitor - start process kube event 2025-01-13 02:19:45.01: EndPointMonitor - Received BOOKMARK: oldResVer=11360 newResVer=11360 2025-01-13 02:19:45.01: EndPointMonitor - start process kube event 2025-01-13 02:19:45.01: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:19:45.01: empty line received 2025-01-13 02:19:45.01: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:19:45.01: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:19:45.01: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:19:45.01: EndPointMonitor - start process kube event 2025-01-13 02:19:46.08: NamespaceMonitor - Received BOOKMARK: oldResVer=11393 newResVer=11393 2025-01-13 02:19:46.08: NamespaceMonitor - start process kube event 2025-01-13 02:19:46.08: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:19:46.08: empty line received 2025-01-13 02:19:46.08: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:19:46.08: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:19:46.08: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:19:46.08: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:19:46.08: NamespaceMonitor - start process kube event 2025-01-13 02:20:19.62: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:20:19.62: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:20:19.62: PodMonitor - start process kube event 2025-01-13 02:20:19.62: empty line received 2025-01-13 02:20:19.62: PodMonitor - start process kube event 2025-01-13 02:20:31.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:20:31.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:20:31.55: PodMonitor - start process kube event 2025-01-13 02:20:31.55: empty line received 2025-01-13 02:20:31.55: PodMonitor - start process kube event 2025-01-13 02:20:41.21: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11462 newResVer=11462 2025-01-13 02:20:41.21: NetworkPolicyMonitor - start process kube event 2025-01-13 02:20:41.21: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:20:41.21: empty line received 2025-01-13 02:20:41.21: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:20:41.21: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:20:41.21: NetworkPolicyMonitor - start process kube event 2025-01-13 02:20:41.21: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:20:41.21: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:20:42.12: NetworkMonitor - Received BOOKMARK: oldResVer=11145 newResVer=11145 2025-01-13 02:20:42.12: NetworkMonitor - start process kube event 2025-01-13 02:20:42.12: empty line received 2025-01-13 02:20:42.12: NetworkMonitor - start process kube event 2025-01-13 02:20:43.31: ServiceMonitor - Received BOOKMARK: oldResVer=11424 newResVer=11424 2025-01-13 02:20:43.31: ServiceMonitor - start process kube event 2025-01-13 02:20:43.31: empty line received 2025-01-13 02:20:43.31: ServiceMonitor - start process kube event 2025-01-13 02:20:43.53: IngressMonitor - Received BOOKMARK: oldResVer=10951 newResVer=11904 2025-01-13 02:20:43.53: IngressMonitor - start process kube event 2025-01-13 02:20:43.53: empty line received 2025-01-13 02:20:43.53: IngressMonitor - start process kube event 2025-01-13 02:20:44.24: PodMonitor - Received BOOKMARK: oldResVer=11698 newResVer=11946 2025-01-13 02:20:44.24: PodMonitor - start process kube event 2025-01-13 02:20:44.24: empty line received 2025-01-13 02:20:44.24: PodMonitor - start process kube event 2025-01-13 02:20:45.93: EndPointMonitor - Received BOOKMARK: oldResVer=11360 newResVer=11360 2025-01-13 02:20:45.93: EndPointMonitor - start process kube event 2025-01-13 02:20:45.93: empty line received 2025-01-13 02:20:45.93: EndPointMonitor - start process kube event 2025-01-13 02:20:46.50: NamespaceMonitor - Received BOOKMARK: oldResVer=11393 newResVer=11393 2025-01-13 02:20:46.50: NamespaceMonitor - start process kube event 2025-01-13 02:20:46.50: empty line received 2025-01-13 02:20:46.50: NamespaceMonitor - start process kube event 2025-01-13 02:21:41.72: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11462 newResVer=11462 2025-01-13 02:21:41.72: NetworkPolicyMonitor - start process kube event 2025-01-13 02:21:41.72: empty line received 2025-01-13 02:21:41.72: NetworkPolicyMonitor - start process kube event 2025-01-13 02:21:42.22: NetworkMonitor - Received BOOKMARK: oldResVer=11145 newResVer=11145 2025-01-13 02:21:42.22: NetworkMonitor - start process kube event 2025-01-13 02:21:42.22: empty line received 2025-01-13 02:21:42.22: NetworkMonitor - start process kube event 2025-01-13 02:21:43.40: ServiceMonitor - Received BOOKMARK: oldResVer=11424 newResVer=11424 2025-01-13 02:21:43.40: ServiceMonitor - start process kube event 2025-01-13 02:21:43.40: empty line received 2025-01-13 02:21:43.40: ServiceMonitor - start process kube event 2025-01-13 02:21:43.87: IngressMonitor - Received BOOKMARK: oldResVer=11904 newResVer=11904 2025-01-13 02:21:43.87: IngressMonitor - start process kube event 2025-01-13 02:21:43.87: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:21:43.87: empty line received 2025-01-13 02:21:43.87: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:21:43.87: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:21:43.87: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:21:43.87: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:21:43.87: IngressMonitor - start process kube event 2025-01-13 02:21:44.20: PodMonitor - Received BOOKMARK: oldResVer=11946 newResVer=11946 2025-01-13 02:21:44.20: PodMonitor - start process kube event 2025-01-13 02:21:44.20: empty line received 2025-01-13 02:21:44.20: PodMonitor - start process kube event 2025-01-13 02:21:45.94: EndPointMonitor - Received BOOKMARK: oldResVer=11360 newResVer=11360 2025-01-13 02:21:45.94: EndPointMonitor - start process kube event 2025-01-13 02:21:45.94: empty line received 2025-01-13 02:21:45.94: EndPointMonitor - start process kube event 2025-01-13 02:21:46.26: NamespaceMonitor - Received BOOKMARK: oldResVer=11393 newResVer=11393 2025-01-13 02:21:46.26: NamespaceMonitor - start process kube event 2025-01-13 02:21:46.26: empty line received 2025-01-13 02:21:46.26: NamespaceMonitor - start process kube event 2025-01-13 02:22:41.78: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11462 newResVer=11462 2025-01-13 02:22:41.78: NetworkPolicyMonitor - start process kube event 2025-01-13 02:22:41.78: empty line received 2025-01-13 02:22:41.78: NetworkPolicyMonitor - start process kube event 2025-01-13 02:22:42.43: NetworkMonitor - Received BOOKMARK: oldResVer=11145 newResVer=12068 2025-01-13 02:22:42.43: NetworkMonitor - start process kube event 2025-01-13 02:22:42.43: empty line received 2025-01-13 02:22:42.43: NetworkMonitor - start process kube event 2025-01-13 02:22:43.45: ServiceMonitor - Received BOOKMARK: oldResVer=11424 newResVer=11424 2025-01-13 02:22:43.46: IngressMonitor - Received BOOKMARK: oldResVer=11904 newResVer=11904 2025-01-13 02:22:43.46: ServiceMonitor - start process kube event 2025-01-13 02:22:43.46: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:22:43.46: empty line received 2025-01-13 02:22:43.46: IngressMonitor - start process kube event 2025-01-13 02:22:43.46: empty line received 2025-01-13 02:22:43.46: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:22:43.46: VncKubernetes - vnc_sync - Service start 2025-01-13 02:22:43.46: VncKubernetes - vnc_sync - Service done 2025-01-13 02:22:43.46: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:22:43.46: ServiceMonitor - start process kube event 2025-01-13 02:22:43.46: IngressMonitor - start process kube event 2025-01-13 02:22:44.73: PodMonitor - Received BOOKMARK: oldResVer=11946 newResVer=11946 2025-01-13 02:22:44.73: PodMonitor - start process kube event 2025-01-13 02:22:44.73: PodMonitor - _schedule_vnc_sync 2025-01-13 02:22:44.73: empty line received 2025-01-13 02:22:44.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:22:44.73: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:22:44.73: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:22:44.73: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:22:44.73: PodMonitor - start process kube event 2025-01-13 02:22:45.93: NamespaceMonitor - Received BOOKMARK: oldResVer=11393 newResVer=11393 2025-01-13 02:22:45.93: NamespaceMonitor - start process kube event 2025-01-13 02:22:45.93: empty line received 2025-01-13 02:22:45.93: NamespaceMonitor - start process kube event 2025-01-13 02:22:46.27: EndPointMonitor - Received BOOKMARK: oldResVer=11360 newResVer=11360 2025-01-13 02:22:46.27: EndPointMonitor - start process kube event 2025-01-13 02:22:46.27: empty line received 2025-01-13 02:22:46.27: EndPointMonitor - start process kube event 2025-01-13 02:22:51.17: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:22:51.17: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:22:51.17: PodMonitor - start process kube event 2025-01-13 02:22:51.17: empty line received 2025-01-13 02:22:51.17: PodMonitor - start process kube event 2025-01-13 02:23:41.12: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11462 newResVer=11462 2025-01-13 02:23:41.12: NetworkPolicyMonitor - start process kube event 2025-01-13 02:23:41.12: empty line received 2025-01-13 02:23:41.12: NetworkPolicyMonitor - start process kube event 2025-01-13 02:23:41.96: NetworkMonitor - Received BOOKMARK: oldResVer=12068 newResVer=12068 2025-01-13 02:23:41.96: NetworkMonitor - start process kube event 2025-01-13 02:23:41.96: empty line received 2025-01-13 02:23:41.96: NetworkMonitor - start process kube event 2025-01-13 02:23:43.02: IngressMonitor - Received BOOKMARK: oldResVer=11904 newResVer=11904 2025-01-13 02:23:43.02: IngressMonitor - start process kube event 2025-01-13 02:23:43.02: empty line received 2025-01-13 02:23:43.02: IngressMonitor - start process kube event 2025-01-13 02:23:43.55: ServiceMonitor - Received BOOKMARK: oldResVer=11424 newResVer=11424 2025-01-13 02:23:43.55: ServiceMonitor - start process kube event 2025-01-13 02:23:43.55: empty line received 2025-01-13 02:23:43.55: ServiceMonitor - start process kube event 2025-01-13 02:23:44.72: PodMonitor - Received BOOKMARK: oldResVer=11946 newResVer=12141 2025-01-13 02:23:44.72: PodMonitor - start process kube event 2025-01-13 02:23:44.72: empty line received 2025-01-13 02:23:44.72: PodMonitor - start process kube event 2025-01-13 02:23:45.97: EndPointMonitor - Received BOOKMARK: oldResVer=11360 newResVer=11360 2025-01-13 02:23:45.97: EndPointMonitor - start process kube event 2025-01-13 02:23:45.97: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:23:45.97: empty line received 2025-01-13 02:23:45.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:23:45.97: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:23:45.97: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:23:45.97: EndPointMonitor - start process kube event 2025-01-13 02:23:46.08: NamespaceMonitor - Received BOOKMARK: oldResVer=11393 newResVer=11393 2025-01-13 02:23:46.08: NamespaceMonitor - start process kube event 2025-01-13 02:23:46.08: empty line received 2025-01-13 02:23:46.08: NamespaceMonitor - start process kube event 2025-01-13 02:23:51.65: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:23:51.65: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:23:51.65: PodMonitor - start process kube event 2025-01-13 02:23:51.65: empty line received 2025-01-13 02:23:51.65: PodMonitor - start process kube event 2025-01-13 02:24:05.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:24:05.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:24:05.55: PodMonitor - start process kube event 2025-01-13 02:24:05.55: empty line received 2025-01-13 02:24:05.55: PodMonitor - start process kube event 2025-01-13 02:24:41.18: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11462 newResVer=11462 2025-01-13 02:24:41.18: NetworkPolicyMonitor - start process kube event 2025-01-13 02:24:41.18: empty line received 2025-01-13 02:24:41.18: NetworkPolicyMonitor - start process kube event 2025-01-13 02:24:42.25: NetworkMonitor - Received BOOKMARK: oldResVer=12068 newResVer=12068 2025-01-13 02:24:42.25: NetworkMonitor - start process kube event 2025-01-13 02:24:42.25: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:24:42.25: empty line received 2025-01-13 02:24:42.25: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:24:42.25: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:24:42.25: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:24:42.25: NetworkMonitor - start process kube event 2025-01-13 02:24:43.08: ServiceMonitor - Received BOOKMARK: oldResVer=11424 newResVer=11424 2025-01-13 02:24:43.08: ServiceMonitor - start process kube event 2025-01-13 02:24:43.08: empty line received 2025-01-13 02:24:43.08: ServiceMonitor - start process kube event 2025-01-13 02:24:43.65: IngressMonitor - Received BOOKMARK: oldResVer=11904 newResVer=11904 2025-01-13 02:24:43.65: IngressMonitor - start process kube event 2025-01-13 02:24:43.65: empty line received 2025-01-13 02:24:43.65: IngressMonitor - start process kube event 2025-01-13 02:24:44.59: PodMonitor - Received BOOKMARK: oldResVer=12141 newResVer=12249 2025-01-13 02:24:44.59: PodMonitor - start process kube event 2025-01-13 02:24:44.59: empty line received 2025-01-13 02:24:44.59: PodMonitor - start process kube event 2025-01-13 02:24:46.40: NamespaceMonitor - Received BOOKMARK: oldResVer=11393 newResVer=12291 2025-01-13 02:24:46.40: NamespaceMonitor - start process kube event 2025-01-13 02:24:46.40: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:24:46.40: empty line received 2025-01-13 02:24:46.40: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:24:46.40: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:24:46.40: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:24:46.40: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:24:46.40: NamespaceMonitor - start process kube event 2025-01-13 02:24:46.45: EndPointMonitor - Received BOOKMARK: oldResVer=11360 newResVer=12259 2025-01-13 02:24:46.46: EndPointMonitor - start process kube event 2025-01-13 02:24:46.46: empty line received 2025-01-13 02:24:46.46: EndPointMonitor - start process kube event 2025-01-13 02:25:20.98: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:25:20.98: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:25:20.98: PodMonitor - start process kube event 2025-01-13 02:25:20.98: empty line received 2025-01-13 02:25:20.98: PodMonitor - start process kube event 2025-01-13 02:25:22.05: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:25:22.05: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:25:22.05: PodMonitor - start process kube event 2025-01-13 02:25:22.05: empty line received 2025-01-13 02:25:22.05: PodMonitor - start process kube event 2025-01-13 02:25:33.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:25:33.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:25:33.55: PodMonitor - start process kube event 2025-01-13 02:25:33.55: empty line received 2025-01-13 02:25:33.55: PodMonitor - start process kube event 2025-01-13 02:25:41.77: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11462 newResVer=12366 2025-01-13 02:25:41.77: NetworkPolicyMonitor - start process kube event 2025-01-13 02:25:41.77: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:25:41.77: empty line received 2025-01-13 02:25:41.77: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:25:41.77: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:25:41.77: NetworkPolicyMonitor - start process kube event 2025-01-13 02:25:41.78: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:25:41.78: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:25:42.72: NetworkMonitor - Received BOOKMARK: oldResVer=12068 newResVer=12068 2025-01-13 02:25:42.72: NetworkMonitor - start process kube event 2025-01-13 02:25:42.72: empty line received 2025-01-13 02:25:42.72: NetworkMonitor - start process kube event 2025-01-13 02:25:43.19: IngressMonitor - Received BOOKMARK: oldResVer=11904 newResVer=11904 2025-01-13 02:25:43.19: IngressMonitor - start process kube event 2025-01-13 02:25:43.19: empty line received 2025-01-13 02:25:43.19: IngressMonitor - start process kube event 2025-01-13 02:25:43.61: ServiceMonitor - Received BOOKMARK: oldResVer=11424 newResVer=12324 2025-01-13 02:25:43.61: ServiceMonitor - start process kube event 2025-01-13 02:25:43.61: empty line received 2025-01-13 02:25:43.61: ServiceMonitor - start process kube event 2025-01-13 02:25:43.86: PodMonitor - Received BOOKMARK: oldResVer=12249 newResVer=12376 2025-01-13 02:25:43.86: PodMonitor - start process kube event 2025-01-13 02:25:43.86: empty line received 2025-01-13 02:25:43.86: PodMonitor - start process kube event 2025-01-13 02:25:46.15: NamespaceMonitor - Received BOOKMARK: oldResVer=12291 newResVer=12291 2025-01-13 02:25:46.15: NamespaceMonitor - start process kube event 2025-01-13 02:25:46.15: empty line received 2025-01-13 02:25:46.15: NamespaceMonitor - start process kube event 2025-01-13 02:25:46.55: EndPointMonitor - Received BOOKMARK: oldResVer=12259 newResVer=12259 2025-01-13 02:25:46.55: EndPointMonitor - start process kube event 2025-01-13 02:25:46.55: empty line received 2025-01-13 02:25:46.55: EndPointMonitor - start process kube event 2025-01-13 02:26:41.13: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=12366 2025-01-13 02:26:41.13: NetworkPolicyMonitor - start process kube event 2025-01-13 02:26:41.13: empty line received 2025-01-13 02:26:41.13: NetworkPolicyMonitor - start process kube event 2025-01-13 02:26:42.86: NetworkMonitor - Received BOOKMARK: oldResVer=12068 newResVer=12068 2025-01-13 02:26:42.86: NetworkMonitor - start process kube event 2025-01-13 02:26:42.86: empty line received 2025-01-13 02:26:42.86: NetworkMonitor - start process kube event 2025-01-13 02:26:43.08: ServiceMonitor - Received BOOKMARK: oldResVer=12324 newResVer=12324 2025-01-13 02:26:43.08: ServiceMonitor - start process kube event 2025-01-13 02:26:43.08: empty line received 2025-01-13 02:26:43.08: ServiceMonitor - start process kube event 2025-01-13 02:26:43.81: IngressMonitor - Received BOOKMARK: oldResVer=11904 newResVer=11904 2025-01-13 02:26:43.81: IngressMonitor - start process kube event 2025-01-13 02:26:43.81: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:26:43.81: empty line received 2025-01-13 02:26:43.81: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:26:43.81: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:26:43.81: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:26:43.81: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:26:43.81: IngressMonitor - start process kube event 2025-01-13 02:26:44.22: PodMonitor - Received BOOKMARK: oldResVer=12376 newResVer=12376 2025-01-13 02:26:44.23: PodMonitor - start process kube event 2025-01-13 02:26:44.23: empty line received 2025-01-13 02:26:44.23: PodMonitor - start process kube event 2025-01-13 02:26:46.46: NamespaceMonitor - Received BOOKMARK: oldResVer=12291 newResVer=12291 2025-01-13 02:26:46.46: NamespaceMonitor - start process kube event 2025-01-13 02:26:46.46: empty line received 2025-01-13 02:26:46.46: NamespaceMonitor - start process kube event 2025-01-13 02:26:46.89: EndPointMonitor - Received BOOKMARK: oldResVer=12259 newResVer=12259 2025-01-13 02:26:46.89: EndPointMonitor - start process kube event 2025-01-13 02:26:46.89: empty line received 2025-01-13 02:26:46.89: EndPointMonitor - start process kube event 2025-01-13 02:27:41.35: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=12366 2025-01-13 02:27:41.35: NetworkPolicyMonitor - start process kube event 2025-01-13 02:27:41.35: empty line received 2025-01-13 02:27:41.35: NetworkPolicyMonitor - start process kube event 2025-01-13 02:27:42.59: NetworkMonitor - Received BOOKMARK: oldResVer=12068 newResVer=12068 2025-01-13 02:27:42.59: NetworkMonitor - start process kube event 2025-01-13 02:27:42.59: empty line received 2025-01-13 02:27:42.59: NetworkMonitor - start process kube event 2025-01-13 02:27:43.24: IngressMonitor - Received BOOKMARK: oldResVer=11904 newResVer=11904 2025-01-13 02:27:43.24: IngressMonitor - start process kube event 2025-01-13 02:27:43.24: empty line received 2025-01-13 02:27:43.24: IngressMonitor - start process kube event 2025-01-13 02:27:43.73: ServiceMonitor - Received BOOKMARK: oldResVer=12324 newResVer=12324 2025-01-13 02:27:43.73: ServiceMonitor - start process kube event 2025-01-13 02:27:43.73: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:27:43.73: empty line received 2025-01-13 02:27:43.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:27:43.73: VncKubernetes - vnc_sync - Service start 2025-01-13 02:27:43.73: VncKubernetes - vnc_sync - Service done 2025-01-13 02:27:43.73: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:27:43.73: ServiceMonitor - start process kube event 2025-01-13 02:27:44.47: PodMonitor - Received BOOKMARK: oldResVer=12376 newResVer=12376 2025-01-13 02:27:44.47: PodMonitor - start process kube event 2025-01-13 02:27:44.47: PodMonitor - _schedule_vnc_sync 2025-01-13 02:27:44.47: empty line received 2025-01-13 02:27:44.47: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:27:44.47: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:27:44.47: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:27:44.47: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:27:44.47: PodMonitor - start process kube event 2025-01-13 02:27:46.63: NamespaceMonitor - Received BOOKMARK: oldResVer=12291 newResVer=12291 2025-01-13 02:27:46.63: NamespaceMonitor - start process kube event 2025-01-13 02:27:46.63: empty line received 2025-01-13 02:27:46.63: NamespaceMonitor - start process kube event 2025-01-13 02:27:47.62: EndPointMonitor - Received BOOKMARK: oldResVer=12259 newResVer=12259 2025-01-13 02:27:47.62: EndPointMonitor - start process kube event 2025-01-13 02:27:47.62: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:27:47.62: empty line received 2025-01-13 02:27:47.62: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:27:47.62: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:27:47.62: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:27:47.62: EndPointMonitor - start process kube event 2025-01-13 02:28:41.20: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=12366 2025-01-13 02:28:41.20: NetworkPolicyMonitor - start process kube event 2025-01-13 02:28:41.20: empty line received 2025-01-13 02:28:41.20: NetworkPolicyMonitor - start process kube event 2025-01-13 02:28:42.24: NetworkMonitor - Received BOOKMARK: oldResVer=12068 newResVer=12068 2025-01-13 02:28:42.24: NetworkMonitor - start process kube event 2025-01-13 02:28:42.24: empty line received 2025-01-13 02:28:42.24: NetworkMonitor - start process kube event 2025-01-13 02:28:43.59: IngressMonitor - Received BOOKMARK: oldResVer=11904 newResVer=11904 2025-01-13 02:28:43.59: IngressMonitor - start process kube event 2025-01-13 02:28:43.59: empty line received 2025-01-13 02:28:43.59: IngressMonitor - start process kube event 2025-01-13 02:28:43.86: ServiceMonitor - Received BOOKMARK: oldResVer=12324 newResVer=12324 2025-01-13 02:28:43.86: ServiceMonitor - start process kube event 2025-01-13 02:28:43.86: empty line received 2025-01-13 02:28:43.86: ServiceMonitor - start process kube event 2025-01-13 02:28:44.17: PodMonitor - Received BOOKMARK: oldResVer=12376 newResVer=12376 2025-01-13 02:28:44.17: PodMonitor - start process kube event 2025-01-13 02:28:44.17: empty line received 2025-01-13 02:28:44.17: PodMonitor - start process kube event 2025-01-13 02:28:45.95: NamespaceMonitor - Received BOOKMARK: oldResVer=12291 newResVer=12291 2025-01-13 02:28:45.95: NamespaceMonitor - start process kube event 2025-01-13 02:28:45.95: empty line received 2025-01-13 02:28:45.95: NamespaceMonitor - start process kube event 2025-01-13 02:28:47.92: EndPointMonitor - Received BOOKMARK: oldResVer=12259 newResVer=12259 2025-01-13 02:28:47.92: EndPointMonitor - start process kube event 2025-01-13 02:28:47.92: empty line received 2025-01-13 02:28:47.92: EndPointMonitor - start process kube event 2025-01-13 02:28:57.53: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:28:57.53: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:28:57.53: PodMonitor - start process kube event 2025-01-13 02:28:57.53: empty line received 2025-01-13 02:28:57.53: PodMonitor - start process kube event 2025-01-13 02:29:41.38: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=12366 2025-01-13 02:29:41.38: NetworkPolicyMonitor - start process kube event 2025-01-13 02:29:41.38: empty line received 2025-01-13 02:29:41.38: NetworkPolicyMonitor - start process kube event 2025-01-13 02:29:42.45: NetworkMonitor - Received BOOKMARK: oldResVer=12068 newResVer=12068 2025-01-13 02:29:42.45: NetworkMonitor - start process kube event 2025-01-13 02:29:42.45: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:29:42.45: empty line received 2025-01-13 02:29:42.45: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:29:42.45: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:29:42.45: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:29:42.45: NetworkMonitor - start process kube event 2025-01-13 02:29:43.85: ServiceMonitor - Received BOOKMARK: oldResVer=12324 newResVer=12324 2025-01-13 02:29:43.85: ServiceMonitor - start process kube event 2025-01-13 02:29:43.85: empty line received 2025-01-13 02:29:43.85: ServiceMonitor - start process kube event 2025-01-13 02:29:43.96: IngressMonitor - Received BOOKMARK: oldResVer=11904 newResVer=11904 2025-01-13 02:29:43.96: IngressMonitor - start process kube event 2025-01-13 02:29:43.96: empty line received 2025-01-13 02:29:43.96: IngressMonitor - start process kube event 2025-01-13 02:29:44.01: PodMonitor - Received BOOKMARK: oldResVer=12376 newResVer=12662 2025-01-13 02:29:44.01: PodMonitor - start process kube event 2025-01-13 02:29:44.01: empty line received 2025-01-13 02:29:44.01: PodMonitor - start process kube event 2025-01-13 02:29:46.62: NamespaceMonitor - Received BOOKMARK: oldResVer=12291 newResVer=12291 2025-01-13 02:29:46.62: NamespaceMonitor - start process kube event 2025-01-13 02:29:46.62: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:29:46.62: empty line received 2025-01-13 02:29:46.62: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:29:46.62: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:29:46.62: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:29:46.62: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:29:46.62: NamespaceMonitor - start process kube event 2025-01-13 02:29:47.88: EndPointMonitor - Received BOOKMARK: oldResVer=12259 newResVer=12259 2025-01-13 02:29:47.88: EndPointMonitor - start process kube event 2025-01-13 02:29:47.88: empty line received 2025-01-13 02:29:47.88: EndPointMonitor - start process kube event 2025-01-13 02:29:57.04: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:29:57.04: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:29:57.04: PodMonitor - start process kube event 2025-01-13 02:29:57.04: empty line received 2025-01-13 02:29:57.04: PodMonitor - start process kube event 2025-01-13 02:29:58.08: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:29:58.08: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:29:58.08: PodMonitor - start process kube event 2025-01-13 02:29:58.08: empty line received 2025-01-13 02:29:58.08: PodMonitor - start process kube event 2025-01-13 02:30:22.75: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:30:22.75: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:30:22.75: PodMonitor - start process kube event 2025-01-13 02:30:22.75: empty line received 2025-01-13 02:30:22.75: PodMonitor - start process kube event 2025-01-13 02:30:23.83: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:30:23.83: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:30:23.83: PodMonitor - start process kube event 2025-01-13 02:30:23.83: empty line received 2025-01-13 02:30:23.83: PodMonitor - start process kube event 2025-01-13 02:30:37.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:30:37.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:30:37.55: PodMonitor - start process kube event 2025-01-13 02:30:37.55: empty line received 2025-01-13 02:30:37.55: PodMonitor - start process kube event 2025-01-13 02:30:40.93: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=12366 2025-01-13 02:30:40.93: NetworkPolicyMonitor - start process kube event 2025-01-13 02:30:40.93: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:30:40.93: empty line received 2025-01-13 02:30:40.93: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:30:40.93: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:30:40.93: NetworkPolicyMonitor - start process kube event 2025-01-13 02:30:40.93: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:30:40.93: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:30:42.99: NetworkMonitor - Received BOOKMARK: oldResVer=12068 newResVer=12068 2025-01-13 02:30:42.99: NetworkMonitor - start process kube event 2025-01-13 02:30:42.99: empty line received 2025-01-13 02:30:42.99: NetworkMonitor - start process kube event 2025-01-13 02:30:44.38: IngressMonitor - Received BOOKMARK: oldResVer=11904 newResVer=11904 2025-01-13 02:30:44.38: IngressMonitor - start process kube event 2025-01-13 02:30:44.38: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:30:44.38: empty line received 2025-01-13 02:30:44.38: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:30:44.38: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:30:44.38: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:30:44.38: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:30:44.38: IngressMonitor - start process kube event 2025-01-13 02:30:44.53: ServiceMonitor - Received BOOKMARK: oldResVer=12324 newResVer=12324 2025-01-13 02:30:44.53: ServiceMonitor - start process kube event 2025-01-13 02:30:44.53: empty line received 2025-01-13 02:30:44.53: ServiceMonitor - start process kube event 2025-01-13 02:30:44.94: PodMonitor - Received BOOKMARK: oldResVer=12662 newResVer=12809 2025-01-13 02:30:44.94: PodMonitor - start process kube event 2025-01-13 02:30:44.94: empty line received 2025-01-13 02:30:44.94: PodMonitor - start process kube event 2025-01-13 02:30:46.15: NamespaceMonitor - Received BOOKMARK: oldResVer=12291 newResVer=12291 2025-01-13 02:30:46.15: NamespaceMonitor - start process kube event 2025-01-13 02:30:46.15: empty line received 2025-01-13 02:30:46.15: NamespaceMonitor - start process kube event 2025-01-13 02:30:48.09: EndPointMonitor - Received BOOKMARK: oldResVer=12259 newResVer=12259 2025-01-13 02:30:48.09: EndPointMonitor - start process kube event 2025-01-13 02:30:48.09: empty line received 2025-01-13 02:30:48.09: EndPointMonitor - start process kube event 2025-01-13 02:31:41.08: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=12366 2025-01-13 02:31:41.08: NetworkPolicyMonitor - start process kube event 2025-01-13 02:31:41.08: empty line received 2025-01-13 02:31:41.08: NetworkPolicyMonitor - start process kube event 2025-01-13 02:31:43.11: NetworkMonitor - Received BOOKMARK: oldResVer=12068 newResVer=12068 2025-01-13 02:31:43.11: NetworkMonitor - start process kube event 2025-01-13 02:31:43.11: empty line received 2025-01-13 02:31:43.11: NetworkMonitor - start process kube event 2025-01-13 02:31:44.81: ServiceMonitor - Received BOOKMARK: oldResVer=12324 newResVer=12324 2025-01-13 02:31:44.81: ServiceMonitor - start process kube event 2025-01-13 02:31:44.81: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:31:44.81: empty line received 2025-01-13 02:31:44.81: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:31:44.81: VncKubernetes - vnc_sync - Service start 2025-01-13 02:31:44.81: VncKubernetes - vnc_sync - Service done 2025-01-13 02:31:44.81: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:31:44.81: ServiceMonitor - start process kube event 2025-01-13 02:31:44.91: IngressMonitor - Received BOOKMARK: oldResVer=11904 newResVer=12842 2025-01-13 02:31:44.91: IngressMonitor - start process kube event 2025-01-13 02:31:44.91: empty line received 2025-01-13 02:31:44.91: IngressMonitor - start process kube event 2025-01-13 02:31:45.00: PodMonitor - Received BOOKMARK: oldResVer=12809 newResVer=12809 2025-01-13 02:31:45.00: PodMonitor - start process kube event 2025-01-13 02:31:45.00: PodMonitor - _schedule_vnc_sync 2025-01-13 02:31:45.00: empty line received 2025-01-13 02:31:45.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:31:45.00: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:31:45.00: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:31:45.00: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:31:45.00: PodMonitor - start process kube event 2025-01-13 02:31:45.95: NamespaceMonitor - Received BOOKMARK: oldResVer=12291 newResVer=12291 2025-01-13 02:31:45.95: NamespaceMonitor - start process kube event 2025-01-13 02:31:45.95: empty line received 2025-01-13 02:31:45.95: NamespaceMonitor - start process kube event 2025-01-13 02:31:48.43: EndPointMonitor - Received BOOKMARK: oldResVer=12259 newResVer=12259 2025-01-13 02:31:48.43: EndPointMonitor - start process kube event 2025-01-13 02:31:48.43: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:31:48.43: empty line received 2025-01-13 02:31:48.43: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:31:48.43: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:31:48.43: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:31:48.43: EndPointMonitor - start process kube event 2025-01-13 02:32:40.99: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=12366 2025-01-13 02:32:40.99: NetworkPolicyMonitor - start process kube event 2025-01-13 02:32:40.99: empty line received 2025-01-13 02:32:40.99: NetworkPolicyMonitor - start process kube event 2025-01-13 02:32:43.06: NetworkMonitor - Received BOOKMARK: oldResVer=12068 newResVer=12977 2025-01-13 02:32:43.06: NetworkMonitor - start process kube event 2025-01-13 02:32:43.06: empty line received 2025-01-13 02:32:43.06: NetworkMonitor - start process kube event 2025-01-13 02:32:44.13: IngressMonitor - Received BOOKMARK: oldResVer=12842 newResVer=12842 2025-01-13 02:32:44.13: IngressMonitor - start process kube event 2025-01-13 02:32:44.13: empty line received 2025-01-13 02:32:44.13: IngressMonitor - start process kube event 2025-01-13 02:32:44.54: ServiceMonitor - Received BOOKMARK: oldResVer=12324 newResVer=12324 2025-01-13 02:32:44.54: ServiceMonitor - start process kube event 2025-01-13 02:32:44.54: empty line received 2025-01-13 02:32:44.55: ServiceMonitor - start process kube event 2025-01-13 02:32:45.11: PodMonitor - Received BOOKMARK: oldResVer=12809 newResVer=12809 2025-01-13 02:32:45.11: PodMonitor - start process kube event 2025-01-13 02:32:45.11: empty line received 2025-01-13 02:32:45.11: PodMonitor - start process kube event 2025-01-13 02:32:46.33: NamespaceMonitor - Received BOOKMARK: oldResVer=12291 newResVer=12291 2025-01-13 02:32:46.33: NamespaceMonitor - start process kube event 2025-01-13 02:32:46.33: empty line received 2025-01-13 02:32:46.33: NamespaceMonitor - start process kube event 2025-01-13 02:32:48.88: EndPointMonitor - Received BOOKMARK: oldResVer=12259 newResVer=12259 2025-01-13 02:32:48.88: EndPointMonitor - start process kube event 2025-01-13 02:32:48.88: empty line received 2025-01-13 02:32:48.88: EndPointMonitor - start process kube event 2025-01-13 02:33:41.76: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=12366 2025-01-13 02:33:41.76: NetworkPolicyMonitor - start process kube event 2025-01-13 02:33:41.76: empty line received 2025-01-13 02:33:41.76: NetworkPolicyMonitor - start process kube event 2025-01-13 02:33:43.65: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:33:43.65: NetworkMonitor - start process kube event 2025-01-13 02:33:43.65: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:33:43.65: empty line received 2025-01-13 02:33:43.65: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:33:43.65: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:33:43.65: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:33:43.65: NetworkMonitor - start process kube event 2025-01-13 02:33:43.91: ServiceMonitor - Received BOOKMARK: oldResVer=12324 newResVer=12324 2025-01-13 02:33:43.91: ServiceMonitor - start process kube event 2025-01-13 02:33:43.91: empty line received 2025-01-13 02:33:43.91: ServiceMonitor - start process kube event 2025-01-13 02:33:44.32: IngressMonitor - Received BOOKMARK: oldResVer=12842 newResVer=12842 2025-01-13 02:33:44.32: IngressMonitor - start process kube event 2025-01-13 02:33:44.32: empty line received 2025-01-13 02:33:44.32: IngressMonitor - start process kube event 2025-01-13 02:33:45.48: PodMonitor - Received BOOKMARK: oldResVer=12809 newResVer=12809 2025-01-13 02:33:45.48: PodMonitor - start process kube event 2025-01-13 02:33:45.48: empty line received 2025-01-13 02:33:45.48: PodMonitor - start process kube event 2025-01-13 02:33:46.14: NamespaceMonitor - Received BOOKMARK: oldResVer=12291 newResVer=12291 2025-01-13 02:33:46.14: NamespaceMonitor - start process kube event 2025-01-13 02:33:46.14: empty line received 2025-01-13 02:33:46.14: NamespaceMonitor - start process kube event 2025-01-13 02:33:49.62: EndPointMonitor - Received BOOKMARK: oldResVer=12259 newResVer=12259 2025-01-13 02:33:49.62: EndPointMonitor - start process kube event 2025-01-13 02:33:49.62: empty line received 2025-01-13 02:33:49.62: EndPointMonitor - start process kube event 2025-01-13 02:34:41.79: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=12366 2025-01-13 02:34:41.79: NetworkPolicyMonitor - start process kube event 2025-01-13 02:34:41.79: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:34:41.79: empty line received 2025-01-13 02:34:41.79: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:34:41.79: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:34:41.79: NetworkPolicyMonitor - start process kube event 2025-01-13 02:34:41.80: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:34:41.80: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:34:43.37: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:34:43.37: NetworkMonitor - start process kube event 2025-01-13 02:34:43.37: empty line received 2025-01-13 02:34:43.37: NetworkMonitor - start process kube event 2025-01-13 02:34:44.47: ServiceMonitor - Received BOOKMARK: oldResVer=12324 newResVer=12324 2025-01-13 02:34:44.47: ServiceMonitor - start process kube event 2025-01-13 02:34:44.47: empty line received 2025-01-13 02:34:44.47: ServiceMonitor - start process kube event 2025-01-13 02:34:44.88: IngressMonitor - Received BOOKMARK: oldResVer=12842 newResVer=12842 2025-01-13 02:34:44.88: IngressMonitor - start process kube event 2025-01-13 02:34:44.88: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:34:44.88: empty line received 2025-01-13 02:34:44.88: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:34:44.88: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:34:44.88: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:34:44.88: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:34:44.88: IngressMonitor - start process kube event 2025-01-13 02:34:45.27: PodMonitor - Received BOOKMARK: oldResVer=12809 newResVer=12809 2025-01-13 02:34:45.27: PodMonitor - start process kube event 2025-01-13 02:34:45.27: empty line received 2025-01-13 02:34:45.27: PodMonitor - start process kube event 2025-01-13 02:34:46.80: NamespaceMonitor - Received BOOKMARK: oldResVer=12291 newResVer=12291 2025-01-13 02:34:46.80: NamespaceMonitor - start process kube event 2025-01-13 02:34:46.80: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:34:46.80: empty line received 2025-01-13 02:34:46.80: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:34:46.80: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:34:46.80: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:34:46.80: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:34:46.80: NamespaceMonitor - start process kube event 2025-01-13 02:34:48.83: EndPointMonitor - Received BOOKMARK: oldResVer=12259 newResVer=13147 2025-01-13 02:34:48.83: EndPointMonitor - start process kube event 2025-01-13 02:34:48.83: empty line received 2025-01-13 02:34:48.83: EndPointMonitor - start process kube event 2025-01-13 02:35:03.97: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:35:03.97: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:35:03.97: PodMonitor - start process kube event 2025-01-13 02:35:03.97: empty line received 2025-01-13 02:35:03.97: PodMonitor - start process kube event 2025-01-13 02:35:30.79: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:35:30.79: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:35:30.79: PodMonitor - start process kube event 2025-01-13 02:35:30.79: empty line received 2025-01-13 02:35:30.79: PodMonitor - start process kube event 2025-01-13 02:35:34.94: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=12366 2025-01-13 02:35:34.94: NetworkPolicyMonitor - start process kube event 2025-01-13 02:35:34.94: empty line received 2025-01-13 02:35:34.94: NetworkPolicyMonitor - start process kube event 2025-01-13 02:35:36.01: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=12366 2025-01-13 02:35:36.01: NetworkPolicyMonitor - start process kube event 2025-01-13 02:35:36.01: empty line received 2025-01-13 02:35:36.01: NetworkPolicyMonitor - start process kube event 2025-01-13 02:35:37.63: stop iteration NetworkPolicyMonitor 2025-01-13 02:35:37.63: NetworkPolicyMonitor - start process kube event 2025-01-13 02:35:37.63: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12366 2025-01-13 02:35:37.63: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:35:37.63: NetworkPolicyMonitor - Connect Kube API result 0 2025-01-13 02:35:37.63: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:35:37.63: NetworkPolicyMonitor - Start Watching request https://10.0.0.27:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12366'})(timeout=120) 2025-01-13 02:35:37.63: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:35:37.63: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:35:37.64: NetworkPolicyMonitor - Watches https://10.0.0.27:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12366'}) 2025-01-13 02:35:37.64: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:35:37.64: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:35:43.30: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:35:43.30: NetworkMonitor - start process kube event 2025-01-13 02:35:43.30: empty line received 2025-01-13 02:35:43.30: NetworkMonitor - start process kube event 2025-01-13 02:35:44.25: IngressMonitor - Received BOOKMARK: oldResVer=12842 newResVer=12842 2025-01-13 02:35:44.25: IngressMonitor - start process kube event 2025-01-13 02:35:44.25: empty line received 2025-01-13 02:35:44.25: IngressMonitor - start process kube event 2025-01-13 02:35:44.27: ServiceMonitor - Received BOOKMARK: oldResVer=12324 newResVer=13219 2025-01-13 02:35:44.27: ServiceMonitor - start process kube event 2025-01-13 02:35:44.27: empty line received 2025-01-13 02:35:44.27: ServiceMonitor - start process kube event 2025-01-13 02:35:45.41: PodMonitor - Received BOOKMARK: oldResVer=12809 newResVer=13220 2025-01-13 02:35:45.41: PodMonitor - start process kube event 2025-01-13 02:35:45.41: PodMonitor - _schedule_vnc_sync 2025-01-13 02:35:45.41: empty line received 2025-01-13 02:35:45.41: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:35:45.41: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:35:45.41: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:35:45.41: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:35:45.41: PodMonitor - start process kube event 2025-01-13 02:35:45.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:35:45.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:35:45.55: PodMonitor - start process kube event 2025-01-13 02:35:45.55: empty line received 2025-01-13 02:35:45.55: PodMonitor - start process kube event 2025-01-13 02:35:47.53: NamespaceMonitor - Received BOOKMARK: oldResVer=12291 newResVer=13183 2025-01-13 02:35:47.53: NamespaceMonitor - start process kube event 2025-01-13 02:35:47.53: empty line received 2025-01-13 02:35:47.53: NamespaceMonitor - start process kube event 2025-01-13 02:35:49.18: EndPointMonitor - Received BOOKMARK: oldResVer=13147 newResVer=13147 2025-01-13 02:35:49.18: EndPointMonitor - start process kube event 2025-01-13 02:35:49.18: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:35:49.18: empty line received 2025-01-13 02:35:49.18: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:35:49.18: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:35:49.18: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:35:49.18: EndPointMonitor - start process kube event 2025-01-13 02:36:04.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:36:04.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:36:04.68: PodMonitor - start process kube event 2025-01-13 02:36:04.68: empty line received 2025-01-13 02:36:04.68: PodMonitor - start process kube event 2025-01-13 02:36:18.56: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:36:18.56: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:36:18.56: PodMonitor - start process kube event 2025-01-13 02:36:18.56: empty line received 2025-01-13 02:36:18.56: PodMonitor - start process kube event 2025-01-13 02:36:20.49: PodMonitor - Received BOOKMARK: oldResVer=13220 newResVer=13291 2025-01-13 02:36:20.49: PodMonitor - start process kube event 2025-01-13 02:36:20.49: empty line received 2025-01-13 02:36:20.49: PodMonitor - start process kube event 2025-01-13 02:36:21.99: stop iteration PodMonitor 2025-01-13 02:36:21.99: PodMonitor - start process kube event 2025-01-13 02:36:21.99: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13291 2025-01-13 02:36:21.99: PodMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:36:21.99: PodMonitor - Connect Kube API result 0 2025-01-13 02:36:21.99: PodMonitor - _schedule_vnc_sync 2025-01-13 02:36:21.99: PodMonitor - Start Watching request https://10.0.0.27:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13291'})(timeout=120) 2025-01-13 02:36:21.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:36:21.99: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:36:21.99: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:36:21.99: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:36:21.99: PodMonitor - Watches https://10.0.0.27:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13291'}) 2025-01-13 02:36:37.00: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=12366 newResVer=13265 2025-01-13 02:36:37.00: NetworkPolicyMonitor - start process kube event 2025-01-13 02:36:37.00: empty line received 2025-01-13 02:36:37.00: NetworkPolicyMonitor - start process kube event 2025-01-13 02:36:42.97: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:36:42.97: NetworkMonitor - start process kube event 2025-01-13 02:36:42.97: empty line received 2025-01-13 02:36:42.97: NetworkMonitor - start process kube event 2025-01-13 02:36:44.22: ServiceMonitor - Received BOOKMARK: oldResVer=13219 newResVer=13219 2025-01-13 02:36:44.22: ServiceMonitor - start process kube event 2025-01-13 02:36:44.22: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:36:44.22: empty line received 2025-01-13 02:36:44.22: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:36:44.22: VncKubernetes - vnc_sync - Service start 2025-01-13 02:36:44.22: VncKubernetes - vnc_sync - Service done 2025-01-13 02:36:44.22: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:36:44.22: ServiceMonitor - start process kube event 2025-01-13 02:36:44.41: IngressMonitor - Received BOOKMARK: oldResVer=12842 newResVer=12842 2025-01-13 02:36:44.41: IngressMonitor - start process kube event 2025-01-13 02:36:44.41: empty line received 2025-01-13 02:36:44.41: IngressMonitor - start process kube event 2025-01-13 02:36:47.64: NamespaceMonitor - Received BOOKMARK: oldResVer=13183 newResVer=13183 2025-01-13 02:36:47.64: NamespaceMonitor - start process kube event 2025-01-13 02:36:47.64: empty line received 2025-01-13 02:36:47.64: NamespaceMonitor - start process kube event 2025-01-13 02:36:49.71: EndPointMonitor - Received BOOKMARK: oldResVer=13147 newResVer=13147 2025-01-13 02:36:49.71: EndPointMonitor - start process kube event 2025-01-13 02:36:49.71: empty line received 2025-01-13 02:36:49.71: EndPointMonitor - start process kube event 2025-01-13 02:37:37.46: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13265 newResVer=13265 2025-01-13 02:37:37.46: NetworkPolicyMonitor - start process kube event 2025-01-13 02:37:37.46: empty line received 2025-01-13 02:37:37.46: NetworkPolicyMonitor - start process kube event 2025-01-13 02:37:43.72: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:37:43.72: NetworkMonitor - start process kube event 2025-01-13 02:37:43.72: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:37:43.72: empty line received 2025-01-13 02:37:43.72: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:37:43.72: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:37:43.72: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:37:43.72: NetworkMonitor - start process kube event 2025-01-13 02:37:43.94: ServiceMonitor - Received BOOKMARK: oldResVer=13219 newResVer=13219 2025-01-13 02:37:43.94: ServiceMonitor - start process kube event 2025-01-13 02:37:43.94: empty line received 2025-01-13 02:37:43.94: ServiceMonitor - start process kube event 2025-01-13 02:37:44.51: IngressMonitor - Received BOOKMARK: oldResVer=12842 newResVer=12842 2025-01-13 02:37:44.51: IngressMonitor - start process kube event 2025-01-13 02:37:44.51: empty line received 2025-01-13 02:37:44.51: IngressMonitor - start process kube event 2025-01-13 02:37:47.39: NamespaceMonitor - Received BOOKMARK: oldResVer=13183 newResVer=13183 2025-01-13 02:37:47.39: NamespaceMonitor - start process kube event 2025-01-13 02:37:47.39: empty line received 2025-01-13 02:37:47.39: NamespaceMonitor - start process kube event 2025-01-13 02:37:49.22: EndPointMonitor - Received BOOKMARK: oldResVer=13147 newResVer=13147 2025-01-13 02:37:49.22: EndPointMonitor - start process kube event 2025-01-13 02:37:49.22: empty line received 2025-01-13 02:37:49.22: EndPointMonitor - start process kube event 2025-01-13 02:38:21.99: IOError PodMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:38:21.99: PodMonitor - start process kube event 2025-01-13 02:38:21.99: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13291 2025-01-13 02:38:21.99: PodMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:38:21.99: PodMonitor - Connect Kube API result 0 2025-01-13 02:38:22.00: PodMonitor - _schedule_vnc_sync 2025-01-13 02:38:22.00: PodMonitor - Start Watching request https://10.0.0.27:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13291'})(timeout=120) 2025-01-13 02:38:22.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:38:22.00: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:38:22.00: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:38:22.00: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:38:22.01: PodMonitor - Watches https://10.0.0.27:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13291'}) 2025-01-13 02:38:37.79: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13265 newResVer=13265 2025-01-13 02:38:37.79: NetworkPolicyMonitor - start process kube event 2025-01-13 02:38:37.79: empty line received 2025-01-13 02:38:37.79: NetworkPolicyMonitor - start process kube event 2025-01-13 02:38:43.25: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:38:43.25: NetworkMonitor - start process kube event 2025-01-13 02:38:43.25: empty line received 2025-01-13 02:38:43.25: NetworkMonitor - start process kube event 2025-01-13 02:38:44.69: IngressMonitor - Received BOOKMARK: oldResVer=12842 newResVer=12842 2025-01-13 02:38:44.69: IngressMonitor - start process kube event 2025-01-13 02:38:44.69: empty line received 2025-01-13 02:38:44.69: IngressMonitor - start process kube event 2025-01-13 02:38:44.79: ServiceMonitor - Received BOOKMARK: oldResVer=13219 newResVer=13219 2025-01-13 02:38:44.79: ServiceMonitor - start process kube event 2025-01-13 02:38:44.79: empty line received 2025-01-13 02:38:44.79: ServiceMonitor - start process kube event 2025-01-13 02:38:47.82: NamespaceMonitor - Received BOOKMARK: oldResVer=13183 newResVer=13183 2025-01-13 02:38:47.82: NamespaceMonitor - start process kube event 2025-01-13 02:38:47.82: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:38:47.82: empty line received 2025-01-13 02:38:47.82: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:38:47.82: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:38:47.82: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:38:47.82: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:38:47.82: NamespaceMonitor - start process kube event 2025-01-13 02:38:48.82: EndPointMonitor - Received BOOKMARK: oldResVer=13147 newResVer=13147 2025-01-13 02:38:48.82: EndPointMonitor - start process kube event 2025-01-13 02:38:48.82: empty line received 2025-01-13 02:38:48.82: EndPointMonitor - start process kube event 2025-01-13 02:39:37.66: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13265 newResVer=13265 2025-01-13 02:39:37.66: NetworkPolicyMonitor - start process kube event 2025-01-13 02:39:37.66: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:39:37.66: empty line received 2025-01-13 02:39:37.66: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:39:37.66: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:39:37.66: NetworkPolicyMonitor - start process kube event 2025-01-13 02:39:37.66: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:39:37.66: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:39:43.25: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:39:43.25: NetworkMonitor - start process kube event 2025-01-13 02:39:43.25: empty line received 2025-01-13 02:39:43.25: NetworkMonitor - start process kube event 2025-01-13 02:39:43.89: ServiceMonitor - Received BOOKMARK: oldResVer=13219 newResVer=13219 2025-01-13 02:39:43.89: ServiceMonitor - start process kube event 2025-01-13 02:39:43.89: empty line received 2025-01-13 02:39:43.89: ServiceMonitor - start process kube event 2025-01-13 02:39:44.25: IngressMonitor - Received BOOKMARK: oldResVer=12842 newResVer=12842 2025-01-13 02:39:44.25: IngressMonitor - start process kube event 2025-01-13 02:39:44.25: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:39:44.25: empty line received 2025-01-13 02:39:44.25: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:39:44.25: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:39:44.25: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:39:44.25: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:39:44.25: IngressMonitor - start process kube event 2025-01-13 02:39:46.67: NamespaceMonitor - Received BOOKMARK: oldResVer=13183 newResVer=13183 2025-01-13 02:39:46.67: NamespaceMonitor - start process kube event 2025-01-13 02:39:46.67: empty line received 2025-01-13 02:39:46.67: NamespaceMonitor - start process kube event 2025-01-13 02:39:48.33: stop iteration NamespaceMonitor 2025-01-13 02:39:48.33: NamespaceMonitor - start process kube event 2025-01-13 02:39:48.33: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13183 2025-01-13 02:39:48.33: NamespaceMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:39:48.33: NamespaceMonitor - Connect Kube API result 0 2025-01-13 02:39:48.33: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:39:48.33: NamespaceMonitor - Start Watching request https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13183'})(timeout=120) 2025-01-13 02:39:48.33: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:39:48.33: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:39:48.33: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:39:48.33: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:39:48.34: NamespaceMonitor - Watches https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13183'}) 2025-01-13 02:39:49.94: EndPointMonitor - Received BOOKMARK: oldResVer=13147 newResVer=13147 2025-01-13 02:39:49.94: EndPointMonitor - start process kube event 2025-01-13 02:39:49.94: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:39:49.94: empty line received 2025-01-13 02:39:49.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:39:49.94: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:39:49.94: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:39:49.94: EndPointMonitor - start process kube event 2025-01-13 02:40:22.01: IOError PodMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:40:22.01: PodMonitor - start process kube event 2025-01-13 02:40:22.01: PodMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13291 2025-01-13 02:40:22.01: PodMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:40:22.01: PodMonitor - Connect Kube API result 0 2025-01-13 02:40:22.01: PodMonitor - _schedule_vnc_sync 2025-01-13 02:40:22.01: PodMonitor - Start Watching request https://10.0.0.27:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13291'})(timeout=120) 2025-01-13 02:40:22.01: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:40:22.01: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:40:22.01: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:40:22.01: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:40:22.02: PodMonitor - Watches https://10.0.0.27:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13291'}) 2025-01-13 02:40:36.96: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13265 newResVer=13265 2025-01-13 02:40:36.96: NetworkPolicyMonitor - start process kube event 2025-01-13 02:40:36.96: empty line received 2025-01-13 02:40:36.96: NetworkPolicyMonitor - start process kube event 2025-01-13 02:40:38.53: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:40:38.53: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:40:38.53: PodMonitor - start process kube event 2025-01-13 02:40:38.53: empty line received 2025-01-13 02:40:38.53: PodMonitor - start process kube event 2025-01-13 02:40:43.73: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:40:43.73: NetworkMonitor - start process kube event 2025-01-13 02:40:43.73: empty line received 2025-01-13 02:40:43.73: NetworkMonitor - start process kube event 2025-01-13 02:40:44.32: IngressMonitor - Received BOOKMARK: oldResVer=12842 newResVer=12842 2025-01-13 02:40:44.32: IngressMonitor - start process kube event 2025-01-13 02:40:44.32: empty line received 2025-01-13 02:40:44.32: IngressMonitor - start process kube event 2025-01-13 02:40:44.64: ServiceMonitor - Received BOOKMARK: oldResVer=13219 newResVer=13219 2025-01-13 02:40:44.64: ServiceMonitor - start process kube event 2025-01-13 02:40:44.64: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:40:44.64: empty line received 2025-01-13 02:40:44.64: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:40:44.64: VncKubernetes - vnc_sync - Service start 2025-01-13 02:40:44.64: VncKubernetes - vnc_sync - Service done 2025-01-13 02:40:44.64: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:40:44.64: ServiceMonitor - start process kube event 2025-01-13 02:40:50.67: EndPointMonitor - Received BOOKMARK: oldResVer=13147 newResVer=13147 2025-01-13 02:40:50.67: EndPointMonitor - start process kube event 2025-01-13 02:40:50.67: empty line received 2025-01-13 02:40:50.67: EndPointMonitor - start process kube event 2025-01-13 02:40:52.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:40:52.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:40:52.55: PodMonitor - start process kube event 2025-01-13 02:40:52.55: empty line received 2025-01-13 02:40:52.55: PodMonitor - start process kube event 2025-01-13 02:41:16.51: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:41:16.51: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:41:16.51: PodMonitor - start process kube event 2025-01-13 02:41:16.51: empty line received 2025-01-13 02:41:16.51: PodMonitor - start process kube event 2025-01-13 02:41:22.33: PodMonitor - Received BOOKMARK: oldResVer=13291 newResVer=13712 2025-01-13 02:41:22.33: PodMonitor - start process kube event 2025-01-13 02:41:22.33: empty line received 2025-01-13 02:41:22.33: PodMonitor - start process kube event 2025-01-13 02:41:37.57: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13265 newResVer=13265 2025-01-13 02:41:37.57: NetworkPolicyMonitor - start process kube event 2025-01-13 02:41:37.57: empty line received 2025-01-13 02:41:37.57: NetworkPolicyMonitor - start process kube event 2025-01-13 02:41:43.91: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:41:43.91: NetworkMonitor - start process kube event 2025-01-13 02:41:43.91: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:41:43.91: empty line received 2025-01-13 02:41:43.91: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:41:43.91: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:41:43.91: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:41:43.91: NetworkMonitor - start process kube event 2025-01-13 02:41:43.96: IngressMonitor - Received BOOKMARK: oldResVer=12842 newResVer=12842 2025-01-13 02:41:43.96: IngressMonitor - start process kube event 2025-01-13 02:41:43.96: empty line received 2025-01-13 02:41:43.96: IngressMonitor - start process kube event 2025-01-13 02:41:44.10: ServiceMonitor - Received BOOKMARK: oldResVer=13219 newResVer=13219 2025-01-13 02:41:44.10: ServiceMonitor - start process kube event 2025-01-13 02:41:44.10: empty line received 2025-01-13 02:41:44.10: ServiceMonitor - start process kube event 2025-01-13 02:41:48.34: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:41:48.34: NamespaceMonitor - start process kube event 2025-01-13 02:41:48.34: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13183 2025-01-13 02:41:48.34: NamespaceMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:41:48.34: NamespaceMonitor - Connect Kube API result 0 2025-01-13 02:41:48.34: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:41:48.34: NamespaceMonitor - Start Watching request https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13183'})(timeout=120) 2025-01-13 02:41:48.34: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:41:48.34: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:41:48.34: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:41:48.34: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:41:48.35: NamespaceMonitor - Watches https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13183'}) 2025-01-13 02:41:50.09: EndPointMonitor - Received BOOKMARK: oldResVer=13147 newResVer=13147 2025-01-13 02:41:50.10: EndPointMonitor - start process kube event 2025-01-13 02:41:50.10: empty line received 2025-01-13 02:41:50.10: EndPointMonitor - start process kube event 2025-01-13 02:42:15.95: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:42:15.95: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:42:15.95: PodMonitor - start process kube event 2025-01-13 02:42:15.95: empty line received 2025-01-13 02:42:15.95: PodMonitor - start process kube event 2025-01-13 02:42:17.00: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:42:17.00: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:42:17.00: PodMonitor - start process kube event 2025-01-13 02:42:17.00: empty line received 2025-01-13 02:42:17.00: PodMonitor - start process kube event 2025-01-13 02:42:22.13: PodMonitor - Received BOOKMARK: oldResVer=13712 newResVer=13798 2025-01-13 02:42:22.13: PodMonitor - start process kube event 2025-01-13 02:42:22.13: empty line received 2025-01-13 02:42:22.13: PodMonitor - start process kube event 2025-01-13 02:42:29.59: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:42:29.59: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:42:29.59: PodMonitor - start process kube event 2025-01-13 02:42:29.59: empty line received 2025-01-13 02:42:29.59: PodMonitor - start process kube event 2025-01-13 02:42:37.58: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13265 newResVer=13265 2025-01-13 02:42:37.58: NetworkPolicyMonitor - start process kube event 2025-01-13 02:42:37.58: empty line received 2025-01-13 02:42:37.58: NetworkPolicyMonitor - start process kube event 2025-01-13 02:42:44.47: IngressMonitor - Received BOOKMARK: oldResVer=12842 newResVer=13773 2025-01-13 02:42:44.47: IngressMonitor - start process kube event 2025-01-13 02:42:44.47: empty line received 2025-01-13 02:42:44.47: IngressMonitor - start process kube event 2025-01-13 02:42:44.68: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:42:44.68: NetworkMonitor - start process kube event 2025-01-13 02:42:44.68: empty line received 2025-01-13 02:42:44.68: NetworkMonitor - start process kube event 2025-01-13 02:42:44.94: ServiceMonitor - Received BOOKMARK: oldResVer=13219 newResVer=13219 2025-01-13 02:42:44.94: ServiceMonitor - start process kube event 2025-01-13 02:42:44.94: empty line received 2025-01-13 02:42:44.94: ServiceMonitor - start process kube event 2025-01-13 02:42:50.38: EndPointMonitor - Received BOOKMARK: oldResVer=13147 newResVer=13147 2025-01-13 02:42:50.38: EndPointMonitor - start process kube event 2025-01-13 02:42:50.38: empty line received 2025-01-13 02:42:50.38: EndPointMonitor - start process kube event 2025-01-13 02:43:04.91: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:43:04.91: NetworkMonitor - start process kube event 2025-01-13 02:43:04.91: empty line received 2025-01-13 02:43:04.91: NetworkMonitor - start process kube event 2025-01-13 02:43:06.07: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=12977 2025-01-13 02:43:06.07: NetworkMonitor - start process kube event 2025-01-13 02:43:06.07: empty line received 2025-01-13 02:43:06.07: NetworkMonitor - start process kube event 2025-01-13 02:43:07.77: stop iteration NetworkMonitor 2025-01-13 02:43:07.77: NetworkMonitor - start process kube event 2025-01-13 02:43:07.77: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=12977 2025-01-13 02:43:07.77: NetworkMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:43:07.77: NetworkMonitor - Connect Kube API result 0 2025-01-13 02:43:07.77: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:43:07.77: NetworkMonitor - Start Watching request https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12977'})(timeout=120) 2025-01-13 02:43:07.78: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:43:07.78: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:43:07.78: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:43:07.78: NetworkMonitor - Watches https://10.0.0.27:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '12977'}) 2025-01-13 02:43:22.72: PodMonitor - Received BOOKMARK: oldResVer=13798 newResVer=13817 2025-01-13 02:43:22.72: PodMonitor - start process kube event 2025-01-13 02:43:22.72: empty line received 2025-01-13 02:43:22.72: PodMonitor - start process kube event 2025-01-13 02:43:22.86: ServiceMonitor - Received BOOKMARK: oldResVer=13219 newResVer=13219 2025-01-13 02:43:22.86: ServiceMonitor - start process kube event 2025-01-13 02:43:22.87: empty line received 2025-01-13 02:43:22.87: ServiceMonitor - start process kube event 2025-01-13 02:43:23.91: ServiceMonitor - Received BOOKMARK: oldResVer=13219 newResVer=13219 2025-01-13 02:43:23.91: ServiceMonitor - start process kube event 2025-01-13 02:43:23.91: empty line received 2025-01-13 02:43:23.91: ServiceMonitor - start process kube event 2025-01-13 02:43:25.08: stop iteration ServiceMonitor 2025-01-13 02:43:25.08: ServiceMonitor - start process kube event 2025-01-13 02:43:25.08: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13219 2025-01-13 02:43:25.08: ServiceMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:43:25.08: ServiceMonitor - Connect Kube API result 0 2025-01-13 02:43:25.08: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:43:25.08: ServiceMonitor - Start Watching request https://10.0.0.27:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13219'})(timeout=120) 2025-01-13 02:43:25.08: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:43:25.08: VncKubernetes - vnc_sync - Service start 2025-01-13 02:43:25.08: VncKubernetes - vnc_sync - Service done 2025-01-13 02:43:25.08: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:43:25.08: ServiceMonitor - Watches https://10.0.0.27:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13219'}) 2025-01-13 02:43:37.39: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13265 newResVer=13265 2025-01-13 02:43:37.39: NetworkPolicyMonitor - start process kube event 2025-01-13 02:43:37.39: empty line received 2025-01-13 02:43:37.40: NetworkPolicyMonitor - start process kube event 2025-01-13 02:43:44.59: IngressMonitor - Received BOOKMARK: oldResVer=13773 newResVer=13773 2025-01-13 02:43:44.59: IngressMonitor - start process kube event 2025-01-13 02:43:44.59: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:43:44.59: empty line received 2025-01-13 02:43:44.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:43:44.59: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:43:44.59: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:43:44.59: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:43:44.59: IngressMonitor - start process kube event 2025-01-13 02:43:48.35: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:43:48.35: NamespaceMonitor - start process kube event 2025-01-13 02:43:48.35: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13183 2025-01-13 02:43:48.35: NamespaceMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:43:48.35: NamespaceMonitor - Connect Kube API result 0 2025-01-13 02:43:48.35: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:43:48.35: NamespaceMonitor - Start Watching request https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13183'})(timeout=120) 2025-01-13 02:43:48.35: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:43:48.35: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:43:48.35: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:43:48.35: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:43:48.36: NamespaceMonitor - Watches https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13183'}) 2025-01-13 02:43:50.99: EndPointMonitor - Received BOOKMARK: oldResVer=13147 newResVer=13147 2025-01-13 02:43:50.99: EndPointMonitor - start process kube event 2025-01-13 02:43:50.99: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:43:50.99: empty line received 2025-01-13 02:43:50.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:43:50.99: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:43:50.99: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:43:50.99: EndPointMonitor - start process kube event 2025-01-13 02:44:07.13: NetworkMonitor - Received BOOKMARK: oldResVer=12977 newResVer=13885 2025-01-13 02:44:07.13: NetworkMonitor - start process kube event 2025-01-13 02:44:07.13: empty line received 2025-01-13 02:44:07.13: NetworkMonitor - start process kube event 2025-01-13 02:44:22.07: PodMonitor - Received BOOKMARK: oldResVer=13817 newResVer=13817 2025-01-13 02:44:22.07: PodMonitor - start process kube event 2025-01-13 02:44:22.07: PodMonitor - _schedule_vnc_sync 2025-01-13 02:44:22.07: empty line received 2025-01-13 02:44:22.07: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:44:22.07: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:44:22.07: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:44:22.07: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:44:22.07: PodMonitor - start process kube event 2025-01-13 02:44:37.37: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13265 newResVer=13265 2025-01-13 02:44:37.37: NetworkPolicyMonitor - start process kube event 2025-01-13 02:44:37.37: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:44:37.37: empty line received 2025-01-13 02:44:37.37: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:44:37.37: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:44:37.37: NetworkPolicyMonitor - start process kube event 2025-01-13 02:44:37.37: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:44:37.37: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:44:44.10: IngressMonitor - Received BOOKMARK: oldResVer=13773 newResVer=13773 2025-01-13 02:44:44.10: IngressMonitor - start process kube event 2025-01-13 02:44:44.10: empty line received 2025-01-13 02:44:44.10: IngressMonitor - start process kube event 2025-01-13 02:44:51.21: EndPointMonitor - Received BOOKMARK: oldResVer=13147 newResVer=13147 2025-01-13 02:44:51.21: EndPointMonitor - start process kube event 2025-01-13 02:44:51.21: empty line received 2025-01-13 02:44:51.21: EndPointMonitor - start process kube event 2025-01-13 02:45:07.84: NetworkMonitor - Received BOOKMARK: oldResVer=13885 newResVer=13885 2025-01-13 02:45:07.84: NetworkMonitor - start process kube event 2025-01-13 02:45:07.84: empty line received 2025-01-13 02:45:07.84: NetworkMonitor - start process kube event 2025-01-13 02:45:21.92: PodMonitor - Received BOOKMARK: oldResVer=13817 newResVer=13817 2025-01-13 02:45:21.92: PodMonitor - start process kube event 2025-01-13 02:45:21.92: empty line received 2025-01-13 02:45:21.92: PodMonitor - start process kube event 2025-01-13 02:45:25.08: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:45:25.08: ServiceMonitor - start process kube event 2025-01-13 02:45:25.08: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13219 2025-01-13 02:45:25.08: ServiceMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:45:25.08: ServiceMonitor - Connect Kube API result 0 2025-01-13 02:45:25.08: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:45:25.08: ServiceMonitor - Start Watching request https://10.0.0.27:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13219'})(timeout=120) 2025-01-13 02:45:25.08: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:45:25.08: VncKubernetes - vnc_sync - Service start 2025-01-13 02:45:25.08: VncKubernetes - vnc_sync - Service done 2025-01-13 02:45:25.08: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:45:25.09: ServiceMonitor - Watches https://10.0.0.27:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13219'}) 2025-01-13 02:45:35.89: EndPointMonitor - Received BOOKMARK: oldResVer=13147 newResVer=14038 2025-01-13 02:45:35.89: EndPointMonitor - start process kube event 2025-01-13 02:45:35.89: empty line received 2025-01-13 02:45:35.89: EndPointMonitor - start process kube event 2025-01-13 02:45:37.09: EndPointMonitor - Received BOOKMARK: oldResVer=14038 newResVer=14038 2025-01-13 02:45:37.09: EndPointMonitor - start process kube event 2025-01-13 02:45:37.09: empty line received 2025-01-13 02:45:37.09: EndPointMonitor - start process kube event 2025-01-13 02:45:37.37: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13265 newResVer=13265 2025-01-13 02:45:37.37: NetworkPolicyMonitor - start process kube event 2025-01-13 02:45:37.37: empty line received 2025-01-13 02:45:37.37: NetworkPolicyMonitor - start process kube event 2025-01-13 02:45:38.44: stop iteration EndPointMonitor 2025-01-13 02:45:38.44: EndPointMonitor - start process kube event 2025-01-13 02:45:38.44: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=14038 2025-01-13 02:45:38.44: EndPointMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:45:38.44: EndPointMonitor - Connect Kube API result 0 2025-01-13 02:45:38.44: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:45:38.44: EndPointMonitor - Start Watching request https://10.0.0.27:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '14038'})(timeout=120) 2025-01-13 02:45:38.44: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:45:38.44: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:45:38.44: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:45:38.45: EndPointMonitor - Watches https://10.0.0.27:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '14038'}) 2025-01-13 02:45:45.16: IngressMonitor - Received BOOKMARK: oldResVer=13773 newResVer=13773 2025-01-13 02:45:45.16: IngressMonitor - start process kube event 2025-01-13 02:45:45.16: empty line received 2025-01-13 02:45:45.16: IngressMonitor - start process kube event 2025-01-13 02:45:48.36: IOError NamespaceMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:45:48.36: NamespaceMonitor - start process kube event 2025-01-13 02:45:48.36: NamespaceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=13183 2025-01-13 02:45:48.36: NamespaceMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:45:48.36: NamespaceMonitor - Connect Kube API result 0 2025-01-13 02:45:48.36: NamespaceMonitor - _schedule_vnc_sync 2025-01-13 02:45:48.36: NamespaceMonitor - Start Watching request https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13183'})(timeout=120) 2025-01-13 02:45:48.36: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None) 2025-01-13 02:45:48.36: VncKubernetes - vnc_sync - Namespace start 2025-01-13 02:45:48.36: VncKubernetes - vnc_sync - Namespace done 2025-01-13 02:45:48.36: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:45:48.37: NamespaceMonitor - Watches https://10.0.0.27:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '13183'}) 2025-01-13 02:45:52.34: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:45:52.34: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:45:52.34: PodMonitor - start process kube event 2025-01-13 02:45:52.34: empty line received 2025-01-13 02:45:52.34: PodMonitor - start process kube event 2025-01-13 02:46:07.48: NetworkMonitor - Received BOOKMARK: oldResVer=13885 newResVer=13885 2025-01-13 02:46:07.48: NetworkMonitor - start process kube event 2025-01-13 02:46:07.48: empty line received 2025-01-13 02:46:07.48: NetworkMonitor - start process kube event 2025-01-13 02:46:07.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:46:07.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:46:07.55: PodMonitor - start process kube event 2025-01-13 02:46:07.55: empty line received 2025-01-13 02:46:07.55: PodMonitor - start process kube event 2025-01-13 02:46:22.42: PodMonitor - Received BOOKMARK: oldResVer=13817 newResVer=14126 2025-01-13 02:46:22.42: PodMonitor - start process kube event 2025-01-13 02:46:22.42: empty line received 2025-01-13 02:46:22.42: PodMonitor - start process kube event 2025-01-13 02:46:25.45: ServiceMonitor - Received BOOKMARK: oldResVer=13219 newResVer=14115 2025-01-13 02:46:25.45: ServiceMonitor - start process kube event 2025-01-13 02:46:25.45: empty line received 2025-01-13 02:46:25.45: ServiceMonitor - start process kube event 2025-01-13 02:46:37.70: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=13265 newResVer=14163 2025-01-13 02:46:37.70: NetworkPolicyMonitor - start process kube event 2025-01-13 02:46:37.70: empty line received 2025-01-13 02:46:37.70: NetworkPolicyMonitor - start process kube event 2025-01-13 02:46:45.02: IngressMonitor - Received BOOKMARK: oldResVer=13773 newResVer=13773 2025-01-13 02:46:45.02: IngressMonitor - start process kube event 2025-01-13 02:46:45.02: empty line received 2025-01-13 02:46:45.03: IngressMonitor - start process kube event 2025-01-13 02:46:48.27: NamespaceMonitor - Received BOOKMARK: oldResVer=13183 newResVer=14075 2025-01-13 02:46:48.27: NamespaceMonitor - start process kube event 2025-01-13 02:46:48.27: empty line received 2025-01-13 02:46:48.27: NamespaceMonitor - start process kube event 2025-01-13 02:47:07.65: NetworkMonitor - Received BOOKMARK: oldResVer=13885 newResVer=13885 2025-01-13 02:47:07.65: NetworkMonitor - start process kube event 2025-01-13 02:47:07.65: empty line received 2025-01-13 02:47:07.65: NetworkMonitor - start process kube event 2025-01-13 02:47:22.27: PodMonitor - Received BOOKMARK: oldResVer=14126 newResVer=14126 2025-01-13 02:47:22.27: PodMonitor - start process kube event 2025-01-13 02:47:22.27: empty line received 2025-01-13 02:47:22.27: PodMonitor - start process kube event 2025-01-13 02:47:23.56: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:47:23.56: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:47:23.56: PodMonitor - start process kube event 2025-01-13 02:47:23.56: empty line received 2025-01-13 02:47:23.56: PodMonitor - start process kube event 2025-01-13 02:47:25.38: ServiceMonitor - Received BOOKMARK: oldResVer=14115 newResVer=14115 2025-01-13 02:47:25.38: ServiceMonitor - start process kube event 2025-01-13 02:47:25.38: empty line received 2025-01-13 02:47:25.38: ServiceMonitor - start process kube event 2025-01-13 02:47:37.30: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=14163 newResVer=14163 2025-01-13 02:47:37.30: NetworkPolicyMonitor - start process kube event 2025-01-13 02:47:37.30: empty line received 2025-01-13 02:47:37.30: NetworkPolicyMonitor - start process kube event 2025-01-13 02:47:38.45: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:47:38.45: EndPointMonitor - start process kube event 2025-01-13 02:47:38.45: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=14038 2025-01-13 02:47:38.45: EndPointMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:47:38.45: EndPointMonitor - Connect Kube API result 0 2025-01-13 02:47:38.45: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:47:38.45: EndPointMonitor - Start Watching request https://10.0.0.27:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '14038'})(timeout=120) 2025-01-13 02:47:38.45: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:47:38.45: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:47:38.45: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:47:38.46: EndPointMonitor - Watches https://10.0.0.27:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '14038'}) 2025-01-13 02:47:45.45: IngressMonitor - Received BOOKMARK: oldResVer=13773 newResVer=13773 2025-01-13 02:47:45.45: IngressMonitor - start process kube event 2025-01-13 02:47:45.45: IngressMonitor - _schedule_vnc_sync 2025-01-13 02:47:45.45: empty line received 2025-01-13 02:47:45.45: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None) 2025-01-13 02:47:45.45: VncKubernetes - vnc_sync - Ingress start 2025-01-13 02:47:45.45: VncKubernetes - vnc_sync - Ingress done 2025-01-13 02:47:45.45: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:47:45.45: IngressMonitor - start process kube event 2025-01-13 02:47:48.11: NamespaceMonitor - Received BOOKMARK: oldResVer=14075 newResVer=14075 2025-01-13 02:47:48.11: NamespaceMonitor - start process kube event 2025-01-13 02:47:48.11: empty line received 2025-01-13 02:47:48.11: NamespaceMonitor - start process kube event 2025-01-13 02:48:06.97: NetworkMonitor - Received BOOKMARK: oldResVer=13885 newResVer=13885 2025-01-13 02:48:06.97: NetworkMonitor - start process kube event 2025-01-13 02:48:06.97: NetworkMonitor - _schedule_vnc_sync 2025-01-13 02:48:06.97: empty line received 2025-01-13 02:48:06.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None) 2025-01-13 02:48:06.97: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip 2025-01-13 02:48:06.97: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:48:06.97: NetworkMonitor - start process kube event 2025-01-13 02:48:21.98: PodMonitor - Received BOOKMARK: oldResVer=14126 newResVer=14234 2025-01-13 02:48:21.98: PodMonitor - start process kube event 2025-01-13 02:48:21.98: empty line received 2025-01-13 02:48:21.98: PodMonitor - start process kube event 2025-01-13 02:48:23.16: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:48:23.16: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:48:23.16: PodMonitor - start process kube event 2025-01-13 02:48:23.16: PodMonitor - _schedule_vnc_sync 2025-01-13 02:48:23.16: empty line received 2025-01-13 02:48:23.16: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None) 2025-01-13 02:48:23.16: VncKubernetes - vnc_sync - Pod start 2025-01-13 02:48:23.16: VncKubernetes - vnc_sync - Pod done 2025-01-13 02:48:23.16: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:48:23.16: PodMonitor - start process kube event 2025-01-13 02:48:25.15: ServiceMonitor - Received BOOKMARK: oldResVer=14115 newResVer=14115 2025-01-13 02:48:25.15: ServiceMonitor - start process kube event 2025-01-13 02:48:25.15: empty line received 2025-01-13 02:48:25.15: ServiceMonitor - start process kube event 2025-01-13 02:48:37.51: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=14163 newResVer=14163 2025-01-13 02:48:37.51: NetworkPolicyMonitor - start process kube event 2025-01-13 02:48:37.51: NetworkPolicyMonitor - _schedule_vnc_sync 2025-01-13 02:48:37.51: empty line received 2025-01-13 02:48:37.51: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None) 2025-01-13 02:48:37.51: VncKubernetes - vnc_sync - NetworkPolicy start 2025-01-13 02:48:37.51: NetworkPolicyMonitor - start process kube event 2025-01-13 02:48:37.51: VncKubernetes - vnc_sync - NetworkPolicy done 2025-01-13 02:48:37.51: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:48:37.55: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-v9xs7:a6645381-22f2-4954-bb72-7814da4204d5 2025-01-13 02:48:37.55: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-v9xs7 (hostNetwork=True) 2025-01-13 02:48:37.55: PodMonitor - start process kube event 2025-01-13 02:48:37.55: empty line received 2025-01-13 02:48:37.55: PodMonitor - start process kube event 2025-01-13 02:48:45.15: IngressMonitor - Received BOOKMARK: oldResVer=13773 newResVer=13773 2025-01-13 02:48:45.15: IngressMonitor - start process kube event 2025-01-13 02:48:45.15: empty line received 2025-01-13 02:48:45.15: IngressMonitor - start process kube event 2025-01-13 02:48:48.45: NamespaceMonitor - Received BOOKMARK: oldResVer=14075 newResVer=14075 2025-01-13 02:48:48.45: NamespaceMonitor - start process kube event 2025-01-13 02:48:48.45: empty line received 2025-01-13 02:48:48.45: NamespaceMonitor - start process kube event 2025-01-13 02:49:07.40: NetworkMonitor - Received BOOKMARK: oldResVer=13885 newResVer=13885 2025-01-13 02:49:07.40: NetworkMonitor - start process kube event 2025-01-13 02:49:07.40: empty line received 2025-01-13 02:49:07.40: NetworkMonitor - start process kube event 2025-01-13 02:49:22.17: PodMonitor - Received BOOKMARK: oldResVer=14234 newResVer=14340 2025-01-13 02:49:22.17: PodMonitor - start process kube event 2025-01-13 02:49:22.17: empty line received 2025-01-13 02:49:22.17: PodMonitor - start process kube event 2025-01-13 02:49:25.68: ServiceMonitor - Received BOOKMARK: oldResVer=14115 newResVer=14115 2025-01-13 02:49:25.68: ServiceMonitor - start process kube event 2025-01-13 02:49:25.68: ServiceMonitor - _schedule_vnc_sync 2025-01-13 02:49:25.68: empty line received 2025-01-13 02:49:25.68: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None) 2025-01-13 02:49:25.68: VncKubernetes - vnc_sync - Service start 2025-01-13 02:49:25.68: VncKubernetes - vnc_sync - Service done 2025-01-13 02:49:25.68: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:49:25.68: ServiceMonitor - start process kube event 2025-01-13 02:49:37.81: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=14163 newResVer=14163 2025-01-13 02:49:37.81: NetworkPolicyMonitor - start process kube event 2025-01-13 02:49:37.81: empty line received 2025-01-13 02:49:37.81: NetworkPolicyMonitor - start process kube event 2025-01-13 02:49:38.46: IOError EndPointMonitor - HTTPSConnectionPool(host='10.0.0.27', port=6443): Read timed out. 2025-01-13 02:49:38.46: EndPointMonitor - start process kube event 2025-01-13 02:49:38.46: EndPointMonitor - Re-registering event handler. resource_version_valid=True, resource_version=14038 2025-01-13 02:49:38.46: EndPointMonitor - Try to connect Kube API 10.0.0.27:6443 2025-01-13 02:49:38.46: EndPointMonitor - Connect Kube API result 0 2025-01-13 02:49:38.47: EndPointMonitor - _schedule_vnc_sync 2025-01-13 02:49:38.47: EndPointMonitor - Start Watching request https://10.0.0.27:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '14038'})(timeout=120) 2025-01-13 02:49:38.47: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None) 2025-01-13 02:49:38.47: VncKubernetes - vnc_sync - Endpoints - no handler - skip 2025-01-13 02:49:38.47: VncKubernetes - wait event (qsize=0 timeout=120) 2025-01-13 02:49:38.47: EndPointMonitor - Watches https://10.0.0.27:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '14038'}) 2025-01-13 02:49:45.45: IngressMonitor - Received BOOKMARK: oldResVer=13773 newResVer=13773 2025-01-13 02:49:45.45: IngressMonitor - start process kube event 2025-01-13 02:49:45.45: empty line received 2025-01-13 02:49:45.45: IngressMonitor - start process kube event 2025-01-13 02:49:47.96: NamespaceMonitor - Received BOOKMARK: oldResVer=14075 newResVer=14075 2025-01-13 02:49:47.96: NamespaceMonitor - start process kube event 2025-01-13 02:49:47.96: empty line received 2025-01-13 02:49:47.96: NamespaceMonitor - start process kube event