| 2024-04-19 07:32:16 |
Adam Rozman |
description |
The idea would be to implement a configuration option that would allow IPA to suppress the disk metadata cleanup related errors and instead of causing a provisioning / cleanup failure.
Instead of causing a failure, IPA would just log the exception with some additional information (when the option is activated), then IPA would stop the cleaning process of the faulty disk and continue the cleanup process with the next disk.
The configuration option could be provided as part of the IPA config file, cmdline argument or a kernel cmdline parameter.
Reasoning:
It could be argued that if there is a disk cleanup failure on a machine then that means that the machine in question is unreliable and should not be used until the disk issue has been sorted out. The issue is that without an option to suppress cleanup errors it becomes harder to handle temporary disk issues and that could hurt business continuity. If one disk has issues that does not automatically means that the disk has any actual effect on the day to day operations of a machine, the disk could be an unused one, or users could just temporally not use the disk.
Example scenario:
Imagine a shared hardware lab that is used by multiple development organizations and one of the organization would like to test a software stack that involves IPA provisioning. The machines in the lab have tens of disks directly attached and there is even a SAN attached to the machines thus from Linux perspective there are 100s of individual disk detected, out of all the disks 1 disk on 1 machine goes bad and causes I/O errors during disk metadata cleanup thus causing delays in the testing/verification of the whole stack thus causing delays in sw releasing and so on... |
The idea would be to implement a configuration option that would allow IPA to suppress the disk metadata cleanup related errors
to avoid instead of causing a provisioning / cleanup failure.
Instead of causing a failure, IPA would just log the exception with some additional information (when the option is activated), then IPA would stop the cleaning process of the faulty disk and continue the cleanup process with the next disk.
The configuration option could be provided as part of the IPA config file, cmdline argument or a kernel cmdline parameter.
Reasoning:
It could be argued that if there is a disk cleanup failure on a machine then that means that the machine in question is unreliable and should not be used until the disk issue has been sorted out. The issue is that without an option to suppress cleanup errors it becomes harder to handle temporary disk issues and that could hurt business continuity. If one disk has issues that does not automatically means that the disk has any actual effect on the day to day operations of a machine, the disk could be an unused one, or users could just temporally not use the disk.
Example scenario:
Imagine a shared hardware lab that is used by multiple development organizations and one of the organization would like to test a software stack that involves IPA provisioning. The machines in the lab have tens of disks directly attached and there is even a SAN attached to the machines thus from Linux perspective there are 100s of individual disk detected, out of all the disks 1 disk on 1 machine goes bad and causes I/O errors during disk metadata cleanup thus causing delays in the testing/verification of the whole stack thus causing delays in sw releasing and so on... |
|
