[JBoss JIRA] (JBIDE-25611) Server adapter: timeouts when starting into "Debug" on OpenShift Online
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25611:
------------------------------------------
Some of the problems with non-matching pods are apparently related to bad setup: btw. 2 "sessions" i use "Delete Resources" which it turns out incompletely removes resources: JBIDE-25611
> Server adapter: timeouts when starting into "Debug" on OpenShift Online
> -----------------------------------------------------------------------
>
> Key: JBIDE-25611
> URL: https://issues.jboss.org/browse/JBIDE-25611
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.3.AM1
>
> Attachments: error-waiting-for-new-pod.png, image-2018-01-24-18-58-29-159.png, image-2018-01-25-10-49-09-369.png, image-2018-01-26-00-49-39-691.png, pod-ports-cdk.png, pod-ports-online.png, port-missing.png
>
>
> # ASSERT: have an account on OpenShift Online
> # EXEC: create a new application via template nodejs-mongo-persistent
> # EXEC: have the project imported into the workspace and the server adapter for it created
> # ASSERT: you have a new server adapter for your app in state [stopped]
> # EXEC: start the adapter into "Debug"
> Result:
> The adapter takes a lot of time to start but wont succeed eventually. You get the following error dialog:
> !error-waiting-for-new-pod.png!
> In the Eclipse log you'll find the following:
> {code}
> org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for nodejs-mongo-persistent
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25670:
------------------------------------------
[~jeffmaury] that's what you experienced, too, right?
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25670:
-------------------------------------
Description:
This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
steps:
# ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
# EXEC: launch "Delete Resources" wizard
# ASSERT: you see deployment configs, replication controllers, pods etc.
# EXEC: select all resources and hit "Finish"
# ASSERT: wait for all removal jobs to be finished
# EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
Result:
!image-2018-01-29-09-34-08-598.png!
Replication controller(s) and pods are left in place, they were not deleted.
Some pods may be in terminating state and disappear eventually.
was:
This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
steps:
# ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
# EXEC: launch "Delete Resources" wizard
# ASSERT: you see deployment configs, replication controllers, pods etc.
# EXEC: select all resources and hit "Finish"
# ASSERT: wait for all removal jobs to be finished
# EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
Result:
!image-2018-01-29-09-34-08-598.png!
Replication controller(s) and pods are left in place, they were not deleted.
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
> Some pods may be in terminating state and disappear eventually.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-25670:
----------------------------------------
Summary: Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
Key: JBIDE-25670
URL: https://issues.jboss.org/browse/JBIDE-25670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.5.2.Final
Reporter: Andre Dietisheim
Attachments: image-2018-01-29-09-34-08-598.png
This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
steps:
# ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
# EXEC: launch "Delete Resources" wizard
# ASSERT: you see deployment configs, replication controllers, pods etc.
# EXEC: select all resources and hit "Finish"
# ASSERT: wait for all removal jobs to be finished
# EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
Result:
!image-2018-01-29-09-34-08-598.png!
Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25670:
-------------------------------------
Fix Version/s: 4.5.3.AM1
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-25670:
----------------------------------------
Assignee: Andre Dietisheim
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25670:
-------------------------------------
Labels: delete_resources (was: )
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25670) Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25670?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25670:
-------------------------------------
Sprint: devex #144 January 2018
> Delete Resources: replication controllers and pods are not deleted (on OpenShift Online)
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25670
> URL: https://issues.jboss.org/browse/JBIDE-25670
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM1
>
> Attachments: image-2018-01-29-09-34-08-598.png
>
>
> This is most likely a timing issue, thus it is usually not observable when using a local CDK but always reproducible on OpenShift Online:
> steps:
> # ASSERT: have an application - with deployment configs, replication controllers, pods, etc.) running in OpenShift Online (ex. created via nodejs-mongo-persistent)
> # EXEC: launch "Delete Resources" wizard
> # ASSERT: you see deployment configs, replication controllers, pods etc.
> # EXEC: select all resources and hit "Finish"
> # ASSERT: wait for all removal jobs to be finished
> # EXEC: launch "Delete Resource" wizard again and inspect the resources that are still there
> Result:
> !image-2018-01-29-09-34-08-598.png!
> Replication controller(s) and pods are left in place, they were not deleted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25669) Unexpected JAX-RS validation error for Feature
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25669?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25669:
-------------------------------
Fix Version/s: 4.5.3.AM2
> Unexpected JAX-RS validation error for Feature
> ----------------------------------------------
>
> Key: JBIDE-25669
> URL: https://issues.jboss.org/browse/JBIDE-25669
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.2.Final
> Reporter: Cody Lerum
> Assignee: Jeff MAURY
> Labels: jax-rs, respin-a
> Fix For: 4.5.3.AM2
>
>
> We are using JAX-RS client filters in our project. One of the classes looks like this:
> ...
> import java.io.IOException;
> import javax.ws.rs.client.ClientRequestContext;
> import javax.ws.rs.client.ClientRequestFilter;
> import javax.ws.rs.ext.Provider;
> ...
> @Provider
> public class ClientFilter implements ClientRequestFilter
> {
> ...
> }
> The class is part of a Dynamic Web Project with JAX-RS support turned on.
> The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error:
> The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver.
> I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25669) Unexpected JAX-RS validation error for Feature
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25669?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-25669:
----------------------------------
Assignee: Jeff MAURY (was: Xavier Coulon)
> Unexpected JAX-RS validation error for Feature
> ----------------------------------------------
>
> Key: JBIDE-25669
> URL: https://issues.jboss.org/browse/JBIDE-25669
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.2.Final
> Reporter: Cody Lerum
> Assignee: Jeff MAURY
> Labels: jax-rs, respin-a
>
> We are using JAX-RS client filters in our project. One of the classes looks like this:
> ...
> import java.io.IOException;
> import javax.ws.rs.client.ClientRequestContext;
> import javax.ws.rs.client.ClientRequestFilter;
> import javax.ws.rs.ext.Provider;
> ...
> @Provider
> public class ClientFilter implements ClientRequestFilter
> {
> ...
> }
> The class is part of a Dynamic Web Project with JAX-RS support turned on.
> The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error:
> The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver.
> I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months