Comments (16)
same error on ocp 4.6.19
from cluster-nfd-operator.
Hi @lgc0313 I am going to fix this today, looks like the community operator on OperatorHub is outdated
from cluster-nfd-operator.
@ArangoGutierrez Thanks.Waiting for repair online
from cluster-nfd-operator.
operator-framework/community-operators#3402 is merged, give it a day to roll out, all fixes should be in place now
from cluster-nfd-operator.
@ArangoGutierrez There is still the same issue now.
from cluster-nfd-operator.
Hi @rupang790 @lgc0313 is this still an issue?
if so, would you let me know the versions of your cluster, and version of the operatorhub?
from cluster-nfd-operator.
Hi, @ArangoGutierrez
on my OKD Cluster (4.6.0-0.okd-2021-02-14-205305) It is installed well through operatorHub.
I used NFD version 4.7 and It works for me. For @lgc0313, I will not close this issue.
However, if I would like to install Special-Resource-operator, should I delete NFD-operator for it?
(Because It saw Special-Resource-Operator install NFD itself again.)
Thank you for fix the issue.
from cluster-nfd-operator.
for SRO let's ask @dagrayvid
from cluster-nfd-operator.
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!
from cluster-nfd-operator.
@dagrayvid, I tried to install SRO on my cluster but it seems not installing status.
I used OperatorHub to install and check NFD version as 4.7.
I can see that it created service only (no deployments or daemonset about operators)
Every 1.0s: oc get all -n openshift-operators okd-bastion01: Tue Apr 20 08:21:27 2021
NAME READY STATUS RESTARTS AGE
pod/nfd-master-2xk2r 1/1 Running 0 31h
pod/nfd-master-qzxs2 1/1 Running 0 31h
pod/nfd-master-w5t5c 1/1 Running 0 31h
pod/nfd-operator-576d77d47f-r9qrf 1/1 Running 0 31h
pod/nfd-worker-2hc2f 1/1 Running 0 31h
pod/nfd-worker-4jrs8 1/1 Running 0 31h
pod/nfd-worker-4q8jt 1/1 Running 0 31h
pod/nfd-worker-k5xmz 1/1 Running 0 31h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/nfd-master ClusterIP 172.30.101.100 <none> 12000/TCP 31h
service/special-resource-controller-manager-metrics-service ClusterIP 172.30.200.31 <none> 8443/TCP 10m
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/nfd-master 3 3 3 3 3 node-role.kubernetes.io/master= 31h
daemonset.apps/nfd-worker 4 4 4 4 4 <none> 31h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/nfd-operator 1/1 1 1 31h
NAME DESIRED CURRENT READY AGE
replicaset.apps/nfd-operator-576d77d47f 1 1 1 31h
NAME AGE
vmimportconfig.v2v.kubevirt.io/vmimport-kubevirt-hyperconverged 39d
Do there have any logs about installation of operators?
One more thing is, Is SRO could be installed when GPU device existed on Node?
If I should create new Issue about this on SRO GitHub, please tell me.
Thank you for comment.
from cluster-nfd-operator.
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.
from cluster-nfd-operator.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
from cluster-nfd-operator.
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?
from cluster-nfd-operator.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
/remove-lifecycle stale
from cluster-nfd-operator.
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
from cluster-nfd-operator.
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen
.
Mark the issue as fresh by commenting/remove-lifecycle rotten
.
Exclude this issue from closing again by commenting/lifecycle frozen
./close
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.
from cluster-nfd-operator.
Related Issues (20)
- OCP build error: CSV annotations cannot be null HOT 6
- Small mistake in the README HOT 4
- Operator's controller logs are repeated when they shouldn't be. Possible duplicate function calls. HOT 7
- NFD Operator's controller manager crashes when an existing NFD instance is deleted HOT 2
- Name on CSV doesn't match entry in art.yaml (4.8 only) HOT 1
- Creating, deleting, then recreating an NFD instance causes the controller manager to crash HOT 5
- The command line option to disable leader election does not function as intended HOT 6
- NFD logs crash approximately 7 hours after installation without touching the cluster HOT 4
- how enable NFD extended resources HOT 1
- Merge detect Intel SGX fixing into nfd-operator and OCP HOT 6
- The proper way to deploy NFD on OCP through NFD-operator HOT 3
- NFD 4.9.0-202202211131 instance is going to degraded state HOT 3
- OCP version label missing after upgrade to 4.10.x (NFD version - v4.10.0-202204010807)
- NFD 4.10 / broken ServiceMonitor HOT 9
- nfd.v4.9.0 installed via OLM on OKD cannot run without redhat credentials HOT 12
- OLM-installed nfd.v4.10.0's nfd-controller-manager fails to start HOT 10
- Please prepare bundle for OCP 4.12 HOT 4
- Node Feature Discovery Operator failing to properly default image in operator HOT 3
- OpenShift NFD --enable-taints option not supported HOT 2
- OpenShift NFD extendedResources for SGX on 4.14 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cluster-nfd-operator.