Deployment hang when last action call used Murano Agent

[Stan Lagun]

When action get called and that action sends something to Murano Agent all subsequent deployments or action calls that also send commands to agent are very likely to hang

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/159482

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/159482
Committed: https://git.openstack.org/cgit/stackforge/murano/commit/?id=83ba5fa73187dd821f29bc6faf7ea992fb4844a3
Submitter: Jenkins
Branch: master

commit 83ba5fa73187dd821f29bc6faf7ea992fb4844a3
Author: Stan Lagun <email address hidden>
Date: Thu Feb 26 17:24:24 2015 +0300

    Fixes agent call may hanged upon action call

    When action called AgentListener automatically starts listening upon
    first EP send to the agent. But Environment.deploy() were the only
    place where AgentLister was stopped. So when action other than
    Environment.deploy() was called there is no one to stop listener.
    Thus on each action call new listener on the same RabbitMQ queue
    was started causing listeners to steal messages from each other.
    Agent.call() that never received response from agent caused
    deployment/action hang.

    Change-Id: Ia778c816a0e2f57d1f694fd1f128848f61b21a2d
    Closes-Bug: #1425963

[Serg Melikyan (smelikyan)]

Fixed by https://review.openstack.org/159270 in stable/juno