Hello Yang, you are correct, the action chain executes as quickly as possible. Meaning it will execute actions for different servers parallel. This is, so that if you patch 100 servers and add a reboot to the action chain, it doesn't wait for every single server to be done with updating before it starts rebooting all the servers.
The action chain tells the server what to do in what order. Once the server checked back with spacewalk (or you did rhn_check) it will call its own chain of events and execute them. It's independent of what other servers do meanwhile. regards, Wafa -----Ursprüngliche Nachricht----- Von: spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von YANG LI Gesendet: Donnerstag, 8. Februar 2018 20:49 An: spacewalk-list@redhat.com Betreff: [Spacewalk-list] spacewalk action chain question I am testing spacewalk action chain. Our current version of spacewalk is 2.6. when I schedule action chain. Action 1 Server1: sleep 10 Action 2 Server2: sleep 20 Action 3 Server3: stop a service I thought the action 1 from server1 should be executed first and finished before action 2 can started. then action 2 start and finished before action3 can start. But based on looking at completed action. All three actions are started at same time, since action 3 only run a simple command, so it completed first. Then action1 completed and action2 completed. Look like the action chain order only matters if it is for same server, but if it is for different server, the action chain order does not matter. Is this true? Thanks, Yang _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
