Creating SriovNetwork overwrites NetworkAttachmentDefinitions of other types.

If I create a NetworkAttachmentDefinition of type "bridge" named "storage-network", and then I attempt to create another NetworkAttachmentDefinition of type "ptp" named "storage-network", the API server returns "AlreadyExists". Furthermore, I could also list all NetworkAttachmentDefinitions and see that "storage-network" already exists.

This is not the case with SriovNetwork. If I create a NetworkAttachmentDefinition of type "bridge" named "storage-network" and then I create an SriovNetwork named "storage-network", the operation will succeed. The SR-IOV operator would then overwrite my previously created NetworkAttachmentDefinition of type "bridge" and cripple all the Pods that were using it. There is no "AlreadyExists" response and a user who does not understand the internal working of the SR-IOV operator cannot know what SriovNetwork does to NetworkAttachmentDefinition.

OCP 4.13

Always

1. Create a NetworkAttachmentDefinition of type "bridge" named "network"
2. Create an SriovNetwork named "network"

The NetworkAttachmentDefinition of type "bridge" is replaced

SriovNetwork would be marked as degraded if the NetworkAttachmentDefinition it tries to write to already exists and is not of type "sriov"

This OCPBUG is based on https://bugzilla.redhat.com/show_bug.cgi?id=2214457