Improve mistral errors logging in tripleo
Bug #1611101 reported by
Sagi (Sergey) Shnaidman
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mistral |
Invalid
|
Low
|
Unassigned | ||
| tripleo |
Invalid
|
Wishlist
|
Unassigned | ||
Bug Description
So far mistral failure logs are thrown into console file without any reference, just pure python errors:
2016-08-08 07:21:14.862745 | (pymysql.
Should be nice logging with identifying service which failed (mistral), ERROR prefix, text of failure.
| description: | updated |
| Changed in tripleo: | |
| importance: | Undecided → Low |
| Changed in tripleo: | |
| status: | New → Triaged |
| milestone: | none → newton-3 |
| Changed in tripleo: | |
| milestone: | newton-3 → newton-rc1 |
| Changed in tripleo: | |
| milestone: | newton-rc1 → newton-rc2 |
| Changed in tripleo: | |
| milestone: | newton-rc2 → ocata-1 |
Revision history for this message
| Dougal Matthews (d0ugal) wrote | #1 |
| Changed in mistral: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in tripleo: | |
| milestone: | ocata-1 → ocata-2 |
| Changed in tripleo: | |
| milestone: | ocata-2 → ocata-3 |
| Changed in tripleo: | |
| milestone: | ocata-3 → pike-1 |
| Changed in tripleo: | |
| milestone: | pike-1 → pike-2 |
| Changed in tripleo: | |
| milestone: | pike-2 → pike-3 |
Revision history for this message
| Ryan Brady (rbrady) wrote | #2 |
| Changed in tripleo: | |
| importance: | Low → Wishlist |
| milestone: | pike-3 → none |
| status: | Triaged → Invalid |
| Changed in mistral: | |
| status: | Triaged → Incomplete |
Revision history for this message
| Dougal Matthews (d0ugal) wrote | #3 |
| Changed in mistral: | |
| status: | Incomplete → Invalid |
To post a comment you must log in.
Can you provide more details about this? Unfortunately the link to the CI output doesn't exist anymore. What commands or actions are causing this output? Can you still reproduce it?