Bug 2037240 - NNCP name cant be the same has node
Summary: NNCP name cant be the same has node
Keywords:
Status: CLOSED DUPLICATE of bug 2033252
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Networking
Version: 4.8.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Ben Nemec
QA Contact: Victor Voronkov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-05 10:24 UTC by Kobig
Modified: 2025-04-04 14:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-12 16:38:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-15812 0 None None None 2025-04-04 14:03:42 UTC

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 ***
Note You need to log in before you can comment on or make changes to this bug.