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

CPT 4.18 failed due to high scale of 'oc login'

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 4.18
    • oc
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • Rejected
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Multi oc login failed in OCP 4.18  

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

          4.18.0

      How reproducible:

          Run high scale of 'oc login'

      Steps to Reproduce:

      Run 'oc login' in multi thread and notice that the config file get empty template (just keys left)
      
      Example for empty config yaml:
      
      apiVersion: v1
      clusters: null
      contexts: null
      current-context: ""
      kind: Config
      preferences: {}
      users:
      - name: kube:admin/api-bm-perfci-com:6443
        user:
          token: sha256~gnJ1NpkMz9MciF-iv-SFqzhQyPC8cPyvh2n75vosSqM       
      
      ** This issue is not reproduced in OCP version 4.17 or lower.
      
      Reproduced on:
      Server:4.18.0-rc.10
      Client Version: 4.18.0-rc.10

      Actual results:

      oc login failed  

      Expected results:

       oc login should pass successfully 

      Additional info:

      In some scenario, oc login pass but ask for api url server:
      
      https://localhost:8443
      So need to add the api url server into 'oc login'
      oc login https://api.your-cluster.example.com:6443 --username=admin --password=yourpassword
      

              aguclu@redhat.com Arda Guclu
              ebattat@redhat.com Eli Battat
              None
              None
              Zhaohua Sun Zhaohua Sun
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: