Description of problem: Scheduling a config file deployment on a group of system (using SSM) we see the actions are displayed separately for each system. Version-Release number of selected component (if applicable): Red Hat Network Satellite 5.3.0 How reproducible: Always Steps to Reproduce: 1. Select 10 systems which are having provisioning entitlement as well as subscribed to same config channel 2. Go to system set manager -> configuration -> schedule a config file to be deployed on those systems 3. Go to system set manager -> packages -> schedule a package to be installed on them 4. Go to Schedule tab Actual results: - Here you see that there are 10 actions listed which show config file deployment scheduled on those 10 systems - And just 1 action is listed with # of systems showing as 10 for the package install scheduled. Expected results: - Actions listed for config file deployment should also show just 1 with # of systems as 10 very similar to the way it shows for package install scheduled on multiple systems.
fixed in spacewalk master: 99feaf6706156e003c28d7f673a499d92e0b0e18
test procedure: 1. Select 10 systems which are having provisioning entitlement as well as subscribed to same config channel 2. Go to system set manager -> configuration -> schedule a config file to be deployed on those systems 3. Go to system set manager -> packages -> schedule a package to be installed on them 4. Go to Schedule tab Package installation is one action now. tested with: Satellite-5.4.0-RHEL5-re20101001.1
(In reply to comment #4) > test procedure: > > 1. Select 10 systems which are having provisioning entitlement as well as > subscribed to same config channel > 2. Go to system set manager -> configuration -> schedule a config file to be > deployed on those systems > 3. Go to system set manager -> packages -> schedule a package to be installed > on them > 4. Go to Schedule tab > I meant one action for configuration file deployment. filled during testing: Bug 641019 - Individual actions are created while scheduling VERIFY and UPGRADE on number of Systems using SSM
The 5.4.0 RHN Satellite and RHN Proxy release has occurred. This issue has been resolved with this release. RHEA-2010:0801 - RHN Satellite Server 5.4.0 Upgrade https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10332 RHEA-2010:0803 - RHN Tools enhancement update https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10333 RHEA-2010:0802 - RHN Proxy Server 5.4.0 bug fix update https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10334 RHEA-2010:0800 - RHN Satellite Server 5.4.0 https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10335 Docs are available: http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/index.html Regards, Clifford