Bug #22804
closed
Origin for report is not set reliably
Added by Marek Hulán almost 7 years ago.
Updated over 4 years ago.
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}
- Status changed from New to Ready For Testing
- Assignee set to Ondřej Pražák
- Pull request https://github.com/theforeman/foreman_ansible/pull/261 added
- Bugzilla link set to 1825761
- Subject changed from Origin for report is not correctly set for failed runs to Origin for report is not set reliably
- Bugzilla link changed from 1825761 to 1800870
- Related to Bug #28069: Origin for report is not shown using ansible 2.8.5 added
- Related to Refactor #30408: ReportScanner should get all raw report data in case those could be useful. added
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF