[JBoss JIRA] (JBIDE-26902) Connection wizard: opening conn without token cannot be finished (have to wait for period)
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26902?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26902:
-------------------------------------
Description:
Steps:
# ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
# ASSERT: make sure that you have current server for oc NOT to be reachable (ex. current server is a cdk/crc that is *NOT* running)
# ASSERT: have oc binary set as oc binary in preferences
# EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
# ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
# EXEC: retrieve token / provide pw
# EXEC: try to "Finish"
Result:
You cannot hit "Finish", it's disabled:
!screenshot-1.png!
If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
If you wait a bit "Finish" gets enabled. "Finish" gets enabled as soon as the oc binary timed out trying to connect to the current server.
was:
Steps:
# ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
# ASSERT: make sure that you have current server for oc NOT to be reachable (ex. current server is a cdk/crc that is *NOT* running)
# ASSERT: have oc v4 binary set as oc binary in preferences
# EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
# ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
# EXEC: retrieve token / provide pw
# EXEC: try to "Finish"
Result:
You cannot hit "Finish", it's disabled:
!screenshot-1.png!
If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
If you wait a bit "Finish" gets enabled. This actually happens once the oc binary timed out trying to connect to the current server
> Connection wizard: opening conn without token cannot be finished (have to wait for period)
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-26902
> URL: https://issues.jboss.org/browse/JBIDE-26902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.14.x
>
> Attachments: screenshot-1.png
>
>
> Steps:
> # ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
> # ASSERT: make sure that you have current server for oc NOT to be reachable (ex. current server is a cdk/crc that is *NOT* running)
> # ASSERT: have oc binary set as oc binary in preferences
> # EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
> # ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
> # EXEC: retrieve token / provide pw
> # EXEC: try to "Finish"
> Result:
> You cannot hit "Finish", it's disabled:
> !screenshot-1.png!
> If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
> If you wait a bit "Finish" gets enabled. "Finish" gets enabled as soon as the oc binary timed out trying to connect to the current server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26902) Connection wizard: opening conn without token cannot be finished
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26902?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26902:
-------------------------------------
Description:
Steps:
# ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
# ASSERT: make sure that you have current server for oc NOT to be reachable (ex. current server is a cdk/crc that is *NOT* running)
# ASSERT: have oc v4 binary set as oc binary in preferences
# EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
# ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
# EXEC: retrieve token / provide pw
# EXEC: try to "Finish"
Result:
You cannot hit "Finish", it's disabled:
!screenshot-1.png!
If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
If you wait a bit "Finish" gets enabled. This actually happens once the oc binary timed out trying to connect to the current server
was:
Steps:
# ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
# ASSERT: have oc v4 binary set as oc binary in preferences and crc *NOT* running
# EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
# ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
# EXEC: retrieve token / provide pw
# EXEC: try to "Finish"
Result:
You cannot hit "Finish", it's disabled:
!screenshot-1.png!
If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
> Connection wizard: opening conn without token cannot be finished
> ----------------------------------------------------------------
>
> Key: JBIDE-26902
> URL: https://issues.jboss.org/browse/JBIDE-26902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.14.x
>
> Attachments: screenshot-1.png
>
>
> Steps:
> # ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
> # ASSERT: make sure that you have current server for oc NOT to be reachable (ex. current server is a cdk/crc that is *NOT* running)
> # ASSERT: have oc v4 binary set as oc binary in preferences
> # EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
> # ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
> # EXEC: retrieve token / provide pw
> # EXEC: try to "Finish"
> Result:
> You cannot hit "Finish", it's disabled:
> !screenshot-1.png!
> If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
> If you wait a bit "Finish" gets enabled. This actually happens once the oc binary timed out trying to connect to the current server
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26902) Connection wizard: opening conn without token cannot be finished (have to wait for period)
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26902?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26902:
-------------------------------------
Summary: Connection wizard: opening conn without token cannot be finished (have to wait for period) (was: Connection wizard: opening conn without token cannot be finished)
> Connection wizard: opening conn without token cannot be finished (have to wait for period)
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-26902
> URL: https://issues.jboss.org/browse/JBIDE-26902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.14.x
>
> Attachments: screenshot-1.png
>
>
> Steps:
> # ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
> # ASSERT: make sure that you have current server for oc NOT to be reachable (ex. current server is a cdk/crc that is *NOT* running)
> # ASSERT: have oc v4 binary set as oc binary in preferences
> # EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
> # ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
> # EXEC: retrieve token / provide pw
> # EXEC: try to "Finish"
> Result:
> You cannot hit "Finish", it's disabled:
> !screenshot-1.png!
> If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
> If you wait a bit "Finish" gets enabled. This actually happens once the oc binary timed out trying to connect to the current server
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26902) Connection wizard: opening conn without token cannot be finished
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26902?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26902:
-------------------------------------
Description:
Steps:
# ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
# ASSERT: have oc v4 binary set as oc binary in preferences and crc *NOT* running
# EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
# ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
# EXEC: retrieve token / provide pw
# EXEC: try to "Finish"
Result:
You cannot hit "Finish", it's disabled:
!screenshot-1.png!
If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
was:
Steps:
# ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
# ASSERT: have oc v4 binary set as oc binary in preferences
# EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
# ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
# EXEC: retrieve token / provide pw
# EXEC: try to "Finish"
Result:
You cannot hit "Finish", it's disabled:
!screenshot-1.png!
If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
> Connection wizard: opening conn without token cannot be finished
> ----------------------------------------------------------------
>
> Key: JBIDE-26902
> URL: https://issues.jboss.org/browse/JBIDE-26902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.14.x
>
> Attachments: screenshot-1.png
>
>
> Steps:
> # ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
> # ASSERT: have oc v4 binary set as oc binary in preferences and crc *NOT* running
> # EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
> # ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
> # EXEC: retrieve token / provide pw
> # EXEC: try to "Finish"
> Result:
> You cannot hit "Finish", it's disabled:
> !screenshot-1.png!
> If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26902) Connection wizard: opening conn without token cannot be finished
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26902?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26902:
-------------------------------------
Labels: connection_wizard (was: )
> Connection wizard: opening conn without token cannot be finished
> ----------------------------------------------------------------
>
> Key: JBIDE-26902
> URL: https://issues.jboss.org/browse/JBIDE-26902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.14.x
>
> Attachments: screenshot-1.png
>
>
> Steps:
> # ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
> # ASSERT: have oc v4 binary set as oc binary in preferences
> # EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
> # ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
> # EXEC: retrieve token / provide pw
> # EXEC: try to "Finish"
> Result:
> You cannot hit "Finish", it's disabled:
> !screenshot-1.png!
> If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26902) Connection wizard: opening conn without token cannot be finished
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26902?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26902:
-------------------------------------
Attachment: screenshot-1.png
> Connection wizard: opening conn without token cannot be finished
> ----------------------------------------------------------------
>
> Key: JBIDE-26902
> URL: https://issues.jboss.org/browse/JBIDE-26902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.14.x
>
> Attachments: screenshot-1.png
>
>
> Steps:
> # ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
> # ASSERT: have oc v4 binary set as oc binary in preferences
> # EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
> # ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
> # EXEC: retrieve token / provide pw
> # EXEC: try to "Finish"
> Result:
> You cannot hit "Finish", it's disabled:
> !screenshot-1.png!
> If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26902) Connection wizard: opening conn without token cannot be finished
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26902?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26902:
-------------------------------------
Attachment: (was: screenshot-1.png)
> Connection wizard: opening conn without token cannot be finished
> ----------------------------------------------------------------
>
> Key: JBIDE-26902
> URL: https://issues.jboss.org/browse/JBIDE-26902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Fix For: 4.14.x
>
>
> Steps:
> # ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
> # ASSERT: have oc v4 binary set as oc binary in preferences
> # EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
> # ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
> # EXEC: retrieve token / provide pw
> # EXEC: try to "Finish"
> Result:
> You cannot hit "Finish", it's disabled:
> !screenshot-1.png!
> If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26902) Connection wizard: opening conn without token cannot be finished
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26902?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26902:
-------------------------------------
Attachment: screenshot-1.png
> Connection wizard: opening conn without token cannot be finished
> ----------------------------------------------------------------
>
> Key: JBIDE-26902
> URL: https://issues.jboss.org/browse/JBIDE-26902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Fix For: 4.14.x
>
> Attachments: screenshot-1.png
>
>
> Steps:
> # ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
> # ASSERT: have oc v4 binary set as oc binary in preferences
> # EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
> # ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
> # EXEC: retrieve token / provide pw
> # EXEC: try to "Finish"
> Result:
> You cannot hit "Finish", it's disabled:
> !image-2019-10-21-14-22-55-122.png!
> If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (JBIDE-26902) Connection wizard: opening conn without token cannot be finished
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26902?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26902:
-------------------------------------
Description:
Steps:
# ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
# ASSERT: have oc v4 binary set as oc binary in preferences
# EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
# ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
# EXEC: retrieve token / provide pw
# EXEC: try to "Finish"
Result:
You cannot hit "Finish", it's disabled:
!screenshot-1.png!
If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
was:
Steps:
# ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
# ASSERT: have oc v4 binary set as oc binary in preferences
# EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
# ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
# EXEC: retrieve token / provide pw
# EXEC: try to "Finish"
Result:
You cannot hit "Finish", it's disabled:
!image-2019-10-21-14-22-55-122.png!
If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
> Connection wizard: opening conn without token cannot be finished
> ----------------------------------------------------------------
>
> Key: JBIDE-26902
> URL: https://issues.jboss.org/browse/JBIDE-26902
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Priority: Major
> Fix For: 4.14.x
>
> Attachments: screenshot-1.png
>
>
> Steps:
> # ASSERT: have a connection to an OS3 server *WITHOUT* token/pw saved
> # ASSERT: have oc v4 binary set as oc binary in preferences
> # EXEC: OpenShift explorer: restart Eclipse and once back in Eclipse, open up the connection OS3 server
> # ASSERT: connection wizard pops up so that you can retrieve a token/provide pw
> # EXEC: retrieve token / provide pw
> # EXEC: try to "Finish"
> Result:
> You cannot hit "Finish", it's disabled:
> !screenshot-1.png!
> If you look closer you discover that the title area shows that it's stuck trying to verify the oc version.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years