Bug 1117277

Summary:	Test Packstack/RHEL OSP on RHEL 7 nodes where Network Manager is NOT disabled
Product:	Red Hat OpenStack	Reporter:	Perry Myers <pmyers>
Component:	openstack-packstack	Assignee:	Gaël Chamoulaud <gchamoul>
Status:	CLOSED ERRATA	QA Contact:	Nir Magnezi <nmagnezi>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 7)	CC:	aberezin, ajeain, aortega, derekh, dnavale, gchamoul, majopela, mburns, oblaut, ohochman, rhos-maint, tfreger, yeylon
Target Milestone:	z2	Keywords:	TestOnly, ZStream
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-packstack-2014.2-0.17.dev1462.gbb05296.el7ost	Doc Type:	Enhancement
Doc Text:	With this enhancement, if OpenStack Networking is enabled, Packstack will display a warning if the Network Manager service is active on hosts.	Story Points:	---
Clone Of:	1117276	Environment:
Last Closed:	2015-04-07 15:09:54 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:
Bug Depends On:	1049480, 1117276, 1117539, 1201451
Bug Blocks:

Description Perry Myers 2014-07-08 12:40:40 UTC

Description of problem:
RHEL OSP 5 on RHEL 6 and RHEL 7 require that Network Manager be disabled.  This was primarily due to lack of resources to determine what issues would arise with NM enabled.

We should reenable NM and uncover any issues that arise.  This bug serves as an overall Tracker for issues encountered relating to NM usage when Packstack is deploying onto RHEL 7 hosts where NM is enabled

Comment 1 Perry Myers 2014-07-08 12:42:48 UTC

Note: Bug # 1117115 is for printing out a warning message when Packstack detects that NM is enabled.  This warning message will need to be reverted as part of the work on this bug.

Comment 2 Perry Myers 2014-07-09 17:07:44 UTC

Notes from mangelajo about possible sources of problems w/ OVS

Comment 5 Nir Magnezi 2015-03-19 08:16:18 UTC

Tested With: openstack-packstack-2014.2-0.17.dev1462.gbb05296.el7ost.noarch

Verification Steps:
===================
1. Deployed & Tested[1] an OpenStack setup with NetworkManager enabled.
2. Left the setup with running 6 instances for 2 Days.

Result:
=======
Instances are still reachable.

Should I test for anything in addition to that?


[1] http://jenkins-hurricane.scl.lab.tlv.redhat.com:8080/view/robot/job/robot-rhel-osp6-rhel7.1/22/console

Comment 7 Ofer Blaut 2015-03-24 05:28:10 UTC

I think the test is good, if there is a need for more testing , please update the bug

Comment 8 Miguel Angel Ajo 2015-03-30 07:07:14 UTC

The errors with NM won't happen over static execution, they usually happen when new tap devices come and go into the system, that means, creating new networks, creating new instances, destroying instances.

It's good that we run longevity tests, but may be the best approach would be running tempest several times a day over the same installation, to make sure everything seems fine over time.

Comment 10 errata-xmlrpc 2015-04-07 15:09:54 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0789.html