[ZBX-21455] Proxmox template - VM and LXC restart trigger needs extra status check Created: 2022 Aug 10  Updated: 2024 Apr 10  Resolved: 2022 Aug 24

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 6.2.0
Fix Version/s: 6.0.8rc1, 6.2.2rc1, 6.4.0alpha1, 6.4 (plan)

Type: Problem report Priority: Trivial
Reporter: H. Assignee: Evgenii Gordymov
Resolution: Fixed Votes: 0
Labels: Proxmox, triggers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team INT
Sprint: Sprint 91 (Aug 2022)
Story Points: 1

 Description   

The proxmox template could use an extra check in its expression if the VM/LXC status is actually running for the following triggers:

  • Proxmox: VM [ {#NODE.NAME}/{#QEMU.NAME}|#NODE.NAME}/{#QEMU.NAME}]: has been restarted
    * Proxmox: LXC [{#NODE.NAME}

    /{#LXC.NAME}|#NODE.NAME}/{#LXC.NAME}]: has been restarted

If the status of the VM/LXC is stopped the uptime is set to 0 by proxmox which results in the above triggers being triggered on every check (...even though the VM/LXC is not running).

 Comments   
Comment by Evgenii Gordymov [ 2022 Aug 18 ]

Available in:

Generated at Mon Jun 02 17:18:28 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.