Forgot to mention this is only an issue when selecting "deploy file" from the config file view. "GlobalRevisionDeploy.do"
If done via SSM, it does group them into one action. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, December 08, 2011 10:21 AM To: [email protected] Subject: [Spacewalk-list] Mass config file deployment Hello... When deploying a config file to thousands of systems, it creates a scheduled action for each system, thus crowding the scheduled action's history. Other mass actions have only 1 action with a list of all the systems inside. Is there a way to make the config deploy action like all the others? Thanks -Josh
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
