| 1 |
--- |
| 2 |
upgrade: |
| 3 |
- | |
| 4 |
In certain environments (Kubernetes for example) indirect calls to the LVM |
| 5 |
commands result in file descriptor leak warning messages which in turn cause |
| 6 |
the process_execution method to raise and exception. |
| 7 |
|
| 8 |
To accommodate these environments, and to maintain backward compatibility |
| 9 |
in Newton we add a ``lvm_suppress_fd_warnings`` bool config to the LVM driver. |
| 10 |
Setting this to True will append the LVM env vars to include the variable |
| 11 |
``LVM_SUPPRESS_FD_WARNINGS=1``. |
| 12 |
|
| 13 |
This is made an optional configuration because it only applies to very specific |
| 14 |
environments. If we were to make this global that would require a rootwrap/privsep |
| 15 |
update that could break compatibility when trying to do rolling upgrades of the |
| 16 |
volume service. |
| 17 |
|