Zun

Activity log for bug #1644570

Date Who What changed Old value New value Message
2016-11-24 14:27:18 hongbin bug added bug
2016-11-24 14:27:32 hongbin zun: status New Triaged
2016-11-24 14:27:36 hongbin zun: importance Undecided Low
2016-11-24 14:27:45 hongbin zun: importance Low Wishlist
2016-11-24 14:30:00 hongbin description See @Shubham's comment in review https://review.openstack.org/#/c/396896/ : If we are at this line then we can safely assume that sandbox container for this container was started successfully. But here container creation has failed but respective sandbox container will still be in running state. Should we stop corresponding sandbox container? If we do not do that then we will have sandbox containers piled up for each failed instance of container create . Right now, the sandbox container is always running when the normal container is created. An improvement is to stop the sandbox container when the normal container is stopped. Consider this as an optional improvement. See @Shubham's comment in review https://review.openstack.org/#/c/396896/ :   If we are at this line then we can safely assume that sandbox container for this container was started successfully. But here container creation has failed but respective sandbox container will still be in running state. Should we stop corresponding sandbox container?   If we do not do that then we will have sandbox containers piled up for each failed instance of container create . Right now, the sandbox container is always running when the normal container is created. An improvement is to stop the sandbox container when the normal container is stopped. Consider this as an optional improvement. We don't need this right away.
2016-11-25 02:14:57 Pradeep Kumar Singh zun: assignee Pradeep Kumar Singh (pradeep-singh-u)
2016-12-07 03:48:59 Pradeep Kumar Singh zun: status Triaged In Progress
2016-12-28 11:17:57 aditi sharma zun: status In Progress Fix Committed