Description of problem: Os-net-config validation throws error when cpu_list parameter is used for vrouter dpdk nic type. Sep 4 09:00:07 compute1 os-collect-config: [2019/09/04 08:57:03 AM] [WARNING] Config file failed schema validation at network_config/4: Sep 4 09:00:07 compute1 os-collect-config: {'persist_mapping': False, 'addresses': [{'ip_netmask': '172.16.0.12/23'}], 'cpu_list': '0x1554', 'nic_mapping': None, 'driver': 'vfio-pci', 'mtu': 9000, 'bond_ mode': 4, 'members': [{'type': 'interface', 'name': 'p1p1', 'mtu': 9096}, {'type': 'interface', 'name': 'p1p2', 'mtu': 9096}], 'use_dhcp': False, 'bond_policy': 'layer3+4', 'type': 'contrail_vrouter_dpdk', 'name': 'vhost0'} is not valid under any of the given schemas Sep 4 09:00:07 compute1 os-collect-config: Sub-schemas tested and not matching: Sep 4 09:00:07 compute1 os-collect-config: - items/oneOf/contrail_vrouter_dpdk/additionalProperties: Additional properties are not allowed ('cpu_list' was unexpected) RH OpenStack Platform 13 How reproducible: Always Actual results: os-net-config throws validation error Expected results: os-net-config validation should succeed Additional info: This should be backport of https://review.opendev.org/#/c/601615/1
There was a typo with MTU. Sep 4 09:00:07 compute1 os-collect-config: [2019/09/04 08:57:03 AM] [WARNING] Config file failed schema validation at network_config/4: Sep 4 09:00:07 compute1 os-collect-config: {'persist_mapping': False, 'addresses': [{'ip_netmask': '172.16.0.12/23'}], 'cpu_list': '0x1554', 'nic_mapping': None, 'driver': 'vfio-pci', 'mtu': 9000, 'bond_ mode': 4, 'members': [{'type': 'interface', 'name': 'p1p1', 'mtu': 9000}, {'type': 'interface', 'name': 'p1p2', 'mtu': 9000}], 'use_dhcp': False, 'bond_policy': 'layer3+4', 'type': 'contrail_vrouter_dpdk', 'name': 'vhost0'} is not valid under any of the given schemas Sep 4 09:00:07 compute1 os-collect-config: Sub-schemas tested and not matching: Sep 4 09:00:07 compute1 os-collect-config: - items/oneOf/contrail_vrouter_dpdk/additionalProperties: Additional properties are not allowed ('cpu_list' was unexpected)
Verified that cpu_list is now used instead of coremask in schema.yaml.
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:3794