[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693799#comment-13693799
 ] 

Thomas O'Dowd commented on CLOUDSTACK-3204:
-------------------------------------------

Ok. This seems unrelated to memory. I shut stuff down and cleaned up more 
memory. restarted and had 4 alerts. Went to Dashboard -> view alerts and 
deleted the alerts in different order. Mostly they worked but one of them 
didn't. It was a different one this time. Not usage-server alert but management 
server startup notice. It didn't disappear from the list even though it the 
deleted popup came. Then hovered over it and the same error popup happened. 

Checked the terminal and no memory exceptions so that doesn't seem to cause the 
issue. No errors were logged either, except on the gui.
If I navigate back to the dashboard, then all alerts are gone as expected, so 
it really was deleted... just the gui didn't update or something.

Thanks for the tip Prasanna. I'll try that separately.
                
> Dashboard deleted alert remains and causes popup error on quickview hover.
> --------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3204
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3204
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.2.0
>         Environment: Chrome on Linux
>            Reporter: Thomas O'Dowd
>
> Latest master branch developer build when running devcloud.
> 1. Browse to dashboard.
> 2. View Alerts 
> 3. select quickview on an alert (I did this on usage server not running 
> alert).
> 4. select delete on that alert from the quickview popup.
> 5. alert remains on list
> 6. hover over that alerts quickview again.
> result is a popup error.
> "Unable to execute API command listalerts due to invalid value. Invalid 
> parameter id value=f878d88c-8ac0-4c99-b54f-90d4e9809958 due to incorrect long 
> value format, or entity does not exist or due to incorrect parameter 
> annotation for the field in api cmd class."
> Expected result would be that after step 4, the alert is removed from the 
> alert list.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to