Hide Forgot
Description of problem: dnf install <packagename> hangs at confirmation prompt if autologin is enabled for the systemd container. Version-Release number of selected component (if applicable): dnf-1.1.5-1.fc22.noarch How reproducible: Steps to Reproduce: dnf -y --releasever=22 --nogpg --installroot=/var/lib/machines/container1 --disablerepo='*' --enablerepo=fedora --enablerepo=updates install fedora-release systemd passwd rootfiles dnf vim-minimal sed -i '/^root/s!*!!' /var/lib/machines/container1/etc/shadow cp /var/lib/machines/container1/usr/lib/systemd/system/container-getty\@.service /var/lib/machines/container1/etc/systemd/system sed -i '/^ExecStart=/s!--keep-baud!--keep-baud --autologin root!' /var/lib/machines/nagios/etc/systemd/system/container-getty\@.service machinectl start container1 machinectl login container1 dnf install <arbitrary-package> ... *** HANG *** Actual results: Expected results: Wouldn't expect autologin to hang dnf. Additional info:
P.S. I just noticed a typo in the second sed command I supplied. It should have been: sed -i '/^ExecStart=/s!--keep-baud!--keep-baud --autologin root!' /var/lib/machines/container1/etc/systemd/system/container-getty\@.service
Does it hang in transaction confirmation prompt or during gpg key import? Does it work if you add `-y` as a parameter?
With '-y', dnf install <package> works. Without '-y', when I type "y<enter>" at the prompt, the carriage returns, but the line does not advance on the terminal and at that point, dnf is hung.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.