Project

General

Profile

Bug #22804

Origin for report is not set reliably

Added by Marek Hulán over 2 years ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

To reproduce:
1) make target host offline
2) run a job against that offline host
3) see you have a report that has N/A as origin

The only content of that report is resource "Gathering Facts" with following message {"msg": "Failed to connect to the host via ssh: ssh: connect to host abel-debolt.example.tst port 22: Connection timed out\r\n", "unreachable": true, "changed": false}


Related issues

Related to Ansible - Bug #28069: Origin for report is not shown using ansible 2.8.5Duplicate
Related to Foreman - Refactor #30408: ReportScanner should get all raw report data in case those could be useful.Closed

Associated revisions

Revision 16bef911 (diff)
Added by Ondřej Pražák 4 months ago

Fixes #22804 - Scan for origin in new ansible log format

History

#1 Updated by The Foreman Bot over 1 year ago

  • Assignee set to Ondřej Pražák
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_ansible/pull/261 added

#2 Updated by Shira Maximov 7 months ago

  • Bugzilla link set to 1825761

#3 Updated by Ondřej Ezr 5 months ago

  • Bugzilla link changed from 1825761 to 1800870
  • Subject changed from Origin for report is not correctly set for failed runs to Origin for report is not set reliably

#4 Updated by Ondřej Ezr 5 months ago

  • Related to Bug #28069: Origin for report is not shown using ansible 2.8.5 added

#5 Updated by Ondřej Ezr 5 months ago

  • Related to Refactor #30408: ReportScanner should get all raw report data in case those could be useful. added

#6 Updated by Anonymous 4 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF