Description of problem:
Enabling configuration actions and remote commands does not work in a bootstrap
script when the script is generated without the --enable options.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a new bootstrap script with "rhn-bootstrap", without specifying the
--allow-config-actions and --allow-remote-commands options.
2. In the generated file, enable configuration actions and remote commands by
changing the ALLOW_CONFIG_ACTIONS and ALLOW_REMOTE_COMMANDS variables from 0 to 1.
3. Register a system using this bootstrap script.
Configuration actions and remote commands are not enabled on the registered system.
Setting the variables to "1" should have the same effect as specifying the
--enable options for rhn-bootstrap.
Looking at the generated script, it's clear what the problem is. The lines for
configuration actions and remote commands are omitted when the --enable options
are not given. The fix is to include them - they won't do any harm if the the
ALLOW variables are set to "0".
The RHN Satellite 4.x and RHN Proxy 4.x products have reached their end of life. Please see:
Satellite 4 EOL Errata
RHN Proxy 4 EOL Errata
This bugzilla was reported for a product which is no longer supported. As such we are closing this bugzilla out. If you feel this bug report should be reviewed again since it is valid for a currently supported product version, then please feel free to re-open this bug report.