b65ab065ea
Previously the ramdisk logs were only stored if the ramdisk reported an error. However, we are moving from ramdisk-side validation to server-side, so we need ramdisk logs to be available if processing fails too. This change moves storing ramdisk logs from a ramdisk_error plugin to core processing code. As before, it can be disabled by setting ramdisk_logs_dir to an empty value. Change-Id: Ib3742ee1c1d4f2f96d29466626e1121694610dc3 Closes-Bug: #1564448
12 lines
513 B
YAML
12 lines
513 B
YAML
---
|
|
fixes:
|
|
- The ramdisk logs are now stored on all preprocessing errors, not only
|
|
ones reported by the ramdisk itself. This required moving the ramdisk
|
|
logs handling from the "ramdisk_error" plugin to the generic processing
|
|
code.
|
|
upgrade:
|
|
- Handling ramdisk logs was moved out of the "ramdisk_error" plugin, so
|
|
disabling it will no longer disable handling ramdisk logs. As before,
|
|
you can set "ramdisk_logs_dir" option to an empty value (the default)
|
|
to disable storing ramdisk logs.
|