Created attachment 1640536 [details] console instance not ready Description of problem: The CR is not updating its status, even if it's running or not. Version-Release number of selected component (if applicable): 4.3 How reproducible: Install Jaeger Steps to Reproduce: 1. Install it in the Web console, for example: "Operators"->"OperatorHub"->"Jaegar" [scolange@scolange ~]$ oc get sub NAME PACKAGE SOURCE CHANNEL elasticsearch-operator-4.2-redhat-operators-openshift-marketplace elasticsearch-operator redhat-operators 4.2 jaeger-product jaeger-product redhat-operators stable [scolange@scolange ~]$ oc get csv NAME DISPLAY VERSION REPLACES PHASE elasticsearch-operator.4.2.4-201911050122 Elasticsearch Operator 4.2.4-201911050122 Succeeded jaeger-operator.v1.13.1 Jaeger Operator 1.13.1 Succeeded [scolange@scolange ~]$ oc get ip NAME CSV APPROVAL APPROVED install-ksrzw elasticsearch-operator.4.2.4-201911050122 Automatic true 2. Create Instance all-one-in-memory from "console" 3. Check the pods oc get pods -n openshift-operators NAME READY STATUS RESTARTS AGE elasticsearch-operator-5dbcffcf8-vghjp 1/1 Running 0 18m jaeger-all-in-one-inmemory-856b547bf-pmfdt 2/2 Running 0 6m28s jaeger-operator-98dd965f5-cvwxk 1/1 Running 0 6m43s 4.Verify the cr Jaeger oc get Jaeger jaeger-all-in-one-inmemory -n openshift-operators -o yaml apiVersion: jaegertracing.io/v1 kind: Jaeger metadata: creationTimestamp: "2019-11-26T16:34:24Z" generation: 2 name: jaeger-all-in-one-inmemory namespace: openshift-operators resourceVersion: "409738" selfLink: /apis/jaegertracing.io/v1/namespaces/openshift-operators/jaegers/jaeger-all-in-one-inmemory uid: 9b674bc1-106a-11ea-89c9-06469dd65190 spec: agent: image: registry.redhat.io/distributed-tracing/jaeger-agent-rhel7:1.13.1 options: {} resourc apiVersion: jaegertracing.io/v1 .... .... ... ... 5. Check on console if the status became ready. Actual results: No status show in the console about Expected results: Status become ready for Additional info: [scolange@scolange ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.3.0-0.nightly-2019-11-28-103851 True False 8h Cluster version is 4.3.0-0.nightly-2019-11-28-103851 https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-26057
Yes, I met this issue too, no ready status display. it's better to add a screenshot, here: https://user-images.githubusercontent.com/15416633/69839750-d9b17680-1293-11ea-9aef-8fd1f85f6bb8.png
Fix will be provided with version OSSM-1.0.4 - can be tracked at: https://issues.redhat.com/browse/OSSM-126
Hi , The status still not ready in openshift-console steps to Reproduce: 1. Install it in the Web console, for example: "Operators"->"OperatorHub"->"Jaegar" [scolange@scolange ~]$ oc get sub NAME PACKAGE SOURCE CHANNEL elasticsearch-operator-4.2-redhat-operators-openshift-marketplace elasticsearch-operator redhat-operators 4.2 jaeger-product jaeger-product redhat-operators stable [scolange@scolange ~]$ oc get csv NAME DISPLAY VERSION REPLACES PHASE elasticsearch-operator.4.2.4-201911050122 Elasticsearch Operator 4.2.4-201911050122 Succeeded jaeger-operator.v1.13.1 Jaeger Operator 1.13.1 Succeeded [scolange@scolange ~]$ oc get ip NAME CSV APPROVAL APPROVED install-ksrzw elasticsearch-operator.4.2.4-201911050122 Automatic true 2. Create Instance all-one-in-memory from "console" 3. Check the pods oc get pods -n openshift-operators NAME READY STATUS RESTARTS AGE elasticsearch-operator-5dbcffcf8-vghjp 1/1 Running 0 18m jaeger-all-in-one-inmemory-856b547bf-pmfdt 2/2 Running 0 6m28s jaeger-operator-98dd965f5-cvwxk 1/1 Running 0 6m43s 4.Verify the cr Jaeger scolange@scolange ~]$ oc get Jaeger jaeger-all-in-one-inmemory -n openshift-operators -o yaml apiVersion: jaegertracing.io/v1 kind: Jaeger metadata: creationTimestamp: "2019-12-13T13:47:53Z" generation: 2 name: jaeger-all-in-one-inmemory namespace: openshift-operators resourceVersion: "24376" selfLink: /apis/jaegertracing.io/v1/namespaces/openshift-operators/jaegers/jaeger-all-in-one-inmemory uid: 28f71986-1daf-11ea-a8da-0aa851ae6e86 spec: agent: image: registry.redhat.io/distributed-tracing/jaeger-agent-rhel7:1.13.1 options: {} resources: {} allInOne: image: registry.redhat.io/distributed-tracing/jaeger-all-in-one-rhel7:1.13.1 options: {} resources: {} collector: options: {} resources: {} ingester: options: {} resources: {} ingress: openshift: {} resources: {} security: oauth-proxy query: options: {} resources: {} resources: {} sampling: options: {} storage: cassandraCreateSchema: {} dependencies: image: jaegertracing/spark-dependencies schedule: 55 23 * * * elasticsearch: nodeCount: 1 redundancyPolicy: ZeroRedundancy resources: {} storage: {} esIndexCleaner: image: registry.redhat.io/distributed-tracing/jaeger-es-index-cleaner-rhel7:1.13.1 numberOfDays: 7 schedule: 55 23 * * * esRollover: image: jaegertracing/jaeger-es-rollover:1.13.1 schedule: '*/30 * * * *' options: {} type: memory strategy: allInOne ui: options: menu: - items: - label: Documentation url: https://www.jaegertracing.io/docs/latest label: About - anchorTarget: _self label: Log Out url: /oauth/sign_in status: {} 5. Check on console if the status became ready. No statsu ready see the attachment Actual results: No status show in the console about Expected results: Status become ready for
Created attachment 1644873 [details] NO status jeager
This feature is still not available in the product, only upstream. I'm not sure I would classify this as a bug, but in any case, it should be available starting from version 1.16, to be released in the coming weeks.
Hi , I agree but in the console should appaer the right status instaed now is "Unknow"
Created attachment 1688130 [details] Image showing the running status.
I believe this issue can be closed, as fixed in Jaeger operator 1.17.x.
[scolange@scolange operators]$ oc -n openshift-operators get csv NAME DISPLAY VERSION REPLACES PHASE jaeger-operator.v1.21.3 Community Jaeger Operator 1.21.3 jaeger-operator.v1.20.0 Succeeded [scolange@scolange operators]$ oc -n openshift-operators get sub NAME PACKAGE SOURCE CHANNEL jaeger jaeger community-operators stable [scolange@scolange operators]$ oc -n openshift-operators get ip NAME CSV APPROVAL APPROVED install-s7nwf jaeger-operator.v1.21.3 Automatic true [scolange@scolange operators]$ oc -n openshift-operators get pod NAME READY STATUS RESTARTS AGE jaeger-all-in-one-inmemory-64b6cdf7c-n7pbw 2/2 Running 0 83s jaeger-operator-6f4754f778-tz7wl 1/1 Running 0 2m46s [scolange@scolange operators]$ [scolange@scolange operators]$ oc get cluserversion error: the server doesn't have a resource type "cluserversion" [scolange@scolange operators]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2021-03-16-094919 True False 9h Cluster version is 4.8.0-0.nightly-2021-03-16-094919 The status is ok in console LGMT!