6bc671a46a
* sysctl will now return an error if the value is invalid sysctl can fail to set a value even if it returns an exit status 0. More details: https://bugzilla.redhat.com/show_bug.cgi?id=1264080. Because of this in case of an invalid value or a read-only file system, sysctl module would return OK, even though it didn't set anything. To be sure that sysctl correctly applied the changes we also need to check the output of stderr. (cherry picked from commit 0432b7f2522dbf82c4fabdb3fd17f7ac83f34e62) * Run sysctl with LANG=C Because we are parsing sysctl stderr we need to make sure that errors are persistent across different system language settings. (cherry picked from commit a16128f778b1e7574c5986aed26e146ac0561533) * Add changelog fragment for sysctl (cherry picked from commit 3ad9d4d83c1d2bbfccefb8388904c596d98f8731) |
||
---|---|---|
.. | ||
host_vars | ||
targets | ||
cloud-config-aws.yml.template | ||
cloud-config-azure.yml.template | ||
cloud-config-cs.ini.template | ||
cloud-config-gcp.yml.template | ||
cloud-config-opennebula.yml.template | ||
cloud-config-openshift.kubeconfig.template | ||
cloud-config-tower.cfg.template | ||
integration.cfg | ||
integration_config.yml | ||
inventory | ||
inventory.networking.template | ||
inventory.remote.template | ||
inventory.winrm.template | ||
network-integration.cfg | ||
target-prefixes.network | ||
windows-integration.cfg |