fuel-octane doesn't check if service up after upgrade-control
Bug #1499696 reported by
Sergey Murashov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Yuriy Taraday | ||
7.0.x |
Fix Committed
|
High
|
slava valyavskiy |
Bug Description
Steps to reproduce:
1) Launch octane upgrade-control
Actual result:
Octane starts services on new controller, but doesn't check that they are started
Changed in fuel: | |
assignee: | nobody → Fuel Octane Dev Team (fuel-octane) |
Changed in fuel: | |
milestone: | none → 8.0 |
importance: | Undecided → High |
status: | New → Confirmed |
tags: | added: module-octane |
Changed in fuel: | |
assignee: | Fuel Octane Dev Team (fuel-octane) → Oleg S. Gelbukh (gelbuhos) |
status: | Confirmed → In Progress |
tags: | added: feature-upgrade |
tags: | added: area-octane |
tags: |
added: area-python removed: area-octane |
tags: | added: on-verification |
tags: | removed: on-verification |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: stable/7.0 /review. openstack. org/231199
Review: https:/