Description of problem: When the client system is missing deploy capability, upon file deployment, rhn_check -vv complains about not being able to deploy files but returns 0 How reproducible: Always Steps to Reproduce: 1. In bug #1158957 , reproduce steps 1 to 10 2. Notice the output of rhn_check -vv: "D: do_call configfiles.deploy({'files': []},){'cache_only': None} D: Sending back response(42, 'Local permission not set for action type configfiles.deploy', {})" 3. Notice in events->history, the "Deploy config files to system scheduled by admin" action is marked as failed 4. Therefore, the rhn_check failed and should have returned non-zero. Notice, however, it returned 0. Actual results: rhn_check returned 0 Expected results: It (partly) failed so it should have returned non-zero
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.