Hide Forgot
Created attachment 1151485 [details] Logs from /tmp while a failed installation continues to be active. Description of problem: Trying to kickstart a Dell R630 with ten total Ethernet ports, I see this output. Starting installer, one moment... anaconda 23.19.10-1 for Fedora 23 started. * installation log files are stored in /tmp during the installation * shell is available on TTY2 * when reporting a bug add logs from /tmp as separate text/plain attachments 18:03:37 Not asking for VNC because of an automated install Starting automated install........................................................................................................................................................................................... The dots continue "forever". Version-Release number of selected component (if applicable): Fedora 23 How reproducible: About 35% of the time. Steps to Reproduce: 1. Tell machine to boot via PXE. 2. Wait. 3. Actual results: Stalled installation. Expected results: Completed installation. Additional info: Of five identical machines I attempted to install yesterday, three failed in this way. Restarting installation on those three, one more succeeded. Two continue to fail as of this time, after about 16 hours. Note that the log files (attached) were not updated after the first few seconds of the installation attempt.
Created attachment 1151486 [details] /tmp/anaconda.log
Created attachment 1151487 [details] /tmp/dnf.log
Created attachment 1151488 [details] /tmp/dnf.rpm.log
Created attachment 1151489 [details] /tmp/ifcfg.log
Created attachment 1151490 [details] /tmp/program.log
Created attachment 1151491 [details] /tmp/storage.log
Created attachment 1151492 [details] /tmp/syslog
It looks like udev settle got stuck? 18:03:38,917 INFO program: Running... udevadm settle --timeout=300 Is it still showing up in ps -ax | grep [u]devadm If so what does udevadm monitor show? Activity of any kind? It also looks like there are several large time jumps in syslog, that may or may not have anything to do with it.
For the current failures, I was able to complete the installations by re-starting the process. I don't have a current failure on which to run the suggested commands. Experience says it will happen again so I'll report that result when it does. If the time jumps are around 7 or 8 hours, that would probably be related to the difference between PDT and UTC. Kickstart is generally used unattended. That means a failure of this sort doesn't show up until someone notices that things haven't finished. Process automation isn't reliable and manual intervention is needed. I'd really like to find a way to insure that any failure is either reported quickly or re-tried until it succeeds.
It took longer than expected but I now have another example to report. Unfortunately, "ps -ax | grep [u]devadm" does not report an active process. "top" reports that top itself is the only continuously active process, though tmux shows up occasionally. A complete "ps -ef" output is attached.
Created attachment 1177488 [details] Output of "ps -ef" while problem is active.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.