Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1509060

Summary: Login intermittently fails with unexpected response: 200
Product: OpenShift Container Platform Reporter: Steven Walter <stwalter>
Component: MasterAssignee: Michal Fojtik <mfojtik>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Wang Haoran <haowang>
Severity: high Docs Contact:
Priority: high    
Version: 3.2.1CC: aos-bugs, eparis, erich, jokerman, mkhan, mmccomas, sttts, stwalter
Target Milestone: ---Keywords: UpcomingRelease
Target Release: 3.2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-08 21:07:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Steven Walter 2017-11-02 20:27:41 UTC
Description of problem

Login to Openshift console fails intermittently and gives the below Error message 
Error
An error has occurred


Login to Openshift  from command line fails intermittently with and  gives the below error message
Error from server: Internal error occurred: unexpected response: 200


Version-Release number of selected component (if applicable):
atomic-openshift-3.2.1.31-1
atomic-openshift-utils-3.2.56-1
atomic-openshift-clients-3.2.1.31-1
atomic-openshift-master-3.2.1.31-1


How reproducible:
Unconfirmed

Steps to Reproduce:
1. `oc login` or login to web console

Actual results:
I0829 14:03:45.425772   13836 debugging.go:130]     Content-Length: 756
I0829 14:03:45.428772   13836 helpers.go:142] server response object: [{
  "metadata": {},
  "status": "Failure",
  "message": "Internal error occurred: unexpected response: 200",
  "reason": "InternalError",
  "details": {
    "causes": [
      {
        "message": "unexpected response: 200"
      }
    ]
  },
  "code": 500
}]

Expected results:
successful login

Comment 26 Michal Fojtik 2018-01-03 16:14:03 UTC
This is waiting for a customer, not blocking 3.9.

Comment 27 Steven Walter 2018-01-08 21:07:09 UTC
Case remains waiting on customer, it appears to have helped based on their last feedback. Looks like etcd speed issue, not a bug.