Bug 224127

Summary: ALLOW_CONFIG_ACTIONS doesn't work without --allow-config-actions
Product: Red Hat Satellite 5 Reporter: Carsten Clasohm <clasohm>
Component: ServerAssignee: Clifford Perry <cperry>
Status: CLOSED WONTFIX QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 400CC: cperry
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-05 22:32:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 462714    

Description Carsten Clasohm 2007-01-24 10:34:27 UTC 
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):
rhns-certs-tools-4.1.0-4

How reproducible:
always

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.
  
Actual results:
Configuration actions and remote commands are not enabled on the registered system.

Expected results:
Setting the variables to "1" should have the same effect as specifying the
--enable options for rhn-bootstrap.

Additional info:
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".
Comment 2 Clifford Perry 2011-01-05 22:32:40 UTC 
The RHN Satellite 4.x and RHN Proxy 4.x products have reached their end of life. Please see:

Satellite 4 EOL Errata
 - https://rhn.redhat.com/errata/RHSA-2011-0001.html

RHN Proxy 4 EOL Errata
 - https://rhn.redhat.com/errata/RHSA-2011-0002.html

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. 

Regards,
Clifford