Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1945566

Summary: ClusterNetworkOperator stuck processing additionalNetworks is NameSpace for one doesn't exist beforehand
Product: OpenShift Container Platform Reporter: David Juran <djuran>
Component: NetworkingAssignee: Feng Pan <fpan>
Networking sub component: multus QA Contact: Weibin Liang <weliang>
Status: CLOSED DUPLICATE Docs Contact:
Severity: unspecified    
Priority: unspecified CC: alosadag, dosmith
Version: 4.6   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-05 14:37:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Sample config none

Description David Juran 2021-04-01 09:54:01 UTC 
Description of problem:
When setting up net-attach-defs for secondary Pod networks using the ClusterNetworkOperator, as described e.g. in our docs[1], if one of the namespaces in which the net-attach-def will be created doesn't exist beforehand, the CNO goes into degraded state and will not process any of the following additionalNetworks until the NameSpace is created.

This situation could occur e.g. in a setup where the configuration of additionalNetworks is controlled by the cloud administrator while the NameSpaces are created through self-service.

[1]
https://docs.openshift.com/container-platform/4.6/networking/multiple_networks/configuring-macvlan.html#nw-multus-create-network_configuring-macvlan
Comment 1 David Juran 2021-04-01 10:10:19 UTC 
Created attachment 1768232 [details]
Sample config

Example config demonstrating the issue

Do note none of the net-attach-defs get created and CNO is in degraded state
Comment 2 Douglas Smith 2021-04-05 14:37:13 UTC 

*** This bug has been marked as a duplicate of bug 1896533 ***