No feedback when websocket is down
Bug #1619712 reported by
Julie Pichon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Julie Pichon |
Bug Description
If for some reason the client cannot establish a connection to the websocket when launching a Mistral workflow, the user gets no feedback on the command and only an unhelpful 'Connection refused' message.
$ openstack overcloud node introspect --all-manageable
Waiting for introspection to finish...
[Errno 111] Connection refused
Bug 1618445 is somewhat related (Zaqar timeouts).
Steps to reproduce:
1. Shut down the Zaqar service
2. Run one of the commands that uses a Mistral workflow, e.g. openstack overcloud node introspect --all-manageable
Changed in tripleo: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → newton-rc1 |
Changed in tripleo: | |
assignee: | nobody → Julie Pichon (jpichon) |
Changed in tripleo: | |
milestone: | newton-rc1 → newton-rc2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/368791
Review: https:/