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

Martin Eppel updated STRATOS-985:
---------------------------------
    Description: 
Testing terminate-all flag: for application / groups see attached json def 
files.

Observed behavior: after killing  "c1alias61", cartridge  "c1alias51" and  
"c1alias71" keep running, "c1alias61" is not being started up.

Expected behavior: after terminating "c1alias61" all VMs should be terminated:
group6 has as members group7, cartridge "c1alias61" and termination behavior: 
"terminate-all". 
Terminating cartridge "c1alias61" requires all members to be killed as well, 
including group7 (which includes members of group7).
group5 has members depending on group6, once group6 is terminated (inactive), 
dependents will be killed as well.

Logs and application definition is attached, please note, VM is being killed 
after time stamp:  TID: [0] [STRATOS] [2014-11-19 00:27:22,272]

  was:
Testing terminate-all flag: for application / groups see attached json def 
files.
Expected behavior: after terminating ""c1alias61" all VMs should be terminated:
group6 has as members group7, cartridge "c1alias61" and termination behavior: 
"terminate-all". 
Terminating cartridge "c1alias61" requires all members to be killed as well, 
including group7 (which includes members of group7).
group5 has members depending on group6, once group6 is terminated (inactive), 
dependents will be killed as well.

Logs and application definition is attached, please note, VM is being killed 
after time stamp:  TID: [0] [STRATOS] [2014-11-19 00:27:22,272]


> [grouping][testing] terminate-all not working in nested group scenario
> ----------------------------------------------------------------------
>
>                 Key: STRATOS-985
>                 URL: https://issues.apache.org/jira/browse/STRATOS-985
>             Project: Stratos
>          Issue Type: Bug
>            Reporter: Martin Eppel
>
> Testing terminate-all flag: for application / groups see attached json def 
> files.
> Observed behavior: after killing  "c1alias61", cartridge  "c1alias51" and  
> "c1alias71" keep running, "c1alias61" is not being started up.
> Expected behavior: after terminating "c1alias61" all VMs should be terminated:
> group6 has as members group7, cartridge "c1alias61" and termination behavior: 
> "terminate-all". 
> Terminating cartridge "c1alias61" requires all members to be killed as well, 
> including group7 (which includes members of group7).
> group5 has members depending on group6, once group6 is terminated (inactive), 
> dependents will be killed as well.
> Logs and application definition is attached, please note, VM is being killed 
> after time stamp:  TID: [0] [STRATOS] [2014-11-19 00:27:22,272]



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

Reply via email to