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

Changing Proxy parameters in Windows Containers node Proxy ends with Windows Nodes NotReady

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 4.16.0, 4.16.z
    • Windows Containers
    • None
    • None
    • 3
    • False
    • Hide

      None

      Show
      None

      Based on the test case https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-65980 after removing the following proxy parameters 

      oc patch proxy cluster --type=json -p='[{"op": "replace", "path": "/spec/trustedCA/name", "value": ""}]'
oc patch proxy cluster --type=json -p='[{"op": "remove", "path": "/spec/noProxy"}]'

      Windows nodes are in NotReady Status 

       oc get nodes -l kubernetes.io/os=windows
NAME                                        STATUS     ROLES    AGE   VERSION
ip-10-0-68-214.us-east-2.compute.internal   NotReady   worker   39m   v1.29.7+6abe8a1
ip-10-0-79-112.us-east-2.compute.internal   NotReady   worker   31m   v1.29.7+6abe8a1

      How to reproduce:

      1. create a node proxy on AWS with Windows workers machineset nodes
      2. remove the trustedCA from cluster proxy
      3. remove noProxy configuration from clsuter proxy
      4. wait until WMCO restarts 

              team-winc Team WinC
              rrasouli Aharon Rasouli
              Aharon Rasouli Aharon Rasouli
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: