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

The unmarshal error showed after setting obfuscation as a string

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • CCXDEV Sprint 156
    • 1
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      Description of problem:

          There are some unmarshal error logs showing in the IO after we set the obfuscation as a string type in the IO conf.

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

          

      How reproducible:

          Set the obfuscation as a string type obj in the IO conf and check the IO logs.

      Steps to Reproduce:

      1. Set the `insights-config` configmap of IO as below:

      apiVersion: v1
      data:
        config.yaml: |
          dataReporting:
            obfuscation: ''     

      2. Restart IO.

      3. View the IO logs.

      Actual results:

      3. The IO logs showed the following error:

          E1202 07:17:49.376342       1 config_aggregator.go:97] Failed to read configmap configuration: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal string into Go struct field DataReportingSerialized.dataReporting.obfuscation of type config.Obfuscation

      Expected results:

      3. There should not be any unmarsha error logs. 

      Additional info:

      Another fixing suggestion is that we can forbid setting a string obj for the obfuscation field, this problem should be solved since it fails to set at the very beginning.

              rh-ee-kborgulo Katarina Borgulova
              rh-ee-bazhou Baiyang Zhou
              None
              None
              Baiyang Zhou Baiyang Zhou
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: