Description of problem: The rollback feature, says it redeploys all the configuration files even when there is no config files to be redeployed (and no config channel). This might be misleading. Also, a snapshot is added after redeployal of these 0 config files. This is inconsistent with sat560 where the action isn't added. How reproducible: Always Steps to Reproduce: 1. Have a satellite 5.7.0 2. Register a system, add provisioning entitlement to the system. On the client system, do "rhn-actions-control --disable-deploy" 3. Do some action, e.g. schedule a package installation 4. On the client system, do rhn_check 5. Go to provisioning->snapshots , select the first snapshot ("Entitlements Updated" - the provisioning entitlement adding) 6. Notice the text in bold: "all snapshotted configuration files will be redeployed". Notice the system doesn't have any config channel, 7. Click "Rollback to Snapshot" 8. Notice the "Deploy config files to system scheduled by admin". Notice there is nothing to be deployed. 9. On the client system, do "rhn_check -vv; echo $?". 10. Go to Events->history. Notice the deploy action is marked as failed. This is because deploy capabality has been disabled. However, there was no need to redeploy the config files as there are none, this capability shouldn't be necessary and the action shouldn't show at all. Also, notice the rhn_check output complaining about not being able to redeploy files but returning 0. 11. Go to provisioning->snapshots once again and notice there is nothing about file deployment 12. Enable deploy capability. Goto 3. Here, notice that another snapshot is added: deployment of 0 config files "Scheduled action completion: Deploy config files to system". Actual results: There was nothing to redeploy. There was no config channel. However, there was another snapshot added, another event (that fails when I do not have an ability to redeploy those 0 files), rhn_check -vv showed error (and then returned 0, I will make another bug for this). Expected results: There shouldn't be any mention of config files at all.
Note that mentioned "empty config files deployment action" can be seen in `rhn_check -vv` output when rollbacking.
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.