Description of problem: I am attaching a screenshot with the current display of this page. In short, the instructions on the page are vague, and does not make it easy to get a system ready for remote command execution. Recommend that in addition to the page saying that the allowed-actions/..... file needs to exist, you state explicitly that you need to join the system to the RHN tools channel and up2date rhncfg-actions. The three packages needed to execute scripts remotely are rhncfg, rhncfg-actions, and rhncfg-client, but doing an up2date for -actions gets the other 2 as dependencies. Version-Release number of selected component (if applicable): 360 How reproducible: Always Steps to Reproduce: 1. See desc. 2. 3.
Created attachment 105699 [details] screenshot of the offending page
qa plan: got to the systems->details->remote command verify the following text: >>>>>> Run Remote Command You can schedule a remote script to execute on this system below. The script will run as the user you specify. You must enable Remote Command execution on the target system, by adding a file to the local rhn configuration directory: allowed-actions/script/run. You must have the latest version of the RHN Configuration Client installed to use this feature. Join the system to the RHN Tools Channel and up2date rhncfg, rhncfg-actions and rhncfg-client packages. >>>>
ON_DEV/QA_READY --> ON_QA (webQA and RHN Sat ISO/package push complete)
ON_DEV/QA_READY --> ON_QA (webQA and RHN Sat ISO/package push complete) REALLY!
Fixed.
Mass move from PROD_READY to CLOSED:CURRENTRELEASE