[
https://issues.redhat.com/browse/JBIDE-26899?page=com.atlassian.jira.plug...
]
Jeff MAURY updated JBIDE-26899:
-------------------------------
Sprint: devex #174 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019, devex #177
Dec 2019 (was: devex #174 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019)
Refreshing non-functional connection to CRC doesnt help (need to
create new)
----------------------------------------------------------------------------
Key: JBIDE-26899
URL:
https://issues.redhat.com/browse/JBIDE-26899
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.13.0.Final
Environment: CRC
Reporter: André Dietisheim
Assignee: André Dietisheim
Priority: Major
Fix For: 4.14.0.AM1
*Steps* - not reproducibe at 100%, happens from time to time:
# ASSERT: have ~/.crc folder killed
# EXEC: create new CRC server adapter & Start it
# ASSERT: OpenShift connection is created
# ASSERT: Connection fails to authorize, reports that it cannot access resources using
system:anonymous.
# EXEC: try to login with *oc login*. If oc reports *Error from server (InternalError):
Internal error occurred: unexpected response: 400*, repeat until it succeeds (waiting
required)
# EXEC: Once oc login succeeds: refresh the connection in Eclipse
Result:
Connecting still fails with the same error.
Expected result:
Refreshing the connection should succeed once the server is fully up and running and oc
succeeds to log in.
Workaround:
# EXEC: edit the connection instead of refreshing it (ex. remove a character from
username and add it back again)
Result:
Connecting succeeds
--
This message was sent by Atlassian Jira
(v7.13.8#713008)