Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1124076

Summary: Rubygem-Staypuft: /etc/sysconfig/network-scripts/ifcfg-ethX files contain MACs of other interfaces from the same machine. This causes some interfaces not to come up on boot and eventually fails deployment.
Product: Red Hat OpenStack Reporter: Alexander Chuzhoy <sasha>
Component: rubygem-staypuftAssignee: Mike Burns <mburns>
Status: CLOSED WORKSFORME QA Contact: Omri Hochman <ohochman>
Severity: high Docs Contact:
Priority: high    
Version: 5.0 (RHEL 7)CC: aberezin, lars, mburns, morazi, yeylon
Target Milestone: ga   
Target Release: Installer   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-05 18:31:05 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:
Attachments:
Description Flags
/var/log/messages file from the compute node. none

Description Alexander Chuzhoy 2014-07-28 23:31:45 UTC 
Rubygem-Staypuft:  /etc/sysconfig/network-scripts/ifcfg-ethX files contain MACs of other interfaces from the same machine. This causes some interfaces not to come up on boot and eventually fails deployment.

Environment:
rhel-osp-installer-0.1.6-3.el6ost.noarch
openstack-foreman-installer-2.0.16-1.el6ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch
openstack-puppet-modules-2014.1-19.8.el6ost.noarch


Steps to reproduce:
1. Install rhel-osp-installer.
2. Create/run a deployment of Neutron (1 controller +1 networker +1 compute) where the interfaces are connected following this layout: https://docs.google.com/drawings/d/14dkoYRNckSv0M3ffXLVbIZtUwrW0rX7wDYkPbyU1YkQ/edit


Result: The deployment will get stuck installing the compute node on 60%.
Some investigation shows that the /etc/sysconfig/network-scripts/ifcfg-ethX files have MACs of other interfaces, i.e. eth0 has the mac of eth2, etc. This causes some interfaces not to be able to come up on boot. Here's an example:
ifup eth1
ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device eth1 has different MAC address than expected, ignoring.

After fixing all the interfaces, brought UP the interface from the same subnet with the puppet server and was able to run the puppet agent, which (after resuming the de[ployment) resulted in successful deployment.

Expected result: Deployment that completed 100%.
Comment 2 Alexander Chuzhoy 2014-07-28 23:35:22 UTC 
Created attachment 921982 [details]
/var/log/messages file from the compute node.
Comment 4 Lars Kellogg-Stedman 2014-07-29 13:58:49 UTC 
Based on discussions on irc, we suspect that this was the result of booting with net.ifnames=0. We've decided to solve the NIC naming issue via documentation pending the release of a RHEL7 discovery image, so unless this issue crops up without setting net.ifnames=0, this isn't a problem that needs to be addressed.
Comment 5 Mike Burns 2014-08-05 18:31:05 UTC 
based on comment 4, closing this as WORKSFORME.  If you reproduce without net.ifnames-0, please re-open