Bug 1201201
| Summary: | Installer hangs at "Performing post installation tasks" | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | colin <bugzilla.redhat.com> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | anaconda-maint-list, bugzilla, bugzilla.redhat.com, g.kaviyarasu, jonathan, vanmeeuwen+fedora |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-04-29 17:35:59 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
colin
2015-03-12 10:08:22 UTC
So I re-did the F22 Alpha install. This time I did a completely bare install, with no extra packages selected. The only non-default option was to (again) create a user 'admin' As before I was monitoring progress in my VM manager ( in this case ProxmoxVE ) and could see that the installer was not 'frozen' like last time but still using CPU and Harddrive IO. The whole install took 21 minutes. !!!! :-( I would estimate that at least 15 minutes of that was the installer 'waiting' at the final screen. Please separately attach logs from /tmp (or /var/log/anaconda): program.log, anaconda.log, storage.log. Created attachment 1001535 [details]
/var/log/anaconda.log
Created attachment 1001536 [details]
/var/log/program.log
Created attachment 1001537 [details]
/var/log/storage.log
Can you please attach the other log files from /tmp? Does this problem still occur with F22 Beta? Sorry the requested files are no longer available, also I seemed to recall looking in /tmp as requested at the time and not seeing the log files although that would have been after a few reboots, so maybe they were purged already. - Hence why I uploaded the logs from /var/log/ as requested. However I did do another fresh install from the newer image: Fedora-Server-netinst-x86_64-22_Beta_TC8.iso and all went smoothly. :-) So feel free to ignore this BZ. Thanks. Colin Glad to hear So I was prematurely optimistic in stating that my last install was fine and thus the problem was gone. The installer 'hang' that I originally reported does in fact still exist. I have investigated further and can now describe the circumstances in which the installer _does_ and _does_not_ eventually complete. I performed all of the tests for this BZ thread on the same ProxmoxVE host as previously and have grabbed screen shots for illustration. I was successful in a completely fresh install of Fedora-Server-DVD-x86_64-22_Beta.iso which is todays current RC3 For clarity of comparison - I will upload screen grabs of this successful install to this comment, and then continue with the problematic case in a subsequent comment. Created attachment 1019400 [details]
Screengrab1 vm124 Fedora-Server-DVD-x86_64-22_Beta.iso
You can see from the CPU Usage graph that the installation takes about 21 minutes.
Created attachment 1019401 [details]
Screengrab2 vm124 Fedora-Server-DVD-x86_64-22_Beta.iso
Unfortunately the resource usage graphs do not all fit on the screen together.
You can see from the bottom graph the disk IO which is completed around 18:23.
F22 install screen shows install completed and button on bottom right changed to 'Reboot'.
:-)
Having gone through this process at least seven times now for various versions of F22Server Alpha TC8 and Beta TC2 TC3 TC8 and RC3 DVD and netinstall I note a couple of things that are NOT helpful 1) In the screengrabs above of the Fedora-Server-DVD-x86_64-22_Beta.iso install completeting - the screen still shows : 'User Creation' 'Administrator admin will be created' Clearly this gives the wrong impression that the requested new user _has_not _been_created_yet_ . This erronoeus 'information' was a contributor to me not wanting to just reboot a 'hung' install to see what state it was in, since it _falsely__ claims to not have finished doing its installation procedures. 2) I had no way of knowing the IP address of the installation - so could not even attempt to ssh in to it. 3) There is no differentiation detailing what image you are installing. Only the text 'FEDORA 22_BETA INSTALLATION' which is not helpful when you have been installing multiple versions e.g. Server and DVD and netinstall. comment from thread starting post still applies > I have seen the request for more information for RHBZ #1146015 > but am unable to switch to another console (or ssh) so cannot see howto view >log files or run 'ps -ef' @David in comment 6 > Can you please attach the other log files from /tmp? Does this problem still > occur with F22 Beta? The authenticity of host '192.168.11.133 (192.168.11.133)' can't be established. ECDSA key fingerprint is 88:36:f2:c1:f6:6a:3c:b9:59:0f:76:7e:9d:d4:36:74. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.11.133' (ECDSA) to the list of known hosts. root.11.133's password: Last login: Mon Apr 27 18:32:30 2015 [root@localhost ~]# cd /tmp/ [root@localhost tmp]# ls -alrt total 4 drwxrwxrwt. 7 root root 140 Apr 27 18:52 . dr-xr-xr-x. 17 root root 4096 Apr 27 2015 .. drwxrwxrwt. 2 root root 40 Apr 27 2015 .X11-unix drwxrwxrwt. 2 root root 40 Apr 27 2015 .XIM-unix drwxrwxrwt. 2 root root 40 Apr 27 2015 .font-unix drwxrwxrwt. 2 root root 40 Apr 27 2015 .Test-unix drwxrwxrwt. 2 root root 40 Apr 27 2015 .ICE-unix [root@localhost tmp]# [root@localhost tmp]# ls -alrt /var/log/anaconda/ total 1200 -rw-------. 1 root root 20895 Apr 27 18:22 anaconda.log -rw-------. 1 root root 72727 Apr 27 18:22 syslog -rw-------. 1 root root 17081 Apr 27 18:22 X.log -rw-------. 1 root root 29639 Apr 27 18:22 program.log -rw-------. 1 root root 2193 Apr 27 18:22 packaging.log -rw-------. 1 root root 84132 Apr 27 18:22 storage.log -rw-------. 1 root root 6198 Apr 27 18:22 ifcfg.log -rw-------. 1 root root 10637 Apr 27 18:22 dnf.log -rw-------. 1 root root 44401 Apr 27 18:22 dnf.rpm.log -rw-------. 1 root root 0 Apr 27 18:22 ks-script-ZiVZMq.log drwxr-xr-x. 2 root root 4096 Apr 27 18:22 . -rw-------. 1 root root 909537 Apr 27 18:22 journal.log drwxr-xr-x. 10 root root 4096 Apr 27 18:42 .. [root@localhost tmp]# I can post these if requested. And so to an install that did not complete. This 'hung' and failed to complete just as reported in comment 1 Currently latest build publicly available on: https://dl.fedoraproject.org/pub/alt/stage/ which is 22_Beta_RC3/Server from: https://dl.fedoraproject.org/pub/alt/stage/22_Beta_RC3/Server/x86_64/iso/ Fedora-Server-netinst-x86_64-22_Beta.iso I saved some screen grabs and will upload now. Created attachment 1019410 [details]
ScreengrabA vm121 Fedora-Server-netinst-x86_64-22_Beta.iso RC3
Again all 4 of the resource usage graphs do not fit on screen together.
this first screengrab shows the CPU usage
ih high from 16:06 to 16:48
I also was running an htop on the Proxmox host so could could watch the host CPU usage in realtime.
Created attachment 1019411 [details]
ScreengrabB vm121 Fedora-Server-netinst-x86_64-22_Beta.iso RC3
screengrab scrolled down shows the Disk IO usage
you can see the diskIO from 16:16 is minimal whilst I click through the setup options
Then peaks as packages are installed at 16:31
Then tails off by 16:47
Unlike in the case of the Server DVD above - the installation never actually completes.
*** This bug has been marked as a duplicate of bug 1204242 *** |