Freezer Agent does not trap tar restore errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Backup/Restore and DR (Freezer) |
Fix Released
|
Undecided
|
Deklan Dieterly | ||
Mitaka |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
When doing a restore, if an error occurs with tar, the tar error is not logged. Only
Engine error: [Errno 32] Broken pipe
is logged. The root cause of the error is not captured and logged. This is because the exception is bypassing the process error checks.
For example.
2016-06-16 15:18:44.364 10868 INFO freezer.job [-] [*] Executing FS restore...
2016-06-16 15:18:44.378 10868 INFO freezer.
2016-06-16 15:18:44.378 10868 INFO freezer.
2016-06-16 15:18:44.378 10868 INFO freezer.
2016-06-16 15:18:44.426 10868 CRITICAL freezer.
2016-06-16 15:18:44.427 10868 CRITICAL freezer.main [-] [*] Critical Error: Engine error. Failed to restore file.
Changed in freezer: | |
status: | New → In Progress |
assignee: | nobody → Deklan Dieterly (deklan) |
Changed in freezer: | |
milestone: | none → newton-2 |
Fix proposed to branch: master /review. openstack. org/333543
Review: https:/