[ 
https://issues.apache.org/jira/browse/AMBARI-14564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Laszlo Puskas updated AMBARI-14564:
-----------------------------------
    Attachment: AMBARI-14564.v1.patch

> Fix unit test failures 
> -----------------------
>
>                 Key: AMBARI-14564
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14564
>             Project: Ambari
>          Issue Type: Bug
>          Components: alerts, ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Laszlo Puskas
>            Assignee: Laszlo Puskas
>             Fix For: 2.2.1
>
>         Attachments: AMBARI-14564.v1.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Some unit tests started to fail after a previously introduced change.
> Context:
> - subsequently changing alert targets (changing alert groups attached to 
> alert targets) resulted in ConcurrentModificationException
> - changing the code that updates alert groups fixed the CME, however another 
> issue arose: after subsequently changing alert targets, at a given point 
> changes were not reflected after save
> - excluding the relationship between alert targets and alert groups from 
> caching solved the problem
> This solution apparently caused a regression in the cluster deletion process.
> This issue is about removing @Ignore annotations and providing a good 
> implementation for the causing issue. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to