[ZBX-16135] Error in XML exported file when User has missing permission for Host Prototype Group Created: 2019 May 16  Updated: 2024 Apr 10  Resolved: 2019 Jul 23

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: API (A), Frontend (F)
Affects Version/s: None
Fix Version/s: 4.0.11rc1, 4.2.5rc1, 4.4.0alpha1, 4.4 (plan)

Type: Problem report Priority: Major
Reporter: Larisa Grigorjeva Assignee: Andrejs Verza
Resolution: Fixed Votes: 0
Labels: export, permissions
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File before-and-after.png     PNG File multimessage.png    
Issue Links:
Duplicate
duplicates ZBX-15446 Exporting a host/template via fronten... Closed
Team: Team B
Sprint: Sprint 52 (May 2019), Sprint 53 (Jun 2019), Sprint 54 (Jul 2019)
Story Points: 2

 Description   

1. Log in as Super Admin.
2. Create Host group HOST_GROUP with host HOST.
3. On HOST create Discovery rule RULE with {#HOST_PROTOTYPE}
4. {#HOST_PROTOTYPE} assign to group Zabbix servers.
5. Create USERS_GROUP with W+R permissions for HOST_GROUP and with NONE/DENY permissions for Zabbix servers.
6. Create USER with Simple Admin rights and add him to USERS_GROUP
7. Log in with USER.
8. Open Configuration ->Hosts, find HOST, check it and Export.
9. Open Exported XML file.
Result:
Exported file contains error:
[error] System error occurred. Please contact Zabbix administrator.

Expected:
Error message should be displayed to user and should be more descriptive.



 Comments   
Comment by richlv [ 2019 May 16 ]

Might be a duplicate of ZBX-4971.
<averza> Agreed.

Comment by Andrejs Verza [ 2019 May 20 ]

Resolved in development branch feature/ZBX-16135-4.0.

Comment by Andrejs Verza [ 2019 Jul 05 ]

Fixed in:

Comment by Andrejs Verza [ 2019 Jul 16 ]

Broken header in error messages after applying the fix:

Comment by Andrejs Verza [ 2019 Jul 16 ]

Resolved in development branch feature/ZBX-16135-4.0.

Comment by Andrejs Verza [ 2019 Jul 22 ]

Fixed in:

Generated at Sat Apr 27 07:04:23 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.