Bug 1327407 - NetworkManager should be disable per default in baremetal image
Summary: NetworkManager should be disable per default in baremetal image
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
: 10.0 (Newton)
Assignee: Mike Burns
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-15 06:11 UTC by Cyril Lopez
Modified: 2019-12-16 05:39 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-14 15:55:11 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.