stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Eppel (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (STRATOS-974) [Grouping][testing] - single cartridge, VM is not restored after being killed
Date Mon, 17 Nov 2014 23:13:34 GMT

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

Martin Eppel updated STRATOS-974:
---------------------------------
    Description: 
I deployed a application with single cartridge, no group.
After VM comes up, deleted VM and expected a new instance to be spun up - no instance was
spun up. Logs are attached

As it turned out the VM eventually came up, but it took a long time. Subsequent tests didn't
show the same issue, VM comes up as expected. 
It might still be a good idea to analyze the logs to see if anything unusual happened. Added
the log file which has all the scenarios (original which took a long time and all subsequent
retries)

app definition:
 
{
  "applicationId": "test_app5",
  "alias": "myapp5",
  "components": {
    "groups": [
    ],
    "subscribables": [
      {
        "type": "cisco-sample-vm",
        "alias": "c1xxx"
      }
    ]
  },
  "subscribableInfo": [
    {
      "alias": "c1xxx",
      "deploymentPolicy": "static-1-Core",
      "autoscalingPolicy": "economyPolicy",
      "privateRepo": "true",
      "repoPassword": "password",
      "repoURL": "http://xxx:10080/git/default.git",
      "repoUsername": "user"
    }
  ]
}


  was:
I deployed a application with single cartridge, no group.
After VM comes up, deleted VM and expected a new instance to be spun up - no instance was
spun up. Logs are attached

app definition:
 
{
  "applicationId": "test_app5",
  "alias": "myapp5",
  "components": {
    "groups": [
    ],
    "subscribables": [
      {
        "type": "cisco-sample-vm",
        "alias": "c1xxx"
      }
    ]
  },
  "subscribableInfo": [
    {
      "alias": "c1xxx",
      "deploymentPolicy": "static-1-Core",
      "autoscalingPolicy": "economyPolicy",
      "privateRepo": "true",
      "repoPassword": "password",
      "repoURL": "http://xxx:10080/git/default.git",
      "repoUsername": "user"
    }
  ]
}



> [Grouping][testing] - single cartridge, VM is not restored after being killed
> -----------------------------------------------------------------------------
>
>                 Key: STRATOS-974
>                 URL: https://issues.apache.org/jira/browse/STRATOS-974
>             Project: Stratos
>          Issue Type: Bug
>          Components: Autoscaler
>    Affects Versions: 4.1.0 M4
>            Reporter: Martin Eppel
>         Attachments: wso2carbon.log.gz
>
>
> I deployed a application with single cartridge, no group.
> After VM comes up, deleted VM and expected a new instance to be spun up - no instance
was spun up. Logs are attached
> As it turned out the VM eventually came up, but it took a long time. Subsequent tests
didn't show the same issue, VM comes up as expected. 
> It might still be a good idea to analyze the logs to see if anything unusual happened.
Added the log file which has all the scenarios (original which took a long time and all subsequent
retries)
> app definition:
>  
> {
>   "applicationId": "test_app5",
>   "alias": "myapp5",
>   "components": {
>     "groups": [
>     ],
>     "subscribables": [
>       {
>         "type": "cisco-sample-vm",
>         "alias": "c1xxx"
>       }
>     ]
>   },
>   "subscribableInfo": [
>     {
>       "alias": "c1xxx",
>       "deploymentPolicy": "static-1-Core",
>       "autoscalingPolicy": "economyPolicy",
>       "privateRepo": "true",
>       "repoPassword": "password",
>       "repoURL": "http://xxx:10080/git/default.git",
>       "repoUsername": "user"
>     }
>   ]
> }



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

Mime
View raw message