-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not install NodeFeatureDiscovery on OKD4.5 and 4.6 Cluster by operatorHub. #144
Comments
same error on ocp 4.6.19 |
Hi @lgc0313 I am going to fix this today, looks like the community operator on OperatorHub is outdated |
@ArangoGutierrez Thanks.Waiting for repair online |
operator-framework/community-operators#3402 is merged, give it a day to roll out, all fixes should be in place now |
@ArangoGutierrez There is still the same issue now. |
Hi @rupang790 @lgc0313 is this still an issue? |
Hi, @ArangoGutierrez However, if I would like to install Special-Resource-operator, should I delete NFD-operator for it? Thank you for fix the issue. |
for SRO let's ask @dagrayvid |
Hi @rupang790, we shouldn't need to uninstall NFD before installing SRO. I think the reason that it would have been installing NFD again is because SRO's dependency on NFD was out-of-date and looking for an NFD version older than 4.7, hence it was installing 4.5 or 4.6 in addition to the already installed NFD 4.7. This was updated last Friday in communityoperators so it should now work with NFD 4.7 already installed. Let me know if you have any questions or are still running into this issue! |
@dagrayvid, I tried to install SRO on my cluster but it seems not installing status. I can see that it created service only (no deployments or daemonset about operators)
Do there have any logs about installation of operators? If I should create new Issue about this on SRO GitHub, please tell me. |
Hi @rupang790 I haven't seen this error before, so I will have to investigate. Please open an issue on the upstream SRO GitHub to track this. Is this on OKD? Having GPU devices on the node should not cause any problems. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
I am trying install NFD 4.7 on OCP 4.6.26, but getting this error @rupang790 @dagrayvid were you able to get this working? |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
On my OKD Cluster, I found the NFD operator on operatorHub, so I tried to install it from operatorHub.
But It was not installed.
(Before I found it on operatorHub, I used to install it manually, which I cloned from git and use
make
command to deploy.)Installation proceeded in two ways ( Install on All Namespaces-default / specific Namespace ), but the following error occurred:
![image](https://user-images.githubusercontent.com/40801176/111579516-7be2ce00-87f9-11eb-8282-ffe41b0e3d44.png)
How can I solve this? Do anyone have same error with?
The text was updated successfully, but these errors were encountered: