Once provision/deployment started at some point service receiverd grab a 100% resources of one core and remains in that state very long time.
/api/versions
{"build_id": "2014-10-15_17-45-06", "ostf_sha": "de177931b53fbe9655502b73d03910b8118e25f1", "build_number": "23", "auth_required": true, "api": "1.0", "nailgun_sha": "d9facd6a32293da786b738d1a9b1459e36aa3006", "production": "docker", "fuelmain_sha": "18b8264c17782c4dbb77412d3d4fe256a2083d7d", "astute_sha": "c3e7c7a18528cf9acca48021488a93dff74f5c97", "feature_groups": ["mirantis"], "release": "6.0", "release_versions": {"2014.2-6.0": {"VERSION": {"build_id": "2014-10-15_17-45-06", "ostf_sha": "de177931b53fbe9655502b73d03910b8118e25f1", "build_number": "23", "api": "1.0", "nailgun_sha": "d9facd6a32293da786b738d1a9b1459e36aa3006", "production": "docker", "fuelmain_sha": "18b8264c17782c4dbb77412d3d4fe256a2083d7d", "astute_sha": "c3e7c7a18528cf9acca48021488a93dff74f5c97", "feature_groups": ["mirantis"], "release": "6.0", "fuellib_sha": "b3f6943326dac065464555a320ed4b2d4bdbb699"}}}, "fuellib_sha": "b3f6943326dac065464555a320ed4b2d4bdbb699"}
I believe that's because it's getting a lot of stuff from Astute over RPC - like progress values. We need to take a look on logs, and ideally profile - what procedures take that much of CPU.
Alex - can you attach a diagnostic snapshot please? Should help to faster resolve an issue.