docker container failures are not reported back to heat
Bug #1696961 reported by
Damien Ciabrini
This bug report is a duplicate of:
Bug #1723163: puppet apply on the host via ansible never fails.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Triaged
|
High
|
Unassigned | ||
Bug Description
It seems that there has been a change lately in how docker-cmd runs containers, we have noticed that when the command that is being run returns an error code (e.g. 1), the docker-cmd hook does not catch that: no error log in the journal, and apparently the error code is not return appropriately.
Consequently, the overcloud deploy is not notified of the error and happily continues deploying whereas it should stop right away.
| Changed in tripleo: | |
| status: | New → Triaged |
| tags: | added: containers |
| Changed in tripleo: | |
| milestone: | none → pike-3 |
| importance: | Undecided → High |
| Changed in tripleo: | |
| milestone: | pike-3 → pike-rc1 |
| Changed in tripleo: | |
| milestone: | pike-rc1 → pike-rc2 |
| Changed in tripleo: | |
| milestone: | pike-rc2 → queens-1 |
Revision history for this message
| Damien Ciabrini (dciabrin) wrote | #1 |
To post a comment you must log in.
After some digging into the problem with Michele, we pinpointed it in https:/
I'm closing this bug as a duplicate.