Bug 1477316 - os-net-config does not pick up an existing mapping file
Summary: os-net-config does not pick up an existing mapping file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: os-net-config
Version: 10.0 (Newton)
Hardware: x86_64
OS: Linux
high
high
Target Milestone: z5
: 10.0 (Newton)
Assignee: RHOS Maint
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On: 1457465
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-01 18:40 UTC by Bob Fournier
Modified: 2020-08-13 09:42 UTC (History)
17 users (show)

Fixed In Version: os-net-config-5.2.0-4.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1457465
Environment:
Last Closed: 2017-09-28 16:35:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 470073 0 None None None 2017-08-01 18:40:47 UTC
OpenStack gerrit 475531 0 None None None 2017-08-01 18:40:47 UTC
OpenStack gerrit 489709 0 None None None 2017-08-31 19:58:28 UTC
Red Hat Product Errata RHBA-2017:2825 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 10 director Bug Fix Advisory 2017-09-28 20:33:35 UTC

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
Note You need to log in before you can comment on or make changes to this bug.