Bug 2022030 - Validations callback doesn't properly record details about about validation executions failing due to unreachable hosts
Summary: Validations callback doesn't properly record details about about validation e...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: validations-common
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Alpha
: ---
Assignee: Jiri Podivin
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-10 15:36 UTC by Jiri Podivin
Modified: 2023-08-04 07:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-22 15:27:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-10753 0 None None None 2021-11-10 15:42:22 UTC
Red Hat Issue Tracker VALFRWK-687 0 None None None 2021-11-10 16:27:39 UTC

Description Jiri Podivin 2021-11-10 15:36:14 UTC
Description of problem:
When validation targets a host that is unreachable, but still present in the inventory, it fails and displays the reason in the immediate output after execution, and within the complete display of validations history.

However, when requesting details of the execution, no information or explanatory output is displayed, unless the '--full' flag is provided.




Version-Release number of selected component (if applicable):
16, 17 and builds from current (10-11-2021) master of the validations-libs and validations-common repos.

How reproducible:
Always

Steps to Reproduce:
1. execute validation targeting unreachable host
2. attempt to view the validation results after execution fails


Actual results:
No output is shown.

Expected results:
Reason for failure is displayed. 

Additional info:
Issue should be easy to fix, in the validations-common callback, the validations-json.py, providing method for the case of unreachable host.

Alternatively, validations-libs GetHistory.takeAction method could be refactored to accept results without elements in the 'validation_output' list.
Although I wouldn't consider it to be an ideal outcome.

Comment 1 Jiri Podivin 2021-12-13 12:03:59 UTC
The work on this is delayed until after the callback reorganization is finished.


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