Message about resetting environment after stopping deploy on the post_deployment stage
Bug #1464326 reported by
Alexander Kurenyshev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Ihor Kalnytskyi |
Bug Description
Steps to reproduce:
1) Install master node
2) Create environment
3) Deploy cluster
4) Wait until post_deployment tasks will be executed
5) Stop Deploy
Expected result:
Deploy is stopped. There is a message from astute that we need to reset environment.
Actual result:
Deploy is stopped. Nodes are in the ready state, Deploy Changes button is disabled. (see picture)
tags: | added: module-nailgun |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Igor Kalnitsky (ikalnitsky) |
status: | Confirmed → In Progress |
To post a comment you must log in.
@Alexander,
Why do you expect message that we need to reset env? I always thought we shouldn't reset env after stopping.
As far as I know the Stop feature was designed the following way:
* if we didn't deploy critical node roles - we're resetting entire
* if we do have deployed critical node roles - we stop deploying new nodes and keep what was deployed as is (since it should be a working openstack cluster).
Looks invalid to me. Please correct me if I'm wrong.