Bug 1113636

Summary: Disable NetworkManager.
Product: Red Hat OpenStack Reporter: Lee Yarwood <lyarwood>
Component: openstack-packstackAssignee: Martin Magr <mmagr>
Status: CLOSED DUPLICATE QA Contact: Ami Jeain <ajeain>
Severity: high Docs Contact:
Priority: high    
Version: 5.0 (RHEL 7)CC: acathrow, aortega, derekh, yeylon
Target Milestone: rc   
Target Release: 5.0 (RHEL 7)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-26 15:14:38 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 Lee Yarwood 2014-06-26 14:19:54 UTC
Description of problem:
We currently require NetworkManager to be disabled in RHEL OSP environments [1]. I don't believe this has changed with RHEL {6,7} OSP 5 and so it would be great to automate this via the puppet modules.

[1] https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/5/html-single/Installation_and_Configuration_Guide/index.html#Disabling_Network_Manager

Version-Release number of selected component (if applicable):
openstack-puppet-modules-2014.1-9.el7ost

How reproducible:
Always.

Steps to Reproduce:
1. Install RHEL OSP using puppet / Foreman.
2. Confirm if NetworkManager is enabled.

Actual results:
NetworkManager is left enabled or disabled.

Expected results:
NetworkManager is disabled across all hosts.

Additional info:
BZ#967366 is the original docs bug.

Comment 2 Perry Myers 2014-06-26 14:44:00 UTC
I'm moving this bug to openstack-packstack since we probably need to implement disabling of NM in Packstack itself, since on the Foreman side we handle this via the kickstarts used to provision the systems.

@aortega, please weigh in when you've had a chance to investigate.

Comment 3 Alvaro Lopez Ortega 2014-06-26 14:53:09 UTC
Ivan just found this related commit:
https://github.com/stackforge/packstack/commit/2249cd37156c477e1a4f08d5497d4a3854c4f4a7

Comment 4 Martin Magr 2014-06-26 15:14:38 UTC
Disabling NM and enabling network service during packstack run disconnects packstack from nodes, so this is not doable. If we want to disable it, it has to be disabled manually before packstack run.

*** This bug has been marked as a duplicate of bug 967369 ***