Description of problem: During overcloud deployment, when attempting to configure SR-IOV VF 0, a python exception will be raised. Example NIC config passed during deployment: - type: sriov_vf vlan_id: get_param: InternalApiNetworkVlanID device: p7p2 vfid: 0 addresses: - ip_netmask: get_param: InternalApiIpSubnet os-net-config will fail to run with the following exception which will cause the deployment to fail: Traceback (most recent call last): File "/usr/bin/os-net-config", line 10, in <module> sys.exit(main()) File "/usr/lib/python2.7/site-packages/os_net_config/cli.py", line 269, in main obj = objects.object_from_json(iface_json) File "/usr/lib/python2.7/site-packages/os_net_config/objects.py", line 87, in object_from_json return SriovVF.from_json(json) File "/usr/lib/python2.7/site-packages/os_net_config/objects.py", line 1253, in from_json vfid = _get_required_field(json, 'vfid', 'SriovVF') File "/usr/lib/python2.7/site-packages/os_net_config/objects.py", line 95, in _get_required_field raise InvalidConfigException(msg) os_net_config.objects.InvalidConfigException: SriovVF JSON objects require 'vfid' to be configured. If a VF > 0 supplied, os-net-config will be executed successfully. Version-Release number of selected component (if applicable): Puddle: 2019-05-15.1 rpm -qa | grep os-net-config os-net-config-8.4.4-1.el7ost.noarch How reproducible: Always Steps to Reproduce: 1. Prepare NIC configuration containing SR-IOV VFs 2. Deploy Overcloud 3. Execute os-net-config Actual results: os-net-config fails to run causing the deployment to fail. Expected results: os-net-config executed successfully. Additional info:
Approving hotfix. Note that the package in FixedInVersion contains fixes for the following bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1722272 https://bugzilla.redhat.com/show_bug.cgi?id=1714966 https://bugzilla.redhat.com/show_bug.cgi?id=1721079 https://bugzilla.redhat.com/show_bug.cgi?id=1712401 https://bugzilla.redhat.com/show_bug.cgi?id=1701105
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-2019:2624