-
Bug
-
Resolution: Done
-
Major
-
4.3.1.Beta1
-
ASSERT: Have an OpenShift 3 connection created in previous session (or create a connection and restart IDE) and do not store token in secure storage.
EXEC: Double click connection.
ASSERT: Connection dialog to fill in token is shown.
EXEC: Click Cancel.
ASSERT: There is an error tree item under the connection as shown below:
EXEC: Choose edit connection in context menu of a connection.
EXEC: Fill in token in shown Connection dialog.
EXEC: Click Finish.RESULT: Connection is not refreshed and still show error item.
EXPECTED RESULT: Connection shown projects if there are any or nothing at all.ASSERT: Have an OpenShift 3 connection created in previous session (or create a connection and restart IDE) and do not store token in secure storage. EXEC: Double click connection. ASSERT: Connection dialog to fill in token is shown. EXEC: Click Cancel. ASSERT: There is an error tree item under the connection as shown below: EXEC: Choose edit connection in context menu of a connection. EXEC: Fill in token in shown Connection dialog. EXEC: Click Finish. RESULT: Connection is not refreshed and still show error item. EXPECTED RESULT: Connection shown projects if there are any or nothing at all. -
Workaround Exists
-
After editing a connection which was without credentials (e.g. token was not stored in secure storage and eclipse got restarted) and there is tree item informing about such an error, editing the connection does not refresh connection item in OpenShift explorer view and it is necessary to refresh it via context menu of the connection.
- is incorporated by
-
-
- Closed
-
-
-
- Closed
-
