[ZBX-11445] Mass update for jmx agent items does not work Created: 2016 Nov 09  Updated: 2017 May 30  Resolved: 2016 Nov 24

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 3.0.5
Fix Version/s: 3.0.6rc1, 3.2.2rc1, 3.4.0alpha1

Type: Incident report Priority: Critical
Reporter: Sergey Korobeiko Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2016-11-09 at 14.31.09.png    

 Description   

Go to items in template.
Choose jmx item and press mass update button.
Next you will see the attached screenshot.
Almost nothing can be changed.



 Comments   
Comment by Aleksandrs Saveljevs [ 2016 Nov 09 ]

"Mass update" for items in a template does not seem to have the "Host interface" option. Maybe some other details are important?

Comment by Sergey Korobeiko [ 2016 Nov 09 ]

Sorry. Please choose host with jmx item.

Comment by Aleksandrs Saveljevs [ 2016 Nov 09 ]

Seems to be the case indeed, so setting to "Confirmed".

One detail: in order to reproduce the issue, it seems that a host needs to have both JMX items and some other items that are attached to different interface types. Having only JMX items is not enough.

Comment by vitalijs.cemeris (Inactive) [ 2016 Nov 22 ]

To reproduce message "To set a host interface select a single item type for all items", host should have at least 2 items with different host interface types
Message occurs while mass updating host item.

Message seems to be correct in cases when we mass update multiple items of different type, however it should not occur when all items in mass update are of same type.

Comment by vitalijs.cemeris (Inactive) [ 2016 Nov 23 ]

(1) No translation strings changed.

gunarspujats CLOSED

Comment by vitalijs.cemeris (Inactive) [ 2016 Nov 23 ]

Fixed in the development branch svn://svn.zabbix.com/branches/dev/ZBX-11445

Comment by Gunars Pujats (Inactive) [ 2016 Nov 23 ]

Tested

Comment by vitalijs.cemeris (Inactive) [ 2016 Nov 24 ]

Fixed in pre-3.0.6rc1 (r63971), pre-3.2.2rc1 (r63972), pre-3.3.0 (r63973)

Generated at Fri Apr 26 12:51:04 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.