Created attachment 1862507 [details] grub.cfg Description of problem: I have a pxe server that provides fedora 36 with kickstart, because in fedora 35 anaconda aborts with an error because of a known bug with systemd/etc/resolv.d. when i boot that and try to install it (same configuration as with F35), it never stops. I let it run for about 10 hours, no change, it only prints tons of "......" Version-Release number of selected component (if applicable): Used all packages from Fedora-Everything-netinst-x86_64-36-20220218.n.0.iso How reproducible: always Steps to Reproduce: 1. boot with the attached kickstart and grub.cfg over pxe Actual results: it only prints "...." Expected results: to finish the installation Additional info:
Created attachment 1862508 [details] kickstart file
Created attachment 1862511 [details] anaconda.log
Created attachment 1862512 [details] dbus.log
Created attachment 1862513 [details] dnf.librepo.log
Created attachment 1862514 [details] packaging.log
Created attachment 1862515 [details] program.log
Created attachment 1862516 [details] storage.log
Created attachment 1862517 [details] storage.state
Created attachment 1862518 [details] syslog
i changed the inst.addrepo url and now it seems to work. i thought its enough to replace the 35 with 36 in inst.addrepo=http://download.fedoraproject.org/pub/fedora/linux/releases/35/Everything/x86_64/os/ maybe that could be somehow improved that an error is thrown if the location does not exist? right now it just tries endlessly to access the url, no matter if its valid or not
its failing again with the same behaviour, the url is correct, so i assume it is something else
i booted now multiple times the server-dvd iso, that worked. so i assume, something is broken in the netinst iso i raise the severity to medium
Hi, http://download.fedoraproject.org/pub/fedora/linux/releases/36/Everything/x86_64/os/ doesn't exist, because Fedora 36 wasn't released yet. It should be http://download.fedoraproject.org/pub/fedora/linux/development/36/Everything/x86_64/os/. The DVD ISO probably works, because the repositories are part of the ISO.
maybe i wrote wrong.. its like 2 problems. 1) if the url is wrong (like as you mentioned releases vs development), there is no error thrown 2) if the url is correct (i applied it) and boot the netinst, it still gets into an endless loop with "..." - the server dvd works without problems
I am seeing the same behavior with text-mode kickstarts seemingly printing endless series of dots with f36. (I'm building VMs using virt-install and passing a kickstart through).
Proposed as a Blocker for 36-final by Fedora user mhjacks using the blocker tracking app because: Text-mode installation via kickstart does not complete, violating (as I understand it) https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_Text.
OK, upon further review: the url= line in my kickstart was pointing to an http URL which did not in fact exist (404). When I corrected the URL to point to a repo that very definitely _does_ exist, the kickstart installation began and proceeded as expected. On that basis, I believe my nomination of this bug for blocker status was in error.
I tested a simple kickstart installation in a VM using https://fedorapeople.org/groups/qa/kickstarts/example-minimal.ks . I only added "text" as the first line for force text-based install. Everything worked fine. A graphical install also worked fine. However, I had networking in my VM broken initially. And when I started a graphical installation during that, I only saw a gray screen, forever, with no error message, nothing. Looking into logs I saw that repos metadata failed to download. So there indeed might be a problem when repos are inaccessible, when anaconda waits forever, even in graphical mode.
imo: it would help a lot if there would be any kind of progress information about what actually happens behind the scenes. i had this only with the netinstall a couple of weeks ago, the server dvd did not have this behaviour. i will test this weekend when i continue my thesis if i can still reproduce that
The basic issue, "Anaconda prints dots instead of reporting issues" is stil in F37.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.