Bug 1394907 - [RFE] Provide way to reset introspection of node
Summary: [RFE] Provide way to reset introspection of node
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-ironic-inspector-client
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: nlevinki
URL:
Whiteboard: NeedsAllocation
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-14 17:06 UTC by Andreas Karis
Modified: 2020-02-14 18:08 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-29 14:32:57 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2766271 0 None None None 2016-12-02 20:01:17 UTC

Description Andreas Karis 2016-11-14 17:06:17 UTC
Description of problem:
When you have to cancel an Introspection, it's not obvious that you need to run the following 2 commands to get the nodes back into an "Available" state:
1. ironic node-set-provision-state <uuid> provide
2. ironic node-set-power-state <uuid> off

The nodes went from it went from Manageable to Available after that:
openstack baremetal introspection status <uuid>

 It's not obvious that you first need to set the state to "provide" and then set the power state to off. This could be improved by having the unified OpenStack CLI (the openstack command) handle these 2 commands.

Perhaps it could be something like:
openstack baremetal introspection reset

Comment 3 Beth White 2017-07-26 15:22:27 UTC
Hi Julie, Is this something you are already working on?

Comment 4 Julie Pichon 2017-08-14 08:52:33 UTC
Hi Beth, no it's not something I'm currently working on.

A couple of thoughts:
- It sounds like making cancelling introspection easier, should be something specifically for Ironic / Ironic Inspector to consider?
- If not, then the component should probably be moved to python-tripleoclient, which owns some of the baremetal introspection commands... though we've been deprecating them [1] and aim to move away from using the 'baremetal' keyword in the tripleo cli from what I understand.
- I'm not convinced by the Priority being set to High, since there it's possible to do this already with the commands provided in comment 0 (if I understand correctly) and I'm not sure how frequent "cancelling introspection" is as an operation. Perhaps it should be in the Inspector docs [2] as well.

[1] e.g. https://review.openstack.org/#/c/416229/
[2] https://docs.openstack.org/ironic-inspector/latest/user/usage.html

Comment 8 Julie Pichon 2018-01-26 11:12:19 UTC
Moving to HardProv due to introspection-related questions. Still uncertain what the component should be - inspector client? ironic client? tripleo client? The commands for the workaround all seem to use the ironic client but the start/status commands to do with the actual introspection apparently live in python-ironic-inspector-client so moving it there for now. Thanks!

Comment 9 Bob Fournier 2018-08-29 14:32:57 UTC
We can abort an introspection but don't plan on making the changes requested here.


Note You need to log in before you can comment on or make changes to this bug.