Hide Forgot
Description of problem: Following setup is used: - kickstart has a reboot command - kickstart is fetched on a dhcp server, over a VLAN (vlan id 8 in our case) - installation is done through the network (NFS server reached through vlan id 8) - installation is stuck at the end, the machine does not reboot. Version-Release number of selected component (if applicable): anaconda-21.48.22.56-1.el7 How reproducible: Systematic Steps to Reproduce: 1. Write a kickstart file with the command reboot in it. The repo used for installation has to be located on a NFS server that is reached through a VLAN. 2. Set up dhcp server that will serve the kickstart over a VLAN 3. On target machine, specify anaconda boot parameters "vlan=eth2.8:eth2 ks" 4. Let the installation run 5. Installation will hang at reboot. Control + Alt + FX does not work, Control + Alt + Del does not work. Actual results: Installation is stuck at the end. Expected results: Machine reboots to newly installed system. Additional info: When the command "systemctl --no-wall reboot" is issued by anaconda, NetworkManager will bring down the parent interface of the VLAN (eth2 in our case). Since we have the NFS mount through the VLAN interface, system is stuck.
Please attach the logs from /tmp/*log as individual text/plain attachments. Also include the output of mount, this sounds similar to the iscsi problems where dracut didn't know it was a network mount and wasn't umounting in the right order.
Created attachment 1154533 [details] Result of mount command in anaconda
Created attachment 1154534 [details] Anaconda log - journal.log
Created attachment 1154535 [details] Anaconda log - anaconda.log
Created attachment 1154536 [details] Anaconda log - ifcfg.log
Created attachment 1154538 [details] Anaconda log - storage.log
Created attachment 1154540 [details] Anaconda log - syslog
There you go ! Let me know if you need more logs.
systemd should be unmounting the nfs mounts before shutting down the network.
Looks like the issues with missing After=dbus.service inside NetworkManager.service. If I am wrong feel free to reassign this back.
We found a workaround in the meantime; if we assign an IP address to the parent interface (eth2) using the network command in kickstart, then the machine reboots after installation. I also tested Lukas' suggestion and manually added "After=dbus.service" to NetworkManager.service during installation and the machine reboots correctly after installation.
(In reply to nico.martin from comment #12) > I also tested Lukas' suggestion and manually added "After=dbus.service" to > NetworkManager.service during installation and the machine reboots correctly > after installation. Does this work even without the workaround of assigning an IP address to the parent interface? If so, probably we can close this as duplicate of bug 1311988
Yes, manually adding "After=dbus.service" to NetworkManager.service makes it work without any other modification/workaround.
(In reply to nico.martin from comment #14) > Yes, manually adding "After=dbus.service" to NetworkManager.service makes it > work without any other modification/workaround. Thanks, this has been fixed in NM 1.2. *** This bug has been marked as a duplicate of bug 1311988 ***