| Key: |
CIB-2258
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
3
|
| Assignee: |
Unassigned
|
| Reporter: |
Daniel Ostermeier
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 05/Jan/10 10:07 PM
Updated: 19/Jan/10 09:27 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
2.1.15
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
If things fail, then the first thing we ask for is a log file. When the failure relates to something to do with upgrades, then a second question that pops up is did the upgrade tasks run.
To avoid the need for the extra question, we should print the upgrade details (name of tasks and final status) into the log.
Include the time it took for each task to complete.
|
|
Description
|
If things fail, then the first thing we ask for is a log file. When the failure relates to something to do with upgrades, then a second question that pops up is did the upgrade tasks run.
To avoid the need for the extra question, we should print the upgrade details (name of tasks and final status) into the log.
Include the time it took for each task to complete. |
Show » |
|
Provide some trace of what upgrade tasks are run in the logs