Bug 1606922

Summary: Anaconda after starting automated install and never completes
Product: [Fedora] Fedora Reporter: Loren M. Lang <lorenl>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: anaconda-maint-list, jonathan, kellin, lorenl, mkolman, redhat.com, vanmeeuwen+fedora, vponcova, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 11:21:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Kickstart
none
anaconda log
none
storage log
none
program log
none
main log
none
console log none

Description Loren M. Lang 2018-07-20 23:29:16 UTC 
Created attachment 1469618 [details]
Kickstart

Description of problem: On some occassions while installing Fedora 28 inside a KVM virtual machine, Anaconda will state that it's starting the automated install, but it just continues to produce dots on it's output and never continues past this point.

Version-Release number of selected component (if applicable):
First seen with Fedora 27, and continuing to plaque Fedora 28.

How reproducible:
Roughly about 1 in 10 VMs fail to install. Every VM is created with a basically identical environment.

Steps to Reproduce:
1. Set-up HTTP server to host mounted Fedora 28 ISO.
2. Set-up fully-automated Kickstart file to be hosted on server.
3. Start install of Fedora 28 with virt-install:

virt-install --os-variant=fedora25 \
    --graphics none \
    --console pty,target_type=virtio \
    --channel \
'unix,path=/var/lib/libvirt/qemu/f16x86_64.agent,mode=bind,target_type=virtio,name=org.qemu.guest_agent.0' \
    --cpu host \
    --network bridge=host_br0,model=virtio \
    --location http://server/fedora/Fedora-28-x86_64/ \
    --extra-args 'ks=http://server/deploy/fedora28.cfg console=hvc0' \
    --hostdev pci_0000_10_00_0 \
    --name ABCDE \
    --vcpus 8 \
    --memory 4096 \
    --disk size=20.0


Actual results:
Installer prints out "Starting automated install." and continues to prints dots forever.

Expected results:
Fedora 28 should be fully installed and rebooted into OS.

Additional info:
First seen with Fedora 27. There was no problem using a similar setup with Fedora 26. Kickstart and logs will be attached.
Comment 1 Loren M. Lang 2018-07-20 23:30:09 UTC 
Created attachment 1469619 [details]
anaconda log
Comment 2 Loren M. Lang 2018-07-20 23:30:25 UTC 
Created attachment 1469620 [details]
storage log
Comment 3 Loren M. Lang 2018-07-20 23:30:44 UTC 
Created attachment 1469621 [details]
program log
Comment 4 Loren M. Lang 2018-07-20 23:31:02 UTC 
Created attachment 1469622 [details]
main log
Comment 5 Loren M. Lang 2018-07-20 23:34:40 UTC 
Created attachment 1469623 [details]
console log
Comment 7 Vendula Poncova 2018-07-23 10:59:12 UTC 
Hi, you might try to switch to the graphical mode as a workaround.
Comment 8 Loren M. Lang 2018-08-22 16:27:08 UTC 
That does not work for us. These are automated installs using kickstart inside a KVM environment. There is no VGA console nor user to interact with. We do about 40 installs every morning for running various test suites. This issue does not happen with a high percentage, but with as many installs as we do, we see it regularly.
Comment 9 Martin Kolman 2018-08-23 09:16:41 UTC 
(In reply to Loren M. Lang from comment #8)
> That does not work for us. These are automated installs using kickstart
> inside a KVM environment. There is no VGA console nor user to interact with.
> We do about 40 installs every morning for running various test suites. This
> issue does not happen with a high percentage, but with as many installs as
> we do, we see it regularly.
The installation will still be fully automatic and non-interactive, just running with a graphical interface. As long as the GUI can start, it should work around the issue, even if no monitors are connected and no one is actually looking at the GUI.
Comment 10 Vendula Poncova 2018-08-28 11:48:56 UTC 
Hi, could you try to run the installation with the following boot option?

inst.updates=https://vponcova.fedorapeople.org/f28_dots.img
Comment 11 John Villalovos 2018-11-26 22:22:19 UTC 
(In reply to Vendula Poncova from comment #10)
> Hi, could you try to run the installation with the following boot option?
> 
> inst.updates=https://vponcova.fedorapeople.org/f28_dots.img

I've been trying this on a Fedora 29 install and so far seems to be resolving the issues I was seeing with the install getting stuck with repeating dots. Since I started using this I haven't seen a stuck install. Before that I was having stuck installs quite often.

I've done about 10 test runs so far. This is done on bare-metal systems under Beaker.
Comment 12 John Villalovos 2018-11-29 17:51:48 UTC 
(In reply to John Villalovos from comment #11)
> I've done about 10 test runs so far. This is done on bare-metal systems
> under Beaker.


I've been using this for several days now and since I started using it I haven't seen a stuck install. Before I was seeing it about 50% of the time.

I would vote for getting the patch merged.
Comment 13 Vendula Poncova 2018-11-30 11:21:16 UTC 
The patch is already part of Fedora 29: https://github.com/rhinstaller/anaconda/pull/1599
Comment 14 John Villalovos 2018-11-30 15:37:53 UTC 
(In reply to Vendula Poncova from comment #13)
> The patch is already part of Fedora 29:
> https://github.com/rhinstaller/anaconda/pull/1599

Thanks. I discovered the 'install.img' file I was using in our network install did not have that patch for some reason.