INFO: =================== Mon Feb 17 01:52:14 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: Waiting for cassandra 11/30
INFO: Cassandra is connected
/usr/local/lib/python3.6/site-packages/cfgm_common/vnc_kombu.py:10: MonkeyPatchWarning: Patching more than once will result in the union of all True parameters being patched
  gevent.monkey.patch_all()
02/17/2025 01:54:04.460 7f0e9de3e788 [contrail-kube-manager] [INFO]: SANDESH: CONNECT TO COLLECTOR: True
02/17/2025 01:54:04.835 7f0e9de3e788 [contrail-kube-manager] [INFO]: SANDESH: Logging: LEVEL: [SYS_INFO] -> [SYS_NOTICE]
2025-02-17 01:54:05.27: KubeMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:54:05.27: KubeMonitor - Connect Kube API result 0
2025-02-17 01:54:05.34: KubeMonitor - KubeMonitor init done: url=https://10.0.0.23:6443/api/v1
2025-02-17 01:54:05.35: NamespaceMonitor - KubeMonitor init done: url=https://10.0.0.23:6443/api/v1
2025-02-17 01:54:05.36: NetworkMonitor - KubeMonitor init done: url=https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1
2025-02-17 01:54:05.36: PodMonitor - KubeMonitor init done: url=https://10.0.0.23:6443/api/v1
2025-02-17 01:54:05.37: ServiceMonitor - KubeMonitor init done: url=https://10.0.0.23:6443/api/v1
2025-02-17 01:54:05.37: NetworkPolicyMonitor - KubeMonitor init done: url=https://10.0.0.23:6443/apis/networking.k8s.io/v1
2025-02-17 01:54:05.38: EndPointMonitor - KubeMonitor init done: url=https://10.0.0.23:6443/api/v1
2025-02-17 01:54:05.38: IngressMonitor - KubeMonitor init done: url=https://10.0.0.23:6443/apis/networking.k8s.io/v1
2025-02-17 01:54:05.38: VncKubernetes - vnc_connect starting
2025-02-17 01:54:05.41: VncKubernetes - vnc_connect failed: 
2025-02-17 01:54:08.45: VncKubernetes - vnc_connect failed: 
2025-02-17 01:54:11.51: VncKubernetes - vnc_connect failed: 
2025-02-17 01:54:14.54: VncKubernetes - vnc_connect done
2025-02-17 01:54:15.03: default-domain domain available.
2025-02-17 01:54:26.78: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:54:26.78: NamespaceMonitor - start process kube event
2025-02-17 01:54:26.78: NamespaceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-17 01:54:26.78: NamespaceMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:54:26.78: NetworkMonitor - start process kube event
2025-02-17 01:54:26.78: NetworkMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-17 01:54:26.78: NetworkMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:54:26.78: PodMonitor - start process kube event
2025-02-17 01:54:26.78: PodMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-17 01:54:26.78: PodMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:54:26.78: ServiceMonitor - start process kube event
2025-02-17 01:54:26.78: ServiceMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-17 01:54:26.78: ServiceMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:54:26.78: NetworkPolicyMonitor - start process kube event
2025-02-17 01:54:26.78: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-17 01:54:26.78: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:54:26.78: EndPointMonitor - start process kube event
2025-02-17 01:54:26.78: EndPointMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-17 01:54:26.78: EndPointMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:54:26.78: IngressMonitor - start process kube event
2025-02-17 01:54:26.78: IngressMonitor - Re-registering event handler. resource_version_valid=False, resource_version=None
2025-02-17 01:54:26.78: IngressMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:54:26.78: IngressMonitor - Connect Kube API result 0
2025-02-17 01:54:26.78: IngressMonitor - Start init url=https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses resource_version=None
2025-02-17 01:54:26.79: EndPointMonitor - Connect Kube API result 0
2025-02-17 01:54:26.79: EndPointMonitor - Start init url=https://10.0.0.23:6443/api/v1/endpoints resource_version=None
2025-02-17 01:54:26.79: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-17 01:54:26.79: NetworkPolicyMonitor - Start init url=https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies resource_version=None
2025-02-17 01:54:26.80: ServiceMonitor - Connect Kube API result 0
2025-02-17 01:54:26.80: ServiceMonitor - Start init url=https://10.0.0.23:6443/api/v1/services resource_version=None
2025-02-17 01:54:26.80: PodMonitor - Connect Kube API result 0
2025-02-17 01:54:26.80: PodMonitor - Start init url=https://10.0.0.23:6443/api/v1/pods resource_version=None
2025-02-17 01:54:26.80: NetworkMonitor - Connect Kube API result 0
2025-02-17 01:54:26.80: NamespaceMonitor - Connect Kube API result 0
2025-02-17 01:54:26.80: NamespaceMonitor - Start init url=https://10.0.0.23:6443/api/v1/namespaces resource_version=None
2025-02-17 01:54:26.85: IngressMonitor - Done init url=https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses, resource_version=9620
2025-02-17 01:54:26.85: IngressMonitor - _schedule_vnc_sync
2025-02-17 01:54:26.85: IngressMonitor - Start Watching request https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:54:26.86: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-17 01:54:26.86: VncKubernetes - vnc_sync - Ingress start
2025-02-17 01:54:26.86: VncKubernetes - vnc_sync - Ingress done
2025-02-17 01:54:26.86: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:54:26.87: NetworkPolicyMonitor - Done init url=https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies, resource_version=9620
2025-02-17 01:54:26.87: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-17 01:54:26.87: NetworkPolicyMonitor - Start Watching request https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:54:26.91: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-17 01:54:26.91: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-17 01:54:26.91: IngressMonitor - Watches https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:54:26.92: EndPointMonitor - Got ADDED Endpoints default:kubernetes:321dfc95-224d-405d-8635-92afdb6fe381
2025-02-17 01:54:26.92: NetworkPolicyMonitor - Watches https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:54:26.93: NamespaceMonitor - Got ADDED Namespace None:default:f86f561d-efdf-4679-8131-253b70c66900
2025-02-17 01:54:26.93: ServiceMonitor - Got ADDED Service default:kubernetes:6a1a17d3-5004-4199-ac71-c055e8580a93
2025-02-17 01:54:26.93: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-17 01:54:26.93: VncKubernetes - wait event (qsize=3 timeout=120)
2025-02-17 01:54:26.93: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Endpoints ns=default)
VncEndpoints - Got ADDED Endpoints default:kubernetes:321dfc95-224d-405d-8635-92afdb6fe381
2025-02-17 01:54:26.93: PodMonitor - Skipped ADDED Pod kube-system:config-zookeeper-47c66 (hostNetwork=True)
2025-02-17 01:54:26.94: EndPointMonitor - Got ADDED Endpoints kube-system:coredns:b24d863f-de2c-4dd5-aa9f-6c346aeb8176
2025-02-17 01:54:26.94: EndPointMonitor - Done init url=https://10.0.0.23:6443/api/v1/endpoints, resource_version=9620
2025-02-17 01:54:26.94: EndPointMonitor - _schedule_vnc_sync
2025-02-17 01:54:26.94: EndPointMonitor - Start Watching request https://10.0.0.23:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:54:26.95: ServiceMonitor - Got ADDED Service kube-system:coredns:7274c386-d504-450b-8e8d-da9d95f6cf75
2025-02-17 01:54:26.95: ServiceMonitor - Done init url=https://10.0.0.23:6443/api/v1/services, resource_version=9620
2025-02-17 01:54:26.95: ServiceMonitor - _schedule_vnc_sync
2025-02-17 01:54:26.95: ServiceMonitor - Start Watching request https://10.0.0.23:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:54:26.95: NamespaceMonitor - Got ADDED Namespace None:kube-node-lease:601e8eff-7f03-4f6c-bea9-53fd77a2f98d
2025-02-17 01:54:26.95: EndPointMonitor - Watches https://10.0.0.23:6443/api/v1/endpoints ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:54:26.95: PodMonitor - Skipped ADDED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:54:26.96: NetworkMonitor - Start init url=https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions resource_version=None
2025-02-17 01:54:26.96: ServiceMonitor - Watches https://10.0.0.23:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:54:26.96: VncKubernetes - wait event (qsize=7 timeout=120)
2025-02-17 01:54:26.96: VncKubernetes - Process event (name=default event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace default:f86f561d-efdf-4679-8131-253b70c66900
2025-02-17 01:54:26.96: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-8kq2b (hostNetwork=True)
2025-02-17 01:54:26.96: NamespaceMonitor - Got ADDED Namespace None:kube-public:3b91a303-f8c7-4c71-bb76-cdaceb40a9ac
2025-02-17 01:54:26.97: NamespaceMonitor - Got ADDED Namespace None:kube-system:9630ac55-659d-4938-812d-625daea6ee9d
2025-02-17 01:54:26.97: NamespaceMonitor - Done init url=https://10.0.0.23:6443/api/v1/namespaces, resource_version=9620
2025-02-17 01:54:26.97: NamespaceMonitor - _schedule_vnc_sync
2025-02-17 01:54:26.97: NamespaceMonitor - Start Watching request https://10.0.0.23:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:54:26.98: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-alarm-t2wjn (hostNetwork=True)
2025-02-17 01:54:26.98: NamespaceMonitor - Watches https://10.0.0.23:6443/api/v1/namespaces ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:54:26.98: NetworkMonitor - Done init url=https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions, resource_version=9626
2025-02-17 01:54:26.98: NetworkMonitor - _schedule_vnc_sync
2025-02-17 01:54:26.98: NetworkMonitor - Start Watching request https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})(timeout=120)
2025-02-17 01:54:26.98: PodMonitor - Skipped ADDED Pod kube-system:contrail-analytics-snmp-g6shn (hostNetwork=True)
2025-02-17 01:54:26.98: NetworkMonitor - Watches https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})
2025-02-17 01:54:26.99: PodMonitor - Skipped ADDED Pod kube-system:contrail-analyticsdb-mftjf (hostNetwork=True)
2025-02-17 01:54:26.99: PodMonitor - Skipped ADDED Pod kube-system:contrail-configdb-5nfvx (hostNetwork=True)
2025-02-17 01:54:27.00: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-config-96rr5 (hostNetwork=True)
2025-02-17 01:54:27.00: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-control-hkgpw (hostNetwork=True)
2025-02-17 01:54:27.01: PodMonitor - Skipped ADDED Pod kube-system:contrail-controller-webui-jfg4b (hostNetwork=True)
2025-02-17 01:54:27.01: PodMonitor - Skipped ADDED Pod kube-system:contrail-kube-manager-xxstm (hostNetwork=True)
2025-02-17 01:54:27.03: PodMonitor - Got ADDED Pod kube-system:coredns-77f7cc69db-c5vz6:89b657b5-2687-4936-9698-06f928cab41d
2025-02-17 01:54:27.04: PodMonitor - Got ADDED Pod kube-system:dns-autoscaler-595558c478-kdcg2:88aa1203-e9ca-42ca-93f3-630d0bff59e5
2025-02-17 01:54:27.04: PodMonitor - Skipped ADDED Pod kube-system:kube-apiserver-cn-jenkins-deploy-platform-k8s-manifests-136-1 (hostNetwork=True)
2025-02-17 01:54:27.05: PodMonitor - Skipped ADDED Pod kube-system:kube-controller-manager-cn-jenkins-deploy-platform-k8s-manifests-136-1 (hostNetwork=True)
2025-02-17 01:54:27.06: PodMonitor - Skipped ADDED Pod kube-system:kube-proxy-rhsgc (hostNetwork=True)
2025-02-17 01:54:27.06: PodMonitor - Skipped ADDED Pod kube-system:kube-scheduler-cn-jenkins-deploy-platform-k8s-manifests-136-1 (hostNetwork=True)
2025-02-17 01:54:27.06: PodMonitor - Skipped ADDED Pod kube-system:rabbitmq-cztlk (hostNetwork=True)
2025-02-17 01:54:27.07: PodMonitor - Skipped ADDED Pod kube-system:redis-nlf4b (hostNetwork=True)
2025-02-17 01:54:27.07: PodMonitor - Done init url=https://10.0.0.23:6443/api/v1/pods, resource_version=9620
2025-02-17 01:54:27.07: PodMonitor - _schedule_vnc_sync
2025-02-17 01:54:27.07: PodMonitor - Start Watching request https://10.0.0.23:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:54:27.07: PodMonitor - Watches https://10.0.0.23:6443/api/v1/pods ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:54:31.13: VncKubernetes - wait event (qsize=13 timeout=120)
2025-02-17 01:54:31.13: VncKubernetes - Process event (name=kubernetes event_type=ADDED kind=Service ns=default)
VncService - Got ADDED Service default:kubernetes:6a1a17d3-5004-4199-ac71-c055e8580a93
2025-02-17 01:54:32.97: VncKubernetes - wait event (qsize=12 timeout=120)
2025-02-17 01:54:32.97: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Endpoints ns=kube-system)
VncEndpoints - Got ADDED Endpoints kube-system:coredns:b24d863f-de2c-4dd5-aa9f-6c346aeb8176
2025-02-17 01:54:33.02: VncKubernetes - wait event (qsize=11 timeout=120)
2025-02-17 01:54:33.02: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-17 01:54:33.02: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-17 01:54:33.02: VncKubernetes - wait event (qsize=10 timeout=120)
2025-02-17 01:54:33.02: VncKubernetes - Process event (name=coredns event_type=ADDED kind=Service ns=kube-system)
VncService - Got ADDED Service kube-system:coredns:7274c386-d504-450b-8e8d-da9d95f6cf75
2025-02-17 01:54:35.81: VncKubernetes - wait event (qsize=9 timeout=120)
2025-02-17 01:54:35.81: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-17 01:54:35.81: VncKubernetes - vnc_sync - Service start
2025-02-17 01:54:35.81: VncKubernetes - vnc_sync - Service done
2025-02-17 01:54:35.81: VncKubernetes - wait event (qsize=8 timeout=120)
2025-02-17 01:54:35.81: VncKubernetes - Process event (name=kube-node-lease event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-node-lease:601e8eff-7f03-4f6c-bea9-53fd77a2f98d
2025-02-17 01:54:38.68: VncKubernetes - wait event (qsize=7 timeout=120)
2025-02-17 01:54:38.68: VncKubernetes - Process event (name=kube-public event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-public:3b91a303-f8c7-4c71-bb76-cdaceb40a9ac
2025-02-17 01:54:41.38: VncKubernetes - wait event (qsize=6 timeout=120)
2025-02-17 01:54:41.38: VncKubernetes - Process event (name=kube-system event_type=ADDED kind=Namespace ns=None)
VncNamespace - Got ADDED Namespace kube-system:9630ac55-659d-4938-812d-625daea6ee9d
2025-02-17 01:54:43.78: VncKubernetes - wait event (qsize=5 timeout=120)
2025-02-17 01:54:43.78: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-17 01:54:43.78: VncKubernetes - vnc_sync - Namespace start
2025-02-17 01:54:43.78: VncKubernetes - vnc_sync - Namespace done
2025-02-17 01:54:43.78: VncKubernetes - wait event (qsize=4 timeout=120)
2025-02-17 01:54:43.78: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-17 01:54:43.78: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-17 01:54:43.78: VncKubernetes - wait event (qsize=3 timeout=120)
2025-02-17 01:54:43.78: VncKubernetes - Process event (name=coredns-77f7cc69db-c5vz6 event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:coredns-77f7cc69db-c5vz6:89b657b5-2687-4936-9698-06f928cab41d
2025-02-17 01:54:44.84: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:54:44.84: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:54:44.84: PodMonitor - start process kube event
2025-02-17 01:54:44.84: empty line received
2025-02-17 01:54:44.84: PodMonitor - start process kube event
2025-02-17 01:54:45.49: PodMonitor - Received MODIFIED Pod kube-system:coredns-77f7cc69db-c5vz6:89b657b5-2687-4936-9698-06f928cab41d
2025-02-17 01:54:45.49: PodMonitor - Got MODIFIED Pod kube-system:coredns-77f7cc69db-c5vz6:89b657b5-2687-4936-9698-06f928cab41d
2025-02-17 01:54:45.49: PodMonitor - start process kube event
2025-02-17 01:54:45.49: empty line received
2025-02-17 01:54:45.49: VncKubernetes - wait event (qsize=3 timeout=120)
2025-02-17 01:54:45.49: VncKubernetes - Process event (name=dns-autoscaler-595558c478-kdcg2 event_type=ADDED kind=Pod ns=kube-system)
VncPod - Got ADDED Pod kube-system:dns-autoscaler-595558c478-kdcg2:88aa1203-e9ca-42ca-93f3-630d0bff59e5
2025-02-17 01:54:45.50: PodMonitor - start process kube event
2025-02-17 01:54:46.88: PodMonitor - Received MODIFIED Pod kube-system:dns-autoscaler-595558c478-kdcg2:88aa1203-e9ca-42ca-93f3-630d0bff59e5
2025-02-17 01:54:46.88: PodMonitor - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-kdcg2:88aa1203-e9ca-42ca-93f3-630d0bff59e5
2025-02-17 01:54:46.88: PodMonitor - start process kube event
2025-02-17 01:54:46.88: empty line received
2025-02-17 01:54:46.88: VncKubernetes - wait event (qsize=3 timeout=120)
2025-02-17 01:54:46.88: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-17 01:54:46.88: VncKubernetes - vnc_sync - Pod start
2025-02-17 01:54:46.88: VncKubernetes - vnc_sync - Pod done
2025-02-17 01:54:46.88: VncKubernetes - wait event (qsize=2 timeout=120)
2025-02-17 01:54:46.88: VncKubernetes - Process event (name=coredns-77f7cc69db-c5vz6 event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:coredns-77f7cc69db-c5vz6:89b657b5-2687-4936-9698-06f928cab41d
2025-02-17 01:54:46.88: PodMonitor - start process kube event
2025-02-17 01:54:46.98: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-17 01:54:46.98: VncKubernetes - Process event (name=dns-autoscaler-595558c478-kdcg2 event_type=MODIFIED kind=Pod ns=kube-system)
VncPod - Got MODIFIED Pod kube-system:dns-autoscaler-595558c478-kdcg2:88aa1203-e9ca-42ca-93f3-630d0bff59e5
2025-02-17 01:54:47.07: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:54:55.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:54:55.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:54:55.68: PodMonitor - start process kube event
2025-02-17 01:54:55.68: empty line received
2025-02-17 01:54:55.68: PodMonitor - start process kube event
2025-02-17 01:54:56.16: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:54:56.16: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:54:56.16: PodMonitor - start process kube event
2025-02-17 01:54:56.16: empty line received
2025-02-17 01:54:56.16: PodMonitor - start process kube event
2025-02-17 01:55:26.99: NamespaceMonitor - Received BOOKMARK: oldResVer=9620 newResVer=9631
2025-02-17 01:55:26.99: NamespaceMonitor - start process kube event
2025-02-17 01:55:26.99: empty line received
2025-02-17 01:55:26.99: NamespaceMonitor - start process kube event
2025-02-17 01:55:28.09: PodMonitor - Received BOOKMARK: oldResVer=9620 newResVer=9670
2025-02-17 01:55:28.09: PodMonitor - start process kube event
2025-02-17 01:55:28.09: empty line received
2025-02-17 01:55:28.09: PodMonitor - start process kube event
2025-02-17 01:55:37.18: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:55:37.18: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:55:37.18: PodMonitor - start process kube event
2025-02-17 01:55:37.18: empty line received
2025-02-17 01:55:37.18: PodMonitor - start process kube event
2025-02-17 01:55:38.23: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:55:38.23: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:55:38.23: PodMonitor - start process kube event
2025-02-17 01:55:38.23: empty line received
2025-02-17 01:55:38.23: PodMonitor - start process kube event
2025-02-17 01:55:56.67: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:55:56.67: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:55:56.67: PodMonitor - start process kube event
2025-02-17 01:55:56.67: empty line received
2025-02-17 01:55:56.67: PodMonitor - start process kube event
2025-02-17 01:56:08.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:56:08.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:56:08.68: PodMonitor - start process kube event
2025-02-17 01:56:08.68: empty line received
2025-02-17 01:56:08.68: PodMonitor - start process kube event
2025-02-17 01:56:24.32: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:56:24.32: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:56:24.32: PodMonitor - start process kube event
2025-02-17 01:56:24.32: empty line received
2025-02-17 01:56:24.32: PodMonitor - start process kube event
2025-02-17 01:56:26.27: EndPointMonitor - Received BOOKMARK: oldResVer=9620 newResVer=9782
2025-02-17 01:56:26.27: EndPointMonitor - start process kube event
2025-02-17 01:56:26.27: empty line received
2025-02-17 01:56:26.27: EndPointMonitor - start process kube event
2025-02-17 01:56:26.92: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 01:56:26.92: IngressMonitor - start process kube event
2025-02-17 01:56:26.92: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 01:56:26.92: IngressMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:56:26.92: IngressMonitor - Connect Kube API result 0
2025-02-17 01:56:26.92: IngressMonitor - _schedule_vnc_sync
2025-02-17 01:56:26.92: IngressMonitor - Start Watching request https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:56:26.92: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-17 01:56:26.92: VncKubernetes - vnc_sync - Ingress start
2025-02-17 01:56:26.92: VncKubernetes - vnc_sync - Ingress done
2025-02-17 01:56:26.92: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:56:26.93: IngressMonitor - Watches https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:56:26.93: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 01:56:26.93: NetworkPolicyMonitor - start process kube event
2025-02-17 01:56:26.93: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 01:56:26.93: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:56:26.93: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-17 01:56:26.93: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-17 01:56:26.93: NetworkPolicyMonitor - Start Watching request https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:56:26.93: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-17 01:56:26.93: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-17 01:56:26.93: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-17 01:56:26.93: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:56:26.93: NetworkPolicyMonitor - Watches https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:56:26.96: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 01:56:26.96: ServiceMonitor - start process kube event
2025-02-17 01:56:26.96: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 01:56:26.96: ServiceMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:56:26.96: ServiceMonitor - Connect Kube API result 0
2025-02-17 01:56:26.96: ServiceMonitor - _schedule_vnc_sync
2025-02-17 01:56:26.96: ServiceMonitor - Start Watching request https://10.0.0.23:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:56:26.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-17 01:56:26.96: VncKubernetes - vnc_sync - Service start
2025-02-17 01:56:26.96: VncKubernetes - vnc_sync - Service done
2025-02-17 01:56:26.96: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:56:26.97: ServiceMonitor - Watches https://10.0.0.23:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:56:26.98: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 01:56:26.99: NetworkMonitor - start process kube event
2025-02-17 01:56:26.99: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9626
2025-02-17 01:56:26.99: NetworkMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:56:26.99: NetworkMonitor - Connect Kube API result 0
2025-02-17 01:56:26.99: NetworkMonitor - _schedule_vnc_sync
2025-02-17 01:56:26.99: NetworkMonitor - Start Watching request https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})(timeout=120)
2025-02-17 01:56:26.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-17 01:56:26.99: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-17 01:56:26.99: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:56:26.99: NetworkMonitor - Watches https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})
2025-02-17 01:56:27.24: NamespaceMonitor - Received BOOKMARK: oldResVer=9631 newResVer=9631
2025-02-17 01:56:27.24: NamespaceMonitor - start process kube event
2025-02-17 01:56:27.24: empty line received
2025-02-17 01:56:27.24: NamespaceMonitor - start process kube event
2025-02-17 01:56:28.36: PodMonitor - Received BOOKMARK: oldResVer=9670 newResVer=9802
2025-02-17 01:56:28.36: PodMonitor - start process kube event
2025-02-17 01:56:28.36: empty line received
2025-02-17 01:56:28.36: PodMonitor - start process kube event
2025-02-17 01:57:24.69: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:57:24.69: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:57:24.69: PodMonitor - start process kube event
2025-02-17 01:57:24.69: empty line received
2025-02-17 01:57:24.69: PodMonitor - start process kube event
2025-02-17 01:57:26.35: EndPointMonitor - Received BOOKMARK: oldResVer=9782 newResVer=9782
2025-02-17 01:57:26.35: EndPointMonitor - start process kube event
2025-02-17 01:57:26.35: empty line received
2025-02-17 01:57:26.35: EndPointMonitor - start process kube event
2025-02-17 01:57:27.40: NamespaceMonitor - Received BOOKMARK: oldResVer=9631 newResVer=9631
2025-02-17 01:57:27.40: NamespaceMonitor - start process kube event
2025-02-17 01:57:27.40: empty line received
2025-02-17 01:57:27.40: NamespaceMonitor - start process kube event
2025-02-17 01:57:29.16: PodMonitor - Received BOOKMARK: oldResVer=9802 newResVer=9894
2025-02-17 01:57:29.16: PodMonitor - start process kube event
2025-02-17 01:57:29.16: empty line received
2025-02-17 01:57:29.16: PodMonitor - start process kube event
2025-02-17 01:57:37.69: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:57:37.69: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:57:37.69: PodMonitor - start process kube event
2025-02-17 01:57:37.69: empty line received
2025-02-17 01:57:37.69: PodMonitor - start process kube event
2025-02-17 01:58:06.66: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:58:06.66: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:58:06.66: PodMonitor - start process kube event
2025-02-17 01:58:06.66: empty line received
2025-02-17 01:58:06.66: PodMonitor - start process kube event
2025-02-17 01:58:20.04: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:58:20.04: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:58:20.05: PodMonitor - start process kube event
2025-02-17 01:58:20.05: empty line received
2025-02-17 01:58:20.05: PodMonitor - start process kube event
2025-02-17 01:58:21.10: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:58:21.10: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:58:21.10: PodMonitor - start process kube event
2025-02-17 01:58:21.10: empty line received
2025-02-17 01:58:21.10: PodMonitor - start process kube event
2025-02-17 01:58:26.74: EndPointMonitor - Received BOOKMARK: oldResVer=9782 newResVer=9782
2025-02-17 01:58:26.74: EndPointMonitor - start process kube event
2025-02-17 01:58:26.74: empty line received
2025-02-17 01:58:26.74: EndPointMonitor - start process kube event
2025-02-17 01:58:26.93: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 01:58:26.93: IngressMonitor - start process kube event
2025-02-17 01:58:26.93: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 01:58:26.93: IngressMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:58:26.93: IngressMonitor - Connect Kube API result 0
2025-02-17 01:58:26.93: IngressMonitor - _schedule_vnc_sync
2025-02-17 01:58:26.93: IngressMonitor - Start Watching request https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:58:26.93: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-17 01:58:26.93: VncKubernetes - vnc_sync - Ingress start
2025-02-17 01:58:26.93: VncKubernetes - vnc_sync - Ingress done
2025-02-17 01:58:26.93: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:58:26.94: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 01:58:26.94: NetworkPolicyMonitor - start process kube event
2025-02-17 01:58:26.94: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 01:58:26.94: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:58:26.94: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-17 01:58:26.94: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-17 01:58:26.94: NetworkPolicyMonitor - Start Watching request https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:58:26.94: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-17 01:58:26.94: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-17 01:58:26.94: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-17 01:58:26.94: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:58:26.95: IngressMonitor - Watches https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:58:26.95: NetworkPolicyMonitor - Watches https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:58:26.97: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 01:58:26.97: ServiceMonitor - start process kube event
2025-02-17 01:58:26.97: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 01:58:26.97: ServiceMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:58:26.97: ServiceMonitor - Connect Kube API result 0
2025-02-17 01:58:26.97: ServiceMonitor - _schedule_vnc_sync
2025-02-17 01:58:26.97: ServiceMonitor - Start Watching request https://10.0.0.23:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 01:58:26.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-17 01:58:26.97: VncKubernetes - vnc_sync - Service start
2025-02-17 01:58:26.97: VncKubernetes - vnc_sync - Service done
2025-02-17 01:58:26.97: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:58:26.98: ServiceMonitor - Watches https://10.0.0.23:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 01:58:26.99: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 01:58:26.99: NetworkMonitor - start process kube event
2025-02-17 01:58:26.99: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9626
2025-02-17 01:58:26.99: NetworkMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 01:58:27.00: NetworkMonitor - Connect Kube API result 0
2025-02-17 01:58:27.00: NetworkMonitor - _schedule_vnc_sync
2025-02-17 01:58:27.00: NetworkMonitor - Start Watching request https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})(timeout=120)
2025-02-17 01:58:27.00: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-17 01:58:27.00: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-17 01:58:27.00: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:58:27.00: NetworkMonitor - Watches https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})
2025-02-17 01:58:27.18: NamespaceMonitor - Received BOOKMARK: oldResVer=9631 newResVer=9631
2025-02-17 01:58:27.18: NamespaceMonitor - start process kube event
2025-02-17 01:58:27.18: NamespaceMonitor - _schedule_vnc_sync
2025-02-17 01:58:27.18: empty line received
2025-02-17 01:58:27.18: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-17 01:58:27.18: VncKubernetes - vnc_sync - Namespace start
2025-02-17 01:58:27.18: VncKubernetes - vnc_sync - Namespace done
2025-02-17 01:58:27.18: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:58:27.18: NamespaceMonitor - start process kube event
2025-02-17 01:58:29.85: PodMonitor - Received BOOKMARK: oldResVer=9894 newResVer=9981
2025-02-17 01:58:29.85: PodMonitor - start process kube event
2025-02-17 01:58:29.85: PodMonitor - _schedule_vnc_sync
2025-02-17 01:58:29.85: empty line received
2025-02-17 01:58:29.85: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-17 01:58:29.85: VncKubernetes - vnc_sync - Pod start
2025-02-17 01:58:29.85: VncKubernetes - vnc_sync - Pod done
2025-02-17 01:58:29.85: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:58:29.85: PodMonitor - start process kube event
2025-02-17 01:58:35.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:58:35.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:58:35.68: PodMonitor - start process kube event
2025-02-17 01:58:35.68: empty line received
2025-02-17 01:58:35.68: PodMonitor - start process kube event
2025-02-17 01:59:06.22: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:59:06.22: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:59:06.22: PodMonitor - start process kube event
2025-02-17 01:59:06.22: empty line received
2025-02-17 01:59:06.22: PodMonitor - start process kube event
2025-02-17 01:59:17.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 01:59:17.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 01:59:17.68: PodMonitor - start process kube event
2025-02-17 01:59:17.68: empty line received
2025-02-17 01:59:17.68: PodMonitor - start process kube event
2025-02-17 01:59:26.66: EndPointMonitor - Received BOOKMARK: oldResVer=9782 newResVer=9782
2025-02-17 01:59:26.66: EndPointMonitor - start process kube event
2025-02-17 01:59:26.66: EndPointMonitor - _schedule_vnc_sync
2025-02-17 01:59:26.66: empty line received
2025-02-17 01:59:26.66: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-17 01:59:26.66: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-17 01:59:26.66: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 01:59:26.66: EndPointMonitor - start process kube event
2025-02-17 01:59:27.05: NamespaceMonitor - Received BOOKMARK: oldResVer=9631 newResVer=9631
2025-02-17 01:59:27.05: NamespaceMonitor - start process kube event
2025-02-17 01:59:27.05: empty line received
2025-02-17 01:59:27.05: NamespaceMonitor - start process kube event
2025-02-17 01:59:29.98: PodMonitor - Received BOOKMARK: oldResVer=9981 newResVer=10068
2025-02-17 01:59:29.98: PodMonitor - start process kube event
2025-02-17 01:59:29.98: empty line received
2025-02-17 01:59:29.98: PodMonitor - start process kube event
2025-02-17 02:00:26.15: EndPointMonitor - Received BOOKMARK: oldResVer=9782 newResVer=9782
2025-02-17 02:00:26.15: EndPointMonitor - start process kube event
2025-02-17 02:00:26.15: empty line received
2025-02-17 02:00:26.15: EndPointMonitor - start process kube event
2025-02-17 02:00:26.95: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 02:00:26.95: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 02:00:26.95: IngressMonitor - start process kube event
2025-02-17 02:00:26.95: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 02:00:26.95: IngressMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 02:00:26.95: NetworkPolicyMonitor - start process kube event
2025-02-17 02:00:26.95: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 02:00:26.95: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 02:00:26.95: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-17 02:00:26.95: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-17 02:00:26.95: NetworkPolicyMonitor - Start Watching request https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 02:00:26.95: IngressMonitor - Connect Kube API result 0
2025-02-17 02:00:26.95: IngressMonitor - _schedule_vnc_sync
2025-02-17 02:00:26.95: IngressMonitor - Start Watching request https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 02:00:26.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-17 02:00:26.96: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-17 02:00:26.96: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-17 02:00:26.96: VncKubernetes - wait event (qsize=1 timeout=120)
2025-02-17 02:00:26.96: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-17 02:00:26.96: VncKubernetes - vnc_sync - Ingress start
2025-02-17 02:00:26.96: VncKubernetes - vnc_sync - Ingress done
2025-02-17 02:00:26.96: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:00:26.96: IngressMonitor - Watches https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 02:00:26.96: NetworkPolicyMonitor - Watches https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 02:00:26.98: IOError ServiceMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 02:00:26.98: ServiceMonitor - start process kube event
2025-02-17 02:00:26.98: ServiceMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 02:00:26.98: ServiceMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 02:00:26.98: ServiceMonitor - Connect Kube API result 0
2025-02-17 02:00:26.98: ServiceMonitor - _schedule_vnc_sync
2025-02-17 02:00:26.98: ServiceMonitor - Start Watching request https://10.0.0.23:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 02:00:26.98: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-17 02:00:26.98: VncKubernetes - vnc_sync - Service start
2025-02-17 02:00:26.98: VncKubernetes - vnc_sync - Service done
2025-02-17 02:00:26.98: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:00:26.99: ServiceMonitor - Watches https://10.0.0.23:6443/api/v1/services ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 02:00:27.01: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 02:00:27.01: NetworkMonitor - start process kube event
2025-02-17 02:00:27.01: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9626
2025-02-17 02:00:27.01: NetworkMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 02:00:27.01: NetworkMonitor - Connect Kube API result 0
2025-02-17 02:00:27.01: NetworkMonitor - _schedule_vnc_sync
2025-02-17 02:00:27.01: NetworkMonitor - Start Watching request https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})(timeout=120)
2025-02-17 02:00:27.01: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-17 02:00:27.01: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-17 02:00:27.01: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:00:27.01: NetworkMonitor - Watches https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})
2025-02-17 02:00:27.21: NamespaceMonitor - Received BOOKMARK: oldResVer=9631 newResVer=9631
2025-02-17 02:00:27.21: NamespaceMonitor - start process kube event
2025-02-17 02:00:27.21: empty line received
2025-02-17 02:00:27.21: NamespaceMonitor - start process kube event
2025-02-17 02:00:29.71: PodMonitor - Received BOOKMARK: oldResVer=10068 newResVer=10068
2025-02-17 02:00:29.71: PodMonitor - start process kube event
2025-02-17 02:00:29.71: empty line received
2025-02-17 02:00:29.71: PodMonitor - start process kube event
2025-02-17 02:00:38.29: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:00:38.29: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:00:38.29: PodMonitor - start process kube event
2025-02-17 02:00:38.29: empty line received
2025-02-17 02:00:38.29: PodMonitor - start process kube event
2025-02-17 02:01:26.48: EndPointMonitor - Received BOOKMARK: oldResVer=9782 newResVer=9782
2025-02-17 02:01:26.48: EndPointMonitor - start process kube event
2025-02-17 02:01:26.48: empty line received
2025-02-17 02:01:26.48: EndPointMonitor - start process kube event
2025-02-17 02:01:26.93: ServiceMonitor - Received BOOKMARK: oldResVer=9620 newResVer=10184
2025-02-17 02:01:26.93: ServiceMonitor - start process kube event
2025-02-17 02:01:26.93: empty line received
2025-02-17 02:01:26.93: ServiceMonitor - start process kube event
2025-02-17 02:01:27.85: NamespaceMonitor - Received BOOKMARK: oldResVer=9631 newResVer=9631
2025-02-17 02:01:27.85: NamespaceMonitor - start process kube event
2025-02-17 02:01:27.85: empty line received
2025-02-17 02:01:27.85: NamespaceMonitor - start process kube event
2025-02-17 02:01:30.08: PodMonitor - Received BOOKMARK: oldResVer=10068 newResVer=10185
2025-02-17 02:01:30.08: PodMonitor - start process kube event
2025-02-17 02:01:30.08: empty line received
2025-02-17 02:01:30.08: PodMonitor - start process kube event
2025-02-17 02:01:38.69: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:01:38.69: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:01:38.69: PodMonitor - start process kube event
2025-02-17 02:01:38.69: empty line received
2025-02-17 02:01:38.69: PodMonitor - start process kube event
2025-02-17 02:01:50.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:01:50.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:01:50.68: PodMonitor - start process kube event
2025-02-17 02:01:50.68: empty line received
2025-02-17 02:01:50.68: PodMonitor - start process kube event
2025-02-17 02:02:26.67: ServiceMonitor - Received BOOKMARK: oldResVer=10184 newResVer=10184
2025-02-17 02:02:26.67: ServiceMonitor - start process kube event
2025-02-17 02:02:26.67: empty line received
2025-02-17 02:02:26.67: ServiceMonitor - start process kube event
2025-02-17 02:02:26.90: EndPointMonitor - Received BOOKMARK: oldResVer=9782 newResVer=9782
2025-02-17 02:02:26.90: EndPointMonitor - start process kube event
2025-02-17 02:02:26.90: empty line received
2025-02-17 02:02:26.90: EndPointMonitor - start process kube event
2025-02-17 02:02:26.96: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 02:02:26.96: IngressMonitor - start process kube event
2025-02-17 02:02:26.96: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 02:02:26.96: IngressMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 02:02:26.96: IngressMonitor - Connect Kube API result 0
2025-02-17 02:02:26.96: IngressMonitor - _schedule_vnc_sync
2025-02-17 02:02:26.96: IngressMonitor - Start Watching request https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 02:02:26.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-17 02:02:26.97: VncKubernetes - vnc_sync - Ingress start
2025-02-17 02:02:26.97: VncKubernetes - vnc_sync - Ingress done
2025-02-17 02:02:26.97: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:02:26.97: IOError NetworkPolicyMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 02:02:26.97: NetworkPolicyMonitor - start process kube event
2025-02-17 02:02:26.97: NetworkPolicyMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 02:02:26.97: NetworkPolicyMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 02:02:26.97: NetworkPolicyMonitor - Connect Kube API result 0
2025-02-17 02:02:26.97: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-17 02:02:26.97: NetworkPolicyMonitor - Start Watching request https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 02:02:26.97: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-17 02:02:26.97: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-17 02:02:26.98: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-17 02:02:26.98: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:02:26.98: NetworkPolicyMonitor - Watches https://10.0.0.23:6443/apis/networking.k8s.io/v1/networkpolicies ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 02:02:26.98: IngressMonitor - Watches https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 02:02:27.02: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 02:02:27.02: NetworkMonitor - start process kube event
2025-02-17 02:02:27.02: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9626
2025-02-17 02:02:27.02: NetworkMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 02:02:27.02: NetworkMonitor - Connect Kube API result 0
2025-02-17 02:02:27.02: NetworkMonitor - _schedule_vnc_sync
2025-02-17 02:02:27.02: NetworkMonitor - Start Watching request https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})(timeout=120)
2025-02-17 02:02:27.02: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-17 02:02:27.02: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-17 02:02:27.02: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:02:27.02: NetworkMonitor - Watches https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})
2025-02-17 02:02:27.17: NamespaceMonitor - Received BOOKMARK: oldResVer=9631 newResVer=9631
2025-02-17 02:02:27.17: NamespaceMonitor - start process kube event
2025-02-17 02:02:27.17: empty line received
2025-02-17 02:02:27.17: NamespaceMonitor - start process kube event
2025-02-17 02:02:30.73: PodMonitor - Received BOOKMARK: oldResVer=10185 newResVer=10293
2025-02-17 02:02:30.73: PodMonitor - start process kube event
2025-02-17 02:02:30.73: PodMonitor - _schedule_vnc_sync
2025-02-17 02:02:30.73: empty line received
2025-02-17 02:02:30.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-17 02:02:30.73: VncKubernetes - vnc_sync - Pod start
2025-02-17 02:02:30.73: VncKubernetes - vnc_sync - Pod done
2025-02-17 02:02:30.73: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:02:30.73: PodMonitor - start process kube event
2025-02-17 02:03:23.13: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:03:23.13: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:03:23.13: PodMonitor - start process kube event
2025-02-17 02:03:23.13: empty line received
2025-02-17 02:03:23.13: PodMonitor - start process kube event
2025-02-17 02:03:24.17: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:03:24.17: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:03:24.17: PodMonitor - start process kube event
2025-02-17 02:03:24.17: empty line received
2025-02-17 02:03:24.17: PodMonitor - start process kube event
2025-02-17 02:03:26.29: EndPointMonitor - Received BOOKMARK: oldResVer=9782 newResVer=9782
2025-02-17 02:03:26.29: EndPointMonitor - start process kube event
2025-02-17 02:03:26.29: empty line received
2025-02-17 02:03:26.29: EndPointMonitor - start process kube event
2025-02-17 02:03:26.55: ServiceMonitor - Received BOOKMARK: oldResVer=10184 newResVer=10184
2025-02-17 02:03:26.55: ServiceMonitor - start process kube event
2025-02-17 02:03:26.55: empty line received
2025-02-17 02:03:26.55: ServiceMonitor - start process kube event
2025-02-17 02:03:26.71: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=9620 newResVer=10408
2025-02-17 02:03:26.71: NetworkPolicyMonitor - start process kube event
2025-02-17 02:03:26.71: empty line received
2025-02-17 02:03:26.71: NetworkPolicyMonitor - start process kube event
2025-02-17 02:03:27.59: NamespaceMonitor - Received BOOKMARK: oldResVer=9631 newResVer=9631
2025-02-17 02:03:27.59: NamespaceMonitor - start process kube event
2025-02-17 02:03:27.59: NamespaceMonitor - _schedule_vnc_sync
2025-02-17 02:03:27.59: empty line received
2025-02-17 02:03:27.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-17 02:03:27.59: VncKubernetes - vnc_sync - Namespace start
2025-02-17 02:03:27.59: VncKubernetes - vnc_sync - Namespace done
2025-02-17 02:03:27.59: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:03:27.59: NamespaceMonitor - start process kube event
2025-02-17 02:03:30.47: PodMonitor - Received BOOKMARK: oldResVer=10293 newResVer=10429
2025-02-17 02:03:30.47: PodMonitor - start process kube event
2025-02-17 02:03:30.47: empty line received
2025-02-17 02:03:30.47: PodMonitor - start process kube event
2025-02-17 02:04:26.10: EndPointMonitor - Received BOOKMARK: oldResVer=9782 newResVer=9782
2025-02-17 02:04:26.10: EndPointMonitor - start process kube event
2025-02-17 02:04:26.10: EndPointMonitor - _schedule_vnc_sync
2025-02-17 02:04:26.10: empty line received
2025-02-17 02:04:26.10: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-17 02:04:26.10: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-17 02:04:26.10: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:04:26.10: EndPointMonitor - start process kube event
2025-02-17 02:04:26.25: ServiceMonitor - Received BOOKMARK: oldResVer=10184 newResVer=10184
2025-02-17 02:04:26.25: ServiceMonitor - start process kube event
2025-02-17 02:04:26.25: empty line received
2025-02-17 02:04:26.25: ServiceMonitor - start process kube event
2025-02-17 02:04:26.43: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10408 newResVer=10408
2025-02-17 02:04:26.43: NetworkPolicyMonitor - start process kube event
2025-02-17 02:04:26.43: empty line received
2025-02-17 02:04:26.43: NetworkPolicyMonitor - start process kube event
2025-02-17 02:04:26.98: IOError IngressMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 02:04:26.98: IngressMonitor - start process kube event
2025-02-17 02:04:26.98: IngressMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9620
2025-02-17 02:04:26.98: IngressMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 02:04:26.98: IngressMonitor - Connect Kube API result 0
2025-02-17 02:04:26.98: IngressMonitor - _schedule_vnc_sync
2025-02-17 02:04:26.98: IngressMonitor - Start Watching request https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})(timeout=120)
2025-02-17 02:04:26.99: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-17 02:04:26.99: VncKubernetes - vnc_sync - Ingress start
2025-02-17 02:04:26.99: VncKubernetes - vnc_sync - Ingress done
2025-02-17 02:04:26.99: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:04:26.99: IngressMonitor - Watches https://10.0.0.23:6443/apis/networking.k8s.io/v1/ingresses ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9620'})
2025-02-17 02:04:27.00: NamespaceMonitor - Received BOOKMARK: oldResVer=9631 newResVer=9631
2025-02-17 02:04:27.00: NamespaceMonitor - start process kube event
2025-02-17 02:04:27.00: empty line received
2025-02-17 02:04:27.00: NamespaceMonitor - start process kube event
2025-02-17 02:04:27.03: IOError NetworkMonitor - HTTPSConnectionPool(host='10.0.0.23', port=6443): Read timed out.
2025-02-17 02:04:27.03: NetworkMonitor - start process kube event
2025-02-17 02:04:27.03: NetworkMonitor - Re-registering event handler. resource_version_valid=True, resource_version=9626
2025-02-17 02:04:27.03: NetworkMonitor - Try to connect Kube API 10.0.0.23:6443
2025-02-17 02:04:27.03: NetworkMonitor - Connect Kube API result 0
2025-02-17 02:04:27.03: NetworkMonitor - _schedule_vnc_sync
2025-02-17 02:04:27.03: NetworkMonitor - Start Watching request https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})(timeout=120)
2025-02-17 02:04:27.03: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-17 02:04:27.03: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-17 02:04:27.03: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:04:27.03: NetworkMonitor - Watches https://10.0.0.23:6443/apis/k8s.cni.cncf.io/v1/network-attachment-definitions ({'watch': 'true', 'allowWatchBookmarks': 'true', 'resourceVersion': '9626'})
2025-02-17 02:04:29.76: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:04:29.76: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:04:29.76: PodMonitor - start process kube event
2025-02-17 02:04:29.76: empty line received
2025-02-17 02:04:29.76: PodMonitor - start process kube event
2025-02-17 02:04:31.02: PodMonitor - Received BOOKMARK: oldResVer=10429 newResVer=10528
2025-02-17 02:04:31.02: PodMonitor - start process kube event
2025-02-17 02:04:31.02: empty line received
2025-02-17 02:04:31.02: PodMonitor - start process kube event
2025-02-17 02:05:26.22: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10408 newResVer=10408
2025-02-17 02:05:26.22: NetworkPolicyMonitor - start process kube event
2025-02-17 02:05:26.22: empty line received
2025-02-17 02:05:26.22: NetworkPolicyMonitor - start process kube event
2025-02-17 02:05:26.52: IngressMonitor - Received BOOKMARK: oldResVer=9620 newResVer=10533
2025-02-17 02:05:26.52: IngressMonitor - start process kube event
2025-02-17 02:05:26.52: empty line received
2025-02-17 02:05:26.52: IngressMonitor - start process kube event
2025-02-17 02:05:26.85: ServiceMonitor - Received BOOKMARK: oldResVer=10184 newResVer=10184
2025-02-17 02:05:26.86: ServiceMonitor - start process kube event
2025-02-17 02:05:26.86: ServiceMonitor - _schedule_vnc_sync
2025-02-17 02:05:26.86: empty line received
2025-02-17 02:05:26.86: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-17 02:05:26.86: VncKubernetes - vnc_sync - Service start
2025-02-17 02:05:26.86: VncKubernetes - vnc_sync - Service done
2025-02-17 02:05:26.86: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:05:26.86: ServiceMonitor - start process kube event
2025-02-17 02:05:26.99: EndPointMonitor - Received BOOKMARK: oldResVer=9782 newResVer=9782
2025-02-17 02:05:26.99: EndPointMonitor - start process kube event
2025-02-17 02:05:26.99: empty line received
2025-02-17 02:05:26.99: EndPointMonitor - start process kube event
2025-02-17 02:05:27.48: NamespaceMonitor - Received BOOKMARK: oldResVer=9631 newResVer=10578
2025-02-17 02:05:27.48: NamespaceMonitor - start process kube event
2025-02-17 02:05:27.48: empty line received
2025-02-17 02:05:27.48: NamespaceMonitor - start process kube event
2025-02-17 02:05:27.79: NetworkMonitor - Received BOOKMARK: oldResVer=9626 newResVer=10550
2025-02-17 02:05:27.79: NetworkMonitor - start process kube event
2025-02-17 02:05:27.79: empty line received
2025-02-17 02:05:27.79: NetworkMonitor - start process kube event
2025-02-17 02:05:29.21: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:05:29.21: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:05:29.21: PodMonitor - start process kube event
2025-02-17 02:05:29.21: empty line received
2025-02-17 02:05:29.21: PodMonitor - start process kube event
2025-02-17 02:05:31.17: PodMonitor - Received BOOKMARK: oldResVer=10528 newResVer=10614
2025-02-17 02:05:31.17: PodMonitor - start process kube event
2025-02-17 02:05:31.17: empty line received
2025-02-17 02:05:31.17: PodMonitor - start process kube event
2025-02-17 02:05:43.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:05:43.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:05:43.68: PodMonitor - start process kube event
2025-02-17 02:05:43.68: empty line received
2025-02-17 02:05:43.68: PodMonitor - start process kube event
2025-02-17 02:06:26.21: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10408 newResVer=10408
2025-02-17 02:06:26.21: NetworkPolicyMonitor - start process kube event
2025-02-17 02:06:26.21: empty line received
2025-02-17 02:06:26.21: NetworkPolicyMonitor - start process kube event
2025-02-17 02:06:26.41: IngressMonitor - Received BOOKMARK: oldResVer=10533 newResVer=10533
2025-02-17 02:06:26.41: IngressMonitor - start process kube event
2025-02-17 02:06:26.41: empty line received
2025-02-17 02:06:26.41: IngressMonitor - start process kube event
2025-02-17 02:06:26.67: ServiceMonitor - Received BOOKMARK: oldResVer=10184 newResVer=10184
2025-02-17 02:06:26.67: ServiceMonitor - start process kube event
2025-02-17 02:06:26.67: empty line received
2025-02-17 02:06:26.67: ServiceMonitor - start process kube event
2025-02-17 02:06:26.97: EndPointMonitor - Received BOOKMARK: oldResVer=9782 newResVer=9782
2025-02-17 02:06:26.97: EndPointMonitor - start process kube event
2025-02-17 02:06:26.97: empty line received
2025-02-17 02:06:26.97: EndPointMonitor - start process kube event
2025-02-17 02:06:27.79: NamespaceMonitor - Received BOOKMARK: oldResVer=10578 newResVer=10578
2025-02-17 02:06:27.79: NamespaceMonitor - start process kube event
2025-02-17 02:06:27.79: empty line received
2025-02-17 02:06:27.79: NamespaceMonitor - start process kube event
2025-02-17 02:06:28.01: NetworkMonitor - Received BOOKMARK: oldResVer=10550 newResVer=10550
2025-02-17 02:06:28.01: NetworkMonitor - start process kube event
2025-02-17 02:06:28.01: empty line received
2025-02-17 02:06:28.01: NetworkMonitor - start process kube event
2025-02-17 02:06:32.05: PodMonitor - Received BOOKMARK: oldResVer=10614 newResVer=10636
2025-02-17 02:06:32.05: PodMonitor - start process kube event
2025-02-17 02:06:32.05: PodMonitor - _schedule_vnc_sync
2025-02-17 02:06:32.05: empty line received
2025-02-17 02:06:32.05: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-17 02:06:32.05: VncKubernetes - vnc_sync - Pod start
2025-02-17 02:06:32.05: VncKubernetes - vnc_sync - Pod done
2025-02-17 02:06:32.05: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:06:32.05: PodMonitor - start process kube event
2025-02-17 02:07:26.23: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10408 newResVer=10408
2025-02-17 02:07:26.23: NetworkPolicyMonitor - start process kube event
2025-02-17 02:07:26.23: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-17 02:07:26.23: empty line received
2025-02-17 02:07:26.23: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-17 02:07:26.23: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-17 02:07:26.23: NetworkPolicyMonitor - start process kube event
2025-02-17 02:07:26.23: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-17 02:07:26.23: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:07:26.32: IngressMonitor - Received BOOKMARK: oldResVer=10533 newResVer=10533
2025-02-17 02:07:26.32: IngressMonitor - start process kube event
2025-02-17 02:07:26.32: empty line received
2025-02-17 02:07:26.32: IngressMonitor - start process kube event
2025-02-17 02:07:26.58: ServiceMonitor - Received BOOKMARK: oldResVer=10184 newResVer=10184
2025-02-17 02:07:26.58: ServiceMonitor - start process kube event
2025-02-17 02:07:26.58: empty line received
2025-02-17 02:07:26.58: ServiceMonitor - start process kube event
2025-02-17 02:07:26.93: EndPointMonitor - Received BOOKMARK: oldResVer=9782 newResVer=10739
2025-02-17 02:07:26.93: EndPointMonitor - start process kube event
2025-02-17 02:07:26.93: empty line received
2025-02-17 02:07:26.93: EndPointMonitor - start process kube event
2025-02-17 02:07:27.82: NamespaceMonitor - Received BOOKMARK: oldResVer=10578 newResVer=10578
2025-02-17 02:07:27.82: NamespaceMonitor - start process kube event
2025-02-17 02:07:27.82: NamespaceMonitor - _schedule_vnc_sync
2025-02-17 02:07:27.82: empty line received
2025-02-17 02:07:27.82: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-17 02:07:27.82: VncKubernetes - vnc_sync - Namespace start
2025-02-17 02:07:27.82: VncKubernetes - vnc_sync - Namespace done
2025-02-17 02:07:27.82: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:07:27.82: NamespaceMonitor - start process kube event
2025-02-17 02:07:28.01: NetworkMonitor - Received BOOKMARK: oldResVer=10550 newResVer=10550
2025-02-17 02:07:28.01: NetworkMonitor - start process kube event
2025-02-17 02:07:28.01: empty line received
2025-02-17 02:07:28.01: NetworkMonitor - start process kube event
2025-02-17 02:07:32.76: PodMonitor - Received BOOKMARK: oldResVer=10636 newResVer=10636
2025-02-17 02:07:32.76: PodMonitor - start process kube event
2025-02-17 02:07:32.76: empty line received
2025-02-17 02:07:32.76: PodMonitor - start process kube event
2025-02-17 02:08:26.16: EndPointMonitor - Received BOOKMARK: oldResVer=10739 newResVer=10739
2025-02-17 02:08:26.16: EndPointMonitor - start process kube event
2025-02-17 02:08:26.16: EndPointMonitor - _schedule_vnc_sync
2025-02-17 02:08:26.16: empty line received
2025-02-17 02:08:26.16: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-17 02:08:26.16: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-17 02:08:26.16: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:08:26.16: EndPointMonitor - start process kube event
2025-02-17 02:08:26.42: ServiceMonitor - Received BOOKMARK: oldResVer=10184 newResVer=10184
2025-02-17 02:08:26.42: ServiceMonitor - start process kube event
2025-02-17 02:08:26.42: empty line received
2025-02-17 02:08:26.42: ServiceMonitor - start process kube event
2025-02-17 02:08:26.85: IngressMonitor - Received BOOKMARK: oldResVer=10533 newResVer=10533
2025-02-17 02:08:26.85: IngressMonitor - start process kube event
2025-02-17 02:08:26.85: empty line received
2025-02-17 02:08:26.85: IngressMonitor - start process kube event
2025-02-17 02:08:26.95: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10408 newResVer=10408
2025-02-17 02:08:26.95: NetworkPolicyMonitor - start process kube event
2025-02-17 02:08:26.95: empty line received
2025-02-17 02:08:26.95: NetworkPolicyMonitor - start process kube event
2025-02-17 02:08:27.47: NamespaceMonitor - Received BOOKMARK: oldResVer=10578 newResVer=10578
2025-02-17 02:08:27.47: NamespaceMonitor - start process kube event
2025-02-17 02:08:27.47: empty line received
2025-02-17 02:08:27.47: NamespaceMonitor - start process kube event
2025-02-17 02:08:28.73: NetworkMonitor - Received BOOKMARK: oldResVer=10550 newResVer=10550
2025-02-17 02:08:28.73: NetworkMonitor - start process kube event
2025-02-17 02:08:28.73: NetworkMonitor - _schedule_vnc_sync
2025-02-17 02:08:28.73: empty line received
2025-02-17 02:08:28.73: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-17 02:08:28.73: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-17 02:08:28.73: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:08:28.73: NetworkMonitor - start process kube event
2025-02-17 02:08:29.36: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:08:29.36: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:08:29.36: PodMonitor - start process kube event
2025-02-17 02:08:29.36: empty line received
2025-02-17 02:08:29.36: PodMonitor - start process kube event
2025-02-17 02:08:32.42: PodMonitor - Received BOOKMARK: oldResVer=10636 newResVer=10875
2025-02-17 02:08:32.42: PodMonitor - start process kube event
2025-02-17 02:08:32.42: empty line received
2025-02-17 02:08:32.42: PodMonitor - start process kube event
2025-02-17 02:08:40.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:08:40.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:08:40.68: PodMonitor - start process kube event
2025-02-17 02:08:40.68: empty line received
2025-02-17 02:08:40.68: PodMonitor - start process kube event
2025-02-17 02:09:26.28: ServiceMonitor - Received BOOKMARK: oldResVer=10184 newResVer=10184
2025-02-17 02:09:26.28: ServiceMonitor - start process kube event
2025-02-17 02:09:26.28: empty line received
2025-02-17 02:09:26.28: ServiceMonitor - start process kube event
2025-02-17 02:09:26.40: EndPointMonitor - Received BOOKMARK: oldResVer=10739 newResVer=10739
2025-02-17 02:09:26.40: EndPointMonitor - start process kube event
2025-02-17 02:09:26.40: empty line received
2025-02-17 02:09:26.40: EndPointMonitor - start process kube event
2025-02-17 02:09:26.62: IngressMonitor - Received BOOKMARK: oldResVer=10533 newResVer=10533
2025-02-17 02:09:26.62: IngressMonitor - start process kube event
2025-02-17 02:09:26.62: IngressMonitor - _schedule_vnc_sync
2025-02-17 02:09:26.62: empty line received
2025-02-17 02:09:26.62: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-17 02:09:26.62: VncKubernetes - vnc_sync - Ingress start
2025-02-17 02:09:26.62: VncKubernetes - vnc_sync - Ingress done
2025-02-17 02:09:26.62: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:09:26.62: IngressMonitor - start process kube event
2025-02-17 02:09:27.12: NamespaceMonitor - Received BOOKMARK: oldResVer=10578 newResVer=10578
2025-02-17 02:09:27.12: NamespaceMonitor - start process kube event
2025-02-17 02:09:27.12: empty line received
2025-02-17 02:09:27.12: NamespaceMonitor - start process kube event
2025-02-17 02:09:27.12: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10408 newResVer=10408
2025-02-17 02:09:27.12: NetworkPolicyMonitor - start process kube event
2025-02-17 02:09:27.12: empty line received
2025-02-17 02:09:27.12: NetworkPolicyMonitor - start process kube event
2025-02-17 02:09:28.03: NetworkMonitor - Received BOOKMARK: oldResVer=10550 newResVer=10550
2025-02-17 02:09:28.03: NetworkMonitor - start process kube event
2025-02-17 02:09:28.03: empty line received
2025-02-17 02:09:28.03: NetworkMonitor - start process kube event
2025-02-17 02:09:32.49: PodMonitor - Received BOOKMARK: oldResVer=10875 newResVer=10893
2025-02-17 02:09:32.49: PodMonitor - start process kube event
2025-02-17 02:09:32.49: empty line received
2025-02-17 02:09:32.49: PodMonitor - start process kube event
2025-02-17 02:10:26.02: EndPointMonitor - Received BOOKMARK: oldResVer=10739 newResVer=10739
2025-02-17 02:10:26.02: EndPointMonitor - start process kube event
2025-02-17 02:10:26.02: empty line received
2025-02-17 02:10:26.02: EndPointMonitor - start process kube event
2025-02-17 02:10:26.16: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10408 newResVer=10408
2025-02-17 02:10:26.16: NetworkPolicyMonitor - start process kube event
2025-02-17 02:10:26.16: empty line received
2025-02-17 02:10:26.16: NetworkPolicyMonitor - start process kube event
2025-02-17 02:10:26.29: IngressMonitor - Received BOOKMARK: oldResVer=10533 newResVer=10533
2025-02-17 02:10:26.29: IngressMonitor - start process kube event
2025-02-17 02:10:26.29: empty line received
2025-02-17 02:10:26.29: IngressMonitor - start process kube event
2025-02-17 02:10:27.10: ServiceMonitor - Received BOOKMARK: oldResVer=10184 newResVer=10184
2025-02-17 02:10:27.10: ServiceMonitor - start process kube event
2025-02-17 02:10:27.10: ServiceMonitor - _schedule_vnc_sync
2025-02-17 02:10:27.10: empty line received
2025-02-17 02:10:27.10: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-17 02:10:27.10: VncKubernetes - vnc_sync - Service start
2025-02-17 02:10:27.10: VncKubernetes - vnc_sync - Service done
2025-02-17 02:10:27.10: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:10:27.10: ServiceMonitor - start process kube event
2025-02-17 02:10:27.58: NamespaceMonitor - Received BOOKMARK: oldResVer=10578 newResVer=10578
2025-02-17 02:10:27.58: NamespaceMonitor - start process kube event
2025-02-17 02:10:27.58: empty line received
2025-02-17 02:10:27.58: NamespaceMonitor - start process kube event
2025-02-17 02:10:28.88: NetworkMonitor - Received BOOKMARK: oldResVer=10550 newResVer=10550
2025-02-17 02:10:28.88: NetworkMonitor - start process kube event
2025-02-17 02:10:28.88: empty line received
2025-02-17 02:10:28.88: NetworkMonitor - start process kube event
2025-02-17 02:10:32.23: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:10:32.23: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:10:32.23: PodMonitor - start process kube event
2025-02-17 02:10:32.23: PodMonitor - _schedule_vnc_sync
2025-02-17 02:10:32.23: empty line received
2025-02-17 02:10:32.23: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-17 02:10:32.23: VncKubernetes - vnc_sync - Pod start
2025-02-17 02:10:32.23: VncKubernetes - vnc_sync - Pod done
2025-02-17 02:10:32.23: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:10:32.23: PodMonitor - start process kube event
2025-02-17 02:10:33.02: PodMonitor - Received BOOKMARK: oldResVer=10893 newResVer=11059
2025-02-17 02:10:33.02: PodMonitor - start process kube event
2025-02-17 02:10:33.02: empty line received
2025-02-17 02:10:33.02: PodMonitor - start process kube event
2025-02-17 02:11:26.61: EndPointMonitor - Received BOOKMARK: oldResVer=10739 newResVer=10739
2025-02-17 02:11:26.61: EndPointMonitor - start process kube event
2025-02-17 02:11:26.61: empty line received
2025-02-17 02:11:26.61: EndPointMonitor - start process kube event
2025-02-17 02:11:26.82: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10408 newResVer=10408
2025-02-17 02:11:26.82: NetworkPolicyMonitor - start process kube event
2025-02-17 02:11:26.82: NetworkPolicyMonitor - _schedule_vnc_sync
2025-02-17 02:11:26.82: empty line received
2025-02-17 02:11:26.82: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkPolicy ns=None)
2025-02-17 02:11:26.82: VncKubernetes - vnc_sync - NetworkPolicy start
2025-02-17 02:11:26.82: NetworkPolicyMonitor - start process kube event
2025-02-17 02:11:26.83: VncKubernetes - vnc_sync - NetworkPolicy done
2025-02-17 02:11:26.83: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:11:26.94: IngressMonitor - Received BOOKMARK: oldResVer=10533 newResVer=10533
2025-02-17 02:11:26.94: IngressMonitor - start process kube event
2025-02-17 02:11:26.94: empty line received
2025-02-17 02:11:26.94: IngressMonitor - start process kube event
2025-02-17 02:11:27.58: ServiceMonitor - Received BOOKMARK: oldResVer=10184 newResVer=11083
2025-02-17 02:11:27.58: ServiceMonitor - start process kube event
2025-02-17 02:11:27.58: empty line received
2025-02-17 02:11:27.58: ServiceMonitor - start process kube event
2025-02-17 02:11:27.80: NamespaceMonitor - Received BOOKMARK: oldResVer=10578 newResVer=10578
2025-02-17 02:11:27.80: NamespaceMonitor - start process kube event
2025-02-17 02:11:27.80: empty line received
2025-02-17 02:11:27.80: NamespaceMonitor - start process kube event
2025-02-17 02:11:28.19: NetworkMonitor - Received BOOKMARK: oldResVer=10550 newResVer=10550
2025-02-17 02:11:28.19: NetworkMonitor - start process kube event
2025-02-17 02:11:28.19: empty line received
2025-02-17 02:11:28.19: NetworkMonitor - start process kube event
2025-02-17 02:11:32.71: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:11:32.71: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:11:32.71: PodMonitor - start process kube event
2025-02-17 02:11:32.71: empty line received
2025-02-17 02:11:32.71: PodMonitor - start process kube event
2025-02-17 02:11:32.95: PodMonitor - Received BOOKMARK: oldResVer=11059 newResVer=11144
2025-02-17 02:11:32.95: PodMonitor - start process kube event
2025-02-17 02:11:32.95: empty line received
2025-02-17 02:11:32.95: PodMonitor - start process kube event
2025-02-17 02:11:47.70: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:11:47.70: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:11:47.70: PodMonitor - start process kube event
2025-02-17 02:11:47.70: empty line received
2025-02-17 02:11:47.70: PodMonitor - start process kube event
2025-02-17 02:12:26.42: EndPointMonitor - Received BOOKMARK: oldResVer=10739 newResVer=10739
2025-02-17 02:12:26.42: EndPointMonitor - start process kube event
2025-02-17 02:12:26.42: EndPointMonitor - _schedule_vnc_sync
2025-02-17 02:12:26.42: empty line received
2025-02-17 02:12:26.42: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Endpoints ns=None)
2025-02-17 02:12:26.42: VncKubernetes - vnc_sync - Endpoints - no handler - skip
2025-02-17 02:12:26.42: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:12:26.42: EndPointMonitor - start process kube event
2025-02-17 02:12:26.58: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10408 newResVer=10408
2025-02-17 02:12:26.58: NetworkPolicyMonitor - start process kube event
2025-02-17 02:12:26.58: empty line received
2025-02-17 02:12:26.58: NetworkPolicyMonitor - start process kube event
2025-02-17 02:12:27.08: IngressMonitor - Received BOOKMARK: oldResVer=10533 newResVer=10533
2025-02-17 02:12:27.08: IngressMonitor - start process kube event
2025-02-17 02:12:27.08: empty line received
2025-02-17 02:12:27.08: IngressMonitor - start process kube event
2025-02-17 02:12:27.49: ServiceMonitor - Received BOOKMARK: oldResVer=11083 newResVer=11083
2025-02-17 02:12:27.49: ServiceMonitor - start process kube event
2025-02-17 02:12:27.49: empty line received
2025-02-17 02:12:27.49: ServiceMonitor - start process kube event
2025-02-17 02:12:28.03: NamespaceMonitor - Received BOOKMARK: oldResVer=10578 newResVer=10578
2025-02-17 02:12:28.03: NamespaceMonitor - start process kube event
2025-02-17 02:12:28.03: NamespaceMonitor - _schedule_vnc_sync
2025-02-17 02:12:28.03: empty line received
2025-02-17 02:12:28.03: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Namespace ns=None)
2025-02-17 02:12:28.03: VncKubernetes - vnc_sync - Namespace start
2025-02-17 02:12:28.03: VncKubernetes - vnc_sync - Namespace done
2025-02-17 02:12:28.03: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:12:28.03: NamespaceMonitor - start process kube event
2025-02-17 02:12:28.36: NetworkMonitor - Received BOOKMARK: oldResVer=10550 newResVer=10550
2025-02-17 02:12:28.36: NetworkMonitor - start process kube event
2025-02-17 02:12:28.36: empty line received
2025-02-17 02:12:28.36: NetworkMonitor - start process kube event
2025-02-17 02:12:33.09: PodMonitor - Received BOOKMARK: oldResVer=11144 newResVer=11168
2025-02-17 02:12:33.09: PodMonitor - start process kube event
2025-02-17 02:12:33.09: empty line received
2025-02-17 02:12:33.09: PodMonitor - start process kube event
2025-02-17 02:13:26.31: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10408 newResVer=10408
2025-02-17 02:13:26.31: NetworkPolicyMonitor - start process kube event
2025-02-17 02:13:26.31: empty line received
2025-02-17 02:13:26.31: NetworkPolicyMonitor - start process kube event
2025-02-17 02:13:26.76: IngressMonitor - Received BOOKMARK: oldResVer=10533 newResVer=10533
2025-02-17 02:13:26.76: IngressMonitor - start process kube event
2025-02-17 02:13:26.76: IngressMonitor - _schedule_vnc_sync
2025-02-17 02:13:26.76: empty line received
2025-02-17 02:13:26.76: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Ingress ns=None)
2025-02-17 02:13:26.76: VncKubernetes - vnc_sync - Ingress start
2025-02-17 02:13:26.76: VncKubernetes - vnc_sync - Ingress done
2025-02-17 02:13:26.76: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:13:26.76: IngressMonitor - start process kube event
2025-02-17 02:13:27.20: EndPointMonitor - Received BOOKMARK: oldResVer=10739 newResVer=10739
2025-02-17 02:13:27.20: EndPointMonitor - start process kube event
2025-02-17 02:13:27.20: empty line received
2025-02-17 02:13:27.20: EndPointMonitor - start process kube event
2025-02-17 02:13:27.51: ServiceMonitor - Received BOOKMARK: oldResVer=11083 newResVer=11083
2025-02-17 02:13:27.51: ServiceMonitor - start process kube event
2025-02-17 02:13:27.51: empty line received
2025-02-17 02:13:27.51: ServiceMonitor - start process kube event
2025-02-17 02:13:28.36: NetworkMonitor - Received BOOKMARK: oldResVer=10550 newResVer=10550
2025-02-17 02:13:28.36: NetworkMonitor - start process kube event
2025-02-17 02:13:28.36: NetworkMonitor - _schedule_vnc_sync
2025-02-17 02:13:28.36: empty line received
2025-02-17 02:13:28.36: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=NetworkAttachmentDefinition ns=None)
2025-02-17 02:13:28.36: VncKubernetes - vnc_sync - NetworkAttachmentDefinition - no handler - skip
2025-02-17 02:13:28.36: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:13:28.36: NetworkMonitor - start process kube event
2025-02-17 02:13:28.69: NamespaceMonitor - Received BOOKMARK: oldResVer=10578 newResVer=10578
2025-02-17 02:13:28.69: NamespaceMonitor - start process kube event
2025-02-17 02:13:28.69: empty line received
2025-02-17 02:13:28.69: NamespaceMonitor - start process kube event
2025-02-17 02:13:32.63: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:13:32.63: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:13:32.63: PodMonitor - start process kube event
2025-02-17 02:13:32.63: empty line received
2025-02-17 02:13:32.63: PodMonitor - start process kube event
2025-02-17 02:13:33.25: PodMonitor - Received BOOKMARK: oldResVer=11168 newResVer=11315
2025-02-17 02:13:33.25: PodMonitor - start process kube event
2025-02-17 02:13:33.25: empty line received
2025-02-17 02:13:33.25: PodMonitor - start process kube event
2025-02-17 02:13:46.68: PodMonitor - Received MODIFIED Pod kube-system:contrail-agent-m9p25:a1cf0168-3bcc-440d-be40-610c1f6af903
2025-02-17 02:13:46.68: PodMonitor - Skipped MODIFIED Pod kube-system:contrail-agent-m9p25 (hostNetwork=True)
2025-02-17 02:13:46.68: PodMonitor - start process kube event
2025-02-17 02:13:46.68: empty line received
2025-02-17 02:13:46.68: PodMonitor - start process kube event
2025-02-17 02:14:26.18: IngressMonitor - Received BOOKMARK: oldResVer=10533 newResVer=10533
2025-02-17 02:14:26.18: IngressMonitor - start process kube event
2025-02-17 02:14:26.18: empty line received
2025-02-17 02:14:26.18: IngressMonitor - start process kube event
2025-02-17 02:14:26.28: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=10408 newResVer=11317
2025-02-17 02:14:26.28: NetworkPolicyMonitor - start process kube event
2025-02-17 02:14:26.28: empty line received
2025-02-17 02:14:26.28: NetworkPolicyMonitor - start process kube event
2025-02-17 02:14:27.63: EndPointMonitor - Received BOOKMARK: oldResVer=10739 newResVer=10739
2025-02-17 02:14:27.63: EndPointMonitor - start process kube event
2025-02-17 02:14:27.63: empty line received
2025-02-17 02:14:27.63: EndPointMonitor - start process kube event
2025-02-17 02:14:27.99: NetworkMonitor - Received BOOKMARK: oldResVer=10550 newResVer=10550
2025-02-17 02:14:27.99: NetworkMonitor - start process kube event
2025-02-17 02:14:27.99: empty line received
2025-02-17 02:14:27.99: NetworkMonitor - start process kube event
2025-02-17 02:14:28.03: ServiceMonitor - Received BOOKMARK: oldResVer=11083 newResVer=11083
2025-02-17 02:14:28.03: ServiceMonitor - start process kube event
2025-02-17 02:14:28.03: ServiceMonitor - _schedule_vnc_sync
2025-02-17 02:14:28.03: empty line received
2025-02-17 02:14:28.03: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Service ns=None)
2025-02-17 02:14:28.03: VncKubernetes - vnc_sync - Service start
2025-02-17 02:14:28.03: VncKubernetes - vnc_sync - Service done
2025-02-17 02:14:28.03: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:14:28.03: ServiceMonitor - start process kube event
2025-02-17 02:14:28.39: NamespaceMonitor - Received BOOKMARK: oldResVer=10578 newResVer=10578
2025-02-17 02:14:28.39: NamespaceMonitor - start process kube event
2025-02-17 02:14:28.39: empty line received
2025-02-17 02:14:28.39: NamespaceMonitor - start process kube event
2025-02-17 02:14:33.59: PodMonitor - Received BOOKMARK: oldResVer=11315 newResVer=11336
2025-02-17 02:14:33.59: PodMonitor - start process kube event
2025-02-17 02:14:33.59: PodMonitor - _schedule_vnc_sync
2025-02-17 02:14:33.59: empty line received
2025-02-17 02:14:33.59: VncKubernetes - Process event (name=None event_type=TF_VNC_SYNC kind=Pod ns=None)
2025-02-17 02:14:33.59: VncKubernetes - vnc_sync - Pod start
2025-02-17 02:14:33.59: VncKubernetes - vnc_sync - Pod done
2025-02-17 02:14:33.59: VncKubernetes - wait event (qsize=0 timeout=120)
2025-02-17 02:14:33.59: PodMonitor - start process kube event
2025-02-17 02:15:26.40: IngressMonitor - Received BOOKMARK: oldResVer=10533 newResVer=11450
2025-02-17 02:15:26.40: IngressMonitor - start process kube event
2025-02-17 02:15:26.40: empty line received
2025-02-17 02:15:26.40: IngressMonitor - start process kube event
2025-02-17 02:15:26.60: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11317 newResVer=11317
2025-02-17 02:15:26.60: NetworkPolicyMonitor - start process kube event
2025-02-17 02:15:26.60: empty line received
2025-02-17 02:15:26.60: NetworkPolicyMonitor - start process kube event
2025-02-17 02:15:27.26: EndPointMonitor - Received BOOKMARK: oldResVer=10739 newResVer=10739
2025-02-17 02:15:27.26: EndPointMonitor - start process kube event
2025-02-17 02:15:27.26: empty line received
2025-02-17 02:15:27.26: EndPointMonitor - start process kube event
2025-02-17 02:15:27.81: ServiceMonitor - Received BOOKMARK: oldResVer=11083 newResVer=11083
2025-02-17 02:15:27.81: ServiceMonitor - start process kube event
2025-02-17 02:15:27.81: empty line received
2025-02-17 02:15:27.81: ServiceMonitor - start process kube event
2025-02-17 02:15:28.47: NetworkMonitor - Received BOOKMARK: oldResVer=10550 newResVer=11450
2025-02-17 02:15:28.47: NetworkMonitor - start process kube event
2025-02-17 02:15:28.47: empty line received
2025-02-17 02:15:28.47: NetworkMonitor - start process kube event
2025-02-17 02:15:28.57: NamespaceMonitor - Received BOOKMARK: oldResVer=10578 newResVer=10578
2025-02-17 02:15:28.57: NamespaceMonitor - start process kube event
2025-02-17 02:15:28.57: empty line received
2025-02-17 02:15:28.57: NamespaceMonitor - start process kube event
2025-02-17 02:15:33.30: PodMonitor - Received BOOKMARK: oldResVer=11336 newResVer=11336
2025-02-17 02:15:33.30: PodMonitor - start process kube event
2025-02-17 02:15:33.30: empty line received
2025-02-17 02:15:33.30: PodMonitor - start process kube event
2025-02-17 02:16:27.11: IngressMonitor - Received BOOKMARK: oldResVer=11450 newResVer=11450
2025-02-17 02:16:27.11: IngressMonitor - start process kube event
2025-02-17 02:16:27.11: empty line received
2025-02-17 02:16:27.11: IngressMonitor - start process kube event
2025-02-17 02:16:27.12: NetworkPolicyMonitor - Received BOOKMARK: oldResVer=11317 newResVer=11317
2025-02-17 02:16:27.12: NetworkPolicyMonitor - start process kube event
2025-02-17 02:16:27.12: NetworkPolicyMonitor - _schedule_vnc_sync