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

[release-4.18] Unable to set the operatorLogLevel to Debug/Trace/TraceAll for insightsoperator object

XMLWordPrintable

    • None
    • CCXDEV Sprint 130
    • 1
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-45044. The following is the description of the original issue:

      Description of problem:

        The operatorLogLevel reverting back to `Normal` automatically for insightsoperator object

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

          4.14,4.15,4.16,4.17

      How reproducible:

          100%

      Steps to Reproduce:

          1. Edit the insightsoperator/cluster object:
      $ oc edit insightsoperator/cluster
      ...
      ...
      spec:
        logLevel: Normal
        managementState: Managed
        operatorLogLevel: Normal ====> Change it to Debug/Trace/TraceAll
      
          2. After 1 Min check if the changes are constant:
      $ oc get insightsoperator/cluster -o yaml
      ...
      ...
      spec:
        logLevel: Normal
        managementState: Managed
        operatorLogLevel: Normal   
      
        3. The OC CLI DOC states that it supports below logLevels:
      
      $ oc explain insightsoperator.spec.operatorLogLevel
      GROUP:      operator.openshift.io
      KIND:       InsightsOperator
      VERSION:    v1FIELD: operatorLogLevel <string>
      ENUM:
          ""
          Normal
          Debug
          Trace
          TraceAll
      DESCRIPTION:
          operatorLogLevel is an intent based logging for the operator itself.  It
          does not give fine grained control, but it is a simple way to manage coarse
          grained logging choices that operators have to interpret for themselves.
           Valid values are: "Normal", "Debug", "Trace", "TraceAll". Defaults to
          "Normal".     

      Actual results:

          The logLevel is set back to Normal automatically.

      Expected results:

          The logLevel should not be changed to Normal until manually modified.

      Additional info:

       The same issue is observed with insightsoperator.spec.logLevel where any logLevel other than Normal getting reverted.

              tremes1@redhat.com Tomas Remes
              openshift-crt-jira-prow OpenShift Prow Bot
              baiyang zhou baiyang zhou
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: