The `hammer` command timeout setting is not respected by the Red Hat Satellite server
Environment
- Red Hat Satellite 6.x
Issue
- When modifying or disabling the
hammercommandrequest_timeoutsetting as per How to setup hammer API request timeout on Satellite 6, the new setting is not respected, and it does not take effect.
Resolution
- Confirm whether you have a
~/.hammer/cli.modules.d/foreman.ymlconfig file on the Satellite server, using the following command:
# ls -laR ~/.hammer/cli.modules.d/
- If such a config file is found, check its content and confirm that it does not have a
request_timeoutsetting that overrides the value configured in/etc/hammer/cli.modules.d/foreman.yml.
For more KB articles/solutions related to Red Hat Satellite 6.x hammer Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x hammer-related Issues
Root Cause
A ~/.hammer/cli.modules.d/foreman.yml config file exists on the Satellite server, and it has request_timeout setting that overrides the value configured in /etc/hammer/cli.modules.d/foreman.yml.
SBR
Product(s)
Components
Category
Tags
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.