[ZBX-7340] "Template Virt VMware" can fail with mysterious message Created: 2013 Nov 12  Updated: 2017 May 30  Resolved: 2013 Nov 27

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: API (A)
Affects Version/s: 2.2.0
Fix Version/s: 2.2.2rc1, 2.3.0

Type: Incident report Priority: Blocker
Reporter: richlv Assignee: Unassigned
Resolution: Fixed Votes: 1
Labels: xml
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

have a clean 2.2.0 install, export vmware templates one by one, delete them. attempt to import "Template Virt VMware". it fails with :

Created: Item prototype "Status of "$2" cluster" on "Template Virt VMware".
No permissions to referred object or it does not exist!

this gives no idea to user what's wrong; the message probably should reference one of the two other vmware templates, as importing those will make "Template Virt VMware" import, too

 Comments   
Comment by Alexander Timakov [ 2013 Nov 13 ]

1. You should import templates in order:
1.1. VM template
1.2. Hypervisor
1.3. Global template - vSphere

2. There is a error in XML file "zbx_export_Virt VMware" - $2 it quoted with two words "&quoted" - remove them with simple text editor.

Comment by richlv [ 2013 Nov 13 ]

sure you have to import templates in order, but the error message should be better

as for the quote issue, what exactly is the problem ?

Comment by Pavels Jelisejevs (Inactive) [ 2013 Nov 27 ]

I've also added error message for a couple of similar scenarios:

  • importing a host prototype that references a missing host group;
  • importing an item or item prototype that references a missing value map;
  • importing a graph or graph prototype that references a missing item as its MIN or MAX value.

RESOLVED in svn://svn.zabbix.com/branches/dev/ZBX-7340.

Eduards CLOSED

Comment by Eduards Samersovs (Inactive) [ 2013 Nov 28 ]

Tested

Comment by Pavels Jelisejevs (Inactive) [ 2013 Nov 28 ]

Fixed in 2.2.1rc1 r40573 and 2.3.0 r40574.

CLOSED.

Generated at Fri Apr 26 10:14:31 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.