[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka commented on JBIDE-26817:
-----------------------------------------
I have good news for everybody - now it finally works for me also.
h3. Tested in Red Hat CodeReady Studio:
Version: 12.13.0.GA
Build id: GA-v20191016-0424-B5159
Build date: 20191016-0424
> link to "Get involved" shows the page for CAT that was suspended in 2016
> ------------------------------------------------------------------------
>
> Key: JBIDE-26817
> URL: https://issues.jboss.org/browse/JBIDE-26817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.12.0.Final
> Reporter: André Dietisheim
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.13.0.Final
>
> Attachments: central.png, image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png, issue.png, page_with_cat.png
>
>
> steps:
> # ASSERT: have central opened
> # EXEC: click on the link "Get involved"
> !image-2019-09-09-21-39-10-326.png!
> result:
> browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016*
> !image-2019-09-09-21-40-21-204.png!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016
by Stephane Bouchet (Jira)
[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ]
Stephane Bouchet edited comment on JBIDE-26817 at 10/16/19 10:28 AM:
---------------------------------------------------------------------
PR merged and ide-config.properties has been uploaded in the server again. should be good now in CodeReady Dev Studio.
was (Author: stephane.bouchet):
PR merged and ide-config.properties has been uploaded in the server again. should be good now in devstudio.
> link to "Get involved" shows the page for CAT that was suspended in 2016
> ------------------------------------------------------------------------
>
> Key: JBIDE-26817
> URL: https://issues.jboss.org/browse/JBIDE-26817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.12.0.Final
> Reporter: André Dietisheim
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.13.0.Final
>
> Attachments: central.png, image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png, issue.png, page_with_cat.png
>
>
> steps:
> # ASSERT: have central opened
> # EXEC: click on the link "Get involved"
> !image-2019-09-09-21-39-10-326.png!
> result:
> browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016*
> !image-2019-09-09-21-40-21-204.png!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016
by Stephane Bouchet (Jira)
[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ]
Stephane Bouchet commented on JBIDE-26817:
------------------------------------------
PR merged and ide-config.properties has been uploaded in the server again. should be good now in devstudio.
> link to "Get involved" shows the page for CAT that was suspended in 2016
> ------------------------------------------------------------------------
>
> Key: JBIDE-26817
> URL: https://issues.jboss.org/browse/JBIDE-26817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.12.0.Final
> Reporter: André Dietisheim
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.13.0.Final
>
> Attachments: central.png, image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png, issue.png, page_with_cat.png
>
>
> steps:
> # ASSERT: have central opened
> # EXEC: click on the link "Get involved"
> !image-2019-09-09-21-39-10-326.png!
> result:
> browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016*
> !image-2019-09-09-21-40-21-204.png!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26869) CRC server adapter: OpenShift connection that is created is unusable at times
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26869?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-26869 at 10/16/19 10:18 AM:
---------------------------------------------------------------------
interestingly, in such situations
* *oc*: login doesnt work either:
{code}
$ ~/.crc/bin/oc login https://api.crc.testing:6443
Error from server (InternalError): Internal error occurred: unexpected response: 400
{code}
* *web console*: login doesnt work when using developer/developer. Login with kubeadmin works though but shows in the dashboard that the cluster is in an error state.
After some waiting both oc and the web console allows login via developer/developer. The error is also gone.
For the Eclipse connection, refresh doesnt help. But editing the connection (faking a change and getting back to original) helps though and login is possible.
[~kumarpraveen] any idea why waiting is required? I suppose that the cluster is not fully started yet. Do we know if there's a way to know when things are all fine?
was (Author: adietish):
interestingly, in such situations
* *oc*: login doesnt work either:
{code}
$ ~/.crc/bin/oc login https://api.crc.testing:6443
Error from server (InternalError): Internal error occurred: unexpected response: 400
{code}
* *web console*: login doesnt work when using developer/developer. Login with kubeadmin works though but shows in the dashboard that the cluster is in an error state.
After some waiting both oc and the web console allows login via developer/developer. The error is also gone.
For the Eclipse connection, refresh doesnt help. But editing the connection (faking a change and getting back to original) helps though and login is possible.
[~kumarpraveen] any idea why waiting is required?
> CRC server adapter: OpenShift connection that is created is unusable at times
> -----------------------------------------------------------------------------
>
> Key: JBIDE-26869
> URL: https://issues.jboss.org/browse/JBIDE-26869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Environment: CRC Beta5
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.0.Final
>
> Attachments: crc-connection-error.mp4, start-crc-error-openshift-conn.mp4
>
>
> *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
> *Result:*
> Connection fails to authorize, reports that it cannot access resources using system:anonymous. Refreshing the connection doesn't help, so it's apparently not a timing issue (ex. creating the connection before the cluster is fully up and running)
> {code}
> com.openshift.restclient.authorization.ResourceForbiddenException: forbidden: User "system:anonymous" cannot get path "/oauth/authorize" forbidden: User "system:anonymous" cannot get path "/oauth/authorize"
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:111)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:66)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184)
> at okhttp3.RealCall.execute(RealCall.kt:66)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.tryAuth(OpenShiftAuthenticator.java:109)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.authenticate(OpenShiftAuthenticator.java:62)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.followUpRequest(RetryAndFollowUpInterceptor.kt:213)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:102)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184)
> at okhttp3.RealCall.execute(RealCall.kt:66)
> at com.openshift.internal.restclient.DefaultClient.request(DefaultClient.java:315)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:307)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:243)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:226)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:423)
> at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:63)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:237)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureOpenshift(ConfigureCRCFrameworksListener.java:102)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureFrameworks(ConfigureCRCFrameworksListener.java:73)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener$1.run(ConfigureCRCFrameworksListener.java:66)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26850) CRC server adapter: push secret path is not remembered & prefilled
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26850?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26850:
-------------------------------------
Fix Version/s: 4.14.x
(was: 4.13.0.Final)
> CRC server adapter: push secret path is not remembered & prefilled
> ------------------------------------------------------------------
>
> Key: JBIDE-26850
> URL: https://issues.jboss.org/browse/JBIDE-26850
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.Final
> Reporter: André Dietisheim
> Priority: Major
> Labels: crc_server_adapter
> Fix For: 4.14.x
>
> Attachments: crc-server-adapter-wizard.png
>
>
> Steps:
> # EXEC: launch server wizard: New > Other > Server > Server > "Red Hat CodeReady Containers 1.0 (Tech Preview)", inform "CRC Binary:" & "CRC Pull Secret File:"
> # EXEC: hit "Cancel"
> # EXEC: launch server wizard again, "Next" to get to the form with the "CRC Binary" and "CRC Pull Secret File"
> Result:
> "CRC Binary:" was remembered and is now prefilled, "CRC Pull Secret File:" is not.
> !crc-server-adapter-wizard.png!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26881) Server adapter: server "JBoss OpenShift 3 Tools" is non-functional
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26881?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26881:
-------------------------------------
Summary: Server adapter: server "JBoss OpenShift 3 Tools" is non-functional (was: Server adapter: erroneous "JBoss OpenShift 3 Tools" showing up as server type)
> Server adapter: server "JBoss OpenShift 3 Tools" is non-functional
> ------------------------------------------------------------------
>
> Key: JBIDE-26881
> URL: https://issues.jboss.org/browse/JBIDE-26881
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Assignee: Rob Stryker
> Priority: Major
> Fix For: 4.13.0.Final
>
> Attachments: image-2019-09-30-17-19-32-079.png, image-2019-09-30-17-20-13-866.png
>
>
> Steps:
> # EXEC: File > New > Other > Server/Server > Red Hat/JBoss OpenShift 3 Tools & hit "Next"
> !image-2019-09-30-17-19-32-079.png!
> Result:
> A lengthy fetch from p2 repositories follows and then an empty page with an error:
> !image-2019-09-30-17-20-13-866.png!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months