[JBoss JIRA] (JBIDE-26550) Cannot delete pod on OpenShift 3.11
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26550?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26550:
------------------------------------------
[~jcantrill] sorry for all the discussions here but it turns out that this error is caused by the following change in the openshift-restclient-java: https://github.com/openshift/openshift-restclient-java/pull/361
> Cannot delete pod on OpenShift 3.11
> -----------------------------------
>
> Key: JBIDE-26550
> URL: https://issues.jboss.org/browse/JBIDE-26550
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.AM1
> Reporter: Andre Dietisheim
> Priority: Critical
> Labels: delete_resource, delete_resources
> Fix For: 4.11.0.AM1
>
> Attachments: error-deleting-pod-openshift-3_10.png, image-2019-02-08-21-12-00-707.png, image-2019-02-08-21-12-12-917.png
>
>
> steps:
> # ASSERT: make sure that you have an application with a pod running on OpenShift 3.11 (ex. https://employee.openshift.com)
> !image-2019-02-08-21-12-00-707.png!
> # EXEC: in Explorer select the pod and choose "Delete"
> Result:
> !image-2019-02-08-21-12-12-917.png!
> {code}
> com.openshift.restclient.OpenShiftException: Exception trying to DELETE https://api.rh-us-east-1.openshift.com/api/v1/namespaces/testomat/pods/wf... response code: 500 no kind "Pod" is registered for version "v1" in scheme "k8s.io/apimachinery/pkg/apis/meta/internalversion/register.go:31"
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:116)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:66)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200)
> at okhttp3.RealCall.execute(RealCall.java:77)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:294)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:268)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:236)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:219)
> at com.openshift.internal.restclient.DefaultClient.delete(DefaultClient.java:388)
> at org.jboss.tools.openshift.core.connection.Connection.deleteResource(Connection.java:549)
> at org.jboss.tools.openshift.internal.core.job.AbstractDeleteResourceJob.delete(AbstractDeleteResourceJob.java:45)
> at org.jboss.tools.openshift.internal.core.job.DeleteResourceJob.doRun(DeleteResourceJob.java:35)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
> ps. Deleting the pod via "oc" command line (oc v3.11.0+0cbc58b) works fine.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26538) Openshift 3 Server Adapter unusable with 100 projects
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26538?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26538 at 2/11/19 3:47 PM:
-------------------------------------------------------------------
[~lionelve] ok, this clears it up. JBoss Tools versions should match Eclipse versions. So in that sense the using Eclipse 4.9 with JBoss Tools 4.9 is the expected combination. Apparently there's no guard that would disallow such combinations.
[~jeffmaury] Shouldn't we make sure that JBoss Tools depends on Eclipse 4.10? Apparently we're not making this ure. Thoughts?
was (Author: adietish):
[~lionelve] ok so this clears it up. JBoss Tools versions should match Eclipse versions. So in that sense the using Eclipse 4.9 with JBoss Tools 4.9 is the expected combination. Apprently there's no guard that would disallow such combinations.
[~jeffmaury] Shouldn't we make sure that JBoss Tools depends on Eclipse 4.10? Apparently we're not making this ure. Thoughts?
> Openshift 3 Server Adapter unusable with 100 projects
> -----------------------------------------------------
>
> Key: JBIDE-26538
> URL: https://issues.jboss.org/browse/JBIDE-26538
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Lionel Orellana
> Priority: Critical
> Labels: server_adapter_wizard
> Fix For: 4.9.0.Final
>
>
> With 100 projects available in the Openshift cluster (3.9) it can take more than an hour to load the Server Adapter wizard while the "Loading projects and services ..." message appears in the progress View.
> Eclipse Neon
> JBoss Tools 4.4.4
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26538) Openshift 3 Server Adapter unusable with 100 projects
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26538?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26538:
------------------------------------------
[~lionelve] ok so this clears it up. JBoss Tools versions should match Eclipse versions. So in that sense the using Eclipse 4.9 with JBoss Tools 4.9 is the expected combination. Apprently there's no guard that would disallow such combinations.
[~jeffmaury] Shouldn't we make sure that JBoss Tools depends on Eclipse 4.10? Apparently we're not making this ure. Thoughts?
> Openshift 3 Server Adapter unusable with 100 projects
> -----------------------------------------------------
>
> Key: JBIDE-26538
> URL: https://issues.jboss.org/browse/JBIDE-26538
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Lionel Orellana
> Priority: Critical
> Labels: server_adapter_wizard
> Fix For: 4.9.0.Final
>
>
> With 100 projects available in the Openshift cluster (3.9) it can take more than an hour to load the Server Adapter wizard while the "Loading projects and services ..." message appears in the progress View.
> Eclipse Neon
> JBoss Tools 4.4.4
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (ERT-706) [Gtk] Regression: KeyEvent keyCode no longer set [EBZ#544296]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-706?page=com.atlassian.jira.plugin.sy... ]
Eric Williams reassigned ERT-706:
---------------------------------
Sprint: devex #162 February 2019
Assignee: Eric Williams
> [Gtk] Regression: KeyEvent keyCode no longer set [EBZ#544296]
> -------------------------------------------------------------
>
> Key: ERT-706
> URL: https://issues.jboss.org/browse/ERT-706
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: 4.11_M3, SWT, bzira
>
> The keyCode in KeyEvent no longer has a value set, for example when pressing the '.' key.
> Following the code in Widget.sendIMKeyEvent, the event parameter is 0, the ptr and state variables are set, but the event remains 0, which leads to calling setInputState instead of setKeyState.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26539) Openshift connection dialog not showing authentication fields
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26539?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26539 at 2/11/19 3:03 PM:
-------------------------------------------------------------------
[~lionelve] So you could reproduce this in both 4.10 only, while things worked fine with 4.9, correct? Did you have 4.9 installed first and then you upgraded to 4.10? Or did you use a fresh install when you tried 4.10?
By chance I stumbled upon a situation where I had the connection dialog showing up like yours in the screenshots.
!image-2019-02-11-21-03-11-730.png!
It turned out that there was a problem with the **openshift-restclient-java-XXX.jar** library in the **org.jboss.tools.openshift.client** plugin. The library needs to be in the **/lib** folder of this plugin.
For 4.10 you need the following files in **org.jboss.tools.openshift.client/lib**
{code}
lib/openshift-restclient-java-7.0.0.Final.jar,
lib/okhttp-3.11.0.jar,
lib/okio-1.14.0.jar,
lib/jboss-dmr-1.3.0.Final.jar,
lib/commons-codec-1.6.jar,
lib/commons-compress-1.18.jar,
lib/commons-io-2.1.jar,
lib/commons-lang-2.6.jar,
lib/log4j-1.2.17.jar,
lib/slf4j-api-1.6.1.jar,
lib/slf4j-log4j12-1.6.1.jar
{code}
How these could be missing or corrupt in your case is still some kind of mystery to me. Do you have a possible explanation?
was (Author: adietish):
[~lionelve] So you could reproduce this in both 4.10 only, while things worked fine with 4.9, correct? Did you have 4.9 installed first and then you upgraded to 4.10? Or did you use a fresh install when you tried 4.10?
By chance I stumbled upon a situation where I had the connection dialog showing up like yours in the screenshots. It turned out that there was a problem with the **openshift-restclient-java-XXX.jar** library in the **org.jboss.tools.openshift.client** plugin. The library needs to be in the **/lib** folder of this plugin.
For 4.10 you need the following files in **org.jboss.tools.openshift.client/lib**
{code}
lib/openshift-restclient-java-7.0.0.Final.jar,
lib/okhttp-3.11.0.jar,
lib/okio-1.14.0.jar,
lib/jboss-dmr-1.3.0.Final.jar,
lib/commons-codec-1.6.jar,
lib/commons-compress-1.18.jar,
lib/commons-io-2.1.jar,
lib/commons-lang-2.6.jar,
lib/log4j-1.2.17.jar,
lib/slf4j-api-1.6.1.jar,
lib/slf4j-log4j12-1.6.1.jar
{code}
How these could be missing or corrupt in your case is still some kind of mystery to me. Do you have a possible explanation?
> Openshift connection dialog not showing authentication fields
> -------------------------------------------------------------
>
> Key: JBIDE-26539
> URL: https://issues.jboss.org/browse/JBIDE-26539
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Reporter: Lionel Orellana
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.11.0.AM1
>
> Attachments: image-2019-02-11-21-03-11-730.png, screenshot-1.png
>
>
> When I open the New Openshift Connection wizard the Authentication panel is empty. There are not fields to chose auth type or anything at all.
> Eclipse 2018-12 (4.10)
> !screenshot-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26539) Openshift connection dialog not showing authentication fields
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26539?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26539 at 2/11/19 2:49 PM:
-------------------------------------------------------------------
[~lionelve] So you could reproduce this in both 4.10 only, while things worked fine with 4.9, correct? Did you have 4.9 installed first and then you upgraded to 4.10? Or did you use a fresh install when you tried 4.10?
By chance I stumbled upon a situation where I had the connection dialog showing up like yours in the screenshots. It turned out that there was a problem with the **openshift-restclient-java-XXX.jar** library in the **org.jboss.tools.openshift.client** plugin. The library needs to be in the **/lib** folder of this plugin.
For 4.10 you need the following files in **org.jboss.tools.openshift.client/lib**
{code}
lib/openshift-restclient-java-7.0.0.Final.jar,
lib/okhttp-3.11.0.jar,
lib/okio-1.14.0.jar,
lib/jboss-dmr-1.3.0.Final.jar,
lib/commons-codec-1.6.jar,
lib/commons-compress-1.18.jar,
lib/commons-io-2.1.jar,
lib/commons-lang-2.6.jar,
lib/log4j-1.2.17.jar,
lib/slf4j-api-1.6.1.jar,
lib/slf4j-log4j12-1.6.1.jar
{code}
How these could be missing or corrupt in your case is still some kind of mystery to me. Do you have a possible explanation?
was (Author: adietish):
[~lionelve] So you could reproduce this in both 4.10 only, while things worked fine with 4.9, correct? Did you have 4.9 installed first and then you upgraded to 4.10? Or did you use a fresh install when you tried 4.10?
I by chance could reproduce this when there was a problem with the **openshift-restclient-java-XXX.jar** library in the **org.jboss.tools.openshift.client** plugin. The library needs to be in the **/lib** folder of this plugin.
For 4.10 you need the following files in **org.jboss.tools.openshift.client/lib**
{code}
lib/openshift-restclient-java-7.0.0.Final.jar,
lib/okhttp-3.11.0.jar,
lib/okio-1.14.0.jar,
lib/jboss-dmr-1.3.0.Final.jar,
lib/commons-codec-1.6.jar,
lib/commons-compress-1.18.jar,
lib/commons-io-2.1.jar,
lib/commons-lang-2.6.jar,
lib/log4j-1.2.17.jar,
lib/slf4j-api-1.6.1.jar,
lib/slf4j-log4j12-1.6.1.jar
{code}
How these could be missing or corrupt is still some kind of mystery to me. Do you have a possible explanation?
> Openshift connection dialog not showing authentication fields
> -------------------------------------------------------------
>
> Key: JBIDE-26539
> URL: https://issues.jboss.org/browse/JBIDE-26539
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Reporter: Lionel Orellana
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.11.0.AM1
>
> Attachments: screenshot-1.png
>
>
> When I open the New Openshift Connection wizard the Authentication panel is empty. There are not fields to chose auth type or anything at all.
> Eclipse 2018-12 (4.10)
> !screenshot-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26539) Openshift connection dialog not showing authentication fields
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26539?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26539:
------------------------------------------
[~lionelve] So you could reproduce this in both 4.10 only, while things worked fine with 4.9, correct? Did you have 4.9 installed first and then you upgraded to 4.10? Or did you use a fresh install when you tried 4.10?
I by chance could reproduce this when there was a problem with the **openshift-restclient-java-XXX.jar** library in the **org.jboss.tools.openshift.client** plugin. The library needs to be in the **/lib** folder of this plugin.
For 4.10 you need the following files in **org.jboss.tools.openshift.client/lib**
{code}
lib/openshift-restclient-java-7.0.0.Final.jar,
lib/okhttp-3.11.0.jar,
lib/okio-1.14.0.jar,
lib/jboss-dmr-1.3.0.Final.jar,
lib/commons-codec-1.6.jar,
lib/commons-compress-1.18.jar,
lib/commons-io-2.1.jar,
lib/commons-lang-2.6.jar,
lib/log4j-1.2.17.jar,
lib/slf4j-api-1.6.1.jar,
lib/slf4j-log4j12-1.6.1.jar
{code}
How these could be missing or corrupt is still some kind of mystery to me. Do you have a possible explanation?
> Openshift connection dialog not showing authentication fields
> -------------------------------------------------------------
>
> Key: JBIDE-26539
> URL: https://issues.jboss.org/browse/JBIDE-26539
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.9.0.Final
> Reporter: Lionel Orellana
> Assignee: Andre Dietisheim
> Priority: Major
> Labels: connection_wizard
> Attachments: screenshot-1.png
>
>
> When I open the New Openshift Connection wizard the Authentication panel is empty. There are not fields to chose auth type or anything at all.
> Eclipse 2018-12 (4.10)
> !screenshot-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month