Description of problem:

When running introspection on my nodes, I received a timed out message for one of the nodes, however, it never reported that it actually completed successfully but the node is now in available state.

(undercloud) [stack@ds-osp14-hf-undercloud ~]$ openstack overcloud node introspect --all-manageable --provide
Waiting for introspection to finish...
Waiting for messages on queue 'tripleo' with no timeout.
Introspection of node a453b4db-b10f-4b51-bddb-51e46b4e6048 timed out.
Introspection of node 16da8ac0-dbb7-460d-b7a4-4681eab45714 completed. Status:SUCCESS. Errors:None
Introspection of node eafd1070-bbe2-468a-b419-e9917cd02c39 completed. Status:SUCCESS. Errors:None
Introspection of node 1b6d6d1e-2a9d-4d92-9055-4d56afbb93d9 completed. Status:SUCCESS. Errors:None
Introspection of node 4f56c499-dd7e-4e7a-b6a3-899afd0695b6 completed. Status:SUCCESS. Errors:None
Introspection of node 288e47d4-32b1-4d00-844d-490a52b86239 completed. Status:SUCCESS. Errors:None
Introspection of node 6dbfd49c-ba30-406c-9690-957f7f14ace1 completed. Status:SUCCESS. Errors:None
Introspection of node fc8ee696-2dcb-4c11-ad84-c4350e97932b completed. Status:SUCCESS. Errors:None
Successfully introspected 8 node(s).

Introspection completed.
Waiting for messages on queue 'tripleo' with no timeout.

8 node(s) successfully moved to the "available" state.


(undercloud) [stack@ds-osp14-hf-undercloud ~]$ openstack baremetal node list
+--------------------------------------+-------------+---------------+-------------+--------------------+-------------+
| UUID                                 | Name        | Instance UUID | Power State | Provisioning State | Maintenance |
+--------------------------------------+-------------+---------------+-------------+--------------------+-------------+
| 1b6d6d1e-2a9d-4d92-9055-4d56afbb93d9 | controller1 | None          | power off   | available          | False       |
| 6dbfd49c-ba30-406c-9690-957f7f14ace1 | controller2 | None          | power off   | available          | False       |
| eafd1070-bbe2-468a-b419-e9917cd02c39 | controller3 | None          | power off   | available          | False       |
| 4f56c499-dd7e-4e7a-b6a3-899afd0695b6 | compute1    | None          | power off   | available          | False       |
| 288e47d4-32b1-4d00-844d-490a52b86239 | compute2    | None          | power off   | available          | False       |
| 16da8ac0-dbb7-460d-b7a4-4681eab45714 | ceph1       | None          | power off   | available          | False       |
| a453b4db-b10f-4b51-bddb-51e46b4e6048 | ceph2       | None          | power off   | available          | False       |
| fc8ee696-2dcb-4c11-ad84-c4350e97932b | ceph3       | None          | power off   | available          | False       |
+--------------------------------------+-------------+---------------+-------------+--------------------+-------------+
(undercloud) [stack@ds-osp14-hf-undercloud ~]$ 

Node a453b4db-b10f-4b51-bddb-51e46b4e6048 timed out, doesn't show success after that however it is reporting that 8 nodes were successful.

It looks like the 'extra' property has data in it which indicates to me that it did actually introspect as that was not there prior to introspection.


Version-Release number of selected component (if applicable):
OSP14

How reproducible:
It happened twice in a row on my environment on different nodes timing out.

Steps to Reproduce:
1. import nodes.json
2. introspect (and hope one node times out)
3. Note output messages and the UUID of the timed out node never shows success but is included in the success count.

Actual results:

Shows SUCCESS for all nodes except the timed out node, but the timed out node was also successful.

Expected results:
If a timed out node is re-tried and successful, it should report it as SUCCESS in the output.

Additional info: