failed to start container when scanbox isn't running

[[e-mail]]

1,
[root@tfg-104 zun(keystone_admin)]# zun list
+--------------------------------------+--------+--------+---------+------------+------------+-------+
| uuid | name | image | status | task_state | addresses | ports |
+--------------------------------------+--------+--------+---------+------------+------------+-------+
| 838f35f2-0ead-43e1-a19f-c9276d3256eb | test | test:1 | Stopped | None | 172.17.0.2 | [] |
+--------------------------------------+--------+--------+---------+------------+------------+-------+

2,
[root@tfg-104 zun(keystone_admin)]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c6820a4093d1 test:1 "supervisord -c /etc/" 18 hours ago Exited (128) 24 minutes ago zun-838f35f2-0ead-43e1-a19f-c9276d3256eb
c3ec9b47d833 kubernetes/pause "/pause" 18 hours ago running zun-sandbox-838f35f2-0ead-43e1-a19f-c9276d3256eb

3,
docker stop c3ec9b47d833

4,
[root@tfg-104 zun(keystone_admin)]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c6820a4093d1 test:1 "supervisord -c /etc/" 18 hours ago Exited (128) 24 minutes ago zun-838f35f2-0ead-43e1-a19f-c9276d3256eb
c3ec9b47d833 kubernetes/pause "/pause" 18 hours ago Exited (128) 24 minutes ago zun-sandbox-838f35f2-0ead-43e1-a19f-c9276d3256eb

5,
zun start test

6,
[root@tfg-104 zun(keystone_admin)]# zun list
+--------------------------------------+--------+--------+---------+------------+------------+-------+
| uuid | name | image | status | task_state | addresses | ports |
+--------------------------------------+--------+--------+---------+------------+------------+-------+
| 838f35f2-0ead-43e1-a19f-c9276d3256eb | test | test:1 | Stopped | None | 172.17.0.2 | [] |
+--------------------------------------+--------+--------+---------+------------+------------+-------+

After starting the container, the status is still Stopped, but there's no error.

I think we should check the status of scanbox, if it's not running, we should raise a error.

[hongbin (hongbin034)]

@Feng,

This is an interesting bug report. I agree that we need to handle this counter case in "start" . Perhaps, the "start" command should check the status of the sandbox first and start it if it is "stopped"? Eventually, I agree with you that Zun should return an error if we are not able to start the sandbox.

[hongbin (hongbin034)]

There is no activity for fixing this bug for a while. I am going to remove assignee so that other contributors can take it.