Actions
Bug #12753
closedExit status timestamp is incorrect
Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Description
The exit status somehow gets reported in the middle of the output time stamps:
{"output_type":"stdout","output":"Exit status: 0","timestamp":1449662024.0}
So it ends up looking like the attached file when viewing the execution later.
Files
Updated by The Foreman Bot about 9 years ago
- Status changed from New to Ready For Testing
- Assignee set to Stephen Benjamin
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/82 added
Updated by Stephen Benjamin about 9 years ago
- Target version changed from 92 to 97
Moving to iteration 5 as it's not critical
Updated by Anonymous almost 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman_plugin|e545fd2f73fb6a54c9dbef61c40e8a36003d7758.
Actions