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

Unable to add windows node to OCP 4.14 cluster with proxy enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • 4.15.0
    • 4.14.z
    • Windows Containers
    • None
    • Moderate
    • No
    • 0
    • WINC - Sprint 248
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      Cause: WMCO performed an erroneous sanitization step that replaced commas with semicolons in the user's cluster-wide proxy configuration.
      Consequence: This was causing Windows to ignore the values set in the noProxy environment variable, incorrectly sending traffic through the proxy for endpoints specified in the no-proxy spec.
      Fix: The sanitization step that replaced commas with semicolons was removed.
      Result: A web request from a Windows node to a cluster-internal endpoint or an endpoint that exists in the noProxy spec) does not go through the proxy.

      Show
      Cause: WMCO performed an erroneous sanitization step that replaced commas with semicolons in the user's cluster-wide proxy configuration. Consequence: This was causing Windows to ignore the values set in the noProxy environment variable, incorrectly sending traffic through the proxy for endpoints specified in the no-proxy spec. Fix: The sanitization step that replaced commas with semicolons was removed. Result: A web request from a Windows node to a cluster-internal endpoint or an endpoint that exists in the noProxy spec) does not go through the proxy.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-24264. The following is the description of the original issue:
      —
      When trying to add a windows nodes to the cluster it is failing with the following error.

      Environment:

      OCP 4.14.3

      WMCO version 9

      error:

      I1129 09:01:57.094173 14376 cleanup.go:55] no associated node found
F1129 09:01:57.101852 14376 cleanup.go:51] cannot get latest services ConfigMap from namespace openshift-windows-machine-config-operator: failed to get API group resources: unable to retrieve the complete list of server APIs: v1: Get "https://api-int.example.com:6443/api/v1": Tunnel or SSL Forbidden

      and:

      {"level":"error","ts":"2023-11-29T09:01:59Z","logger":"wc 10.100.8.156","msg":"error running","cmd":"powershell.exe -NonInteractive -ExecutionPolicy Bypass \"C:\\k\\windows-instance-config-daemon.exe cleanup --kubeconfig C:\\k\\wicd-kubeconfig --namespace openshift-windows-machine-config-operator\"","out":"I1129 09:01:57.094173 14376 cleanup.go:55] no associated node found\nF1129 09:01:57.101852 14376 cleanup.go:51] cannot get latest services ConfigMap from namespace openshift-windows-machine-config-operator: failed to get API group resources: unable to retrieve the complete list of server APIs: v1: Get \"https://api-int.example.com:6443/api/v1\": Tunnel or SSL Forbidden\n","error":"Process exited with status 1","stacktrace":"github.com/openshift/windows-machine-config-operator/pkg/windows.(*windows).Run\n\t/remote-source/build/windows-machine-config-operator/pkg/windows/windows.go:399\ngithub.com/openshift/windows-machine-config-operator/pkg/windows.(*windows).RunWICDCleanup\n\t/remote-source/build/windows-machine-config-operator/pkg/windows/windows.go:437\ngithub.com/openshift/windows-machine-config-operator/pkg/windows.(*windows).Bootstrap\n\t/remote-source/build/windows-machine-config-operator/pkg/windows/windows.go:458\ngithub.com/openshift/windows-machine-config-operator/pkg/nodeconfig.(*nodeConfig).Configure\n\t/remote-source/build/windows-machine-config-operator/pkg/nodeconfig/nodeconfig.go:165\ngithub.com/openshift/windows-machine-config-operator/controllers.(*instanceReconciler).ensureInstanceIsUpToDate\n\t/remote-source/build/windows-machine-config-operator/controllers/controllers.go:110\ngithub.com/openshift/windows-machine-config-operator/controllers.(*WindowsMachineReconciler).configureMachine\n\t/remote-source/build/windows-machine-config-operator/controllers/windowsmachine_controller.go:426\ngithub.com/openshift/windows-machine-config-operator/controllers.(*WindowsMachineReconciler).Reconcile\n\t/remote-source/build/windows-machine-config-operator/controllers/windowsmachine_controller.go:347\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/remote-source/build/windows-machine-config-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:118\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/remote-source/build/windows-machine-config-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:314\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/remote-source/build/windows-machine-config-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/remote-source/build/windows-machine-config-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:226"}

              mohashai Mohammad Shaikh
              openshift-crt-jira-prow OpenShift Prow Bot
              Aharon Rasouli Aharon Rasouli
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: