We upgraded 'neuvector-core' from 2.8.4 to 2.8.5 just fine, but when we then subsequently tried to upgrade 'neuvector-monitor' from 2.8.4 to 2.8.5 the neuvector-prometheus-exporter-pod-* logs immediately showed the following:
│ Login to controller ...
│ Start exporter server ...
│ Register collector ...
│ Traceback (most recent call last):
│ File "/usr/local/bin/nv_exporter.py", line 650, in <module>
│ REGISTRY.register(COLLECTOR)
│ ~~~~~~~~~~~~~~~~~^^^^^^^^^^^
│ File "/.venv/lib64/python3.13/site-packages/prometheus_client/registry.py", line 40, in register
│ names = self._get_names(collector)
│ File "/.venv/lib64/python3.13/site-packages/prometheus_client/registry.py", line 80, in _get_names
│ for metric in desc_func():
│ ~~~~~~~~~^^
│ File "/usr/local/bin/nv_exporter.py", line 455, in collect
│ iwnslist.append(c['workload_domain'])
│ ~^^^^^^^^^^^^^^^^^^^
│ KeyError: 'workload_domain'
I have not run into this issue before. I can see some rearrangement of some potentially relevant code in nv_exporter in the bump from 1.0.2 to 1.0.3 of prometheus-exporter, but I can't figure out why I'm getting that KeyError. When I redeploy the helm chart v2.8.4, it starts working again with no errors.
We are running our deployments in EKS. Everything is managed by helm.
Any help appreciated!
We upgraded 'neuvector-core' from 2.8.4 to 2.8.5 just fine, but when we then subsequently tried to upgrade 'neuvector-monitor' from 2.8.4 to 2.8.5 the
neuvector-prometheus-exporter-pod-*logs immediately showed the following:I have not run into this issue before. I can see some rearrangement of some potentially relevant code in
nv_exporterin the bump from 1.0.2 to 1.0.3 of prometheus-exporter, but I can't figure out why I'm getting that KeyError. When I redeploy the helm chart v2.8.4, it starts working again with no errors.We are running our deployments in EKS. Everything is managed by helm.
Any help appreciated!