New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NPE when no Step in execution plan #152

Closed
malonem opened this Issue Aug 1, 2012 · 2 comments

Comments

Projects
None yet
2 participants
@malonem

malonem commented Aug 1, 2012

This happens after the user selects a plan, but then deselects the parent Step and executes the plan.

Glu: 4.3.1

Error 500: Executing action [execute] of controller [org.linkedin.glu.console.controllers.PlanController] caused exception: null
Servlet: grails
URI: /console/grails/plan/execute.dispatch
Exception Message: 
Caused by: 
Class: PlanController 
At Line: [122] 
Code Snippet:
Stack Trace:
java.lang.NullPointerException
    at org.linkedin.glu.provisioner.plan.impl.StepExecutionContext.createExecutor(StepExecutionContext.java:102)
    at org.linkedin.glu.provisioner.plan.impl.StepExecutionContext.executePlan(StepExecutionContext.java:120)
    at org.linkedin.glu.provisioner.plan.impl.PlanExecutor.executePlan(PlanExecutor.java:120)
    at org.linkedin.glu.orchestration.engine.deployment.DeployerImpl.executePlan(DeployerImpl.java:58)
    at org.linkedin.glu.orchestration.engine.deployment.DeploymentServiceImpl.executeDeploymentPlan(DeploymentServiceImpl.groovy:306)
    at org.linkedin.glu.orchestration.engine.deployment.DeploymentService$executeDeploymentPlan.call(Unknown Source)
    at org.linkedin.glu.orchestration.engine.deployment.AuditedDeploymentService.executeDeploymentPlan(AuditedDeploymentService.groovy:51)
    at org.linkedin.glu.orchestration.engine.deployment.DeploymentService$executeDeploymentPlan.call(Unknown Source)
@ypujante

This comment has been minimized.

Member

ypujante commented Aug 1, 2012

Hmmm... Thanks for reporting, I will look into it.

ypujante added a commit that referenced this issue Aug 15, 2012

@ypujante

This comment has been minimized.

Member

ypujante commented Aug 15, 2012

Fixed with 4.5.0

@ypujante ypujante closed this Aug 15, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment