Nodes disappeared permanently after the environment they belong to is deleted without deployment

[Alexander Maretskiy]

api: '1.0'
astute_sha: aa5aed61035a8dc4035ab1619a8bb540a7430a95
auth_required: true
build_id: 2014-07-29_02-01-14
build_number: '369'
feature_groups:
- mirantis
fuellib_sha: 851b29ac6434c1671078ef293bb25a04dc492f49
fuelmain_sha: 2379783517e4830868f66b5fbab512eec4695679
nailgun_sha: 98ea1ce54f4d084e2533c7ea23aa98551f955ec5
ostf_sha: 9c0454b2197756051fc9cee3cfd856cf2a4f0875
production: docker
release: '5.1'

Steps to reproduce:
  * having a Fuel installed (this bug is reproduced on Czech Lab #2)
  * create new environment (it seems that configuration does not matter): CentOS|Ubuntu / HA|Multinode / QEMU / Nova|Neutron / any number of Controllers and Computes. For specific example, let it be CentOS/Multinode/QEMU/Nova/1+3
  * do not perform extra actions (e.g. deployment, ect), just delete the environment

Expected result:
  * environment is deleted
  * nodes become unavailable for few minutes (typically 3-6 min), then they appear and ready for usage

Actual result:
 * environment is deleted
 * nodes become unavailable permanently and require reboot launched via some non-Fuel interface (e.g. IPMI)

[Dima Shulyak (dshulyak)]

Can you attach disgnostic snapshot?

I want to check agent interaction with nailgun in this case,
i'm pretty sure that bootstraped node should register itself in nailgun db, after it was deleted, without any need for reboot.

[Dima Shulyak (dshulyak)]

Marking this bug as duplicate for this one https://bugs.launchpad.net/fuel/+bug/1349815, it was fixed after you built this iso.