Bug 1475728 - No vlan device after the first reboot if set vlan by network cmd in kickstart file with liveimg
No vlan device after the first reboot if set vlan by network cmd in kickstart...
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity high
: pre-dev-freeze
: 7.5
Assigned To: Anaconda Maintenance Team
Release Test Team
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-27 04:46 EDT by Qin Yuan
Modified: 2018-03-05 16:02 EST (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


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

  None (edit)
Description Qin Yuan 2017-07-27 04:46:19 EDT
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 04:47 EDT
Created attachment 1305262 [details]
/var/log*,/tmp/*,sosreport
Comment 2 Qin Yuan 2017-07-27 04:50 EDT
Created attachment 1305264 [details]
kickstart file
Comment 3 Ryan Barry 2017-07-27 07:20:39 EDT
Just to confirm, this is with 7.4 Anaconda using `liveimg` in the kickstart only?
Comment 6 Qin Yuan 2017-07-27 10:48:47 EDT
(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 11:15:41 EDT
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)

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