Description of problem: Failed to generate net-att-def CR when ipam is not specified in SriovNetwork CR Version-Release number of selected component (if applicable): How reproducible: Create a SriovNetwork CR without specifying 'ipam' ``` apiVersion: sriovnetwork.openshift.io/v1 kind: SriovNetwork metadata: name: nic2 spec: networkNamespace: default resourceName: nic2 ``` Steps to Reproduce: 1. 2. 3. Actual results: The net-att-def CR was not generated. Expected results: The net-att-def CR shall be generated with empty ipam. Additional info:
Verified this bug with images: quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.6.0-202006111517-ose-sriov-network-operator-20200615.002329 quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.6.0-202006111517-ose-sriov-network-config-daemon-20200615.002329 the net-attach-def can be created when the sriovnetwork without ipam.
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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196