[Spacewalk-list] Grouping of systems in scheduled actions
Jeremy Maes
jma at schaubroeck.be
Tue Feb 3 08:26:34 UTC 2015
Hello
I've noticed for quite some time that, depending on the options you
choose when scheduling actions, systems might get grouped together in
one action or a seperate action might be scheduled for each system.
Example:
- When you put 10 systems in SSM and schedule a package *install*, you
will get one single action for 10 systems. (as expected)
- If you do the same and schedule a package *upgrade* however, you will
get 10 seperate actions scheduled: 1 for each system. (this is not expected)
What's the logic or reason behind this? As when you're managing a lot of
systems it tends to get very hard to keep track of upgrade failures when
there's 300 seperate actions scheduled for a bunch of seperate packages
by different people.
Thanks in advance for your insights.
--
Jeremy Maes
<https://www.linkedin.com/company/schaubroeck-nv>
**** DISCLAIMER ****
http://www.schaubroeck.be/maildisclaimer.htm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20150203/e7ad5a90/attachment.htm>
More information about the Spacewalk-list
mailing list