[AutoQA] #128: pst: Create a mechanism to ensure test clients are fully up-to-date

[fedora-badges]

#128: pst: Create a mechanism to ensure test clients are fully up-to-date
--------------------+-------------------------------------------------------
 Reporter:  kparal  |       Owner:                      
     Type:  task    |      Status:  new                 
 Priority:  major   |   Milestone:  Package Sanity Tests
Component:  tests   |     Version:  1.0                 
 Keywords:  tps     |  
--------------------+-------------------------------------------------------
 For sanity tests we will need that the test client machines are always
 fully up-to-date. We must think about a mechanism that will provide that
 for us.

 Will we have some kind of periodic task that will connect to all clients
 and update them? Or should the TPS test itself ensure the machine is up-
 to-date and only after that start executing itself?

 What about reboot? How do we know when it is necessary to reboot after an
 update? Will we reboot after each update, just to be sure nothing got
 broken?

-- 
Ticket URL: <https://fedorahosted.org/autoqa/ticket/128>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project