Actions
Bug #22804
closed
Origin for report is not set reliably
Difficulty:
Triaged:
No
Bugzilla link:
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}
Updated by The Foreman Bot about 5 years ago
- 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
Updated by
Updated by Ondřej Ezr almost 4 years ago
- 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
Updated by Ondřej Ezr almost 4 years ago
- Related to Bug #28069: Origin for report is not shown using ansible 2.8.5 added
Updated by Ondřej Ezr almost 4 years ago
- Related to Refactor #30408: ReportScanner should get all raw report data in case those could be useful. added
Updated by Anonymous over 3 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_ansible|16bef9111497f79b993dc7ef646cab60cde6c824.
Actions