Wrong node provision detection via target\n
Bug #1455883 reported by
Vladimir Sharshov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Committed
|
High
|
Vladimir Sharshov | ||
Bug Description
Both nodes 1,2 were successfully provisioned
http://
But then
| Changed in fuel: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to fuel-astute (master) | #1 |
| Changed in fuel: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit cb655a9a9ad2684
Author: Vladimir Sharshov (warpc) <email address hidden>
Date: Sun May 17 02:30:26 2015 +0300
Send correct message about failed provision node, fix node type detection
We use 'hook' role because we do not need to calculate
multirole progress. Also for provision we do need role
at all. But here we use DeploymentProxy
need role.
Fix node type detection: 'target\n' or 'target' should
be detected as 'target'
Change-Id: Ibb87bf4a0b0abd
Closes-Bug: #1455824
Closes-Bug: #1455883
Co-Authored-By: Vladimir Kozhukalov <email address hidden>
Co-Authored-By: Łukasz Oleś <email address hidden>