Bug 1368079

Summary: Failed to setup vlan via cfg files
Product: [oVirt] ovirt-node Reporter: dguo
Component: GeneralAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED NOTABUG QA Contact: dguo
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.0CC: bugs, cshao, dguo, huzhao, jiawu, leiwang, rbarry, weiwang, yaniwang, ycui, yzhao
Target Milestone: ---Keywords: Regression, TestBlocker
Target Release: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
ycui: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-18 11:09:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
network scripts
none
ip address before restart network service
none
ip address after restart the network service
none
output of the "journalctl -xe"
none
sosreport none

Description dguo 2016-08-18 10:11:31 UTC
Created attachment 1191839 [details]
network scripts

Description of problem:
Failed to setup vlan via cfg files

Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.0-20160817.0.x86_64
imgbased-0.8.4-1.el7ev.noarch
vdsm-4.18.11-1.el7ev.x86_64
Red Hat Virtualization Manager Version: 4.0.2.6-0.1.el7ev

How reproducible:
100%

Steps to Reproduce:
1. Install RHVH
2. write new cfg files under /etc/sysconfig/network-scripts for creating vlan 
3. Restart the network service "service network restart"

Actual results:
1.After step#3, catch the following error, vlan configuration failed.
"""
Restarting network (via systemctl):  Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details."
"""

From the output of "journalctl -xe", can see 
"""
Error: Connection activation failed: Connection 'Vlan p3p1.20' is not available on the device p3p1.20 at this time.
"""

Expected results:
1. After step#3, the network restart successfully, and the vlan were created successfully with dhcp address.

Additional info:
Even restart the system, the network service could not able to start.

Comment 1 dguo 2016-08-18 10:12:51 UTC
Created attachment 1191840 [details]
ip address before restart network service

Comment 2 dguo 2016-08-18 10:13:47 UTC
Created attachment 1191841 [details]
ip address after restart the network service

Comment 3 dguo 2016-08-18 10:14:39 UTC
Created attachment 1191842 [details]
output of the "journalctl -xe"

Comment 4 dguo 2016-08-18 10:16:15 UTC
Created attachment 1191843 [details]
sosreport

Comment 5 Fabian Deutsch 2016-08-18 10:39:37 UTC
The ifcfg-p3p1.20 file contains:

NM_CONTROLLER="no"

it should be

NM_CONTROLLED="no"

Please retry with this change

Comment 6 dguo 2016-08-18 11:09:19 UTC
Verified after modify the script.

Sorry for such a 'typo' mistake. close it.