a5b6a161b5
* 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. * 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. * Add changelog fragment for sysctl |
||
|---|---|---|
| .. | ||
| host_vars | ||
| targets | ||
| cloud-config-aws.ini.template | ||
| cloud-config-azure.ini.template | ||
| cloud-config-cloudscale.ini.template | ||
| cloud-config-cs.ini.template | ||
| cloud-config-gcp.ini.template | ||
| cloud-config-gitlab.ini.template | ||
| cloud-config-hcloud.ini.template | ||
| cloud-config-hwc.yml.template | ||
| cloud-config-opennebula.ini.template | ||
| cloud-config-openshift.kubeconfig.template | ||
| cloud-config-scaleway.ini.template | ||
| cloud-config-tower.ini.template | ||
| cloud-config-vultr.ini.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 | ||