Bug 1117115
Summary: | packstack should warn installing openstack while NM is active | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Ofer Blaut <oblaut> | |
Component: | openstack-packstack | Assignee: | Gaël Chamoulaud <gchamoul> | |
Status: | CLOSED ERRATA | QA Contact: | Toni Freger <tfreger> | |
Severity: | medium | Docs Contact: | ||
Priority: | low | |||
Version: | 5.0 (RHEL 7) | CC: | ajeain, aortega, ddomingo, derekh, gchamoul, ichavero, oblaut, sclewis, sgordon, slong, yeylon | |
Target Milestone: | z4 | Keywords: | ZStream | |
Target Release: | 5.0 (RHEL 7) | Flags: | gchamoul:
internal-review+
|
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openstack-packstack-2014.1.1-0.45.dev1279.el7ost | Doc Type: | Enhancement | |
Doc Text: |
If OpenStack Networking (neutron) is enabled, Packstack now displays a warning if the Network Manager service is active on hosts.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1130589 (view as bug list) | Environment: | ||
Last Closed: | 2015-04-16 14:02:33 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: | ||||
Bug Blocks: | 1130589 |
Description
Ofer Blaut
2014-07-08 05:17:01 UTC
Hi Ofer, Just to be sure. Is that check should be done on every hosts ? whatever the type of nodes (CONTROLLER/COMPUTE/NETWORK) ... We should warn on every thing Thanks for the clarification, Ofer ! That's what I did in the patch but wanted to be sure ... Have tested in openstack-packstack-2014.1.1-0.41.dev1251.el7ost.noarch During installation with NetworkManager in active mode, no warnings messages appear. Verified on rhel7.1 openstack-packstack-puppet-2014.1.1-0.46.dev1280.el7ost.noarch openstack-packstack-2014.1.1-0.46.dev1280.el7ost.noarch 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-0831.html |