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 1131812 [details] installtion logs Description of problem: During the installation of RHEL 7.2, physical network interface is configured even when the vlan interface is defined in kickstart and had to manually up the VLAN after the first boot. Version-Release number of selected component (if applicable): RHEL 7.2 How reproducible: 100%, the VLAN interface will not come up Steps to Reproduce: 1. kickstart file used in reproducer: ~~~ install text cdrom lang en_US keyboard us #network --bootproto dhcp onboot=yes network --device=eth0 --bootproto=dhcp --onboot=no network --device=eth0 --vlanid=101 --bootproto=static --ip=192.168.100.100 --netmask=255.255.255.0 --gateway=192.168.100.100 --nameserver=192.168.100.100 --hostname=test --onboot=yes zerombr bootloader --location mbr --append=" biosdevname=0 net.ifnames=0 " timezone America/Denver auth --enablemd5 --enableshadow rootpw redhat selinux --disabled firewall --disabled skipx clearpart --all --initlabel part /boot --fstype=ext3 --size=200 part pv.01 --size=1000 --grow part swap --size=1000 --fstype=swap volgroup myvg pv.01 logvol / --vgname=myvg --name=rootvol --size=1000 --grow %packages @base @core %end %post --nochroot dmesg &> /tmp/dmesg.log fdisk -l &> /tmp/fdisk.log parted -sl &> /tmp/parted.log cat /proc/partitions &> /tmp/proc_part.log multipath -ll &> /tmp/mpath.log ls -lR /dev &> /tmp/dev.log cat /proc/scsi/scsi &> /tmp/proc_scsi.log tar cvf /mnt/sysimage/root/installation_logs.tar /tmp/*log* %end ~~~ 2. anaconda logs seen during installation: ~~~ 12:04:01,308 DEBUG anaconda: setting locale to: en_US.UTF-8 12:04:01,322 DEBUG anaconda: network: devices found ['eth0'] 12:04:01,498 DEBUG anaconda: network: pre kickstart - adding connection for eth0.101 12:04:01,507 DEBUG anaconda: network: kickstart pre section applied for devices ['eth0.101'] 12:04:01,624 DEBUG anaconda: setOnboot: UnknownDeviceError('eth0.101', GLib.Error('GDBus.Error:org.freedesktop.NetworkManager.UnknownDevice: No device found for the requested iface.', 'g-io-error-quark', 36)) 12:04:01,625 DEBUG anaconda: network: setting real kickstart ONBOOT value for devices ['eth0', 'eth0.101'] ~~~ Actual results: vlan interface not being activated. Expected results: 1. The interface eth0 had dhcp IP address during installation, as that is a primary device from where installation was carried out, the same settings will reflect on the base machine post installation. 2. the device eth0.101 should have been enabled as it was mentioned --onboot=yes, but it looked onboot=no. 3. After the installation, I did modify both the files /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/network-scripts/ifcfg-eth0.101. 4. The changes were as follows. /etc/sysconfig/network-scripts/ifcfg-eth0 => onboot=no /etc/sysconfig/network-scripts/ifcfg-eth0.101 => onboot=yes 5. Restarted the network service service network restart The device eth0 got down and eth0.101 got up with proper configurations. Additional info: - attaching installation logs (installation_logs.tar) - same behavior seen in RHEL 6.7 testing