
Zun action APIs (i.e. exec, top, etc.) will return 500 if Docker return 409 (Conflict). Below are observations: * Docker will validate container state before executing a specific action, and raise state conflict (409) error if the state of the container doesn't allow the action to perform. For example, 'exec' is not allowed if container is on state 'Stopped'. * Zun will do a similar state validation in zun-api. * Zun will sync the container states from Docker every 60 seconds. As a result, the state in Zun and Docker might be different during the 60 seconds interval. This 500 error happened if the state between Zun and Docker is out-of-sync (sometimes in between the 60 seconds). This makes the state validation passed in Zun but failed in Docker. Change-Id: If1db262881ac89c62d5a2e7f3cfe67a09724ef5a Closes-Bug: #1723499
Team and repository tags
Zun
Container Management service for OpenStack
Zun (ex. Higgins) is a Container Management service for OpenStack. It aims to provide an OpenStack API for launching and managing containers backed by different container technologies.
- Free software: Apache license
- Get Started: https://docs.openstack.org/zun/latest/contributor/quickstart.html
- Documentation: https://docs.openstack.org/zun/latest/
- Source: https://git.openstack.org/cgit/openstack/zun
- Bugs: https://bugs.launchpad.net/zun
- Blueprints: https://blueprints.launchpad.net/zun
- REST Client: https://git.openstack.org/cgit/openstack/python-zunclient
Features
- TODO
Description
Languages
Python
99.3%
Shell
0.7%