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

Bug 1477316

Summary: os-net-config does not pick up an existing mapping file
Product: Red Hat OpenStack Reporter: Bob Fournier <bfournie>
Component: os-net-configAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: Shai Revivo <srevivo>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: aschultz, bfournie, bhaubeck, dyasny, hbrock, ipetrova, jjoyce, jschluet, jslagle, mburns, mlammon, pcaruana, rhel-osp-director-maint, rhos-maint, samccann, sclewis, yjog
Target Milestone: z5Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: os-net-config-5.2.0-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1457465 Environment:
Last Closed: 2017-09-28 16:35:22 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: 1457465    
Bug Blocks:    

Comment 1 Bob Fournier 2017-08-01 18:58:40 UTC 
Upstream backport to stable/newton - https://review.openstack.org/#/c/489709/
Comment 4 mlammon 2017-09-21 20:57:54 UTC 
Worked with Bob Fournier to verify this bug
Installed: /etc/yum.repos.d/rhos-release-10.repo
# rhos-release 10   -p 2017-09-20.2

environment
[root@undercloud ~]# rpm -qa | grep os-net-config-5.2
os-net-config-5.2.0-4.el7ost.noarch

1. checked the patch was there by inspection
2. running os-net-config using —noop with —debug to print out what it would do
3. passed a config.json file that had a bond in it and also mapping file that reversed the normal mapping, so nic1 is mapped to eth1 and nic2 is mapped to eth0

Output 
[2017/06/13 11:56:11 AM] [INFO] nic2 in mapping file mapped to: eth0
Comment 6 errata-xmlrpc 2017-09-28 16:35:22 UTC 
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://access.redhat.com/errata/RHBA-2017:2825