[
https://issues.apache.org/jira/browse/STRATOS-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Eppel updated STRATOS-1345:
----------------------------------
Attachment: application.json
cartridge-groups.json
wso2carbon-debug.log
wso2carbon-debug-2nd-subscription.log
> Stratos 4.1: Nested grouping scenario - not all cartridge instances are spun
> up
> -------------------------------------------------------------------------------
>
> Key: STRATOS-1345
> URL: https://issues.apache.org/jira/browse/STRATOS-1345
> Project: Stratos
> Issue Type: Bug
> Components: Cloud Controller
> Affects Versions: 4.1.0 Beta
> Reporter: Martin Eppel
> Attachments: application.json, cartridge-groups.json,
> wso2carbon-debug-2nd-subscription.log, wso2carbon-debug.log
>
>
> In a nested grouping scenario (see attached artifacts) with 4 defined
> cartridge types not all instances are spun up, see also email thread:
> "Testing stratos 4.1 - nested grouping fails to deploy with unequal cartridge
> types ? on the dev list. Occasionally all instances are spun up. As it seems,
> this happens only when the application is deployed right after starting up
> stratos (see log wso2carbon-debug.log). If the application is removed and
> redeployed all instances will start up correctly (see
> wso2carbon-debug-2nd-subscription.log).
> Attached log files and artifacts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)