Bug 1327407

Summary:	NetworkManager should be disable per default in baremetal image
Product:	Red Hat OpenStack	Reporter:	Cyril Lopez <cylopez>
Component:	rhosp-director	Assignee:	Mike Burns <mburns>
Status:	CLOSED CANTFIX	QA Contact:	Omri Hochman <ohochman>
Severity:	low	Docs Contact:
Priority:	high
Version:	7.0 (Kilo)	CC:	dbecker, dtantsur, hjensas, jcoufal, jschluet, mburns, morazi, rhel-osp-director-maint
Target Milestone:	---
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-14 15:55:11 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:

Description Cyril Lopez 2016-04-15 06:11:11 UTC

Description of problem:
NetworkManager is enable in the baremetal image. 
In first, I don't understand why cause all network are set with NM_CONTROLLED=no.
Second, when the compute use Contrail 3.0.x, could have a kernel panic due to NetworkManager at boot.

Version-Release number of selected component (if applicable):
openstack-full-7.2
kernel-3.10.0-327.3.1.el7.x86_64
Contrail 3.0

How reproducible:


Steps to Reproduce:
1. Deploy with director
2. Install contrail
3. Install vrouter on compute
4. reboot the compute

Actual results:
Kernel panic


Additional info:

Comment 2 Cyril Lopez 2016-04-19 08:51:10 UTC

EDIT :
The kernel panic is related to Contrail 3.0.x vrouter. If the module is not loaded properly and you are doing a ifup on a contrail interface, you got a kernel panic. Is not related to NetworkManager.

Comment 3 Dmitry Tantsur 2016-10-14 15:55:11 UTC

Hi! Judging by comment #2, there is nothing to be fixed on our side, right? Please reopen with more details, if you expect us to change something.