[ZBX-7849] Can't update Action: Maintenance action condition value must be empty. Created: 2014 Feb 20 Updated: 2017 May 30 Resolved: 2014 Mar 06 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F), Server (S) |
Affects Version/s: | 2.2.2 |
Fix Version/s: | 2.2.3rc1, 2.3.0 |
Type: | Incident report | Priority: | Major |
Reporter: | Anton Samets | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | action, maintenance | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | Screen Shot 2014-02-20 at 23.24.54.png |
Description |
I've tried to update some actions, adding more conditions, but right now I've got: Usual things for actions - using condition But right now frontend doesn't allow me to update action. |
Comments |
Comment by Ivo Kurzemnieks [ 2014 Feb 21 ] |
Anton, have to upgraded ZABBIX from version 2.0.x to 2.2.x? UPDATE conditions SET value='' WHERE conditiontype=16; |
Comment by Anton Samets [ 2014 Feb 21 ] |
Yes, we are upgraded to 2.2 from 2.0. |
Comment by Anton Samets [ 2014 Feb 21 ] |
Yes, it solved the issue, thank you. |
Comment by Ivo Kurzemnieks [ 2014 Feb 21 ] |
It was decided not to make any additional patches, since table structure does not change and only incorrect data is beeing manipulated.
Some time later we added 'maintenance status' field validation and now it doesn't accept previously created '0' values in that field. There should've been empty values for 'maintenance status' and so there's nothing really to add for documentation and release notes. |
Comment by Anton Samets [ 2014 Feb 21 ] |
Ok, thank you for information, I should believe that this issue can probably help another persons. |
Comment by richlv [ 2014 Mar 03 ] |
(1) "there was a bug when removing existing table row 'maintenance status' and adding new row 'maintenance status', the value was made '0'" - can you please point at the issue where this was handled ? we might have to at least document this in the troubleshooting section... <richlv> so apparently... latest 2.0 code still writes invalid data (zeroes) in the database. after upgrade to 2.2, this results in errors. |
Comment by Pavels Jelisejevs (Inactive) [ 2014 Mar 06 ] |
This is caused by the fix made in |
Comment by Pavels Jelisejevs (Inactive) [ 2014 Mar 06 ] |
RESOLVED for:
sasha Successfully tested! CLOSED |
Comment by Pavels Jelisejevs (Inactive) [ 2014 Mar 10 ] |
Fixed in 2.2.3rc1 r43317 and 2.3.0 r43321. CLOSED. |