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

When Performed Node stop and start operation on ibmcloud and AWS deployment cluster becomes inaccessible

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • None
    • 4.16
    • kube-apiserver
    • None
    • Yes
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          When Performed Node stop and start operation on ibmcloud deployment cluster becomes inaccessible 

$ oc get nodes
E0514 13:27:38.560306  511051 memcache.go:265] couldn't get current server API group list: Get "https://api.prsurve-ibmojf.ibmcloud2.qe.rh-ocs.com:6443/api?timeout=32s": EOF
E0514 13:27:50.530433  511051 memcache.go:265] couldn't get current server API group list: Get "https://api.prsurve-ibmojf.ibmcloud2.qe.rh-ocs.com:6443/api?timeout=32s": EOF
E0514 13:28:02.517502  511051 memcache.go:265] couldn't get current server API group list: Get "https://api.prsurve-ibmojf.ibmcloud2.qe.rh-ocs.com:6443/api?timeout=32s": EOF

       

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

          4.16.0-0.nightly-2024-05-08-222442

      How reproducible:

      1. Always

      Steps to Reproduce:

      1. Deploy an IBM Cloud IPI cluster     
    2. stop all nodes using ibmcloud is instance-stop <node-name> --force=true
     3. after few min start the nodes again ibmcloud is instance-start <node-name>
    

      Actual results:

          $ oc get nodes
E0514 13:27:38.560306  511051 memcache.go:265] couldn't get current server API group list: Get "https://api.prsurve-ibmojf.ibmcloud2.qe.rh-ocs.com:6443/api?timeout=32s": EOF
E0514 13:27:50.530433  511051 memcache.go:265] couldn't get current server API group list: Get "https://api.prsurve-ibmojf.ibmcloud2.qe.rh-ocs.com:6443/api?timeout=32s": EOF
E0514 13:28:02.517502  511051 memcache.go:265] couldn't get current server API group list: Get "https://api.prsurve-ibmojf.ibmcloud2.qe.rh-ocs.com:6443/api?timeout=32s": EOF
 
when check the vnc console, vm are operational.

      Expected results:

          Cluster should recover and it should be operational

      Additional info:

          Command output: https://url.corp.redhat.com/56e6800

              akashem@redhat.com Abu H Kashem
              prsurve@redhat.com Pratik Surve
              Rahul Gangwar Rahul Gangwar
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: