Bug 1258115

Summary: Do not use NM for br-ex/eth0 in overcloud images
Product: Red Hat OpenStack Reporter: Marko Myllynen <myllynen>
Component: openstack-tripleo-image-elementsAssignee: James Slagle <jslagle>
Status: CLOSED INSUFFICIENT_DATA QA Contact: yeylon <yeylon>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: agarciam, calfonso, dprince, hbrock, mburns, myllynen, rhel-osp-director-maint, srevivo
Target Milestone: ---   
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-30 16:53:00 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 Marko Myllynen 2015-08-29 10:14:05 UTC
Description of problem:
When deploying overcloud with three controllers and two computes we saw compute nodes occasionally becoming unreachable, adding NM_CONTROLLED=no to ifcfg-br-ex and ifcfg-eth0 solved the issue. Looks like this should be by default.

Comment 4 Dan Prince 2015-08-31 14:02:46 UTC
I believe this may be solved by this upstream revision:

http://git.openstack.org/cgit/openstack/os-net-config/commit/?id=afcd514b7cb4b9a465c615c0a16d7f6af2a1d0ed

Is this just something to backport and/or rebase to fix?

Comment 5 James Slagle 2015-08-31 14:07:32 UTC
can you check what version of os-net-config is installed on your overcloud nodes?

rpm -q os-net-config

Comment 6 Hugh Brock 2015-08-31 14:43:03 UTC
This should be in the current version of os-net-config, which is 0.1.4. It was fixed with this patch:

http://git.openstack.org/cgit/openstack/os-net-config/commit/?id=afcd514b7cb4b9a465c615c0a16d7f6af2a1d0ed

It is possible you are using out-of-date images, or non-updated ones. If not, then we need to investigate where this regression came from. Can you have a look at the package versions on your deployment image and the actual code and let us know what the situation is?

Thanks...

Comment 7 chris alfonso 2015-09-14 17:00:10 UTC
Waiting for your result on checking that you are using the latest

Comment 9 Red Hat Bugzilla 2023-09-14 03:04:27 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days