Bug 1663488

Summary:	wrong ovs config disconnects the node
Product:	Container Native Virtualization (CNV)	Reporter:	Vatsal Parekh <vparekh>
Component:	Networking	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED NOTABUG	QA Contact:	Meni Yakove <myakove>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	future	CC:	aconole, atragler, cnv-qe-bugs, ovs-qe
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	CNV 1.4 with OCP 3.11
Last Closed:	2019-01-10 09:58:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vatsal Parekh 2019-01-04 14:02:36 UTC

Description of problem:
While trying the steps mentioned in the doc (https://cnv_setup--ocpdocs.netlify.com/openshift-enterprise/latest/cnv_users_guide/cnv_users_guide.html#cnv_userguide_advanced_vm_config)
```
$ ovs-vsctl add-br br1
$ ovs-vsctl add-port br1 eth1
```
Trying it on a compute node of the cluster, which actually didn't had any interfaces named eth1 in `ifconfig`, after these 2 commands the node gets disconnected, cannot ping or ssh, and the node stays disconnected even after reboot.
Was able to reproduce the same behavior with `eth0` as well
But couldn't get any logs because the node disconnects exactly after `$ ovs-vsctl add-port br1 eth1`

Version-Release number of selected component (if applicable):
CNV 1.4 + OCP 3.11


How reproducible:


Steps to Reproduce:
1.From one of the node
  $ ovs-vsctl add-br br1
  $ ovs-vsctl add-port br1 eth1
2.
3.

Actual results:
The node gets completely disconnected0

Expected results:
Should error if the interface is wrong

Additional info:

Comment 1 Vatsal Parekh 2019-01-09 12:00:28 UTC

Changing this from CNV to RHEL as this seems on OVS and not on CNV.

Comment 3 Aaron Conole 2019-01-09 16:22:46 UTC

I don't understand this bug at all.  I can put lots of invalid configs into my OvS 
instance, and it won't take down networking.  Sounds like something related to 
your setup.

Reassigning to original component.

Comment 4 Vatsal Parekh 2019-01-10 09:58:03 UTC

(In reply to Aaron Conole from comment #3)
> I don't understand this bug at all.  I can put lots of invalid configs into
> my OvS 
> instance, and it won't take down networking.  Sounds like something related
> to 
> your setup.
> 
> Reassigning to original component.

Seems like it was due to some issues with the environment, built a new env and it seems working.
Closing this.