Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.
Comment 13Beniamino Galvani
2016-07-04 09:40:35 UTC
(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.
Comment 15Beniamino Galvani
2016-07-04 09:57:52 UTC
(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 ***