I will make small mirror locally then test it again. It's not likely that 3 times in row installation hang on same package, but still it's worth trying. Bests Alex On 03/29/2017 04:35 PM, Stephan Wiesand wrote: > If it's not a repo problem, when I see such errors they are usually due the networking breaking down mid-install - typically because NetworkManager discovers another interface it likes better than that meant to be used for installation and moves the default route to it. > > - Stephan > >> On 29. Mar 2017, at 15:52, Pat Riehecky <[log in to unmask]> wrote: >> >> Thanks for the report! >> >> I uncovered an unrelated bug in libguestfs, but the repo error is new information. >> >> I do show that version of libguestfs in the repo. >> >> I'll see about double checking the repodata correctly synced up to the distribution servers. >> >> Pat >> >> On 03/29/2017 08:27 AM, aleksander.baranowski wrote: >>> Hi, >>> >>> I tested SL 6.9 x86_64 with netimage >>> [http://ftp.scientificlinux.org/linux/scientific/6rolling/x86_64/iso/SL-6-x86_64-netinstall.iso] >>> you gave us. >>> >>> Installation was on libvirt/qemu/kvm. >>> >>> Installation process went as follow: >>> >>> 1) Test disc - OK >>> 2) Select default options for network configuration in URL submenu >>> 3) Put url >>> http://ftp.scientificlinux.org/linux/scientific/6rolling/x86_64/os/ >>> 4) Wait for retrieving install.img etc... >>> 5) Wait for graphical installer. Next -> Install anyway (alpha/beta >>> infobox). >>> 6) Hostname sl69 >>> 6) Basic Storage Devices >>> 7) Zone - Warsaw, then set root pass. >>> 8) Use All Space twice, on third try I made manual partitioning. >>> 9) Customize now -> Install all package group except language support, >>> without adding optional packages in any group. >>> 10) Install >>> 11) There is error - "libguestfs-1.20.11-20.el6.x86_64.rpm cannot be >>> opened. This is due to a missing file, a corrupt package or corrupt >>> media. Please verify your installation source." >>> Screenshot included. >>> >>> I tried on 3 different installation, (one with only 20 gb of disc space, >>> so I make it bigger 40 gb, when same package had problem I thought that, >>> this might be bug, but to be sure I made 50 gb installation with manual >>> partitioning, same result) >>> >>> I would love to hear if anyone else can reproduce. >>> >>> Bests >>> Alex