-
Problem report
-
Resolution: Unresolved
-
Trivial
-
None
-
5.0.22
-
None
Steps to reproduce:
- On linux.
- Run Zabbix agent on VM supporting hot plugging cpu (example, https://docs.oracle.com/en/virtualization/virtualbox/6.0/admin/cpuhotplug.html)
- Remove cpu in middle (example if 0-4 cpu set, unplug cpu 1,2 or 3)
- Run Zabbix agent
- Execute Zabbix get with key system.cpu.discovery
- Execute Zabbix get with key system.cpu.num[max]
Result:
The removed cpu will be there, for system.cpu.discovery
The removed cpu will not be there, for system.cpu.num[max]
Expected:
The removed cpu will be there, for system.cpu.discovery
The removed cpu will be there, for system.cpu.num[max]
Since Zabbix agent 2 uses the same parameter that Zabbix agent, the issue persists there as well.
- depends on
-
ZBX-20030 system.cpu.num key couldn't get correct number of cpu cores when using zabbix-agent2(both Linux and Windows) on virtual machines with CPU hot-plugging
- Closed