Details
-
Bug
-
Resolution: Done
-
Major
-
6.x.x
Description
If you create a container using controller's REST API and set status to started in this request (<status>STARTED</status>), the container will not be started. However, the state of the container on the controller will be STARTED. This can be seen using both REST API and GUI. When you try to get the container info directly from KIE Server instance, you will see that it does not exist yet. I think there are two options how to fix this:
- Ignore status field in container creation requests but set the container state correctly to STOPPED.
- Start the container automatically if STARTED state is specified in the request.