Description of problem: The page "/rhn/systems/details/SystemRemoteCommand.do?sid=1000010000&" was rewritten from perl to java and behaviour was changed. When registered system is disabled remote command then it is showen page with warning message Old page: /network/systems/details/remote_commands.pxt?sid=1000023953 Message: "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 install rhncfg, rhncfg-actions and rhncfg-client packages." New page: without message and it's possible to create schedule to remote action and then I error message. Version-Release number of selected component (if applicable): spacewalk-java-2.3.8-28.el6sat.noarch How reproducible: Always Steps to Reproduce: 1. register new system to satellite without enable remote command (allowed-actions/script/run) 2. enable Provisioning on webui 3. go to page with remote command Actual results: without message - other behaviour Expected results: same behaviour as in old satellite
A more accurate message is " You must enable Remote Command execution on the target system by installing the rhncfg-actions RPM. " That's all SW/Satellite can check for - whether you *could* enable script.run. We have no idea whether it is currently enabled, or will be enabled when the remote-cmd attempts to run.
SW commit a77eb5df99b5d172af652b5793a810170c90e500
With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug is being moved to a Closed Current Release state. The Satellite 5.7 GA Errata: - https://rhn.redhat.com/errata/RHSA-2015-0033.html Satellite 5.7 Release Notes: - https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Release_Notes/index.html Satellite Customer Portal Blog announcement for release: - https://access.redhat.com/blogs/1169563/posts/1315743 Cliff NOTE: This bug has not been re-verified (moved to RELEASE_PENDING) prior to release. We assume that the bug has indeed been fixed and not regressed since we initially verified it. Please re-open in the future if needed.