Bug 2037240

Summary:	NNCP name cant be the same has node
Product:	Container Native Virtualization (CNV)	Reporter:	Kobig <kgershon>
Component:	Networking	Assignee:	Ben Nemec <bnemec>
Status:	CLOSED DUPLICATE	QA Contact:	Victor Voronkov <vvoronko>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.8.10	CC:	amalykhi, aos-bugs, augol, cnv-qe-bugs, nashok
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:	2022-01-12 16:38:24 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:

Description Kobig 2022-01-05 10:24:42 UTC

Description of problem:
We have two cases (attached) that show that when an NNCP name is the same has the node name it doesn't work well and stuck on "ConfigurationProgressing". 
  

Version-Release number of selected component (if applicable):
4.8.18


How reproducible:
Create NNCP with the same name has the node and see that it not moving into "SuccessfullyConfigured"
The strange part is that it's not happening on all of the nodes.  

Steps to Reproduce:
1. Create NNCP with the name of the node 
2. Check all the nodes and see that it's not getting applied on all of them 

Actual results:
Not all nodes get applied on the NNCP

Expected results:
NNCP will be applied on all nodes 

Additional info:
When we change the names of the NNCP all started to work.

Comment 1 nijin ashok 2022-01-06 03:34:20 UTC

Isn't this a duplicate of BUG 2033252?

Comment 6 Ben Nemec 2022-01-12 16:38:24 UTC

I discussed this with Radim, who is working on the fix for https://bugzilla.redhat.com/show_bug.cgi?id=2033252 , and he thinks it's probably the same underlying problem. I'm going to mark it as a duplicate for now, but feel free to reopen this if it turns out not to be fixed when the other bug is.

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