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

ComplianceScan stuck in launching state

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • 4.14.z
    • Compliance Operator
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • No
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      The compliancescan showing "LAUNCHING" state, it says pending and nothing else. The compliance operator pod is throwing errors. The nodes that it complains is in READY state and no csr is pending.
      
      2024-03-06T09:36:21.837361988Z {"level":"error","ts":"2024-03-06T09:36:21.837Z","logger":"scanctrl","msg":"Error creating the configmap for the runtime kubeletconfig","Request.Namespace":"openshift-compliance","Request.Name":"ocp4-cis-node-worker","node":"bmgpu6.prodmgmtocp.ncs-prod.com","error":"cannot get the runtime kubelet config for node bmgpu6.prodmgmtocp.ncs-prod.com: cannot get the runtime kubelet config for node bmgpu6.prodmgmtocp.ncs-prod.com: error trying to reach service: remote error: tls: internal error","stacktrace":"github.com/ComplianceAsCode/compliance-operator/pkg/controller/compliancescan.(*ReconcileComplianceScan).handleRuntimeKubeletConfig\n\tgithub.com/ComplianceAsCode/compliance-operator/pkg/controller/compliancescan/compliancescan_controller.go:479\ngithub.com/ComplianceAsCode/compliance-operator/pkg/controller/compliancescan.(*ReconcileComplianceScan).phaseLaunchingHandler\n\tgithub.com/ComplianceAsCode/compliance-operator/pkg/controller/compliancescan/compliancescan_controller.go:358\ngithub.com/ComplianceAsCode/compliance-operator/pkg/controller/compliancescan.(*ReconcileComplianceScan).Reconcile\n\tgithub.com/ComplianceAsCode/compliance-operator/pkg/controller/compliancescan/compliancescan_controller.go:189\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\tsigs.k8s.io/controller-runtime@v0.16.3/pkg/internal/controller/controller.go:119\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tsigs.k8s.io/controller-runtime@v0.16.3/pkg/internal/controller/controller.go:316\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsigs.k8s.io/controller-runtime@v0.16.3/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\tsigs.k8s.io/controller-runtime@v0.16.3/pkg/internal/controller/controller.go:227"}
      
      Posted this question in Slack and @Vincent Shen suggested me to open this bug ticket and say the error handling should be more graceful here.

      Slack link: https://redhat-internal.slack.com/archives/CHCRR73PF/p1709813238510689

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

          

      How reproducible:

          

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

              lbragsta@redhat.com Lance Bragstad
              rh-ee-tirvan Tan Suryadi Irvan
              None
              None
              Xiaojie Yuan Xiaojie Yuan
              None
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: