Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-31020

console-config sets telemeterClientDisabled: true when telemeter client is NOT disabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • 4.16.0
    • premerge
    • Management Console
    • None
    • No
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      console-config sets telemeterClientDisabled: true even telemeter client is NOT disabled

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

      a cluster launched by image built with cluster-bot: build 4.16-ci,openshift/console#13677,openshift/console-operator#877    

      How reproducible:

      Always    

      Steps to Reproduce:

      1. Check if telemeter client is enabled
      $ oc -n openshift-monitoring get pod | grep telemeter-clienttelemeter-client-7cc8bf56db-7wcs5                       3/3     Running   0          83m 
      $ oc get cm cluster-monitoring-config -n openshift-monitoring
      Error from server (NotFound): configmaps "cluster-monitoring-config" not found
      
      2. Check console-config settings
      $ oc get cm console-config -n openshift-console -o yaml
      apiVersion: v1
      data:
        console-config.yaml: |
          apiVersion: console.openshift.io/v1
          auth:
            authType: openshift
            clientID: console
            clientSecretFile: /var/oauth-config/clientSecret
            oauthEndpointCAFile: /var/oauth-serving-cert/ca-bundle.crt
          clusterInfo:
            consoleBaseAddress: https://xxxxx
            controlPlaneTopology: HighlyAvailable
            masterPublicURL: https://xxxxx:6443
            nodeArchitectures:
            - amd64
            nodeOperatingSystems:
            - linux
            releaseVersion: 4.16.0-0.test-2024-03-18-024238-ci-ln-0q7bq2t-latest
          customization:
            branding: ocp
            documentationBaseURL: https://access.redhat.com/documentation/en-us/openshift_container_platform/4.16/
          kind: ConsoleConfig
          monitoringInfo:
            alertmanagerTenancyHost: alertmanager-main.openshift-monitoring.svc:9092
            alertmanagerUserWorkloadHost: alertmanager-main.openshift-monitoring.svc:9094
          plugins:
            monitoring-plugin: https://monitoring-plugin.openshift-monitoring.svc.cluster.local:9443/
          providers: {}
          servingInfo:
            bindAddress: https://[::]:8443
            certFile: /var/serving-cert/tls.crt
            keyFile: /var/serving-cert/tls.key
          session: {}
          telemetry:
            telemeterClientDisabled: "true"
      kind: ConfigMap
      metadata:
        creationTimestamp: "2024-03-19T01:20:23Z"
        labels:
          app: console
        name: console-config
        namespace: openshift-console
        resourceVersion: "27723"
        uid: 2f9282c3-1c4a-4400-9908-4e70025afc33    

       

      Actual results:

      in cm/console-config, telemeterClientDisabled is set with 'true'

      Expected results:

      telemeterClientDisabled property should reveal the real status of telemeter client
      
      telemeter client is not disabled because 
      1. telemeter client pod is running
      2. user didn't disable telemeter client manually because 'cluster-monitoring-config' configmap doesn't exist

      Additional info:

          

            rh-ee-jonjacks Jon Jackson
            rhn-support-yapei YaDan Pei
            YaDan Pei YaDan Pei
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: