Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/

Bug 1214349

Summary: [RFE] Use Ironic API instead of discoverd one for discovery/introspection
Product: [Community] RDO Reporter: Dmitry Tantsur <dtantsur>
Component: rdo-managerAssignee: Hugh Brock <hbrock>
Status: CLOSED EOL QA Contact: Shai Revivo <srevivo>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: KiloCC: mburns
Target Milestone: ---Keywords: RFE
Target Release: Kilo   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-19 15:44:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dmitry Tantsur 2015-04-22 13:54:21 UTC
Discoverd API is somewhat low level. The most important thing is that it does not change node state in Ironic. Instead of calling to discoverd for starting introspection, use node.set_provision_state(uuid, 'inspect'). Introspection status can be followed then by querying node details and looking at provision_state field ('inspecting' while introspection is going on, 'inspectfail' on failure, 'manageable' on success), error message will be in last_error field.

Comment 3 Chandan Kumar 2016-05-19 15:44:16 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.