Wrong node provision detection via target\n

Bug #1455883 reported by Vladimir Sharshov
6
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://paste.openstack.org/show/225823/

But then

http://paste.openstack.org/show/225822/

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-astute (master)

Reviewed: https://review.openstack.org/183852
Committed: https://git.openstack.org/cgit/stackforge/fuel-astute/commit/?id=cb655a9a9ad26848bcd9d9ace91857b6f4a0ec15
Submitter: Jenkins
Branch: master

commit cb655a9a9ad26848bcd9d9ace91857b6f4a0ec15
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 DeploymentProxyReporter and
    need role.

    Fix node type detection: 'target\n' or 'target' should
    be detected as 'target'

    Change-Id: Ibb87bf4a0b0abdf5ad0d703bb40cc55ae8ce9104
    Closes-Bug: #1455824
    Closes-Bug: #1455883
    Co-Authored-By: Vladimir Kozhukalov <email address hidden>
    Co-Authored-By: Łukasz Oleś <email address hidden>

Changed in fuel:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.