vmlinuz/initrd files corrupted during when multiple hosts created simultaneously
|Assigned To:||Dmitri Dolguikh|
|Target version:||Foreman - Sprint 26|
|Found in release:||Pull request:|
|Velocity based estimate||-|
Linked BZ describes a side effect of async downloads:
--- Additional comment from James Slagle on 2014-06-17 15:02:27 BST ---
i been able to reliably reproduce this now and I believe what triggers this is assigning a 2nd host to a host group before the vmlinuz/initrd download has finished from the first host to host group assignment.
according to the foreman-proxy.log, the 2nd assignment causes an additional background task to get started to download the files. You then have multiple downloads clobbering each other.
likewise for any subsequent assignment if there is already a download running.
I've attached my foreman-proxy.log. It doesn't show anything different really from a successful download, but you can at least see it starting an additional download task before the first has even finished.
I end up with files that are much larger than they should be:
[root@staypuft boot]# pwd /var/lib/tftpboot/boot [root@staypuft boot]# ll -h total 277M -rw-r--r--. 1 foreman-proxy root 165M Jun 5 14:45 foreman-discovery-image-latest.el6.iso-img -rw-r--r--. 1 foreman-proxy root 3.9M Jun 5 14:45 foreman-discovery-image-latest.el6.iso-vmlinuz -rw-r--r--. 1 foreman-proxy foreman-proxy 101M May 7 03:39 RedHat-7.0-x86_64-initrd.img -rw-r--r--. 1 foreman-proxy foreman-proxy 7.4M May 5 11:21 RedHat-7.0-x86_64-vmlinuz
#2 Updated by Dmitri Dolguikh over 3 years ago
- Status changed from Assigned to Ready For Testing