introspect command logs introspect failed for successful introspections
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
In Progress
|
Medium
|
Steve Baker |
Bug Description
Introspection reported that a node failed but then says successfully introspected the node later on.
(undercloud) [cloud-
Waiting for introspection to finish...
Waiting for messages on queue 'tripleo' with no timeout.
Introspection of node 0256d108-
Introspection of node 43ac4f9d-
Introspection of node ba2fdc05-
Introspection of node 56f75e79-
Successfully introspected 4 node(s).
I think what is happening here is:
1. introspection starts on node
2. call to get introspection status fails due to some interaction between ironic-
3. retry logic checks introspection status, which is now successful, so no retry attempted and no message sent saying it is completed
Proposed fixes:
tripleo-common: Clarify introspection failure message is a failed attempt, not an absolute failure
python-
tripleo-puppet: Fix haproxy occasionally disconnecting requests for ironic-inspector
Changed in tripleo: | |
milestone: | ussuri-1 → ussuri-2 |
Changed in tripleo: | |
milestone: | ussuri-2 → ussuri-3 |
Changed in tripleo: | |
milestone: | ussuri-3 → ussuri-rc3 |
Changed in tripleo: | |
milestone: | ussuri-rc3 → victoria-1 |
Changed in tripleo: | |
milestone: | victoria-1 → victoria-3 |
Fix proposed to branch: master /review. opendev. org/696630
Review: https:/