Confusing error message on interactive run
Bug #1685521 reported by
hongbin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-zunclient |
Fix Released
|
Medium
|
haobing1 |
Bug Description
If I run a container with an incorrect command in interactive mode, it showed a confusing error message "ERROR: Invalid websocket link when attach ...". This error message is sub-optimal because the root cause of the failure is the container entered an error state (because users specify an incorrect command).
$ zun run -i cirros not-a-command
....
Waiting for container start
Waiting for container start
ERROR: Invalid websocket link when attach container:
We need to fix it by checking the state of the container and failed it with a correct message if the container entered an error state.
Changed in zun: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in zun: | |
importance: | High → Medium |
Changed in zun: | |
assignee: | nobody → haobing1 (haobing1) |
affects: | zun → python-zunclient |
Changed in python-zunclient: | |
status: | Triaged → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/459091 /git.openstack. org/cgit/ openstack/ python- zunclient/ commit/ ?id=a7fce1d2007 352a7304028ecb7 df5b496537d0e7
Committed: https:/
Submitter: Jenkins
Branch: master
commit a7fce1d2007352a 7304028ecb7df5b 496537d0e7
Author: haobing1 <email address hidden>
Date: Sun Apr 23 14:00:26 2017 +0800
Fix confusing error message on interactive run
If run a container with an incorrect command in interactive mode,
it showed a confusing error message "ERROR: Invalid websocket link when attach ...".
This error message is sub-optimal because the root cause of the failure is the container
entered an error state (because users specify an incorrect command).
We need to fix it by checking the state of the container and failed it
with a correct message if the container entered an error state.
Change-Id: I630de2414d5e36 e86b246460a6d24 992b06696e3
Closes-Bug: #1685521