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.
Bug 1475728 - No vlan device after the first reboot if set vlan by network cmd in kickstart file with liveimg
Summary: No vlan device after the first reboot if set vlan by network cmd in kickstart...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: pre-dev-freeze
: 7.5
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-27 08:46 UTC by Qin Yuan
Modified: 2019-06-25 08:18 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-25 08:18:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
network-scripts (46.63 KB, application/x-gzip)
2017-07-27 08:46 UTC, Qin Yuan 		no flags Details
/var/log*,/tmp/*,sosreport (9.39 MB, application/x-gzip)
2017-07-27 08:47 UTC, Qin Yuan 		no flags Details
kickstart file (1.59 KB, text/plain)
2017-07-27 08:50 UTC, Qin Yuan 		no flags Details
View All

Description Qin Yuan 2017-07-27 08:46:19 UTC 
Created attachment 1305261 [details]
network-scripts

Description of problem:
Install RHVH via kickstart file, set network as:

network --device=em2 --bootproto=dhcp
network --device=p3p2 --bootproto=dhcp --vlanid=50

After the first reboot, there is no vlan device when checking 'ip addr | grep p3p2.50'.

The vlan device can be activated manually using ifup, or reboot again:

[root@fctest network-scripts]# ifup p3p2.50
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/3)
[root@fctest network-scripts]# ip addr | grep p3p2.50
24: p3p2.50@p3p2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    inet 192.168.50.111/24 brd 192.168.50.255 scope global dynamic p3p2.50 


Version-Release number of selected component (if applicable):
RHVH-4.1-20170723.1-RHVH-x86_64-dvd1.iso
redhat-virtualization-host-4.1-20170721.0
imgbased-0.9.34-0.1.el7ev.noarch 


How reproducible:
100%


Steps to Reproduce:
1. Prepare the kickstart file, set network as above.
2. Install RHVH via PXE.
3. After installation finished, log into system, run 'ip addr' 


Actual results:
1. After step3, there is no vlan device. 


Expected results:
1. After step3, there should be the desired vlan device as specified in kickstart file. 


Additional info:
1. bond+vlan has the same situation.
2. Configuring vlan via Anaconda GUI doesn't has this issue.
2. RHVH 4.1.3 doesn't have this issue.
3. RHEL 7.4(kernel-3.10.0-693.el7.x86_64) doesn't have this issue.
Comment 1 Qin Yuan 2017-07-27 08:47:31 UTC 
Created attachment 1305262 [details]
/var/log*,/tmp/*,sosreport
Comment 2 Qin Yuan 2017-07-27 08:50:43 UTC 
Created attachment 1305264 [details]
kickstart file
Comment 3 Ryan Barry 2017-07-27 11:20:39 UTC 
Just to confirm, this is with 7.4 Anaconda using `liveimg` in the kickstart only?
Comment 6 Qin Yuan 2017-07-27 14:48:47 UTC 
(In reply to Ryan Barry from comment #3)
> Just to confirm, this is with 7.4 Anaconda using `liveimg` in the kickstart
> only?

Actually, I'm not quite sure what do you mean, why emphasize `liveimg`. For RHVH installation via PXE, I don't know other suggested way to specify squashfs in kickstart file except using `liveimg --url=`.

For RHVH, this issue only occurs with Anaconda 7.4.
For RHEL 7.4, I used `url --url=/URL/to/RHEL-7.4-20170711.0/compose/Server/x86_64/os`
Comment 7 Ryan Barry 2017-07-27 15:15:41 UTC 
I emphasized liveimg since the behavior in Anaconda is somewhat different from "repo --url" installs, and this is not reproducible on base RHEL or 7.3 kickstart installs with liveimg (RHVH 4.1.3)
Comment 8 Sandro Bonazzola 2019-06-18 12:35:21 UTC 
Is this still reproducible on RHEL 7.7 based image?
Comment 9 Qin Yuan 2019-06-21 09:02:25 UTC 
Test with redhat-virtualization-host-4.3.5-20190620.2.el7_7, the issue is not reproducible.
Comment 10 Sandro Bonazzola 2019-06-25 08:18:10 UTC 
(In reply to Qin Yuan from comment #9)
> Test with redhat-virtualization-host-4.3.5-20190620.2.el7_7, the issue is
> not reproducible.

closing accordingly
Note You need to log in before you can comment on or make changes to this bug.