Bug 1460904 - [anaconda] Network service doesn't assign IP to VLAN interface while performing L2 iSCSI BFS
[anaconda] Network service doesn't assign IP to VLAN interface while perform...
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager (Show other bugs)
7.3
x86_64 Linux
high Severity high
: rc
: ---
Assigned To: Lubomir Rintel
Desktop QE
:
Depends On:
Blocks: 1470965
  Show dependency treegraph
 
Reported: 2017-06-13 01:48 EDT by Praveen N
Modified: 2017-08-21 07:23 EDT (History)
18 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)
anaconda logs from /tmp and inteface details (10.81 MB, application/zip)
2017-06-13 01:48 EDT, Praveen N
no flags Details
/tmp/syslog (from the Description logs) containing NetworkManager messages (855.51 KB, text/plain)
2017-06-13 04:08 EDT, Radek Vykydal
no flags Details

  None (edit)
Description Praveen N 2017-06-13 01:48:34 EDT
Created attachment 1287163 [details]
anaconda logs from /tmp and inteface details

Description of problem:
Network service fails to assign IP's to VLAN interface while performing L2 iSCSI BFS

Version-Release number of selected component (if applicable):
anaconda-21.48.22.93-1

How reproducible:
Always

Steps to Reproduce:
1.Configure supported NIC to perform L2 iSCSI BFS
2.Mount RHEL7.3-x86_64 iso and proceed for installation
3.Add linux dd ip=ibft boot option to inject drivers and invoke ibft service
4.After injecting drivers and language selection menu enter into terminal by keying Ctrl+Alt+F2
5.Check interface status
  #ip link show; ip addr show 

Actual results:
IP is not assigned to VLAN(ibft0.x) interface created over parent interface(ibft0)

here 'x' refers to VLAN ID

Expected results:
IP should be assigned to VLAN interface for logging into target

Additional info:
1.Link is UP on Parent interface(ibft0) and IP is assigned correctly. 
2.Link is down on VLAN interface(ibft0.x) and no IP is assigned
3.Even if we try to create network config file for ibft0.x using either DHCP/static bootproto still IP is not assigned to ibft0.x
Comment 2 Radek Vykydal 2017-06-13 04:08 EDT
Created attachment 1287184 [details]
/tmp/syslog (from the Description logs) containing NetworkManager messages

Seems that NetworkManager (ibft plugin) fails to activate a connection on ibft0.25 for some reason:

22:03:13,279 DEBUG NetworkManager:<debug> [1497304993.2795] device[0x7fe79c9cec30] (ibft0.25): constructed (NMDeviceVlan)
22:03:13,279 DEBUG NetworkManager:<debug> [1497304993.2795] device[0x7fe79c9cec30] (ibft0.25): start setup of NMDeviceVlan, kernel ifindex 12
22:03:13,280 DEBUG NetworkManager:<debug> [1497304993.2796] platform-linux: error reading /sys/class/net/ibft0.25/phys_port_id: Failed to read from file '/sys/class/net/ibft0.25/phys_port_id': Operation not supported
22:03:13,280 DEBUG NetworkManager:<debug> [1497304993.2796] platform-linux: sysctl: reading '/sys/class/net/ibft0.25/dev_id': '0x0'
22:03:13,280 DEBUG NetworkManager:<debug> [1497304993.2797] device[0x7fe79c9cec30] (ibft0.25): hw-addr: hardware address now 00:0E:1E:D5:C1:57
22:03:13,280 DEBUG NetworkManager:<debug> [1497304993.2797] device[0x7fe79c9cec30] (ibft0.25): hw-addr: update initial MAC address 00:0E:1E:D5:C1:57
22:03:13,280 DEBUG NetworkManager:<debug> [1497304993.2797] device[0x7fe79c9cec30] (ibft0.25): hw-addr: read permanent MAC address '00:0E:1E:D5:C1:57'
22:03:13,280 DEBUG NetworkManager:<debug> [1497304993.2797] device[0x7fe79c9cec30] (ibft0.25): carrier is OFF
22:03:13,280 DEBUG NetworkManager:<debug> [1497304993.2797] device[0x7fe79c9cec30] (ibft0.25): unmanaged: flags set to [platform-init,!parent=0x10/0x14/unmanaged/unrealized, set-managed [parent=0x4])
22:03:13,281 DEBUG NetworkManager:<debug> [1497304993.2797] device[0x7fe79c9cec30] (ibft0.25): unmanaged: flags set to [platform-init,external-down,!parent=0x810/0x814/unmanaged/unrealized, set-unmanaged [external-down=0x800])
22:03:13,281 DEBUG NetworkManager:<debug> [1497304993.2797] device[0x7fe79c9cec30] (ibft0.25): unmanaged: flags set to [platform-init,external-down,!parent,!loopback=0x810/0x81c/unmanaged/unrealized, set-managed [loopback=0x8])
22:03:13,281 DEBUG NetworkManager:<debug> [1497304993.2798] device[0x7fe79c9cec30] (ibft0.25): unmanaged: flags set to [external-down,!parent,!loopback,!platform-init=0x800/0x81c/manageable/unrealized, set-managed [platform-init=0x10])
22:03:13,281 DEBUG NetworkManager:<debug> [1497304993.2798] device[0x7fe79c9cec30] (ibft0.25): unmanaged: flags set to [external-down,!parent,!loopback,!platform-init,!user-settings=0x800/0x85c/manageable/unrealized, set-managed [user-settings=0x40])
22:03:13,281 DEBUG NetworkManager:<debug> [1497304993.2798] device[0x7fe79c9cec30] (ibft0.25): unmanaged: flags set to [external-down,!sleeping,!parent,!loopback,!platform-init,!user-settings=0x800/0x85d/manageable/unrealized, set-managed [sleeping=0x1])
22:03:13,282 INFO NetworkManager:<info>  [1497304993.2808] manager: (ibft0.25): new VLAN device (/org/freedesktop/NetworkManager/Devices/11)
Comment 3 Radek Vykydal 2017-06-13 04:09:41 EDT
Passing to NetworkManager for debugging.

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