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
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.
Notes from mangelajo about possible sources of problems w/ OVS
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
I think the test is good, if there is a need for more testing , please update the bug
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.
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