Created attachment 1616623 [details] catalog-operator log. search nfd-operator for error Description of problem: Installing the NFD operator from OperatorHub results in the install stuck in UpgradePending state. The procedure to test operators from redhat-operators-art registry is being followed (https://docs.google.com/document/d/1t81RSsZbUoGO4r5OgJ1bqAESKt2fM25MvV6pcgQUPSk/edit) Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-09-18-211009 How reproducible: Always Steps to Reproduce: 1. See doc above for testing from redhat-operators-art 2. Upload latest nfd operator and operand to cluster local registry 3. Go to OperatorHub - NFD operator appears there successfully 4. Create openshift-nfd namespace 5. Using OperatorHub, install the NFD operator to the operator-nfd namespace Actual results: NFD operator is stuck in UpgradePending. The catalog-operator log contains a large error message: E0919 07:49:24.283582 1 queueinformer_operator.go:282] sync {"update" "openshift-nfd/install-cxqdk"} failed: error creating csv nfd.4.2.0-201909182219: ClusterServiceVersion.operators.coreos.com "nfd.4.2.0-201909182219" is invalid: []: Invalid value: map[string]interface {}{"apiVersion":"operators.coreos.com/v1alpha1", "kind":"ClusterServiceVersion", "metadata":map[string]interface {}{"annotations":map[string]interface {}{"alm-examples":"[\n {\n \"apiVersion\": \"nfd.openshift.io/v1alpha1\",\n \"kind\": \"NodeFeatureDiscovery\",\n \"metadata\": {\n \"name\": \"nfd-master-server\"\n },\n \"spec\": null\n }\n]", "capabilities":"Basic Install", "categories":"Database", "certified":"false", "containerImage":"", "createdAt":"2019-05-30T00:00:00Z", "description":"This software enables node feature discovery for Kubernetes. It detects hardware features available on each node in a Kubernetes cluster, and advertises those features using node labels.", "provider":"Red Hat", "repository":"https://github.com/openshift/cluster-nfd-operator", "support":"Red Hat"}, "creationTimestamp":"2019-09-19T07:49:23Z", "generation":1, "name":"nfd.4.2.0-201909182219", "namespace":"openshift-nfd", "uid":"ff2d7ed4-dab1-11e9-9cdd-0a38de398e90"}, "spec":map[string]interface {}{"apiservicedefinitions":map[string]interface {}{}, "customresourcedefinitions":map[string]interface {}{"owned":[]interface {}{map[string]interface {}{"description":"The NFD operator creates and maintains the Node Feature Discovery (NFD) on Kubernetes. \nIt detects hardware features available on each node in a Kubernetes cluster, and advertises those features using node labels.\n", "displayName":"Node Feature Discovery", "kind":"NodeFeatureDiscovery", "name":"nodefeaturediscoveries.nfd.openshift.io", "version":"v1alpha1"}}}, "description":"The NFD operator creates and maintiains the Node Feature Discovery (NFD) on Kubernetes. \nIt detects hardware features available on each node in a Kubernetes cluster, and advertises those features using node labels.\n", "displayName":"Node Feature Discovery", "icon":[]interface {}{map[string]interface < lines with encoded binary omitted> {}{"fieldPath":"metadata.name"}}}, map[string]interface {}{"name":"OPERATOR_NAME", "value":"cluster-nfd-operator"}}, "image":"image-registry.openshift-image-registry.svc:5000/openshift/ose-cluster-nfd-operator:v4.2.0-201909182219", "imagePullPolicy":"Always", "name":"nfd-operator", "ports":[]interface {}{map[string]interface {}{"containerPort":60000, "name":"metrics"}}, "readinessProbe":map[string]interface {}{"exec":map[string]interface {}{"command":[]interface {}{"stat", "/tmp/operator-sdk-ready"}}, "failureThreshold":1, "initialDelaySeconds":4, "periodSeconds":10}, "resources":map[string]interface {}{}, "securityContext":map[string]interface {}{"allowPrivilegeEscalation":false, "capabilities":map[string]interface {}{"drop":[]interface {}{"ALL"}}, "readOnlyRootFilesystem":true}, "volumeMounts":[]interface {}{map[string]interface {}{"mountPath":"/tmp", "name":"tmp"}}}}, "nodeSelector":map[string]interface {}{"node-role.kubernetes.io/master":""}, "serviceAccountName":"nfd-operator", "tolerations":[]interface {}{map[string]interface {}{"effect":"NoSchedule", "key":"node-role.kubernetes.io/master", "operator":"Equal"}}, "volumes":[]interface {}{map[string]interface {}{"emptyDir":map[string]interface {}{}, "name":"tmp"}}}}}}}}, "strategy":"deployment"}, "installModes":[]interface {}{map[string]interface {}{"supported":true, "type":"OwnNamespace"}, map[string]interface {}{"supported":true, "type":"SingleNamespace"}, map[string]interface {}{"supported":false, "type":"MultiNamespace"}, map[string]interface {}{"supported":true, "type":"AllNamespaces"}}, "links":[]interface {}{map[string]interface {}{"name":"Documentation operator", "url":"https://github.com/openshift/cluster-nfd-operator"}, map[string]interface {}{"name":"Documentation operand", "url":"https://github.com/openshift/node-feature-discovery"}}, "maintainers":[]interface {}{map[string]interface {}{"name":"Red Hat"}}, "maturity":"alpha", "provider":map[string]interface {}{"name":"Red Hat"}, "version":"4.2.0"}}: validation failure list: spec.maintainers.email in body is required Additional info: Full catalog-operator log attached.
Newest builds of NFD resovle this.
Re: comment 1 - thanks for the update, will try it again tomorrow. Is there a PR that I can track so I know which build it is included in?
https://github.com/openshift/cluster-nfd-operator/pull/27 This fixes the CSV for the Operator.
With the following build levels I was able to successfully install the NFD operator from redhat-operators-art and create a NodeFeatureDiscovery CRD. The operand pods are stuck crash looping, but I will open a new bz for that. This install bz is verified with: ose-cluster-nfd-operator:v4.2.0-201909192219 oose-node-feature-discovery:v4.2.0-201909151553
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922