Bug 2083755 - Node Feature Discovery Operator - no channel heads found in stable channel
Summary: Node Feature Discovery Operator - no channel heads found in stable channel
Keywords:
Status: CLOSED DUPLICATE of bug 2087511
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node Feature Discovery Operator
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Carlos Eduardo Arango Gutierrez
QA Contact: Walid A.
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-10 17:22 UTC by Pawan Khilare
Modified: 2022-05-19 13:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-19 13:39:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Pawan Khilare 2022-05-10 17:22:29 UTC 
Created attachment 1878377 [details]
NFD error

Description of problem:
NFD operator installed successfully but when viewing the subscription of the NFD Operator the following error message is displayed under the conditions:

no channel heads (entries not replaced by another entry) found in channel "stable" of package "nfd"

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

How reproducible: 100%


Steps to Reproduce:
1. Install NFD Operator from OpeartorHub in OCP v4.9.28
2. Once the operator is installed, view the subscription tab and under conditions section below message with Type:ResolutionFailed is displayed.

no channel heads (entries not replaced by another entry) found in channel "stable" of package "nfd"

Actual results: ResolutionFailed with Reason ErrorPreventedResolution is displayed with the above message. 


Expected results: No ResolutionFailed message should be displayed under conditions section


Additional info: Please see the attached screenshots for more details.
Comment 1 Carlos Eduardo Arango Gutierrez 2022-05-19 13:39:40 UTC 

*** This bug has been marked as a duplicate of bug 2087511 ***
Note You need to log in before you can comment on or make changes to this bug.