Yes I could see a design issue in the logic which tries to acquire locks in
the Topology Manager. The problem is that it does not create lock objects
on demand, rather locks are pre-created. As a result there is a possibility
of raising following errors/warning if lock object is not found:
[2015-0
Hi,
When testing the single-cartridge sample for OpenStack, there were several
occasions of instances not being spawned on the IaaS, without showing any
errors on the logs. The log output contains "Application deployed
successfully", however there are few warning messages related acquiring the
loc
