host-deploy cache is timestamp based, max(interface-3). there can be a case in which packages at interface-3 are updated async, in this case if the package that is being updated is older (in term of timestamp) than previous the cache will not be refreshed. we move to hash based.
using hash will force us to read files twice, once per modify check and once when creating the tar, so we can just create the tar always.
Verified on vt17.1 ovirt-host-deploy.tar is recreated before each host deploy
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.
oVirt 3.5.5 has been released including fixes for this issue.