Description of problem: I select all my nodes and click "Introspect Nodes". The execution fails with the following error for each node: Failed to run action [action_ex_id=57e4fac2-0f94-4bac-92c4-995b0d857b9b, action_cls='<class 'mistral.actions.action_factory.BaremetalIntrospectionAction'>', attributes='{u'client_method_name': u'introspect'}', params='{u'uuid': u'0e83c63b-89bf-4092-a72b-627a8eceae99', u'new_ipmi_username': None, u'new_ipmi_password': None}'] BaremetalIntrospectionAction.introspect failed: <class 'ironic_inspector_client.common.http.ClientError'>: Invalid provision state for introspection: "available", valid states are "['manageable', 'inspectfail', 'enroll', 'inspecting']" For OSP10, a node's provision state must be set to "manageable" prior to starting an introspection. So either one of two things needs to happen: a) The Mistral execution needs to include setting the node to "manageable" prior to running the introspection. b) Include a button on the TripleO UI that allows you to change the provision state of the node. Maybe a button next to "Provide Nodes" that says "Manage Nodes". Version-Release number of selected component (if applicable): OSP 10 openstack-tripleo-ui.1.0.3-1.el7ost How reproducible: Always Steps to Reproduce: 1. Select all registered nodes 2. Click "Introspect Nodes" 3. Get error Actual results: See error above Expected results: No error and successful introspection Additional info:
I hit the same error on OSP9 following the instructions at : https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/sect-Scaling_the_Overcloud.html#sect-Adding_Compute_or_Ceph_Storage_Nodes
Doesn't reproduce for me on RHOS 10 GA. Dan, Could you please provide .json file you've used to register the nodes? Also, have you registered the nodes via UI or CLI? Thanks
Reproduced : openstack-tripleo-ui-3.1.0-4.el7ost.noarch steps: 1. provide a node 2. try to introspect previously provided node Failed to run action [action_ex_id=9f4fb7e4-b573-447c-8e9f-a2d1040eddb9, action_cls='<class 'mistral.actions.action_factory.BaremetalIntrospectionAction'>', attributes='{u'client_method_name': u'introspect'}', params='{u'uuid': u'024c7e70-0e18-4b7b-a76e-0507885f82e2', u'new_ipmi_username': None, u'new_ipmi_password': None}'] BaremetalIntrospectionAction.introspect failed: <class 'ironic_inspector_client.common.http.ClientError'>: Invalid provision state for introspection: "available", valid states are "['manageable', 'inspectfail', 'enroll', 'inspecting']"
*** Bug 1432950 has been marked as a duplicate of this bug. ***
Introduce action that moves available -> manageable Better error message from tripleo-common (mistral)
https://bugs.launchpad.net/tripleo/+bug/1639262
https://bugs.launchpad.net/tripleo/+bug/1594879
*** Bug 1427092 has been marked as a duplicate of this bug. ***
If you run the scenario with the latest OSP12, the introspection appears to start but it never ends until the user presses F5. In fact, the introspection didn't even start because you first have to "unmanage" the nodes. The user should get an error in the GUI if he's trying to introspect nodes before unmanaging them. When unmanaging the node and then introspecting it - the system works fine.
I found the source of the issue. I opened a bug upstream, and I'm waiting for confirmation.
Let me point out that there are two issues at play here. 1. The original bug has been solved like this: instead of setting nodes to manageable before running introspection, we provide a new button on the node list page called "Manage nodes" which can be used to set the nodes to the correct state before introspection. This has the benefit of not obscuring Ironic's states and mechanism. 2. There is a regression in introspection error handling. If introspection fails, the loaders on the node list page keep spinning forever. This is Udi's bug from 2017-09-06. This bug is now proposed upstream. https://review.openstack.org/#/c/504035/
https://review.openstack.org/#/c/510862/ merged upstream stable/pike
Verified in openstack-tripleo-ui-7.4.3-2.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462