2014-02-20 09:29:57 |
Andrey Sledzinskiy |
description |
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) |
{"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) |
|