Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 25 Oct 2013 09:34:30 +0000 (UTC)
From: "Anshul Gangwar (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12672086.1380777172685.1487.1382693670568@arcas>
In-Reply-To: <JIRA.12672086.1380777172685@arcas>
References: <JIRA.12672086.1380777172685@arcas>
Subject: [jira] [Resolved] (CLOUDSTACK-4792) Invalid SMTP breaks HA
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Anshul Gangwar resolved CLOUDSTACK-4792.
----------------------------------------

    Resolution: Fixed

merged to 4.2

> Invalid SMTP breaks HA
> ----------------------
>
>                 Key: CLOUDSTACK-4792
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4792
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Anshul Gangwar
>            Assignee: Anshul Gangwar
>            Priority: Critical
>             Fix For: 4.2.1
>
>
> Putting an invalid smtp ip in alert.smtp.host can potentially stop HA from working. If the smtp ip is listening but does not send a proper HELO HA hangs and will not proceed. It seems as if the code (agent.manager.AgentManagerImpl) doesn't receive a timeout it will not proceed.
> I tried putting a bogus ip in alert.smtp.host but HA worked fine. I believe we need to make HA independent of smtp alerts or at least put in a timeout so HA proceeds.


--
This message was sent by Atlassian JIRA
(v6.1#6144)