App startup failure results in deployer being blocked

Bug #1523635 reported by Ashish on 2015-12-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

At times we have seen that an app deploy results in app being in starting_app stage. During this time deployer is blocked because it is continuously trying to ping the recently deployed heat stack. Running any command for example "solum app delete <app_id>"
just holds up in rabbitmq because deployer is blocked for the previous operation.

Ashish (ashish-jain14) on 2015-12-07
tags: added: solum-deployer
Ashish (ashish-jain14) on 2016-02-11
Changed in solum:
assignee: nobody → Ashish (ashish-jain14)
Changed in solum:
importance: Undecided → High
milestone: none → next-mitaka
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers