[
https://issues.apache.org/jira/browse/STRATOS-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185536#comment-14185536
]
Raghavendra Rangrej commented on STRATOS-915:
---------------------------------------------
I see Faulty member logs (see tas-si ) and also its attempt to Terminate the
instance which fails.
When it decides to relaunch the cartridge as declared to be Faulty,, why it
doesn't change its state to nonActive?
Is there any counter on number of Faulty messages which lead to relaunch?
When does CLI declare a Active cartridge to be non Active?. As stated before,
relaunch attempts are on but CLI declares Active.
> Vcloud: cartridge gets relaunched even though active
> ----------------------------------------------------
>
> Key: STRATOS-915
> URL: https://issues.apache.org/jira/browse/STRATOS-915
> Project: Stratos
> Issue Type: Bug
> Components: Cloud Controller
> Affects Versions: 4.0.0
> Environment: vcloud, stratos
> Reporter: Raghavendra Rangrej
> Attachments: wso2.log.tar.gz
>
>
> Hello,
> We are seeing an issue with stratos in vcloud.
> When we launch the cartridges we see that they become Active. After few hours
> the CLI shows they are active but we see that cartridge is tried to be
> getting relaunched.
> Issue here is, stratos CLI and other stratos components are out of sync.
> We expect a Active cartridge shouldn't be relaunched. .
> As the cartridges are configured with a a network of limited IP address, we
> see that next launch fail with no IP address available and it keeps on
> happenning launching 100s of vapps.
> Can you look in to this issue?
> It is blocking us in our orchestration testing.
> The wso2 log will be attached here with
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
