You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/11/25 14:16:12 UTC

[jira] [Commented] (STRATOS-923) vcloud: Status not updated to Inactive for faulty cartridge

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

ASF GitHub Bot commented on STRATOS-923:
----------------------------------------

GitHub user chamilad opened a pull request:

    https://github.com/apache/stratos/pull/120

    [STRATOS-923] - fixed

    Faulty members are not directly terminated, they are added to obsolete list and let Drools rules issue terminate calls. Furthermore, their status is changed to ReadyToShutdown on terminate call. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/chamilad/stratos member-fault-obsolete

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/stratos/pull/120.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #120
    
----
commit 9255d0ee6c754ad83e1ee1d58f5a8eb39f6b9855
Author: Chamila de Alwis <ch...@wso2.com>
Date:   2014-11-25T13:13:18Z

    [STRATOS-923] - fixed

----


> vcloud: Status not updated to Inactive for faulty cartridge
> -----------------------------------------------------------
>
>                 Key: STRATOS-923
>                 URL: https://issues.apache.org/jira/browse/STRATOS-923
>             Project: Stratos
>          Issue Type: Bug
>          Components: CLI, Cloud Controller, Stratos Manager
>    Affects Versions: 4.0.0
>         Environment: vcloud
>            Reporter: Raghavendra Rangrej
>            Priority: Blocker
>         Attachments: wso2.log.boot-issue
>
>
> In follow up with, STRATOS-915, this Jira issue is written.
> In vcloud setup, we saw a behavior where in a cartridge was found to be faulty  and stratos decides to terminate.
> But the cartridge terminate failed for some reason and stratos tries to relaunch the cartridge which too fail because of lack of ip adress in pool.
> While one part of stratos is trying to terminate cartridge and relaunch it, CLI is showing continouslt state as Active for this cartridge.
> This needs to be fixed. The log of STRATOS-915 can be used as it isa same issue.



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