Description of problem: os-net-config reports NIC mapping, but only if you run in debug mode. Furthermore, the mapping output is not easily parsed for use in scripts. This is causing serious issues when troubleshooting or writing validations. os-net-config should contain an option for returning the exact mapping, and it should return an easily consumable JSON or dict. For example, -i or --interfaces could return a mapping of the numeric NICs to real NIC name. This will make it possible to determine whether a mapping file is working correctly, or whether the desired mapped NICs are down (in which case they will not be mapped correctly). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
upstream bug: https://bugs.launchpad.net/os-net-config/+bug/1713137
targeting this for 10.z as this is a request to backport NIC mapping to 10.z.
[root@compute-1 ~]# os-net-config -i nic2 {'nic2': 'eno2'} [root@compute-1 ~]# [root@compute-1 ~]# os-net-config -i nic3 {'nic3': 'ens1f0'} [root@compute-1 ~]# os-net-config -i nic6 {'nic6': 'ens2f1'}
According to our records, this should be resolved by os-net-config-5.2.3-2.el7ost. This build is available now.