Bug 1211069

Summary: [RFE] [RDO-Manager] [discoverd] Add possibility to kill node discovery
Product: [Community] RDO Reporter: Jaromir Coufal <jcoufal>
Component: openstack-ironic-discoverdAssignee: mkovacik
Status: CLOSED CURRENTRELEASE QA Contact: Toure Dunnon <tdunnon>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: trunkCC: dtantsur, hbrock, mburns, mkovacik, nbarcet
Target Milestone: ---Keywords: RFE, Triaged
Target Release: trunk   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-17 18:25:43 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 Jaromir Coufal 2015-04-12 18:50:31 UTC
At the moment there is no way how to kill ironic discovery than to wait for timeout (few hours). So now when user realizes that discovery got stuck, he very likely has to wait few hours without possibility to kill the process and start it again.

Comment 1 Dmitry Tantsur 2015-04-15 16:00:49 UTC
Upstream blueprint: https://blueprints.launchpad.net/ironic-discoverd/+spec/abort-introspection

But we're past FF for discoverd 1.1 series. Are we ok with cherry-picking such a big change? Or will we track discoverd 1.2 instead?

also note that timeout defaults to 1 hr and can be changed via 'timeout' option of discoverd.conf

Comment 3 mkovacik 2016-02-26 11:57:34 UTC
Patch merged in upstream-inspector upstream:
https://github.com/openstack/ironic-inspector/commit/7a3d93700e37a32257ea16ef5cca43e060d3ea9a

Comment 4 Christopher Brown 2017-06-17 16:46:54 UTC
We now have this:

https://docs.openstack.org/developer/tripleo-docs/troubleshooting/troubleshooting-nodes.html

so this can be closed.

Comment 5 Dmitry Tantsur 2017-06-17 18:25:43 UTC
Wow, that's an old bug. Thanks, it can be closed indeed.