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.
Created attachment 1662668[details]
Image with traceback seen on tty1
Description of problem:
If there is a vlan device configured in kickstart that should be activated in installer, and whose IP configuration fails there is a chance that under certain conditions (race) the installation will crash.
Observed with kickstart test:
https://github.com/rhinstaller/kickstart-tests/blob/master/vlan-httpks.ks.in
Version-Release number of selected component (if applicable):
RHEL-8.2.0-20200212.n.0
anaconda-29.19.2.13-1.el8.x86_64.rpm
How reproducible:
In our kickstart tests (using boot.iso) always.
Trying to reproduce in VM I didn't succeed.
Steps to Reproduce:
I can only add our kickstart tests configuration as hints for reproduction:
VM:
2020-02-12 01:44:15,945 INFO kstest-logger: virt-install ['-n', 'kstest-vlan-httpks_(4d8e146d-105e-464f-a678-39cefb3b790c)', '-r', '2048', '--noautoconsole', '--vcpus', '1', '--rng', '/dev/random', '--noreboot', '--graphics', 'vnc', '--disk', 'path=/var/tmp/kstest-vlan-httpks.0kg8kus2/disk-a.img,cache=unsafe,bus=sata', '--network', 'network:default', '--network', 'network:default', '--network', 'network:default', '--network', 'network:default', '--network', 'network:default', '--network', 'network:default', '--disk', 'path=/var/tmp/kstest-vlan-httpks.0kg8kus2/boot.kstest.iso,device=cdrom,readonly=on,shareable=on', '--extra-args', ' debug=1 inst.debug rd.shell=0 rd.emergency=poweroff ip=enp1s0:dhcp ip=enp2s0:dhcp inst.ks=http://10.0.137.9:40000/ks.cfg inst.kernel.hung_task_timeout_secs=1200 stage2=hd:CDLABEL=RHEL-8-2-0-BaseOS-x86_64', '--location', '/var/tmp/kstest-vlan-httpks.0kg8kus2/boot.kstest.iso,kernel=isolinux/vmlinuz,initrd=isolinux/initrd.img', '--channel', 'tcp,host=127.0.0.1:53695,mode=connect,target_type=virtio,name=org.fedoraproject.anaconda.log.0']
Boot options:
01:46:03,778 NOTICE xserver:[ 96.202] Kernel command line: debug=1 inst.debug rd.shell=0 rd.emergency=poweroff ip=enp1s0:dhcp ip=enp2s0:dhcp inst.ks=http://10.0.137.9:40000/ks.cfg inst.kernel.hung_task_timeout_secs=1200 stage2=hd:CDLABEL=RHEL-8-2-0-BaseOS-x86_64
Kickstart:
#test name: vlan-httpks
# repos/default.ks override generated by ansible test tooling
url --url=http://download.eng.brq.redhat.com/rhel-8/nightly/RHEL-8/latest-RHEL-8.2.0/compose/BaseOS/x86_64/os/
repo --name=appstream --baseurl=http://download.eng.brq.redhat.com/rhel-8/nightly/RHEL-8/latest-RHEL-8.2.0/compose/AppStream/x86_64/os/
install
# Parent configured and activated in initramfs
network --device enp2s0 --vlanid 104 --bootproto dhcp --no-activate
# Parent not configured / activated in initramfs
network --device enp3s0 --vlanid 105 --bootproto dhcp
# Parent configured via kickstart, do not activate, onboot yes
network --device enp4s0 --bootproto dhcp
network --device enp4s0 --vlanid 106 --bootproto dhcp
# Parent not configured via kickstart, activate, onboot no
network --device enp5s0 --vlanid 107 --bootproto dhcp --activate --onboot no
# Parent not configured via kickstart, interfacename
network --device enp6s0 --vlanid 1008 --bootproto dhcp --interfacename myvlan1008
bootloader --timeout=1
zerombr
clearpart --all
autopart
keyboard us
lang en
timezone America/New_York
rootpw qweqwe
shutdown
%packages
%end
Actual results:
Installation crashes early after switch root (see attached image).
Expected results:
Installation proceeds.
Additional info:
This in not a problem on master/Fedora.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (anaconda bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4729