Comment 3 for bug 1565712

from nailgun app.log:

2016-04-04 09:43:09.734 INFO [7efc8ad2e880] (base) Trying to start deployment at environment '1'
2016-04-04 09:43:09.795 INFO [7efc8ad2e880] (manager) Trying to start deployment at cluster 'Ironic'
2016-04-04 09:43:09.826 ERROR [7efc8ad2e880] (base) Error during execution of deployment task on environment '1': Cannot perform the actions because there are running tasks [<Task 'provision' 1d6530db-69fb-4019-b68e-5ebe0f85a6ff (1) running>, <Task 'deployment' 2f148a40-c2d6-4d6d-b8cc-493e40c18b6f (1) running>]
2016-04-04 09:43:09.826 ERROR [7efc8ad2e880] (base) Unexpected exception occured
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/nailgun/api/v1/handlers/base.py", line 285, in content_json
    resp = func(cls, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/nailgun/api/v1/handlers/base.py", line 564, in PUT
    task = task_manager.execute()
  File "/usr/lib/python2.7/site-packages/nailgun/task/manager.py", line 174, in execute
    self.check_no_running_deployment(self.cluster)
  File "/usr/lib/python2.7/site-packages/nailgun/task/manager.py", line 132, in check_no_running_deployment
    'running tasks {0}'.format(tasks_q.all()))
DeploymentAlreadyStarted: Cannot perform the actions because there are running tasks [<Task 'provision' 1d6530db-69fb-4019-b68e-5ebe0f85a6ff (1) running>, <Task 'deployment' 2f148a40-c2d6-4d6d-b8cc-493e40c18b6f (1) running>]

from api.log:

016-04-04 09:43:09.725 DEBUG [7efc8ad2e880] (logger) Request PUT /api/clusters/1/changes from 172.18.196.49:39902 {}
2016-04-04 09:43:09.828 ERROR [7efc8ad2e880] (logger) Response code '500 Internal Server Error' for PUT /api/clusters/1/changes from 172.18.196.49:39902
2016-04-04 09:43:10.185 DEBUG [7efc8ad2e880] (logger) Request PUT /api/nodes/agent/ from 10.109.26.4:46522

Looks like here we have the same issue as we have in this bug: https://bugs.launchpad.net/fuel/+bug/1561942

According to the bug#1561942, the fix is merged.

Verified on fuel 10.0 ISO build 464:
using similar environment settings as provided in the bug description, i couldn't reproduce the issue.