OSTF must be allowed if deployment failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Julia Aranovich |
Bug Description
I had a failure in deployment, and was unable to run Health Check because
"You must deploy your OpenStack environment before running tests against it".
I think this behavior should be changed. I may have failure in, let's say, ceilometer installation, which doesn't affect operability of other OpenStack components. And I should be able to run OSTF to see what is actually functioning.
My ISO:
{"build_id": "2014-05-
Changed in fuel: | |
status: | New → Confirmed |
On UI we check the following cases to lock the tab:
1. deployment task is in progress (this check remains unchanged)
2. environment has 'error' status (will be removed due to the ticket)
3. all nodes in environment have 'ready' status.
My question refers to the third point. Should we check node statuses? If yes, should we add 'error' node statuses as allowable for OSTF?