Wrong status of the node that was disabled before reset and then enabled

[Andrey Sledzinskiy]

{"build_id": "2014-02-19_01-17-30", "mirantis": "no", "build_number": "160", "nailgun_sha": "a3fedc45a4f74418a5d56efa5f8170a55ce53d9a", "ostf_sha": "f86abe5544b5ffcf621e0c450bca15737c92361f", "fuelmain_sha": "0b9ba969d1cff3d9de78d9feb4fb0f4539fc74de", "astute_sha": "581643fb9ace27282150fa3951660a9796acb867", "release": "4.1", "fuellib_sha": "8f5fc7f397646933ffba3acab8bb665756caa58b"}

Steps:
1. Create environment with default settings
2. Add controller, compute, cinder node and deploy claster
3. After successful deployment make cinder node offline
4. Open actions tab and click Reset
5. After successful reset make cinder node online

Expected - cinder node is bootstrapped and status of the node is Pending addition
Actual - cinder node is bootstrapped but status of the node is Discovered and status won't change even after re-deploy (see attached screen and snapshot)

[Evgeniy L (rustyrobot)]

Andrey, did it boot to bootstrap after you turned it on? Ot is it about status on UI only?

[Andrey Sledzinskiy (asledzinskiy)]

Yes, it is about status on UI only

[Artem Roma (aroma-x)]

Cannot reproduce. Have been using iso built from master. Move status to incomplete.

[Andrey Sledzinskiy (asledzinskiy)]

Bug isn't reproduced now on {"build_id": "2014-04-18_01-00-26", "mirantis": "yes", "build_number": "112", "nailgun_sha": "cd0f700fb38952139d55d26cc5d97940ce4e6c34", "production": "dev", "ostf_sha": "1ac04769cc8034438ccf1176860b25d0f5601c4a", "fuelmain_sha": "d1c962210f2dd88a2a810a52572597ea9e82d36f", "astute_sha": "0cb0b26773bd269000a14748e8ba49419462ecaf", "release": "5.0", "fuellib_sha": "6c7a341ce529d250e3e95d85361ada91f3f87686"}