Description of problem: Using generic boot.iso from rawhide 20160103 and 20160104, I'm unable to install fedora workstation. The installer is stuck on "installing rootfiles.noarch", nothing else happens. Version-Release number of selected component (if applicable): anaconda 24.8-1 rootfiles-8.1-18.fc23.noarch Steps to Reproduce: 1. boot the installer using generic boot.iso 2. select workstation in software selection 3. proceed in installation with everything else set to default 4. installer will get stuck on "installing rootfiles.noarch"
Created attachment 1111772 [details] anaconda.log
Created attachment 1111773 [details] packaging.log
Created attachment 1111774 [details] dnf.log
Created attachment 1111775 [details] dnf.rpm.log
Interesting is that installing Server from netinst works and rootfiles package is also installed there.
Proposed as a Blocker for 24-alpha by Fedora user lbrabec using the blocker tracking app because: Violation of alpha criterion: Installer requirements - Installation interfaces: When using a dedicated installer image, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces.
Is that really stuck in rootfiles.noarch? In dnf.rpm.log I see: led 05 11:05:55 INFO Installed: rootfiles-8.1-18.fc23.noarch led 05 11:05:55 INFO Installed: rootfiles-8.1-18.fc23.noarch Based on it, it might be the next package in the transaction. There was no update in rootfiles package for quite a long time, so I think something else is causing this issue. This package just creates dotfiles in /root directory.
I did the installation again, but now, I was checking output of 'top' at the end of package installation phase. And truly, it seems that it is not stuck on rootfiles. From what I caught, the next commands eating the most of cpu are: update-mime-database depmod dracut pigz mandb After that, the system gets to relatively idle state (anaconda eating around 2% of cpu). It looks like anaconda does the job in background but the gui doesn't refresh. However, after rebooting from another tty, the system won't boot. I guess that some installation phase was skipped, maybe the action connected to reboot/finish configuration button, which I couldn't click because it wasn't shown?
I tried text installation with same result, it gets stuck on 'Installing rootfiles.noarch', several commands (dracut etc.) then run in background and then idle.
When it gets stuck, can you run 'killall -USR2 anaconda' and attach the /tmp/anaconda-tb* file?
Created attachment 1112208 [details] anaconda-tb-*
I see the same issue, and I think this is a clue: Jan 07 13:31:37 ERR Error in PRETRANS scriptlet in rpm package copy-jdk-configs Jan 07 13:31:37 ERR Error in PRETRANS scriptlet in rpm package copy-jdk-configs See dnf.rpm.log
This error also occurs these days when doing a network install of Fedora 23 using the official boot image! I suppose it is related to a recent bug in copy-jdk-configs which has slipped into the Fedora 23 updates and the developement tree. From the change log: "* Wed Dec 16 2015 Jiri Vanek <jvanek redhat com> - 1.1-2 - package now "installs" also during pretrans, so pretrasn scripts can use it - pretrasn "install" is removed in postrans" I therefore suggest setting the component to copy-jdk-configs.
(In reply to Joachim Frieben from comment #13) > This error also occurs these days when doing a network install of Fedora 23 > using the official boot image! I suppose it is related to a recent bug in Yes, I am using PXE boot and install of FC23, I am observer exactly what the reporter observes - the installation fails and it looks like the reason is 'copy-jdk-configs'
Hello. Have anybdy idea how can I test it with local (theoretically fixed) packages?
Lukas, is there stacktace of copy-jdk-configs please? I have suspicions to: http://pkgs.fedoraproject.org/cgit/rpms/copy-jdk-configs.git/tree/copy-jdk-configs.spec#n37 or http://pkgs.fedoraproject.org/cgit/rpms/copy-jdk-configs.git/tree/copy-jdk-configs.spec#n40 As those two are the only harmfull commands in that pretrans.
Currently I was abel to reproduce by various cheating on /var/lib /var/lib/rpm-state dirs (it is not solid reproducer) From that experience I fixed the packages: http://pkgs.fedoraproject.org/cgit/rpms/copy-jdk-configs.git/commit/?id=5ab2a1f2e5bfb1802ef99a24b60139ef5f09435d Now I'm building it for fedoras: f24 http://koji.fedoraproject.org/koji/taskinfo?taskID=12464996 f23 http://koji.fedoraproject.org/koji/taskinfo?taskID=12464999 and same for f22 and epels (but there it do not harm for now) If anybody is able to confirm that this is fixed, I will be really happy.
(In reply to jiri vanek from comment #17) > If anybody is able to confirm that this is fixed, I will be really happy. Jiri, I am confirming that "copy-jdk-configs-1.1-3.fc23.noarch.rpm" has the problem fixed, hopefully you can have it published soon. Thanks!
Thank you, I'm creating fedora udpates then
copy-jdk-configs-1.1-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-5e1c3ef16e
copy-jdk-configs-1.1-3.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-86c3668bde
copy-jdk-configs-1.1-3.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-aa6237387c
copy-jdk-configs-1.1-3.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-4ee40e04b9
(In reply to Artem Bityutskiy from comment #18) > Jiri, I am confirming that "copy-jdk-configs-1.1-3.fc23.noarch.rpm" has the > problem fixed, hopefully you can have it published soon. > > Thanks! Confirmed.
copy-jdk-configs-1.1-3.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-aa6237387c
copy-jdk-configs-1.1-3.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-4ee40e04b9
copy-jdk-configs-1.1-3.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-86c3668bde
copy-jdk-configs-1.1-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-5e1c3ef16e
copy-jdk-configs-1.1-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
copy-jdk-configs-1.1-3.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
copy-jdk-configs-1.1-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
copy-jdk-configs-1.1-3.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.