Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1117277 - Test Packstack/RHEL OSP on RHEL 7 nodes where Network Manager is NOT disabled
Test Packstack/RHEL OSP on RHEL 7 nodes where Network Manager is NOT disabled
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack (Show other bugs)
5.0 (RHEL 7)
Unspecified Unspecified
high Severity medium
: z2
: 6.0 (Juno)
Assigned To: Gaël Chamoulaud
Nir Magnezi
: TestOnly, ZStream
Depends On: 1049480 1117276 1117539 1201451
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-08 08:40 EDT by Perry Myers
Modified: 2016-09-01 04:56 EDT (History)
13 users (show)

See Also:
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 11:09:54 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 130699 None None None Never
Red Hat Product Errata RHSA-2015:0789 normal SHIPPED_LIVE Important: openstack-packstack and openstack-puppet-modules security and bug fix update 2015-04-07 15:08:02 EDT

  None (edit)
Description Perry Myers 2014-07-08 08:40:40 EDT
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 08:42:48 EDT
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 13:07:44 EDT
Notes from mangelajo about possible sources of problems w/ OVS
Comment 5 Nir Magnezi 2015-03-19 04:16:18 EDT
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 01:28:10 EDT
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 03:07:14 EDT
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 11:09:54 EDT
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

Note You need to log in before you can comment on or make changes to this bug.