when using fuel cli for provision, deploy env.changes and env.status is not updates
Bug #1418744 reported by
Andrew Woodward
This bug report is a duplicate of:
Bug #1449086: Deploy button still shows "Deploy Changes" after provisioning was started from CLI.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Python (Deprecated) | ||
| 6.0.x |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
| 6.1.x |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
| 7.0.x |
Confirmed
|
Medium
|
Fuel Python (Deprecated) | ||
Bug Description
when the manual task executions are completed (usually by fuel cli) the enviornment changes, and status are not updated.
steps to reproduce:
fuel env --create --name test --release 2 --mode ha
fuel --env 1 node set --node 1 --role controller
fuel --env 1 node --node 1 --provision
fuel --env 1 node --node 1 --deploy
fuel env --env 1 should show that there are no changes and status ready.
effects all 6.x and 5.x versions
| Changed in fuel: | |
| milestone: | none → 6.1 |
| tags: | added: module-tasks |
| tags: |
added: module-nailgun removed: module-tasks |
| Changed in fuel: | |
| milestone: | 6.1 → 7.0 |
| Changed in fuel: | |
| milestone: | 7.0 → 6.1 |
| status: | Confirmed → New |
| Changed in fuel: | |
| status: | New → Confirmed |
| Changed in fuel: | |
| milestone: | 6.1 → 7.0 |
| tags: | added: release-notes |
Revision history for this message
| Evgeniy L (rustyrobot) wrote | #1 |
To post a comment you must log in.
It was removed from 6.1 because ticket has Medium priority, also it has 0 deployment impact, which means cluster will function without problems.
Also separate provisioning and deployment were designed for fuel hackers and should not be used for regular deployment.